From: Markus Elfring <Markus.Elfring@web.de>
To: "Ma Ke" <make24@iscas.ac.cn>,
linux-usb@vger.kernel.org,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: r8a66597-udc: validate endpoint index for r8a66597 udc
Date: Sat, 22 Jun 2024 17:30:16 +0200 [thread overview]
Message-ID: <4c28e897-0f44-4927-a4e7-762fce28ae63@web.de> (raw)
In-Reply-To: <20240622142308.1929531-1-make24@iscas.ac.cn>
> We should verify the bound of the array to assure that host
> may not manipulate the index to point past endpoint array.
* Can an imperative wording be more desirable for such a change description?
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/process/submitting-patches.rst?h=v6.10-rc4#n94
* Will any tags (like “Fixes”) become relevant here?
Regards,
Markus
next prev parent reply other threads:[~2024-06-22 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-22 14:23 [PATCH] usb: gadget: r8a66597-udc: validate endpoint index for r8a66597 udc Ma Ke
2024-06-22 15:30 ` Markus Elfring [this message]
2024-06-26 4:32 ` kernel test robot
2024-06-26 5:34 ` kernel test robot
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=4c28e897-0f44-4927-a4e7-762fce28ae63@web.de \
--to=markus.elfring@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=make24@iscas.ac.cn \
--cc=u.kleine-koenig@pengutronix.de \
/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