Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
D
disorderfs
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Merge Requests
1
Merge Requests
1
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Jobs
Commits
Open sidebar
Reproducible Builds
disorderfs
Commits
bd35aeb6
Commit
bd35aeb6
authored
Jan 27, 2019
by
Chris Lamb
💬
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Ignore the return values to fsyncdir to ensure (for example) dpkg(1) can "flush" /var/lib/dpkg.
parent
1986a657
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
1 deletion
+2
-1
disorderfs.cpp
disorderfs.cpp
+2
-1
No files found.
disorderfs.cpp
View file @
bd35aeb6
...
...
@@ -477,7 +477,8 @@ int main (int argc, char** argv)
};
disorderfs_fuse_operations
.
fsyncdir
=
[]
(
const
char
*
path
,
int
is_datasync
,
struct
fuse_file_info
*
info
)
->
int
{
// XXX: is it OK to just use fsync? Not clear on why FUSE has a separate fsyncdir operation
return
wrap
(
is_datasync
?
fdatasync
(
info
->
fh
)
:
fsync
(
info
->
fh
));
wrap
(
is_datasync
?
fdatasync
(
info
->
fh
)
:
fsync
(
info
->
fh
));
return
0
;
// return value is ignored
};
disorderfs_fuse_operations
.
create
=
[]
(
const
char
*
path
,
mode_t
mode
,
struct
fuse_file_info
*
info
)
->
int
{
Guard
g
;
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment