From: Fengguang Wu <fengguang.wu@intel.com>
To: Ted Ts'o <tytso@mit.edu>, Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: writeback: bad unlock balance detected in 3.5-rc1
Date: Sat, 9 Jun 2012 19:07:31 +0800 [thread overview]
Message-ID: <20120609110731.GB14726@localhost> (raw)
In-Reply-To: <20120609023804.GC14153@thunk.org>
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
next prev parent reply other threads:[~2012-06-09 11:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-08 14:36 writeback: bad unlock balance detected in 3.5-rc1 Theodore Ts'o
2012-06-08 15:07 ` Jan Kara
2012-06-08 15:45 ` Fengguang Wu
2012-06-08 15:51 ` Sedat Dilek
2012-06-08 16:00 ` Fengguang Wu
2012-06-08 20:50 ` Jan Kara
2012-06-11 11:21 ` Artem Bityutskiy
2012-06-11 11:21 ` Fengguang Wu
2012-06-08 20:28 ` Ted Ts'o
2012-06-08 23:37 ` Fengguang Wu
2012-06-09 2:38 ` Ted Ts'o
2012-06-09 11:07 ` Fengguang Wu [this message]
2012-06-09 11:17 ` Ted Ts'o
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120609110731.GB14726@localhost \
--to=fengguang.wu@intel.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).