Re: linux-next: Tree for July 7

[Andrew Morton]

On Wed, 7 Jul 2010 16:55:39 +1000
Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/