From: "Danilo Krummrich" <dakr@kernel.org>
To: "Greg KH" <gregkh@linuxfoundation.org>
Cc: "Edward Adam Davis" <eadavis@qq.com>,
<syzbot+b6445765657b5855e869@syzkaller.appspotmail.com>,
<linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rafael@kernel.org>, <syzkaller-bugs@googlegroups.com>
Subject: Re: [PATCH] USB: core: remove the move buf action
Date: Wed, 10 Sep 2025 12:09:38 +0200 [thread overview]
Message-ID: <DCP1E4UJ385D.JEXXJV4PPLJS@kernel.org> (raw)
In-Reply-To: <2025091007-stricken-relock-ef72@gregkh>
On Wed Sep 10, 2025 at 11:00 AM CEST, Greg KH wrote:
> On Wed, Sep 10, 2025 at 03:58:47PM +0800, Edward Adam Davis wrote:
>> The buffer size of sysfs is fixed at PAGE_SIZE, and the page offset
>> of the buf parameter of sysfs_emit_at() must be 0, there is no need
>> to manually manage the buf pointer offset.
>>
>> Fixes: 711d41ab4a0e ("usb: core: Use sysfs_emit_at() when showing dynamic IDs")
>> Reported-by: syzbot+b6445765657b5855e869@syzkaller.appspotmail.com
>> Closes: https://syzkaller.appspot.com/bug?extid=b6445765657b5855e869
>> Tested-by: syzbot+b6445765657b5855e869@syzkaller.appspotmail.com
>> Signed-off-by: Edward Adam Davis <eadavis@qq.com>
>> ---
>> drivers/usb/core/driver.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> While this fix looks correct, your cc: list is very odd as this is a
> linux-usb bug, not a driver core issue, right?
I think Edward derived the Cc: list from the recipients of the syzbot report
in [1].
Not sure how syzbot figures out the relevant recipients to send the report to
though. :)
[1] https://lore.kernel.org/all/68c118e8.a70a0220.3543fc.000e.GAE@google.com/
next prev parent reply other threads:[~2025-09-10 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 6:21 [syzbot] [fs?] WARNING in sysfs_emit_at syzbot
2025-09-10 7:58 ` [PATCH] USB: core: remove the move buf action Edward Adam Davis
2025-09-10 9:00 ` Greg KH
2025-09-10 9:57 ` Edward Adam Davis
2025-09-10 10:09 ` Danilo Krummrich [this message]
2025-09-10 11:00 ` Edward Adam Davis
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=DCP1E4UJ385D.JEXXJV4PPLJS@kernel.org \
--to=dakr@kernel.org \
--cc=eadavis@qq.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzbot+b6445765657b5855e869@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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