public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* [GFS2] Fix incorrect fs sync behaviour [2/5]
@ 2006-11-06 11:07 Steven Whitehouse
  2006-12-01 17:57 ` Russell Cattelan
  0 siblings, 1 reply; 3+ messages in thread
From: Steven Whitehouse @ 2006-11-06 11:07 UTC (permalink / raw)
  To: cluster-devel, linux-kernel; +Cc: Russell Cattelan

>From 4a221953ed121692aa25998451a57c7f4be8b4f6 Mon Sep 17 00:00:00 2001
From: Steven Whitehouse <swhiteho@redhat.com>
Date: Wed, 1 Nov 2006 09:57:57 -0500
Subject: [PATCH] [GFS2] Fix incorrect fs sync behaviour.

This adds a sync_fs superblock operation for GFS2 and removes
the journal flush from write_super in favour of sync_fs where it
ought to be. This is more or less identical to the way in which ext3
does this.

This bug was pointed out by Russell Cattelan <cattelan@redhat.com>

Cc: Russell Cattelan <cattelan@redhat.com>
Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
---
 fs/gfs2/ops_super.c |   44 ++++++++++++++++++++++++++++----------------
 1 files changed, 28 insertions(+), 16 deletions(-)

diff --git a/fs/gfs2/ops_super.c b/fs/gfs2/ops_super.c
index 06f06f7..b47d959 100644
--- a/fs/gfs2/ops_super.c
+++ b/fs/gfs2/ops_super.c
@@ -138,16 +138,27 @@ static void gfs2_put_super(struct super_
 }
 
 /**
- * gfs2_write_super - disk commit all incore transactions
- * @sb: the filesystem
+ * gfs2_write_super
+ * @sb: the superblock
  *
- * This function is called every time sync(2) is called.
- * After this exits, all dirty buffers are synced.
  */
 
 static void gfs2_write_super(struct super_block *sb)
 {
+	sb->s_dirt = 0;
+}
+
+/**
+ * gfs2_sync_fs - sync the filesystem
+ * @sb: the superblock
+ *
+ * Flushes the log to disk.
+ */
+static int gfs2_sync_fs(struct super_block *sb, int wait)
+{
+	sb->s_dirt = 0;
 	gfs2_log_flush(sb->s_fs_info, NULL);
+	return 0;
 }
 
 /**
@@ -452,17 +463,18 @@ static void gfs2_destroy_inode(struct in
 }
 
 struct super_operations gfs2_super_ops = {
-	.alloc_inode = gfs2_alloc_inode,
-	.destroy_inode = gfs2_destroy_inode,
-	.write_inode = gfs2_write_inode,
-	.delete_inode = gfs2_delete_inode,
-	.put_super = gfs2_put_super,
-	.write_super = gfs2_write_super,
-	.write_super_lockfs = gfs2_write_super_lockfs,
-	.unlockfs = gfs2_unlockfs,
-	.statfs = gfs2_statfs,
-	.remount_fs = gfs2_remount_fs,
-	.clear_inode = gfs2_clear_inode,
-	.show_options = gfs2_show_options,
+	.alloc_inode		= gfs2_alloc_inode,
+	.destroy_inode		= gfs2_destroy_inode,
+	.write_inode		= gfs2_write_inode,
+	.delete_inode		= gfs2_delete_inode,
+	.put_super		= gfs2_put_super,
+	.write_super		= gfs2_write_super,
+	.sync_fs		= gfs2_sync_fs,
+	.write_super_lockfs 	= gfs2_write_super_lockfs,
+	.unlockfs		= gfs2_unlockfs,
+	.statfs			= gfs2_statfs,
+	.remount_fs		= gfs2_remount_fs,
+	.clear_inode		= gfs2_clear_inode,
+	.show_options		= gfs2_show_options,
 };
 
-- 
1.4.1




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

* Re: [GFS2] Fix incorrect fs sync behaviour [2/5]
  2006-11-06 11:07 [GFS2] Fix incorrect fs sync behaviour [2/5] Steven Whitehouse
@ 2006-12-01 17:57 ` Russell Cattelan
  2006-12-04  9:12   ` [Cluster-devel] " Steven Whitehouse
  0 siblings, 1 reply; 3+ messages in thread
From: Russell Cattelan @ 2006-12-01 17:57 UTC (permalink / raw)
  To: Steven Whitehouse; +Cc: cluster-devel, linux-kernel

On Mon, 2006-11-06 at 11:07 +0000, Steven Whitehouse wrote:
> >From 4a221953ed121692aa25998451a57c7f4be8b4f6 Mon Sep 17 00:00:00 2001
> From: Steven Whitehouse <swhiteho@redhat.com>
> Date: Wed, 1 Nov 2006 09:57:57 -0500
> Subject: [PATCH] [GFS2] Fix incorrect fs sync behaviour.
> 
> This adds a sync_fs superblock operation for GFS2 and removes
> the journal flush from write_super in favour of sync_fs where it
> ought to be. This is more or less identical to the way in which ext3
> does this.
> 
> This bug was pointed out by Russell Cattelan <cattelan@redhat.com>
> 
> Cc: Russell Cattelan <cattelan@redhat.com>
> Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> ---
>  fs/gfs2/ops_super.c |   44 ++++++++++++++++++++++++++++----------------
>  1 files changed, 28 insertions(+), 16 deletions(-)
> 
> diff --git a/fs/gfs2/ops_super.c b/fs/gfs2/ops_super.c
> index 06f06f7..b47d959 100644
> --- a/fs/gfs2/ops_super.c
> +++ b/fs/gfs2/ops_super.c
> @@ -138,16 +138,27 @@ static void gfs2_put_super(struct super_
>  }
>  
>  /**
> - * gfs2_write_super - disk commit all incore transactions
> - * @sb: the filesystem
> + * gfs2_write_super
> + * @sb: the superblock
>   *
> - * This function is called every time sync(2) is called.
> - * After this exits, all dirty buffers are synced.
>   */
>  
>  static void gfs2_write_super(struct super_block *sb)
>  {
> +	sb->s_dirt = 0;
This is a bit different than my original patch? 
Are you sure we don't need the s_lock here?


> +}
> +
> +/**
> + * gfs2_sync_fs - sync the filesystem
> + * @sb: the superblock
> + *
> + * Flushes the log to disk.
> + */
> +static int gfs2_sync_fs(struct super_block *sb, int wait)
> +{
> +	sb->s_dirt = 0;
>  	gfs2_log_flush(sb->s_fs_info, NULL);
> +	return 0;
>  }
>  
>  /**
> @@ -452,17 +463,18 @@ static void gfs2_destroy_inode(struct in
>  }
>  
>  struct super_operations gfs2_super_ops = {
> -	.alloc_inode = gfs2_alloc_inode,
> -	.destroy_inode = gfs2_destroy_inode,
> -	.write_inode = gfs2_write_inode,
> -	.delete_inode = gfs2_delete_inode,
> -	.put_super = gfs2_put_super,
> -	.write_super = gfs2_write_super,
> -	.write_super_lockfs = gfs2_write_super_lockfs,
> -	.unlockfs = gfs2_unlockfs,
> -	.statfs = gfs2_statfs,
> -	.remount_fs = gfs2_remount_fs,
> -	.clear_inode = gfs2_clear_inode,
> -	.show_options = gfs2_show_options,
> +	.alloc_inode		= gfs2_alloc_inode,
> +	.destroy_inode		= gfs2_destroy_inode,
> +	.write_inode		= gfs2_write_inode,
> +	.delete_inode		= gfs2_delete_inode,
> +	.put_super		= gfs2_put_super,
> +	.write_super		= gfs2_write_super,
> +	.sync_fs		= gfs2_sync_fs,
> +	.write_super_lockfs 	= gfs2_write_super_lockfs,
> +	.unlockfs		= gfs2_unlockfs,
> +	.statfs			= gfs2_statfs,
> +	.remount_fs		= gfs2_remount_fs,
> +	.clear_inode		= gfs2_clear_inode,
> +	.show_options		= gfs2_show_options,
>  };
>  
-- 
Russell Cattelan <cattelan@redhat.com>


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

* Re: [Cluster-devel] Re: [GFS2] Fix incorrect fs sync behaviour [2/5]
  2006-12-01 17:57 ` Russell Cattelan
