Cluster-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Cluster-devel] GFS2: Fix panic in glock memory shrinker
@ 2009-06-30 18:51 Benjamin Marzinski
  2009-06-30 19:02 ` Bob Peterson
  2009-07-01 12:02 ` Steven Whitehouse
  0 siblings, 2 replies; 3+ messages in thread
From: Benjamin Marzinski @ 2009-06-30 18:51 UTC (permalink / raw)
  To: cluster-devel.redhat.com

To: cluster-devel@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);



^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Cluster-devel] GFS2: Fix panic in glock memory shrinker
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Bob Peterson @ 2009-06-30 19:02 UTC (permalink / raw)
  To: cluster-devel.redhat.com

----- "Benjamin Marzinski" <bmarzins@redhat.com> 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);

Hi,

ACKed by Bob Peterson <rpeterso@redhat.com>

Regards,

Bob Peterson
Red Hat File Systems



^ permalink raw reply	[flat|nested] 3+ messages in thread

* [Cluster-devel] GFS2: Fix panic in glock memory shrinker
  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
  1 sibling, 0 replies; 3+ messages in thread
From: Steven Whitehouse @ 2009-07-01 12:02 UTC (permalink / raw)
  To: cluster-devel.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);
> 



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2009-07-01 12:02 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox