Hello,
Toshiyuki reported an ext3 error message which implies that we can have
unlinked but open files on read-only filesystem. Apparently open+unlink
races with remount in some way. Looking at code in do_remount_sb() I don't
see what prevents open("file", O_WRONLY) to happen after the check
fs_may_remount_ro() and before the filesystem is marked as read-only.
So are we expected to prevent these races? If yes, do I just miss something
or the above race is really there? Thanks for reply in advance.
Honza
--
Jan Kara <jack@xxxxxxx>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
