Theodore Ts'o 2ec0ae3ace ext4: Fix race in ext4_inode_info.i_cached_extent ... If two CPU's simultaneously call ext4_ext_get_blocks() at the same time, there is nothing protecting the i_cached_extent structure from being used and updated at the same time. This could potentially cause the wrong location on disk to be read or written to, including potentially causing the corruption of the block group descriptors and/or inode table. This bug has been in the ext4 code since almost the very beginning of ext4's development. Fortunately once the data is stored in the page cache cache, ext4_get_blocks() doesn't need to be called, so trying to replicate this problem to the point where we could identify its root cause was *extremely* difficult. Many thanks to Kevin Shanahan for working over several months to be able to reproduce this easily so we could finally nail down the cause of the corruption. Signed-off-by: "Theodore Ts'o" <tytso@mit.edu> Reviewed-by: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>		2009-05-15 09:07:28 -04:00
..
acl.c
acl.h
balloc.c
bitmap.c
dir.c
ext4_extents.h
ext4_i.h
ext4_jbd2.c
ext4_jbd2.h
ext4_sb.h
ext4.h
extents.c
file.c
fsync.c
group.h
hash.c
ialloc.c
inode.c
ioctl.c
Kconfig
Makefile
mballoc.c
mballoc.h
migrate.c
namei.c
namei.h
resize.c
super.c
symlink.c
xattr_security.c
xattr_trusted.c
xattr_user.c
xattr.c
xattr.h