| commit | 1db58ae0a6e032378326412bd446ea23591ff50c | |
| author | Lukas Czerner <lczerner@redhat.com> | |
| Fri, 20 May 2011 17:55:29 +0000 (20 13:55 -0400) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 3 Jun 2011 01:33:48 +0000 (3 10:33 +0900) | ||
| tree | 192eff2166620883814ebfa182e2b5f56d22b746 | treesnapshot (tar.gz zip) |
| parent | aa0ff541cfa5935a5d52f3807c8a4993c46a2799 | commitdiff |
ext4: fix possible use-after-free in ext4_remove_li_request()
commit 1bb933fb1fa8e4cb337a0d5dfd2ff4c0dc2073e8 upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit 1bb933fb1fa8e4cb337a0d5dfd2ff4c0dc2073e8 upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| fs/ext4/super.c | diffblobblamehistory |