linux-kernel - Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

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: <20101002165433.GL21129@thunk.org>
Date:	Sat, 2 Oct 2010 12:54:33 -0400
From:	Ted Ts'o <tytso@....edu>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	Maciej Rutecki <maciej.rutecki@...il.com>,
	Florian Mickler <florian@...kler.org>,
	Cesar Eduardo Barros <cesarb@...arb.net>
Subject: Re: [Bug #19062] Dirtiable inode bdi default != sb bdi btrfs

On Sun, Sep 26, 2010 at 10:04:15PM +0200, Rafael J. Wysocki wrote:
> The following bug entry is on the current list of known regressions
> from 2.6.35.  Please verify if it still should be listed and let the tracking team
> know (either way).
> 
> 
> Bug-Entry	: http://bugzilla.kernel.org/show_bug.cgi?id=19062
> Subject		: Dirtiable inode bdi default != sb bdi btrfs
> Submitter	: Cesar Eduardo Barros <cesarb@...arb.net>
> Date		: 2010-09-23 0:54 (4 days old)
> Message-ID	: <4C9AA546.6050201@...arb.net>
> References	: http://marc.info/?l=linux-kernel&m=128520328929595&w=2

Note: I'm seeing this warning (Dirtiable inode bdi default != sb bdi)
when I moved from 2.6.36-rc3 to 2.6.36-rc6, using ext4 as a root
partition, and running mke2fs and e2fsck on ext2, ext3, and ext4 file
systems.  So I'm seeing this as a known regression from rc3 to rc6.
Maybe it's different bug with ext4, but in any case, it's highly
annoying.

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