diff options
author | Jan Kara <jack@suse.cz> | 2023-06-15 14:38:48 +0300 |
---|---|---|
committer | Christian Brauner <brauner@kernel.org> | 2023-06-15 17:58:04 +0300 |
commit | c541dce86c537714b6761a79a969c1623dfa222b (patch) | |
tree | ccaed22f2bd48a43552a75ab9d6961f86868b681 /fs/internal.h | |
parent | 2d8c9dcf7158060fcec9f891c0292ffdb4397523 (diff) | |
download | linux-c541dce86c537714b6761a79a969c1623dfa222b.tar.xz |
fs: Protect reconfiguration of sb read-write from racing writes
The reconfigure / remount code takes a lot of effort to protect
filesystem's reconfiguration code from racing writes on remounting
read-only. However during remounting read-only filesystem to read-write
mode userspace writes can start immediately once we clear SB_RDONLY
flag. This is inconvenient for example for ext4 because we need to do
some writes to the filesystem (such as preparation of quota files)
before we can take userspace writes so we are clearing SB_RDONLY flag
before we are fully ready to accept userpace writes and syzbot has found
a way to exploit this [1]. Also as far as I'm reading the code
the filesystem remount code was protected from racing writes in the
legacy mount path by the mount's MNT_READONLY flag so this is relatively
new problem. It is actually fairly easy to protect remount read-write
from racing writes using sb->s_readonly_remount flag so let's just do
that instead of having to workaround these races in the filesystem code.
[1] https://lore.kernel.org/all/00000000000006a0df05f6667499@google.com/T/
Signed-off-by: Jan Kara <jack@suse.cz>
Message-Id: <20230615113848.8439-1-jack@suse.cz>
Signed-off-by: Christian Brauner <brauner@kernel.org>
Diffstat (limited to 'fs/internal.h')
0 files changed, 0 insertions, 0 deletions