linux-ext4 - Re: WARNING: CPU: 26 PID: 93793 at fs/ext4/inode.c:230 ext4_evict_inode+0x4c9/0x500 [ext4]() still in 3.11-rc3

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <52026764.3090305@roeck-us.net>
Date:	Wed, 07 Aug 2013 08:27:32 -0700
From:	Guenter Roeck <linux@...ck-us.net>
To:	Jan Kara <jack@...e.cz>
CC:	Davidlohr Bueso <davidlohr@...com>, Theodore Ts'o <tytso@....edu>,
	LKML <linux-kernel@...r.kernel.org>, linux-ext4@...r.kernel.org
Subject: Re: WARNING: CPU: 26 PID: 93793 at fs/ext4/inode.c:230 ext4_evict_inode+0x4c9/0x500
 [ext4]() still in 3.11-rc3

On 08/07/2013 08:20 AM, Jan Kara wrote:
> On Thu 01-08-13 20:58:46, Davidlohr Bueso wrote:
>> On Thu, 2013-08-01 at 22:33 +0200, Jan Kara wrote:
>>>    Hi,
>>>
>>> On Thu 01-08-13 13:14:19, Davidlohr Bueso wrote:
>>>> FYI I'm seeing loads of the following messages with Linus' latest
>>>> 3.11-rc3 (which includes 822dbba33458cd6ad)
>>>    Thanks for notice. I see you are running reaim to trigger this. What
>>> workload?
>>
>> After re-running the workloads one by one, I finally hit the issue again
>> with 'dbase'. FWIW I'm using ramdisks + ext4.
>    Hum, I'm not able to reproduce this with current Linus' kernel - commit
> e4ef108fcde0b97ed38923ba1ea06c7a152bab9e - I've tried with ramdisk but no
> luck. Are you using some special mount options?
>
I don't see this commit in the upstream kernel ?

I tried reproducing the problem on the same system I had seen 822dbba33458cd6ad on,
with the same workload. It has now been running since last Friday, but I have
not seen any problems.

Guenter

> 								Honza
>
>>>
>>>> ------------[ cut here ]------------
>>>> WARNING: CPU: 26 PID: 93793 at fs/ext4/inode.c:230 ext4_evict_inode+0x4c9/0x500 [ext4]()
>>>> Modules linked in: autofs4 cpufreq_ondemand freq_table sunrpc 8021q garp stp llc 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 dm_mirror dm_region_hash dm_log dm_mod uinput iTCO_wdt iTCO_vendor_support coretemp kvm_intel kvm crc32c_intel ghash_clmulni_intel microcode pcspkr sg lpc_ich mfd_core hpilo hpwdt i7core_edac edac_core netxen_nic mperf ext4 jbd2 mbcache sd_mod crc_t10dif aesni_intel ablk_helper cryptd lrw gf128mul glue_helper aes_x86_64 hpsa radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: freq_table]
>>>> CPU: 26 PID: 93793 Comm: reaim Tainted: G        W    3.11.0-rc3+ #1
>>>> Hardware name: HP ProLiant DL980 G7, BIOS P66 06/24/2011
>>>>   00000000000000e6 ffff8985db603d78 ffffffff8153ce4d 00000000000000e6
>>>>   0000000000000000 ffff8985db603db8 ffffffff8104cf1c ffff8985db603dc8
>>>>   ffff8b05c485b8b0 ffff8b05c485b9b8 ffff8b05c485b800 00000000ffffff9c
>>>> Call Trace:
>>>>   [<ffffffff8153ce4d>] dump_stack+0x49/0x5c
>>>>   [<ffffffff8104cf1c>] warn_slowpath_common+0x8c/0xc0
>>>>   [<ffffffff8104cf6a>] warn_slowpath_null+0x1a/0x20
>>>>   [<ffffffffa02a0179>] ext4_evict_inode+0x4c9/0x500 [ext4]
>>>>   [<ffffffff811915e7>] evict+0xa7/0x1c0
>>>>   [<ffffffff811917e3>] iput_final+0xe3/0x170
>>>>   [<ffffffff811918ae>] iput+0x3e/0x50
>>>>   [<ffffffff81187aa6>] do_unlinkat+0x1c6/0x280
>>>>   [<ffffffff8106f3e4>] ? task_work_run+0x94/0xf0
>>>>   [<ffffffff81003a44>] ? do_notify_resume+0x84/0x90
>>>>   [<ffffffff81187b76>] SyS_unlink+0x16/0x20
>>>>   [<ffffffff81549a02>] system_call_fastpath+0x16/0x1b
>>>> ---[ end trace 15e812809616488b ]---
>>>>
>>>>
>>
>>

--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html