@ 2006-12-04  9:12   ` Steven Whitehouse
  0 siblings, 0 replies; 3+ messages in thread
From: Steven Whitehouse @ 2006-12-04  9:12 UTC (permalink / raw)
  To: Russell Cattelan; +Cc: cluster-devel, linux-kernel

Hi,

On Fri, 2006-12-01 at 11:57 -0600, Russell Cattelan wrote:
> On Mon, 2006-11-06 at 11:07 +0000, Steven Whitehouse wrote:
> > >From 4a221953ed121692aa25998451a57c7f4be8b4f6 Mon Sep 17 00:00:00 2001
> > From: Steven Whitehouse <swhiteho@redhat.com>
> > Date: Wed, 1 Nov 2006 09:57:57 -0500
> > Subject: [PATCH] [GFS2] Fix incorrect fs sync behaviour.
> > 
> > This adds a sync_fs superblock operation for GFS2 and removes
> > the journal flush from write_super in favour of sync_fs where it
> > ought to be. This is more or less identical to the way in which ext3
> > does this.
> > 
> > This bug was pointed out by Russell Cattelan <cattelan@redhat.com>
> > 
> > Cc: Russell Cattelan <cattelan@redhat.com>
> > Signed-off-by: Steven Whitehouse <swhiteho@redhat.com>
> > ---
> >  fs/gfs2/ops_super.c |   44 ++++++++++++++++++++++++++++----------------
> >  1 files changed, 28 insertions(+), 16 deletions(-)
> > 
> > diff --git a/fs/gfs2/ops_super.c b/fs/gfs2/ops_super.c
> > index 06f06f7..b47d959 100644
> > --- a/fs/gfs2/ops_super.c
> > +++ b/fs/gfs2/ops_super.c
> > @@ -138,16 +138,27 @@ static void gfs2_put_super(struct super_
> >  }
> >  
> >  /**
> > - * gfs2_write_super - disk commit all incore transactions
> > - * @sb: the filesystem
> > + * gfs2_write_super
> > + * @sb: the superblock
> >   *
> > - * This function is called every time sync(2) is called.
> > - * After this exits, all dirty buffers are synced.
> >   */
> >  
> >  static void gfs2_write_super(struct super_block *sb)
> >  {
> > +	sb->s_dirt = 0;
> This is a bit different than my original patch?
This was largely taken from the ext3 code as an example, rather than
your patch.

>  
> Are you sure we don't need the s_lock here?
> 
Yes. See linux-2.6/Documentation/filesystems/Locking:


locking rules:
        All may block.
                        BKL     s_lock  s_umount
[snip]
write_super:            no      yes     read

it is already held on entry to write_super,

Steve.



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

end of thread, other threads:[~2006-12-04  9:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-06 11:07 [GFS2] Fix incorrect fs sync behaviour [2/5] Steven Whitehouse
2006-12-01 17:57 ` Russell Cattelan
2006-12-04  9:12   ` [Cluster-devel] " Steven Whitehouse

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox