From: Breno Leitao <leitao@debian.org>
To: pavankumaryalagada@gmail.com
Cc: Andreas Hindborg <a.hindborg@kernel.org>,
Nicholas Bellinger <nab@linux-iscsi.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
syzbot+a9efa71b884a23e74153@syzkaller.appspotmail.com,
stable@vger.kernel.org
Subject: Re: [PATCH] configfs: fix NULL dereference in configfs_depend_item_unlocked()
Date: Mon, 14 Sep 2026 03:05:26 -0700 [thread overview]
Message-ID: <aqfGt6OFIRuqMC6H@gmail.com> (raw)
In-Reply-To: <20260914094426.25595-1-pavankumaryalagada@gmail.com>
On Mon, Sep 14, 2026 at 03:14:26PM +0530, pavankumaryalagada@gmail.com wrote:
> From: Yalagada Pavan Kumar <pavankumaryalagada@gmail.com>
>
> configfs_depend_item_unlocked() can dereference a NULL parent when
> the configfs item is still being created.
>
> The item can be found before it is linked to its parent group,
> so ci_group can still be NULL. Check ci_group before using it
> and return -ENOENT if it is NULL.
The crash itself looks real, but this reads like a fix in the wrong
place. include/linux/configfs.h already documents the opposite
contract for this API:
/*
* These functions can sleep and can alloc with GFP_KERNEL
* NOTE: These should be called only underneath configfs callbacks.
* NOTE: First parameter is a caller's subsystem, not target's.
* WARNING: These cannot be called on newly created item
* (in make_group()/make_item() callback)
*/
int configfs_depend_item_unlocked(struct configfs_subsystem *caller_subsys,
struct config_item *target);
"cannot be called on newly created item" is exactly the case being
patched here.
If configfs is now going to accept a not-yet-linked item and return
-ENOENT for it, shouldn't that comment be updated in the same patch?
And if the contract is meant to stand, shouldn't the caller stop handing
over an unlinked item instead?
> Fixes: 4bb8548df632 ("usb: gadget: f_tcm: add configfs support")
This tag and the diff do not agree. 4bb8548df632 only touches
Documentation/ABI, drivers/usb/gadget/Kconfig and
drivers/usb/gadget/function/f_tcm.c; it does not add or modify anything
under fs/configfs.
--breno
prev parent reply other threads:[~2026-09-14 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 9:44 pavankumaryalagada
2026-09-14 10:05 ` Breno Leitao [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=aqfGt6OFIRuqMC6H@gmail.com \
--to=leitao@debian.org \
--cc=a.hindborg@kernel.org \
--cc=andrzej.p@samsung.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nab@linux-iscsi.org \
--cc=pavankumaryalagada@gmail.com \
--cc=skhan@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+a9efa71b884a23e74153@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®