From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Andrew Morton <akpm@linux-foundation•org>
Cc: Dave Chinner <david@fromorbit•com>,
Al Viro <viro@zeniv•linux.org.uk>,
linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Christoph Hellwig <hch@lst•de>, Jens Axboe <axboe@kernel•dk>,
Jan Kara <jack@suse•cz>
Subject: Re: linux-next: OOPS at boot time
Date: Wed, 21 Jul 2010 17:48:09 +1000 [thread overview]
Message-ID: <20100721174809.4781c244.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100721002907.639802cd.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
On Wed, 21 Jul 2010 00:29:07 -0700 Andrew Morton <akpm@linux-foundation•org> wrote:
>
> On Wed, 21 Jul 2010 15:20:07 +1000 Dave Chinner <david@fromorbit•com> wrote:
>
> > > and they were dirtied within dquot_free_space().
> >
> > AFAICT dquot_free_space() is called deep in the guts of
> > ext3_truncate() via dquot_free_block(), which is called directly
> > before end_writeback(). That should overwrite any state changes made
> > inside ext3_truncate. I wonder if iput_final() is racing with
> > something else here?
> >
>
> This isn't a race. I type `make' and the warnings spew out at hundreds
> per second - every unlink, I'd say.
Bisected to:
commit 8bfe4a06746e5f03c02afe3ceb97b5364c099f63
Author: Al Viro <viro@zeniv•linux.org.uk>
Date: Sun Jun 6 07:08:19 2010 -0400
convert ext3 to ->evict_inode()
Signed-off-by: Al Viro <viro@zeniv•linux.org.uk>
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-07-21 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 6:41 linux-next: OOPS at boot time Stephen Rothwell
2010-07-20 10:36 ` Andrew Morton
2010-07-20 22:45 ` Dave Chinner
2010-07-21 0:44 ` Andrew Morton
2010-07-21 5:20 ` Dave Chinner
2010-07-21 7:29 ` Andrew Morton
2010-07-21 7:48 ` Stephen Rothwell [this message]
2010-07-21 12:11 ` Jan Kara
2010-07-21 17:49 ` Al Viro
2010-07-21 21:40 ` Al Viro
2010-07-23 10:04 ` Jan Kara
2010-07-24 12:27 ` Al Viro
2010-07-21 23:19 ` Dave Chinner
2010-07-21 12:19 ` Jan Kara
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=20100721174809.4781c244.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=akpm@linux-foundation$(echo .)org \
--cc=axboe@kernel$(echo .)dk \
--cc=david@fromorbit$(echo .)com \
--cc=hch@lst$(echo .)de \
--cc=jack@suse$(echo .)cz \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@zeniv$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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