From: Shuah Khan <skhan@linuxfoundation.org>
To: 艾超 <aichao@kylinos.cn>, gregkh <gregkh@linuxfoundation.org>
Cc: b-liu <b-liu@ti.com>, johan <johan@kernel.org>,
badhri <badhri@google.com>,
"heikki.krogerus" <heikki.krogerus@linux.intel.com>,
"valentina.manea.m" <valentina.manea.m@gmail.com>,
shuah <shuah@kernel.org>, i <i@zenithal.me>,
tiwai <tiwai@suse.de>, kees <kees@kernel.org>,
"christophe.jaillet" <christophe.jaillet@wanadoo.fr>,
"prashanth.k" <prashanth.k@oss.qualcomm.com>,
khtsai <khtsai@google.com>, tglx <tglx@kernel.org>,
mingo <mingo@kernel.org>, linux-usb <linux-usb@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Dan Carpenter <dan.carpenter@linaro.org>
Subject: Re: [PATCH 6/6] usbip: vhci_sysfs: Use safer strscpy() instead of strcpy()
Date: Thu, 26 Mar 2026 12:19:24 -0600 [thread overview]
Message-ID: <b3a6543a-9375-4e52-960e-3f8dc4be5526@linuxfoundation.org> (raw)
In-Reply-To: <7990xi1aonqb-79968wxve9t0@nsmail8.2--kylin--1>
On 3/25/26 04:57, 艾超 wrote:
> Dear Shuah:
>
> Test Report for [usbip: vhci_sysfs: Use safer strscpy() instead of strcpy()]
> Environment:
> Kernel Version: v6.12.76+ (with patch applied)
> Hardware/QEMU: Thinkpad E15
> Conclusion:
> The longth of the name is MAX_STATUS_NAME+1 = 17, used the strcpy copy "status-abcdefghijklmnopqrstuvwxyz1234567890" in name and used strscpy copy "status-abcdefghi" in name.
> Tested-by: Aichao@kylinos.cn
>
Thank you for the report.
Acked-by: Shuah Khan <skhan@linuxfoundation.org>
Greg, Please pick this patch up.
thanks,
-- Shuah
next parent reply other threads:[~2026-03-26 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7990xi1aonqb-79968wxve9t0@nsmail8.2--kylin--1>
2026-03-26 18:19 ` Shuah Khan [this message]
2026-03-10 9:44 [PATCH 0/6] Use safer strscpy() instead of strcpy() Ai Chao
2026-03-10 9:44 ` [PATCH 6/6] usbip: vhci_sysfs: " Ai Chao
2026-03-10 22:10 ` Shuah Khan
2026-03-11 7:22 ` Dan Carpenter
2026-03-24 21:34 ` Shuah Khan
2026-03-25 11:09 ` Dan Carpenter
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=b3a6543a-9375-4e52-960e-3f8dc4be5526@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=aichao@kylinos.cn \
--cc=b-liu@ti.com \
--cc=badhri@google.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=dan.carpenter@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=i@zenithal.me \
--cc=johan@kernel.org \
--cc=kees@kernel.org \
--cc=khtsai@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=prashanth.k@oss.qualcomm.com \
--cc=shuah@kernel.org \
--cc=tglx@kernel.org \
--cc=tiwai@suse.de \
--cc=valentina.manea.m@gmail.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