[Bug 213507] [msdosfs] [patch]: Prevent occasional directory corruption while extending it to another cluster

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Oct 17 09:37:59 UTC 2016


--- Comment #8 from Konstantin Belousov <kib at FreeBSD.org> ---
(In reply to Vladislav Movchan from comment #7)
I probably was not clear enough.

The problem is that a previous operation left the pages on the vnode page queue
behind the directory denode end.  The damage is not limited to the situation of
extending the directory, it might have other consequences with varying
severity.  E.g., if the issue also happens for regular files, then extending
file might result in the garbage or some previously removed unrelated disk file
content to appear in the extended portion, readable by user.

That said, your patch seems to only paper over the real problem.  Right thing
to do is to track the location where the damage happens.  E.g., UFS also had
similar problems, where failed file extension (e.g., for lack of free space)
was followed by an incomplete cleanup and dandling buffers and pages.

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-fs mailing list