linux-kernel - Re: merging the per-bdi writeback 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: <20090623111752.GA23813@infradead.org>
Date:	Tue, 23 Jun 2009 07:17:52 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	Christoph Hellwig <hch@...radead.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	akpm@...ux-foundation.org
Subject: Re: merging the per-bdi writeback patchset

On Tue, Jun 23, 2009 at 01:12:10PM +0200, Jens Axboe wrote:
> > Last time we discussed this you said you're happy with 2.6.32.  I really
> > want to take a more detailed look and put that on the not so urgent list
> > because ou didn't seem to rush for .31.  So my vote goes for waiting a
> > bit longer.
> 
> Yeah, 2.6.32 works for me too, .31 would have been nice though so I
> don't have to carry it around anymore. But either is fine, if you and
> Andrew want more time to review this stuff, then lets just settle for
> .32.

Yes, I'd really prefer more time.  I also expect to come up with some
more changes in that area.  Your patch makes the differences between
kupdate and pdflush-stye writeback look even more ugly then it already
is, so I want to see i there's some nicer way to handle it.  I also want
to take a look if it makes sense to distangle data integrity and
background writeback somehow.

--
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/