]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ext4: atomically set inode->i_flags in ext4_set_inode_flags()
authorTheodore Ts'o <tytso@mit.edu>
Mon, 24 Mar 2014 18:43:12 +0000 (14:43 -0400)
committerJiri Slaby <jslaby@suse.cz>
Wed, 3 Dec 2014 10:58:43 +0000 (11:58 +0100)
commitec81c28104fd2198f076203be3d1bae5546e863f
treea0c2a33ae915b3dcc57e55b501b2a8f7b7b9906c
parent692f067fb661c39cc800ae7407ab655173ca2de2
ext4: atomically set inode->i_flags in ext4_set_inode_flags()

commit 5f16f3225b06242a9ee876f07c1c9b6ed36a22b6 upstream.

Use cmpxchg() to atomically set i_flags instead of clearing out the
S_IMMUTABLE, S_APPEND, etc. flags and then setting them from the
EXT4_IMMUTABLE_FL, EXT4_APPEND_FL flags, since this opens up a race
where an immutable file has the immutable flag cleared for a brief
window of time.

js: there is no change for ext4. This patch defines merely
    inode_set_flags for jffs in the next patch. I wonder why do we
    have both inode_set_flags and set_mask_bits? Looks like an
    improperly resolved merge conflict.

Reported-by: John Sullivan <jsrhbz@kanargh.force9.co.uk>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: stable@kernel.org
Signed-off-by: Jiri Slaby <jslaby@suse.cz>
fs/ext4/inode.c
fs/inode.c
include/linux/fs.h