linux-kernel - Re: [PATCH 0/7] Per-bdi writeback flusher threads v20

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: <20090911141659.GA3508@infradead.org>
Date:	Fri, 11 Sep 2009 10:16:59 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Theodore Tso <tytso@....edu>, Jens Axboe <jens.axboe@...cle.com>,
	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	chris.mason@...cle.com, hch@...radead.org,
	akpm@...ux-foundation.org, jack@...e.cz,
	Wu Fengguang <fengguang.wu@...el.com>
Subject: Re: [PATCH 0/7] Per-bdi writeback flusher threads v20

On Fri, Sep 11, 2009 at 09:42:41AM -0400, Theodore Tso wrote:
> > v19 include:
> > 
> > - Drop the max writeback pages patch from Ted. I think we should do
> >   something to that effect, but there's really no reason to entangle
> >   it with this patchset.
> 
> That's reasonable, but I'd really like to know whether some VM hacker
> going to try to deal with this during the 2.6.32 window?  Such as
> maybe Wu Fengguang's patches, perhaps?  
> 
> Or do I need to put in some kind of hack into ext4 ala what XFS did to
> work around this problem until we can come up with a longer-term fix?

I defintively want to see something in the VM, but I also agree with
Jens' decision not to include it in the patchkit.  It's not really
related to the patchkit except for depending on it, and we still
have a lot of discussion going on.  If we can't get an agreement with
the VM people by the end of the regular merge window I'm all for pushing
your simple patch.
--
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/