From: Heiko Carstens <hca@linux.ibm.com>
To: Christian Brauner <brauner@kernel.org>,
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>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: [linux-next: vfs - regression] - merge error?
Date: Fri, 28 Nov 2025 14:11:44 +0100 [thread overview]
Message-ID: <20251128131144.33307A73-hca@linux.ibm.com> (raw)
In-Reply-To: <20251128162928.36eec2d6@canb.auug.org.au>
On Fri, Nov 28, 2025 at 04:29:28PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20251127:
>
> This kernel produces a warning at boot time.
>
> The vfs-brauner tree still had its build failure so I used a supplied
> patch.
ltp's mq_notify03 test case causes this on linux-next as of 20251128:
Unable to handle kernel pointer dereference in virtual kernel address space
Failing address: 0000000000000000 TEID: 0000000000000803
Fault in home space mode while using kernel ASCE.
AS:0000000002528007 R3:00000001ffffc007 S:00000001ffffb801 P:0000000000000400
Oops: 0011 ilc:3 [#1]SMP
Modules linked in:
CPU: 2 UID: 0 PID: 702 Comm: mq_notify03 Not tainted 6.18.0-rc7-00495-g73612a36da1a #17 NONE
Hardware name: IBM 3931 A01 704 (z/VM 7.4.0)
Krnl PSW : 0704e00180000000 000003ffe04f2baa (__fput+0x5a/0x2e0)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3
Krnl GPRS: 0000000080000000 000003ffe1a25200 0000000000000008 000003ffe04f2ea0
000003ffe1a2531d 0000000000000000 00000000899e2300 00000000815e2a20
000000008ce3c008 0000000088789140 00000000040b801f 00000000827ef800
000003ff00000000 00000000899e2300 0000037fe0af3c00 0000037fe0af3b98
Krnl Code: 000003ffe04f2b9c: a7a00600 tmlh %r10,1536
000003ffe04f2ba0: a744002e brc 4,000003ffe04f2bfc
#000003ffe04f2ba4: e35090300004 lg %r5,48(%r9)
>000003ffe04f2baa: e31050280004 lg %r1,40(%r5)
000003ffe04f2bb0: e33013b80004 lg %r3,952(%r1)
000003ffe04f2bb6: ec380023007c cgij %r3,0,8,000003ffe04f2bfc
000003ffe04f2bbc: e30030080004 lg %r0,8(%r3)
000003ffe04f2bc2: ec08001d007c cgij %r0,0,8,000003ffe04f2bfc
Call Trace:
[<000003ffe04f2baa>] __fput+0x5a/0x2e0
([<000003ffe047d38a>] kmem_cache_free+0x40a/0x4a0)
[<000003ffe0199408>] task_work_run+0x88/0xd0
[<000003ffe0174d1a>] do_exit+0x18a/0x4d0
[<000003ffe0175220>] do_group_exit+0x40/0xc0
[<000003ffe018525a>] get_signal+0x80a/0x840
[<000003ffe011e35c>] arch_do_signal_or_restart+0x6c/0x2f0
[<000003ffe0228fc2>] exit_to_user_mode_loop+0xd2/0x190
[<000003ffe0f52154>] __do_syscall+0x324/0x340
[<000003ffe0f5e9fe>] system_call+0x6e/0x90
Last Breaking-Event-Address:
[<000003ffe04f2eac>] ____fput+0xc/0x20
---[ end trace 0000000000000000 ]---
I could bisect this to
commit 73612a36da1a ("Merge branch 'vfs-6.19.fd_prepare' into vfs.all")
which also resolves a merge conflict in ipc/mqueue.c. Looks like the conflict
resolution might not be correct?
next prev parent reply other threads:[~2025-11-28 13:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 5:29 linux-next: Tree for Nov 28 Stephen Rothwell
2025-11-28 13:11 ` Heiko Carstens [this message]
2025-11-28 15:52 ` [linux-next: vfs - regression] - merge error? Christian Brauner
2025-11-30 3:00 ` linux-next: Tree for Nov 28 (drivers/pci/controller/dwc/pcie-nxp-s32g.o) Randy Dunlap
2025-12-01 17:23 ` Bjorn Helgaas
2025-12-02 4:24 ` Manivannan Sadhasivam
2025-12-02 8:54 ` Vincent Guittot
2025-12-02 9:53 ` Manivannan Sadhasivam
2025-12-02 10:03 ` Vincent Guittot
2025-12-02 10:12 ` Manivannan Sadhasivam
2025-12-02 10:24 ` Vincent Guittot
2025-12-02 22:37 ` Randy Dunlap
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=20251128131144.33307A73-hca@linux.ibm.com \
--to=hca@linux.ibm.com \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
/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