From: Jens Axboe <axboe@kernel.dk>
To: alex.popov@linux.com, Jann Horn <jannh@google.com>
Cc: Michal Marek <michal.lkml@markovi.net>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Mukesh Ojha <mojha@codeaurora.org>,
Jiri Kosina <jikos@kernel.org>,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, Denis Efremov <efremov@linux.com>,
linux-block@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
cocci@systeme.lip6.fr
Subject: Re: [Cocci] [PATCH] floppy: fix usercopy direction
Date: Fri, 9 Aug 2019 06:41:28 -0700 [thread overview]
Message-ID: <b324719d-4cb4-89c9-ed00-2e0cd85ee375@kernel.dk> (raw)
In-Reply-To: <9ced7a06-5048-ad1a-3428-c8f943f7469c@linux.com>
On 8/9/19 6:36 AM, Alexander Popov wrote:
> Hello everyone!
>
> On 27.03.2019 1:03, Jann Horn wrote:
>> As sparse points out, these two copy_from_user() should actually be
>> copy_to_user().
>
> I've spent some time on these bugs, but it turned out that they are already public.
>
> I think Jann's patch is lost, it is not applied to the mainline.
> So I add a new floppy maintainer Denis Efremov to CC.
Looks like it got lost indeed, I will just apply this one directly for
5.4.
--
Jens Axboe
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-08-12 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190326220348.61172-1-jannh@google.com>
2019-08-09 13:36 ` [Cocci] [PATCH] floppy: fix usercopy direction Alexander Popov
2019-08-09 13:41 ` Jens Axboe [this message]
2019-08-09 13:43 ` Denis Efremov
2019-08-09 13:56 ` Julia Lawall
2019-08-09 15:05 ` Alexander Popov
2019-08-12 10:00 ` [Cocci] " Markus Elfring
2019-08-12 10:25 ` [Cocci] [PATCH] " Julia Lawall
2019-08-13 7:50 ` [Cocci] " Markus Elfring
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=b324719d-4cb4-89c9-ed00-2e0cd85ee375@kernel.dk \
--to=axboe@kernel.dk \
--cc=alex.popov@linux.com \
--cc=cocci@systeme.lip6.fr \
--cc=efremov@linux.com \
--cc=jannh@google.com \
--cc=jikos@kernel.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=mojha@codeaurora.org \
--cc=nicolas.palix@imag.fr \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).