From: Al Viro <viro@zeniv.linux.org.uk>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, linux-fsdevel@vger.kernel.org
Subject: Re: [viro-vfs:more.configfs] [configfs] 2bbdcd7eab: BUG:kernel_NULL_pointer_dereference,address
Date: Fri, 5 Jun 2026 19:39:27 +0100 [thread overview]
Message-ID: <20260605183927.GA2018146@ZenIV> (raw)
In-Reply-To: <20260605071112.GD2636677@ZenIV>
On Fri, Jun 05, 2026 at 08:11:12AM +0100, Al Viro wrote:
> On Fri, Jun 05, 2026 at 01:52:28PM +0800, kernel test robot wrote:
> >
> >
> >
> > Hello,
> >
> > kernel test robot noticed "BUG:kernel_NULL_pointer_dereference,address" on:
> >
> > commit: 2bbdcd7eabfcd3a5bd2614ab75ece19323d5f4c2 ("configfs: attach the subtree only when it's completely built")
> > https://git.kernel.org/cgit/linux/kernel/git/viro/vfs.git more.configfs
> >
> > in testcase: boot
> >
> > config: i386-randconfig-013-20260604
> > compiler: gcc-14
> > test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 32G
> >
> > (please refer to attached dmesg/kmsg for entire log/backtrace)
>
> D'oh... Minimal incremental to deal with that would probably be something like
> the delta below, but it's probably better to have configfs_add_subtree() return
> the resulting dentry instead...
... as in updated (and force-pushed) branch.
prev parent reply other threads:[~2026-06-05 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 5:52 [viro-vfs:more.configfs] [configfs] 2bbdcd7eab: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2026-06-05 7:11 ` Al Viro
2026-06-05 18:39 ` Al Viro [this message]
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=20260605183927.GA2018146@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.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