lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 6 Nov 2008 14:20:20 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Theodore Tso <tytso@....edu>
Cc:	linux-ext4@...r.kernel.org
Subject: Re: [patch 24/51] ext3: wait on all pending commits in ext3_sync_fs

On Thu, 6 Nov 2008 16:44:31 -0500
Theodore Tso <tytso@....edu> wrote:

> My version of this patch also cleaned up the following comment, which
> has been wrong since 2.5.70 or thereabouts...

oh, I didn't spot that.

I looked at the version in linux-next and saw that it was propagating
the error value back to the VFS as well.  Or maybe that was done in a
separate patch, dunno.  But while that's a good change, I felt that we
should separate it from this bugfix.  I meant to mention it but I
forgot, sorry.
 
> This isn't urgent, so could you just queue this up for the next merge
> window in the -mm tree?
> 
> 						- Ted
> 
> ext3: Clean up outdated and incorrect comment for ext3_write_super()
> 
> Signed-off-by: "Theodore Ts'o" <tytso@....edu>
> Cc: Andrew Morton <akpm@...ux-foundation.org>
> Cc: <linux-ext4@...r.kernel.org>
> ---
> diff --git a/fs/ext3/super.c b/fs/ext3/super.c
> index e5717a4..296c044 100644
> --- a/fs/ext3/super.c
> +++ b/fs/ext3/super.c
> @@ -2375,12 +2375,9 @@ int ext3_force_commit(struct super_block *sb)
>  /*
>   * Ext3 always journals updates to the superblock itself, so we don't
>   * have to propagate any other updates to the superblock on disk at this
> - * point.  Just start an async writeback to get the buffers on their way
> - * to the disk.
> - *
> - * This implicitly triggers the writebehind on sync().
> + * point.  (We can probably nuke this function altogether, and remove
> + * any mention to sb->s_dirt in all of fs/ext3; eventual cleanup...)
>   */
> -
>  static void ext3_write_super (struct super_block * sb)
>  {
>  	if (mutex_trylock(&sb->s_lock) != 0)

Sure.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists