linux-kernel - Re: linux 3.1 issue: bdi dirty threshold goes mad

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

Date:	Mon, 31 Oct 2011 16:33:13 +0800
From:	Wu Fengguang <fengguang.wu@...el.com>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: linux 3.1 issue: bdi dirty threshold goes mad

On Fri, Oct 28, 2011 at 06:58:22AM +0800, Wu Fengguang wrote:
> Hi,
> 
> FYI, I find bdi dirty threshold madness in the newly released v3.1
> according to the gray lines in the attached graphs, which are for
> these test cases:
> 
> 3G-UKEY-HDD/ext4-1dd-4k-8p-2948M-20:10-3.1.0-vanilla+
> 3G-UKEY-HDD/xfs-10dd-4k-8p-2948M-20:10-3.1.0-vanilla+
> 3G-UKEY-HDD/xfs-1dd-4k-8p-2948M-20:10-3.1.0-vanilla+
> 
> It's basically doing concurrent dd's to a USB key and a hard disk.
> 
> Don't know what's going wrong, but at least should be bisectable..

It seems to depend on kernel builds: the problem disappears in the
newly compiled kernels. This makes it pretty hard to catch the root
cause...

Thanks,
Fengguang
--
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/