linux-kernel - Re: 2.6.20-rc6-mm3

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: <20070201062018.GC33919298@melbourne.sgi.com>
Date:	Thu, 1 Feb 2007 17:20:18 +1100
From:	David Chinner <dgc@....com>
To:	Andrew Morton <akpm@...l.org>
Cc:	Christoph Lameter <clameter@....com>, linux-kernel@...r.kernel.org,
	Jens Axboe <jens.axboe@...cle.com>
Subject: Re: 2.6.20-rc6-mm3

On Wed, Jan 31, 2007 at 04:36:38PM -0800, Andrew Morton wrote:
> On Wed, 31 Jan 2007 16:27:16 -0800 (PST)
> Christoph Lameter <clameter@....com> wrote:
> 
> > On Wed, 31 Jan 2007, Andrew Morton wrote:
> > 
> > > ow.  Please don't make me drop git-block-and-lots-of-other-things again.
> > > Was 2.6.20-rc6-mm2 OK?  It didn't have git-block.
> > 
> > Yes, 2.6.20-rc6-mm2 was okay. Sorry.
> 
> OK, thanks.
> 
> Actually, we might not have lost an IO: it could be that we're simply
> missing an unplug.

Could be - I can't be certain but I think we've got one thread
waiting for a buffer to be unpinned before it is written, and
the other thread waiting for log I/O to complete. The first thread
won't unplug the device, and the log I/o is async so it won't either.

What are the new unplugging rules introduced by the git-block
patch? How do they differ from the existing rules?

Cheers,

Dave.
-- 
Dave Chinner
Principal Engineer
SGI Australian Software Group
-
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/