From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] GFS2: Fix panic in glock memory shrinker
Date: Wed, 01 Jul 2009 13:02:10 +0100 [thread overview]
Message-ID: <1246449730.3216.74.camel@localhost.localdomain> (raw)
In-Reply-To: <20090630185111.GP3172@ether.msp.redhat.com>
Hi,
Now in the -nmw git tree. Thanks,
Steve.
On Tue, 2009-06-30 at 13:51 -0500, Benjamin Marzinski wrote:
> To: cluster-devel at redhat.com
> Subject: 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>
> ---
> fs/gfs2/glock.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> Index: kernel-upstream/fs/gfs2/glock.c
> ===================================================================
> --- kernel-upstream.orig/fs/gfs2/glock.c
> +++ kernel-upstream/fs/gfs2/glock.c
> @@ -1314,6 +1314,10 @@ static int gfs2_shrink_glock_memory(int
> list_del_init(&gl->gl_lru);
> atomic_dec(&lru_count);
>
> + /* Check if glock is about to be freed */
> + if (atomic_read(&gl->gl_ref) == 0)
> + continue;
> +
> /* Test for being demotable */
> if (!test_and_set_bit(GLF_LOCK, &gl->gl_flags)) {
> gfs2_glock_hold(gl);
>
prev parent reply other threads:[~2009-07-01 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 18:51 [Cluster-devel] GFS2: Fix panic in glock memory shrinker Benjamin Marzinski
2009-06-30 19:02 ` Bob Peterson
2009-07-01 12:02 ` Steven Whitehouse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1246449730.3216.74.camel@localhost.localdomain \
--to=swhiteho@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox