From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: linux-next: Tree for July 7
Date: Wed, 7 Jul 2010 17:21:36 -0700 [thread overview]
Message-ID: <20100707172136.3658fb17.akpm@linux-foundation.org> (raw)
In-Reply-To: <20100707165539.957e7d1c.sfr@canb.auug.org.au>
(resend with viro cc)
On Wed, 7 Jul 2010 16:55:39 +1000
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ).
I'm getting a vast stream of BUG()s from the
BUG_ON(inode->i_state != (I_FREEING | I_CLEAR));
in iput_final().
After turning it into a WARN_ON():
[ 49.780786] inode->i_state=0x67
[ 49.780945] ------------[ cut here ]------------
[ 49.781113] WARNING: at fs/inode.c:1246 iput+0x232/0x23f()
[ 49.781279] Modules linked in: dm_mirror dm_region_hash dm_log dm_multipath dm_mod video output sbs sbshc battery ac lp parport sg ide_cd_mod cdrom option usb_wwan usbserial serio_raw floppy snd_hda_intel snd_hda_codec snd_seq_oss snd_seq_midi_event snd_seq button snd_seq_device snd_pcm_oss snd_mixer_oss snd_pcm snd_timer i2c_i801 i2c_core snd soundcore snd_page_alloc pcspkr shpchp ehci_hcd ohci_hcd uhci_hcd
[ 49.783960] Pid: 2418, comm: mount Tainted: G W 2.6.35-rc4 #3
[ 49.784127] Call Trace:
[ 49.784288] [<ffffffff810cec31>] ? iput+0x1fe/0x23f
[ 49.784454] [<ffffffff810cec65>] ? iput+0x232/0x23f
[ 49.784623] [<ffffffff81036283>] warn_slowpath_common+0x7e/0x97
[ 49.784790] [<ffffffff810362b1>] warn_slowpath_null+0x15/0x17
[ 49.784958] [<ffffffff810cec65>] iput+0x232/0x23f
[ 49.785134] [<ffffffff810c59a5>] do_unlinkat+0x104/0x15a
[ 49.785301] [<ffffffff81002a1c>] ? sysret_check+0x27/0x62
[ 49.785470] [<ffffffff8137518b>] ? trace_hardirqs_on_thunk+0x3a/0x3f
[ 49.785639] [<ffffffff810c5a0c>] sys_unlink+0x11/0x13
[ 49.785806] [<ffffffff810029eb>] system_call_fastpath+0x16/0x1b
[ 49.785973] ---[ end trace 6458c1d95dac3fde ]---
So I_DIRTY_SYNC, I_DIRTY_DATASYNC and I_DIRTY_PAGES are set.
Config: http://userweb.kernel.org/~akpm/stuff/config-akpm2.txt
next prev parent reply other threads:[~2010-07-08 0:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 6:55 linux-next: Tree for July 7 Stephen Rothwell
2010-07-07 23:20 ` Andrew Morton
2010-07-07 23:41 ` [PATCH -next] IR: jvc-decoder needs BITREVERSE Randy Dunlap
2010-07-08 0:21 ` Andrew Morton [this message]
2010-07-14 22:20 ` linux-next: Tree for July 7 Andrew Morton
2010-07-14 23:45 ` Stephen Rothwell
2010-07-15 0:27 ` Andrew Morton
2010-07-15 0:46 ` Dave Chinner
2010-07-15 0:53 ` Andrew Morton
2010-07-15 2:12 ` Dave Chinner
2010-07-15 7:18 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2011-07-07 7:25 Stephen Rothwell
2009-07-07 6:34 Stephen Rothwell
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=20100707172136.3658fb17.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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).