ext4: fix possible use-after-free in ext4_remove_li_request()
authorLukas Czerner <lczerner@redhat.com>
Fri, 20 May 2011 17:55:29 +0000 (13:55 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 20 May 2011 17:55:29 +0000 (13:55 -0400)
commit1bb933fb1fa8e4cb337a0d5dfd2ff4c0dc2073e8
treed03bbc0de028862fb9df1d7941a03103150d69de
parent51ce65115642b77040f5582b8d2fc8815ac450f9
ext4: fix possible use-after-free in ext4_remove_li_request()

We need to take reference to the s_li_request after we take a mutex,
because it might be freed since then, hence result in accessing old
already freed memory. Also we should protect the whole
ext4_remove_li_request() because ext4_li_info might be in the process of
being freed in ext4_lazyinit_thread().

Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Reviewed-by: Eric Sandeen <sandeen@redhat.com>
fs/ext4/super.c