From: Michael Straube <straube.linux@gmail.com>
To: Charlie Sands <sandsch@northvilleschools.net>,
gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
paskripkin@gmail.com
Subject: Re: [PATCH V2] Fix unsafe memory access by memcmp
Date: Mon, 4 Apr 2022 10:02:17 +0200 [thread overview]
Message-ID: <bdd168a8-b260-0653-f835-a7814a8fd4c8@gmail.com> (raw)
In-Reply-To: <YkpdVyuQguGzPSNE@sckzor-linux.localdomain>
On 4/4/22 04:52, Charlie Sands wrote:
> This patch fixes sparse warnings about the memcmp function unsafely
> accessing userspace memory without first copying it to kernel space.
>
> Signed-off-by: Charlie Sands <sandsch@northvilleschools.net>
> ---
>
> V2: Fixed checkpatch.pl warning and changed variable name as suggested
> by Greg K. H. and improved error checking on the "copy_from_user" function as
> suggested by Pavel Skripkin.
>
> drivers/staging/r8188eu/os_dep/ioctl_linux.c | 21 ++++++++++++--------
> 1 file changed, 13 insertions(+), 8 deletions(-)
>
Hi Charlie,
thanks for your patch. Looks good to me, but you should include
staging: r8188eu: in the subject line.
"staging: r8188eu: Fix unsafe memory access by memcmp"
thanks,
Michael
next prev parent reply other threads:[~2022-04-04 8:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 2:52 Charlie Sands
2022-04-04 8:02 ` Michael Straube [this message]
2022-04-04 10:50 ` Dan Carpenter
2022-04-04 11:25 ` Fabio M. De Francesco
2022-04-04 12:03 ` Dan Carpenter
2022-04-04 14:29 ` Fabio M. De Francesco
2022-04-04 14:35 ` Dan Carpenter
2022-04-04 14:47 ` Fabio M. De Francesco
2022-04-04 14:36 ` Greg KH
2022-04-04 16:33 ` Pavel Skripkin
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=bdd168a8-b260-0653-f835-a7814a8fd4c8@gmail.com \
--to=straube.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=paskripkin@gmail.com \
--cc=phil@philpotter.co.uk \
--cc=sandsch@northvilleschools.net \
/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®