From: Al Viro <viro@zeniv.linux.org.uk>
To: Venkat Rao Bagalkote <venkat88@linux.ibm.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-fsdevel@vger.kernel.org, riteshh@linux.ibm.com
Subject: Re: [linux-next-20250620] Fails to boot to IBM Power Server
Date: Mon, 23 Jun 2025 16:02:53 +0100 [thread overview]
Message-ID: <20250623150253.GC1880847@ZenIV> (raw)
In-Reply-To: <72342657-f579-4c4a-bcda-534e28c40304@linux.ibm.com>
On Mon, Jun 23, 2025 at 08:22:28PM +0530, Venkat Rao Bagalkote wrote:
>
> On 23/06/25 7:26 pm, Al Viro wrote:
> > On Mon, Jun 23, 2025 at 07:20:03PM +0530, Venkat Rao Bagalkote wrote:
> >
> > [NULL pointer dereference somewhere in collect_paths()]
> >
> > Could you put objdump -d of the function in question somewhere?
> > Or just fs/namespace.o from your build...
> >
>
> Attached is the namespace.o file.
Huh...
That looks like NULL first argument (path), which blows up on
struct mount *root = real_mount(path->mnt);
just prior to grabbing namespace_sem...
*blinks*
<obscenities>
Could you check if the delta below fixes it?
diff --git a/kernel/audit_tree.c b/kernel/audit_tree.c
index 68e042ae93c7..b0eae2a3c895 100644
--- a/kernel/audit_tree.c
+++ b/kernel/audit_tree.c
@@ -832,7 +832,7 @@ int audit_add_tree_rule(struct audit_krule *rule)
err = kern_path(tree->pathname, 0, &path);
if (err)
goto Err;
- paths = collect_paths(paths, array, 16);
+ paths = collect_paths(&path, array, 16);
path_put(&path);
if (IS_ERR(paths)) {
err = PTR_ERR(paths);
next prev parent reply other threads:[~2025-06-23 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:50 [linux-next-20250620] Fails to boot to IBM Power Server Venkat Rao Bagalkote
2025-06-23 13:56 ` Al Viro
2025-06-23 14:52 ` Venkat Rao Bagalkote
2025-06-23 15:02 ` Al Viro [this message]
2025-06-23 16:49 ` Venkat Rao Bagalkote
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=20250623150253.GC1880847@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=riteshh@linux.ibm.com \
--cc=sfr@canb.auug.org.au \
--cc=venkat88@linux.ibm.com \
/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).