From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Al Viro <viro@ZenIV•linux.org.uk>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Nikolay Borisov <nborisov@suse•com>
Subject: linux-next: run time BUG after merge of the vfs-fixes tree?
Date: Thu, 25 Jul 2019 14:47:12 +1000 [thread overview]
Message-ID: <20190725144712.39cb1e5b@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3040 bytes --]
Hi all,
During my qemu boot tests (powerpc64 pseries_le_defconfig) today, I got
the following BUG:
# halt
# Stopping network...Saving random seed... [ 6.515368] random: dd: uninitialized urandom read (512 bytes read)
done.
Stopping logging: OK
[ 6.796972] BUG: Unable to handle kernel data access at 0x5deadbeef0000122
[ 6.797133] Faulting instruction address: 0xc00000000041cba4
[ 6.797616] Oops: Kernel access of bad area, sig: 11 [#1]
[ 6.797725] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
[ 6.797987] Modules linked in:
[ 6.798405] CPU: 0 PID: 111 Comm: umount Not tainted 5.3.0-rc1 #2
[ 6.798554] NIP: c00000000041cba4 LR: c00000000041cb90 CTR: 00000000000001fc
[ 6.798664] REGS: c00000007e1eba70 TRAP: 0380 Not tainted (5.3.0-rc1)
[ 6.798716] MSR: 8000000000009033 <SF,EE,ME,IR,DR,RI,LE> CR: 82242884 XER: 20000000
[ 6.798957] CFAR: c00000000041c434 IRQMASK: 0
[ 6.798957] GPR00: c00000000041cb90 c00000007e1ebd00 c00000000110e100 0000000000000001
[ 6.798957] GPR04: 0000000000000800 0000000000000800 0000000000020000 c00000000113dbf8
[ 6.798957] GPR08: 0000000000000048 c00000007a2e2100 5deadbeef0000122 c000000079417380
[ 6.798957] GPR12: 0000000022242884 c0000000012f0000 0000000000000000 0000000000000000
[ 6.798957] GPR16: 0000000000000000 0000000000000000 0000000000000000 0000000000000000
[ 6.798957] GPR20: 0000000000000000 0000000000000000 0000000000000000 00000000100bce20
[ 6.798957] GPR24: 0000000000000000 c00000007a2e2100 0000000000000000 c00000007a2e2188
[ 6.798957] GPR28: 0000000000000000 5deadbeef0000100 5deadbeef0000122 5deadbeef0000100
[ 6.800143] NIP [c00000000041cba4] namespace_unlock+0x194/0x240
[ 6.800208] LR [c00000000041cb90] namespace_unlock+0x180/0x240
[ 6.800366] Call Trace:
[ 6.800456] [c00000007e1ebd00] [c00000000041cb90] namespace_unlock+0x180/0x240 (unreliable)
[ 6.800603] [c00000007e1ebd60] [c00000000041e634] ksys_umount+0x324/0x6f0
[ 6.800760] [c00000007e1ebe00] [c00000000041ea24] sys_umount+0x24/0x40
[ 6.800824] [c00000007e1ebe20] [c00000000000ba64] system_call+0x5c/0x70
[ 6.800940] Instruction dump:
[ 6.801234] 81490124 fba900f0 fbc900f8 2f8a0000 409e00b0 7d234b78 4bfff80d 353fff10
[ 6.801374] 4182007c ebe900f0 e94900f8 2fbf0000 <fbea0000> 409effc8 3ce05dea 60e7dbee
[ 6.801992] ---[ end trace 34315779952607e2 ]---
[ 6.905920]
The system is going down NOW!
5deadbeef is the ppc64 ILLEGAL_POINTER_VALUE. I am guessing that the
problem may have been introduced by commit
2085eeffbc6d ("fix the struct mount leak in umount_tree()")
in the vfs-fixes tree today.
And actually reverting that commit makes the BUG go away.
After doing the revert (and also before today), I get the following log
messages instead of the BUG trace:
umount: devtmpfs busy - remounted read-only
umount: can't unmount /: Invalid argument
So, I have left that commit reverted for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-07-25 4:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 4:47 Stephen Rothwell [this message]
2019-07-25 23:31 ` linux-next: run time BUG after merge of the vfs-fixes tree? Al Viro
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=20190725144712.39cb1e5b@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nborisov@suse$(echo .)com \
--cc=viro@ZenIV$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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