From: Dominique Martinet <asmadeus@codewreck.org>
To: Jackie Liu <liu.yun@linux.dev>
Cc: ericvh@kernel.org, linux_oss@crudebyte.com, v9fs@lists.linux.dev
Subject: Re: [PATCH] net/9p/usbg: require an exact match for device tags
Date: Sun, 13 Sep 2026 17:35:25 +0900 [thread overview]
Message-ID: <aqZgTW38erDV7AZs@codewreck.org> (raw)
In-Reply-To: <20260719040346.88295-1-liu.yun@linux.dev>
Jackie Liu wrote on Sun, Jul 19, 2026 at 12:03:46PM +0800:
> From: Jackie Liu <liuyun01@kylinos.cn>
>
> p9_usbg_create() compares only strlen(devname) bytes while looking up the
> configfs instance named by the mount source. A source that is a prefix of
> an instance name therefore selects that instance. For example, source
> "foo" binds the "foobar" channel instead of failing with -ENOENT.
>
> The configfs layer passes the instance name to usb9pfs_set_inst_tag(), and
> the transport already uses full string comparisons to keep these names
> unique. Use an exact match for mount lookup too.
>
> Fixes: a3be076dc174 ("net/9p/usbg: Add new usb gadget function transport")
> Cc: stable@vger.kernel.org
> Signed-off-by: Jackie Liu <liuyun01@kylinos.cn>
Thank you, there was another identical patch earlier that I hadn't
picked up yet so I'm taking their patch instead, but I've added you as
co-developed-by to the commit instead.
It should get in 7.4
https://lore.kernel.org/r/20260607121907.12588-1-zhaoyz24@mails.tsinghua.edu.cn
https://github.com/martinetd/linux/commit/9ee83ef8d24f11feb55fd0d222c0ec19f09dbd3f
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2026-09-13 8:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 4:03 [PATCH] net/9p/usbg: require an exact match for device tags Jackie Liu
2026-09-13 8:35 ` Dominique Martinet [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=aqZgTW38erDV7AZs@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=liu.yun@linux.dev \
--cc=v9fs@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.