linux-kernel - Re: [2.6.36-rc1] unmount livelock due to racing with bdi-flusher threads

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] [day] [month] [year] [list]

Date:	Thu, 30 Sep 2010 22:59:16 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Jan Kara <jack@...e.cz>
Cc:	Dave Chinner <david@...morbit.com>, linux-kernel@...r.kernel.org,
	linux-fsdevel@...r.kernel.org
Subject: Re: [2.6.36-rc1] unmount livelock due to racing with bdi-flusher
 threads

On Thu, Sep 30, 2010 at 11:02:51PM +0200, Jan Kara wrote:
> I think the best resolution of this problem would be to change the work
> that is submitted via bdi_start_writeback() (i.e., the work without
> superblock = work which needs to do locking) to "target based scheme" like
> Christoph wanted already some time ago. I actually have a patch to do this
> for background writeback so I will just modify it to apply to a wider range
> of writeback as well. Or Christoph, do you already have some patches in
> this direction?

I've not started any work on it yet.

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