From: Jeffin Philip <jeffinphilip14@gmail.com>
To: joshua.crofts1@gmail.com
Cc: a.hindborg@kernel.org, leitao@debian.org,
linux-kernel@vger.kernel.org,
syzbot+35790eb7861f8fc57382@syzkaller.appspotmail.com,
Jeffin Philip <jeffinphilip14@gmail.com>
Subject: Re: [PATCH] configfs: fix refcount warning in configfs_get_config_item()
Date: Wed, 29 Jul 2026 15:21:25 +0530 [thread overview]
Message-ID: <20260729095125.96899-1-jeffinphilip14@gmail.com> (raw)
In-Reply-To: <20260729110018.00005e66@gmail.com>
On Wed, 29 Jul 2026 09:00 +0000
Joshua Crofts <joshua.crofts1@gmail.com> wrote:
>On Wed, 29 Jul 2026 08:55:05 +0000
>Joshua Crofts <joshua.crofts1@gmail.com> wrote:
>
>> syzbot reported a "refcount_t: addition on 0; use-after-free" warning
>> in configfs_get_config_item().
>>
>> This occurs when configfs_get_config_item() races with a concurrent
>> teardown (e.g. rmdir). When the target config_item's refcount drops to
>> 0, configfs_get_config_item() calls config_item_get(), which
>> unconditionally increments the refcount via kref_get(), triggering the
>> refcount warning.
>>
>> Fix this by using config_item_get_unless_zero(), which safely returns
>> NULL if the refcount is already 0.
>> Reported-by: syzbot+35790eb7861f8fc57382@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=35790eb7861f8fc57382
>> Signed-off-by: Joshua Crofts <joshua.crofts1@gmail.com>
>> ---
>> fs/configfs/configfs_internal.h | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/fs/configfs/configfs_internal.h b/fs/configfs/configfs_internal.h
>> index acdeea8e2..5448af3a8 100644
>> --- a/fs/configfs/configfs_internal.h
>> +++ b/fs/configfs/configfs_internal.h
>> @@ -124,7 +124,7 @@ static inline struct config_item *configfs_get_config_item(struct dentry *dentry
>> spin_lock(&dentry->d_lock);
>> if (!d_unhashed(dentry)) {
>> struct configfs_dirent * sd = dentry->d_fsdata;
>> - item = config_item_get(sd->s_element);
>> + item = config_item_get_unless_zero(sd->s_element);
>> }
>> spin_unlock(&dentry->d_lock);
I tested this solution first on syzbot and well, it errored out. But on testing it on a local
build, it seems to trigger a different warning in configfs_get() regarding atomic count. Could you please
look into it?
Thanks,
Jeffin.
next prev parent reply other threads:[~2026-07-29 9:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 8:55 Joshua Crofts
2026-07-29 9:00 ` Joshua Crofts
2026-07-29 9:51 ` Jeffin Philip [this message]
2026-07-29 13:50 ` Joshua Crofts
2026-07-29 10:06 ` Breno Leitao
2026-07-29 13:31 ` Joshua Crofts
2026-07-29 15:05 ` Jeffin Philip
2026-07-30 7:30 ` Joshua Crofts
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=20260729095125.96899-1-jeffinphilip14@gmail.com \
--to=jeffinphilip14@gmail.com \
--cc=a.hindborg@kernel.org \
--cc=joshua.crofts1@gmail.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzbot+35790eb7861f8fc57382@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
Powered by JetHome