| commit | a51b56fff3f04fc5aa66b21a2a6d693ee9862d66 | |
| author | Benjamin Marzinski <bmarzins@redhat.com> | |
| Tue, 30 Jun 2009 18:51:11 +0000 (30 13:51 -0500) | ||
| committer | Steven Whitehouse <swhiteho@redhat.com> | |
| Thu, 30 Jul 2009 09:59:28 +0000 (30 10:59 +0100) | ||
| tree | e93c25ebe818e7a157f2b878a9512ada0f2f2bd1 | treesnapshot (tar.gz zip) |
| parent | 1946f70ab5e4eb8b54a8eaaedba2293a3750ab7e | commitdiff |
GFS2: Fix panic in glock memory shrinker
It is possible for gfs2_shrink_glock_memory() to check a glock for
demotion
that's in the process of being freed by gfs2_glock_put(). In this case,
gfs2_shrink_glock_memory() will acquire a new reference to this glock,
and
then try to free the glock itself when it drops the refernce. To solve
this, gfs2_shrink_glock_memory() just needs to check if the glock is in
the process of being freed, and if so skip it without ever unlocking the
lru_lock.
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Acked-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
It is possible for gfs2_shrink_glock_memory() to check a glock for
demotion
that's in the process of being freed by gfs2_glock_put(). In this case,
gfs2_shrink_glock_memory() will acquire a new reference to this glock,
and
then try to free the glock itself when it drops the refernce. To solve
this, gfs2_shrink_glock_memory() just needs to check if the glock is in
the process of being freed, and if so skip it without ever unlocking the
lru_lock.
Signed-off-by: Benjamin Marzinski <bmarzins@redhat.com>
Acked-by: Bob Peterson <rpeterso@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
| fs/gfs2/glock.c | diffblobblamehistory |