* 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513
@ 2019-03-04 16:02 Pavel Machek
2019-03-04 22:32 ` Theodore Y. Ts'o
0 siblings, 1 reply; 4+ messages in thread
From: Pavel Machek @ 2019-03-04 16:02 UTC (permalink / raw)
To: tytso, adilger.kernel, linux-ext4, kernel list; +Cc: jack, linux-fsdevel
[-- Attachment #1: Type: text/plain, Size: 2738 bytes --]
Hi!
This happened on trying to sync filesystems with unison:
Any ideas?
Should I be forcing fsck soon?
Pavel
[12717.827444] ------------[ cut here ]------------
[12717.827465] kernel BUG at fs/inode.c:513!
[12717.827486] invalid opcode: 0000 [#1] SMP PTI
[12717.827495] CPU: 1 PID: 916 Comm: kswapd0 Not tainted
5.0.0-rc8-next-20190301+ #224
[12717.827501] Hardware name: LENOVO 17097HU/17097HU, BIOS 7BETD8WW
(2.19 ) 03/31/2011
[12717.827515] EIP: clear_inode+0x78/0xa0
[12717.827522] Code: 83 0c 01 00 00 8d 93 0c 01 00 00 39 c2 75 3b c7
83 9c 00 00 00 60 00 00 00 5b 5e 5d c3 90 8d 74 26 00 0f 0b 8d b6 00
00 00 00 <0f> 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6
00 00
[12717.827529] EAX: c57b540c EBX: cea39720 ECX: 00000001 EDX: 00000000
[12717.827535] ESI: cea39860 EDI: cea39824 EBP: f1a61d38 ESP: f1a61d30
[12717.827541] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS:
00010086
[12717.827548] CR0: 80050033 CR2: 1d8e0000 CR3: 06dbc000 CR4: 000006b0
[12717.827553] Call Trace:
[12717.827566] ext4_clear_inode+0x12/0x70
[12717.827575] ext4_evict_inode+0x76/0x460
[12717.827582] evict+0xa4/0x1b0
[12717.827589] dispose_list+0x39/0x50
[12717.827597] prune_icache_sb+0x42/0x60
[12717.827604] ? iput+0x150/0x150
[12717.827613] super_cache_scan+0x106/0x160
[12717.827621] shrink_slab.constprop.82+0x172/0x280
[12717.827629] shrink_node+0x831/0xa00
[12717.827638] ? inactive_list_is_low.constprop.81+0x18a/0x1c0
[12717.827645] kswapd+0x331/0x780
[12717.827651] ? kswapd+0x331/0x780
[12717.827663] kthread+0xe7/0x120
[12717.827669] ? shrink_all_memory+0xd0/0xd0
[12717.827676] ? kthread_park+0xa0/0xa0
[12717.827686] ret_from_fork+0x2e/0x38
[12717.827692] Modules linked in:
[12717.827702] ---[ end trace e6eadf01587ff9cc ]---
[12717.827710] EIP: clear_inode+0x78/0xa0
[12717.827716] Code: 83 0c 01 00 00 8d 93 0c 01 00 00 39 c2 75 3b c7
83 9c 00 00 00 60 00 00 00 5b 5e 5d c3 90 8d 74 26 00 0f 0b 8d b6 00
00 00 00 <0f> 0b 8d b6 00 00 00 00 0f 0b 8d b6 00 00 00 00 0f 0b 8d b6
00 00
[12717.827723] EAX: c57b540c EBX: cea39720 ECX: 00000001 EDX: 00000000
[12717.827729] ESI: cea39860 EDI: cea39824 EBP: f1a61d38 ESP: c526947c
[12717.827735] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS:
00010086
[12717.827741] CR0: 80050033 CR2: 1d8e0000 CR3: 06dbc000 CR4: 000006b0
[12717.833838] wlan0: deauthenticated from 5c:f4:ab:10:d2:bb (Reason:
15=4WAY_HANDSHAKE_TIMEOUT)
[12734.494782] wlan0: authenticate with 5c:f4:ab:10:d2:bb
[12734.495011] wlan0: send auth to 5c:f4:ab:10:d2:bb (try 1/3)
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513
2019-03-04 16:02 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513 Pavel Machek
@ 2019-03-04 22:32 ` Theodore Y. Ts'o
2019-03-04 23:14 ` Pavel Machek
0 siblings, 1 reply; 4+ messages in thread
From: Theodore Y. Ts'o @ 2019-03-04 22:32 UTC (permalink / raw)
To: Pavel Machek; +Cc: adilger.kernel, jack, linux-fsdevel, linux-mm
(Adding linux-mm and moving linux-ext4 and linux-kernel to the bcc
list...)
On Mon, Mar 04, 2019 at 05:02:55PM +0100, Pavel Machek wrote:
>
> This happened on trying to sync filesystems with unison:
>
> Any ideas?
>
> Should I be forcing fsck soon?
> Pavel
>
> [12717.827444] ------------[ cut here ]------------
> [12717.827465] kernel BUG at fs/inode.c:513!
It seems unlikely that fsck is going to help. The BUG_ON in question
appears to be:
BUG_ON(inode->i_data.nrexceptional);
This is an in-memory accounting variable which seems to be related to
tracking DAX and shadow page entries --- and it seems very unlikely to
be the sort of thing triggered by an on-disk corruption.
Do you have a reliable repro for this? If so, the next step would be
to bisect...
- Ted
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513
2019-03-04 22:32 ` Theodore Y. Ts'o
@ 2019-03-04 23:14 ` Pavel Machek
2019-03-05 21:33 ` Theodore Y. Ts'o
0 siblings, 1 reply; 4+ messages in thread
From: Pavel Machek @ 2019-03-04 23:14 UTC (permalink / raw)
To: Theodore Y. Ts'o; +Cc: adilger.kernel, jack, linux-fsdevel, linux-mm
[-- Attachment #1: Type: text/plain, Size: 1364 bytes --]
Hi!
> (Adding linux-mm and moving linux-ext4 and linux-kernel to the bcc
> list...)
Umm. So I ... bcc them too?
> On Mon, Mar 04, 2019 at 05:02:55PM +0100, Pavel Machek wrote:
> >
> > This happened on trying to sync filesystems with unison:
> >
> > Any ideas?
> >
> > Should I be forcing fsck soon?
> > Pavel
> >
> > [12717.827444] ------------[ cut here ]------------
> > [12717.827465] kernel BUG at fs/inode.c:513!
>
> It seems unlikely that fsck is going to help. The BUG_ON in question
> appears to be:
>
> BUG_ON(inode->i_data.nrexceptional);
>
> This is an in-memory accounting variable which seems to be related to
> tracking DAX and shadow page entries --- and it seems very unlikely to
> be the sort of thing triggered by an on-disk corruption.
>
> Do you have a reliable repro for this? If so, the next step would be
> to bisect...
It happened just once... so I don't yet know.
I'm not even sure what file was affected. unison was showing some kind
of png from openstreetmap cache, but I could read it using md5sum just
fine.
-next is normally pretty boring, but it seems to get pretty
interesting around -final release...
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513
2019-03-04 23:14 ` Pavel Machek
@ 2019-03-05 21:33 ` Theodore Y. Ts'o
0 siblings, 0 replies; 4+ messages in thread
From: Theodore Y. Ts'o @ 2019-03-05 21:33 UTC (permalink / raw)
To: Pavel Machek; +Cc: adilger.kernel, jack, linux-fsdevel, linux-mm
On Tue, Mar 05, 2019 at 12:14:26AM +0100, Pavel Machek wrote:
> Hi!
>
> > (Adding linux-mm and moving linux-ext4 and linux-kernel to the bcc
> > list...)
>
> Umm. So I ... bcc them too?
Nah, I bcc'ed them so that people on those lists would understand that
I had dropped them from thread because it probably isn't appropriate
to include them on the thread.
> > Do you have a reliable repro for this? If so, the next step would be
> > to bisect...
>
> It happened just once... so I don't yet know.
>
> I'm not even sure what file was affected. unison was showing some kind
> of png from openstreetmap cache, but I could read it using md5sum just
> fine.
>
> -next is normally pretty boring, but it seems to get pretty
> interesting around -final release...
OK, let's see if anyone else reports a similar failure.
- Ted
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2019-03-05 21:34 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-03-04 16:02 5.0.0-rc8-next-20190301+: kernel bug at fs/inode.c:513 Pavel Machek
2019-03-04 22:32 ` Theodore Y. Ts'o
2019-03-04 23:14 ` Pavel Machek
2019-03-05 21:33 ` Theodore Y. Ts'o
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).