| 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
| ||
|
Date: Sat, 9 Jun 2012 19:07:31 +0800 From: Fengguang Wu <fengguang.wu@...el.com> To: Ted Ts'o <tytso@....edu>, Jan Kara <jack@...e.cz>, linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org Subject: Re: writeback: bad unlock balance detected in 3.5-rc1 On Fri, Jun 08, 2012 at 10:38:04PM -0400, Theodore Ts'o wrote: > On Sat, Jun 09, 2012 at 08:37:28AM +0900, Fengguang Wu wrote: > > > > Here is the updated changelog: > > > > writeback: Fix lock imbalance in writeback_sb_inodes() > > > > Fix bug introduced by 169ebd90. We have to have wb_list_lock locked when > > restarting writeback loop after having waited for inode writeback. > > > > Bug description by Ted Tso: > > > > I can reproduce this fairly easily by using ext4 w/o a journal, running > > under KVM with 1024megs memory, with fsstress (xfstests #13): > > Not that it matters that much, but I typo'ed the description; sorry > about that. The KVM only had 1024k of memory.... 1MB memory? How do you manage to boot it? Recently I tried running a big fat kernel (with almost everything built in) that can easily OOM (at boot time, before swapon) even given 256MB memory... 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/
Powered by blists - more mailing lists