From: Julia Lawall <julia.lawall@lip6.fr>
To: Alexander Popov <alex.popov@linux.com>
Cc: Julia Lawall <julia.lawall@lip6.fr>, Jann Horn <jannh@google.com>,
Jens Axboe <axboe@kernel.dk>, Jiri Kosina <jikos@kernel.org>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Al Viro <viro@zeniv.linux.org.uk>,
Mukesh Ojha <mojha@codeaurora.org>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>,
Denis Efremov <efremov@linux.com>,
Gilles Muller <Gilles.Muller@lip6.fr>,
Nicolas Palix <nicolas.palix@imag.fr>,
Michal Marek <michal.lkml@markovi.net>,
cocci@systeme.lip6.fr
Subject: Re: [PATCH] floppy: fix usercopy direction
Date: Mon, 12 Aug 2019 12:25:45 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908121210570.3718@hadrien> (raw)
In-Reply-To: <3ee24295-6d63-6da9-774f-f1a599418685@linux.com>
On Fri, 9 Aug 2019, Alexander Popov wrote:
> On 09.08.2019 16:56, Julia Lawall wrote:
> > On Fri, 9 Aug 2019, Alexander Popov wrote:
> >> 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 also wrote a coccinelle rule for detecting similar bugs (adding coccinelle
> >> experts to CC).
> >>
> >>
> >> virtual report
> >>
> >> @cfu@
> >
> > You can replace the above line with @cfu exists@. You want to find the
> > existence of such a call, not ensure that the call occurs on every
> > control-flow path, which is the default.
>
> Thanks Julia, I see `exists` allows to drop `<+ +>`, right?
Exists is more efficient when it is possible. It just finds the existence
of a path that has the property rather than collecting information about
all paths. It is related to <+... ...+> because for that there has to
exist at least one match. You could probably do something like
... when any
copy_from_user
... when any
Then with exists you will consider each call one at a time.
>
> > Do you want this rule to go into the kernel?
>
> It turned out that sparse already can find these bugs.
If sparse is already doing this, then perhaps that's sufficient. Someone
just has to be running it :)
julia
> Is this rule useful anyway? If so, I can prepare a patch.
>
> >> identifier f;
> >> type t;
> >> identifier v;
> >> position decl_p;
> >> position copy_p;
> >> @@
> >>
> >> f(..., t v@decl_p, ...)
> >> {
> >> <+...
> >> copy_from_user@copy_p(v, ...)
> >> ...+>
> >> }
> >>
> >> @script:python@
> >> f << cfu.f;
> >> t << cfu.t;
> >> v << cfu.v;
> >> decl_p << cfu.decl_p;
> >> copy_p << cfu.copy_p;
> >> @@
> >>
> >> if '__user' in t:
> >> msg0 = "function \"" + f + "\" has arg \"" + v + "\" of type \"" + t + "\""
> >> coccilib.report.print_report(decl_p[0], msg0)
> >> msg1 = "copy_from_user uses \"" + v + "\" as the destination. What a shame!\n"
> >> coccilib.report.print_report(copy_p[0], msg1)
> >>
> >>
> >> The rule output:
> >>
> >> ./drivers/block/floppy.c:3756:49-52: function "compat_getdrvprm" has arg "arg"
> >> of type "struct compat_floppy_drive_params __user *"
> >> ./drivers/block/floppy.c:3783:5-19: copy_from_user uses "arg" as the
> >> destination. What a shame!
> >>
> >> ./drivers/block/floppy.c:3789:49-52: function "compat_getdrvstat" has arg "arg"
> >> of type "struct compat_floppy_drive_struct __user *"
> >> ./drivers/block/floppy.c:3819:5-19: copy_from_user uses "arg" as the
> >> destination. What a shame!
>
next prev parent reply other threads:[~2019-08-12 10:26 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 ` [PATCH] floppy: fix usercopy direction Alexander Popov
2019-08-09 13:41 ` Jens Axboe
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 ` Markus Elfring
2019-08-12 10:25 ` Julia Lawall [this message]
2019-08-13 7:50 ` 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=alpine.DEB.2.21.1908121210570.3718@hadrien \
--to=julia.lawall@lip6.fr \
--cc=Gilles.Muller@lip6.fr \
--cc=alex.popov@linux.com \
--cc=axboe@kernel.dk \
--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).