linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Davidlohr Bueso <davidlohr@hp.com>
Cc: Jan Kara <jack@suse.cz>,
	tytso@mit.edu, Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-ext4@vger.kernel.org
Subject: Re: still running into WARNING: CPU: at fs/ext4/inode.c:230 ext4_evict_inode+0x4a6/0x4e0
Date: Wed, 16 Oct 2013 14:50:04 +0200	[thread overview]
Message-ID: <20131016125004.GC14278@quack.suse.cz> (raw)
In-Reply-To: <1381888924.2371.5.camel@buesod1.americas.hpqcorp.net>

On Tue 15-10-13 19:02:04, Davidlohr Bueso wrote:
> Hello Jan,
> 
> Just wanted to let you know I hit this[1] again on Linus' latest. The
> setup/workload is *identical* to the reported one a few months ago.
> 
> [1] https://lkml.org/lkml/2013/8/1/532
> 
> Here's the complete output, I hope it helps...
  Thanks for the headup. Last time I wasn't able to reproduce this and
eventually forgot about the problem. Can I send you a debug patch and you
would run a kernel with it? Thanks.

							Honza

> ------------[ cut here ]------------
> WARNING: CPU: 42 PID: 74607 at fs/ext4/inode.c:230 ext4_evict_inode+0x4a6/0x4e0 [ext4]()
> Modules linked in: fuse autofs4 sunrpc 8021q garp stp llc cpufreq_ondemand pcc_cpufreq ipt_REJECT nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ip_tables ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 xt_state nf_conntrack ip6table_filter ip6_tables ipv6 uinput iTCO_wdt iTCO_vendor_support ipmi_si ipmi_msghandler microcode pcspkr serio_raw lpc_ich mfd_core sg hpilo hpwdt i7core_edac edac_core netxen_nic freq_table ext4 jbd2 mbcache sr_mod cdrom sd_mod crc_t10dif crct10dif_common qla2xxx scsi_transport_fc scsi_tgt pata_acpi ata_generic ata_piix hpsa radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core dm_mirror dm_region_hash dm_log dm_mod
> CPU: 42 PID: 74607 Comm: reaim Tainted: G        W    3.12.0-rc5 #40
> Hardware name: HP ProLiant DL980 G7, BIOS P66 08/31/2222
>  00000000000000e6 ffff8908c6c59d28 ffffffff81550dd8 00000000000000e6
>  0000000000000000 ffff8908c6c59d68 ffffffff8104e29c ffff8908c6c59d78
>  ffff880afae83500 ffff880afae83608 ffff880afae83450 ffff880afae83500
> Call Trace:
>  [<ffffffff81550dd8>] dump_stack+0x49/0x61
>  [<ffffffff8104e29c>] warn_slowpath_common+0x8c/0xc0
>  [<ffffffff8104e2ea>] warn_slowpath_null+0x1a/0x20
>  [<ffffffffa03afe16>] ext4_evict_inode+0x4a6/0x4e0 [ext4]
>  [<ffffffff81197ab7>] evict+0xa7/0x1c0
>  [<ffffffff81197cbf>] iput_final+0xef/0x190
>  [<ffffffff81197d9e>] iput+0x3e/0x50
>  [<ffffffff81195858>] d_kill+0xd8/0x110
>  [<ffffffff81195a1b>] dput+0x18b/0x1c0
>  [<ffffffff8117f588>] __fput+0x188/0x270
>  [<ffffffff8117f73e>] ____fput+0xe/0x10
>  [<ffffffff8106d0bf>] task_work_run+0x8f/0xf0
>  [<ffffffff81003a84>] do_notify_resume+0x84/0x90
>  [<ffffffff8155d9da>] int_signal+0x12/0x17
> ---[ end trace ea7184a5fb48e185 ]---
> 
> 
> Thanks,
> Davidlohr
> 
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

  reply	other threads:[~2013-10-16 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16  2:02 still running into WARNING: CPU: at fs/ext4/inode.c:230 ext4_evict_inode+0x4a6/0x4e0 Davidlohr Bueso
2013-10-16 12:50 ` Jan Kara [this message]
2013-10-16 15:56   ` Davidlohr Bueso
2013-10-16 18:38     ` Jan Kara
2013-11-29  7:37       ` Jan Kara
2013-12-03 18:58         ` Davidlohr Bueso

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=20131016125004.GC14278@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=davidlohr@hp.com \
    --cc=linux-ext4@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).