From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alejandro Colomar <alx+linux-hardening@kernel.org>
Cc: Shihuang Liu <shlomojune6@gmail.com>,
linux-input@vger.kernel.org, linux-hardening@vger.kernel.org,
Marcus Folkesson <marcus.folkesson@gmail.com>,
Ville Syrjala <syrjala@sci.fi>,
Henk Vergonet <Henk.Vergonet@gmail.com>,
Henrik Rydberg <rydberg@bitmath.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/6] Input: joystick - use usb_make_subpath()
Date: Wed, 21 Oct 2026 10:00:26 -0700 [thread overview]
Message-ID: <atjvKMOXQY_psYcF@google.com> (raw)
In-Reply-To: <ati7yINv0_Z3yPMg@debian>
On Wed, Oct 21, 2026 at 03:21:28PM +0200, Alejandro Colomar wrote:
> Hi Shihuang,
>
> > Date: 2026-10-21 20:31:42+0800
> > From: Shihuang Liu <shlomojune6@gmail.com>
> >
> > The pxrc and xpad drivers build their input device physical paths
> > by appending "/input0" with strlcat() after usb_make_path().
> >
> > In preparation for removing the deprecated strlcat() API [1],
> > replace each pair of calls with usb_make_subpath(). The helper
> > formats the USB path and the "input0" subpath in one call,
> > avoiding a separate buffer scan and append operation.
> >
> > Link: https://github.com/KSPP/linux/issues/370 [1]
> > Signed-off-by: Shihuang Liu <shlomojune6@gmail.com>
> > ---
> > drivers/input/joystick/pxrc.c | 3 +--
> > drivers/input/joystick/xpad.c | 3 +--
> > 2 files changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/input/joystick/pxrc.c b/drivers/input/joystick/pxrc.c
> > index 52d9eab667b7a..1a11e73d7cd04 100644
> > --- a/drivers/input/joystick/pxrc.c
> > +++ b/drivers/input/joystick/pxrc.c
> > @@ -169,8 +169,7 @@ static int pxrc_probe(struct usb_interface *intf,
> >
> > pxrc->input->name = "PXRC Flight Controller Adapter";
> >
> > - usb_make_path(udev, pxrc->phys, sizeof(pxrc->phys));
> > - strlcat(pxrc->phys, "/input0", sizeof(pxrc->phys));
> > + usb_make_subpath(udev, pxrc->phys, sizeof(pxrc->phys), "input0");
>
> To be honest, I think the composed approach is more readable. You don't
> need to learn a new _subpath function with all the details it has.
>
> Everyone knows what a str*cat() (or str*cpy, FWIW) function does.
>
> I'd rather improve this by adding strscat(). The reason for removing
> strlcat(3) is that it is vulnerable to DoS, and that it is inefficient,
> but it is good at producing readable code, and a replacement should not
> degrade that.
Well, there is absolutely no performance concerns in this code, so
another option is to simply leave it as is. I see no benefit here from
using yet another variant of str*cat().
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-10-21 17:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 12:31 [PATCH v2 0/6] USB: add usb_make_subpath() to replace strlcat() in input drivers Shihuang Liu
2026-10-21 12:31 ` [PATCH v2 1/6] USB: add usb_make_subpath() for formatted device subpaths Shihuang Liu
2026-10-21 13:17 ` Alejandro Colomar
2026-10-22 7:08 ` Shihuang Liu
2026-10-22 9:59 ` Alejandro Colomar
2026-10-21 15:20 ` Greg KH
2026-10-22 6:49 ` Shihuang Liu
2026-10-21 12:31 ` [PATCH v2 2/6] Input: joystick - use usb_make_subpath() Shihuang Liu
2026-10-21 13:21 ` Alejandro Colomar
2026-10-21 17:00 ` Dmitry Torokhov [this message]
2026-10-21 17:20 ` Alejandro Colomar
2026-10-22 7:36 ` Shihuang Liu
2026-10-22 10:03 ` Alejandro Colomar
2026-10-21 12:31 ` [PATCH v2 3/6] Input: misc " Shihuang Liu
2026-10-21 12:31 ` [PATCH v2 4/6] Input: mouse " Shihuang Liu
2026-10-21 12:31 ` [PATCH v2 5/6] Input: tablet " Shihuang Liu
2026-10-21 12:31 ` [PATCH v2 6/6] Input: touchscreen " Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 0/6] USB: add usb_make_subpath() to replace strlcat() in input drivers Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 1/6] USB: add usb_make_subpath() for formatted device subpaths Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 2/6] Input: joystick - use usb_make_subpath() Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 3/6] Input: misc " Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 4/6] Input: mouse " Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 5/6] Input: tablet " Shihuang Liu
2026-10-22 7:09 ` [PATCH v2 RESEND 6/6] Input: touchscreen " Shihuang Liu
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=atjvKMOXQY_psYcF@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=Henk.Vergonet@gmail.com \
--cc=alx+linux-hardening@kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcus.folkesson@gmail.com \
--cc=rydberg@bitmath.org \
--cc=shlomojune6@gmail.com \
--cc=syrjala@sci.fi \
/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®