From: Markus Elfring <Markus.Elfring@web.de>
To: Alexander Popov <alex.popov@linux.com>,
Jann Horn <jannh@google.com>, Julia Lawall <julia.lawall@lip6.fr>,
kernel-janitors@vger.kernel.org, cocci@systeme.lip6.fr
Cc: Jens Axboe <axboe@kernel.dk>, Jiri Kosina <jikos@kernel.org>,
Mukesh Ojha <mojha@codeaurora.org>,
kernel-hardening@lists.openwall.com,
Nicolas Palix <nicolas.palix@imag.fr>,
linux-kernel@vger.kernel.org, Denis Efremov <efremov@linux.com>,
linux-block@vger.kernel.org,
Michal Marek <michal.lkml@markovi.net>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [Cocci] floppy: fix usercopy direction
Date: Mon, 12 Aug 2019 12:00:45 +0200 [thread overview]
Message-ID: <e514a05f-6e9f-1d62-9b38-163e13578bff@web.de> (raw)
In-Reply-To: <3ee24295-6d63-6da9-774f-f1a599418685@linux.com>
> …, I see `exists` allows to drop `<+ +>`, right?
I would interpret the combination of such SmPL specifications in a different way.
> It turned out that sparse already can find these bugs.
This is generally nice, isn't it?
> Is this rule useful anyway?
I hope so.
Can scripts for the semantic patch language help any more?
> If so, I can prepare a patch.
Would you like to take corresponding adjustments into account?
Regards,
Markus
_______________________________________________
Cocci mailing list
Cocci@systeme.lip6.fr
https://systeme.lip6.fr/mailman/listinfo/cocci
next prev parent reply other threads:[~2019-08-12 10:01 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
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 [this message]
2019-08-12 10:25 ` 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=e514a05f-6e9f-1d62-9b38-163e13578bff@web.de \
--to=markus.elfring@web.de \
--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=julia.lawall@lip6.fr \
--cc=kernel-hardening@lists.openwall.com \
--cc=kernel-janitors@vger.kernel.org \
--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).