linux-kernel - Re: [patch 00/27] [rfc] vfs scalability patchset

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 linux-cve-announce 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]

Message-ID: <20090425220522.GA10248@mit.edu>
Date:	Sat, 25 Apr 2009 18:05:22 -0400
From:	Theodore Tso <tytso@....edu>
To:	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	Al Viro <viro@...IV.linux.org.uk>,
	Christoph Hellwig <hch@...radead.org>, npiggin@...e.de,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [patch 00/27] [rfc] vfs scalability patchset

On Sat, Apr 25, 2009 at 01:29:01PM -0700, Eric W. Biederman wrote:
> 
> I didn't trace it all of the way through but this comment in
> ext3_remount fooled me:
> 
> 	/*
> 	 * We have to unlock super so that we can wait for
> 	 * transactions.
> 	 */
> 
> Which was enough to think it might have been deliberate behavior so I figured
> it was worth asking.  It looked like the journal commit logic could have
> been doing the blocking magic to wait on ongoing truncates and the like.

Working on fixing this already for ext4.  Once we're convinced it's
right for ext4, we can backport the fixes for ext3.

      	  	       		    	      - Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/