kernel-hardening.lists.openwall.com archive mirror
 help / color / mirror / Atom feed
From: Markus Elfring <Markus.Elfring@web.de>
To: Alexander Popov <alex.popov@linux.com>, cocci@systeme.lip6.fr
Cc: kernel-hardening@lists.openwall.com, linux-block@vger.kernel.org,
	linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>,
	Denis Efremov <efremov@linux.com>,
	Gilles Muller <Gilles.Muller@lip6.fr>,
	Jann Horn <jannh@google.com>, Jens Axboe <axboe@kernel.dk>,
	Jiri Kosina <jikos@kernel.org>,
	Julia Lawall <julia.lawall@lip6.fr>,
	Michal Marek <michal.lkml@markovi.net>,
	Mukesh Ojha <mojha@codeaurora.org>,
	Nicolas Palix <nicolas.palix@imag.fr>
Subject: Re: floppy: fix usercopy direction
Date: Tue, 13 Aug 2019 09:50:54 +0200	[thread overview]
Message-ID: <6168f58a-891c-1527-93ec-4d3778a59aa2@web.de> (raw)
In-Reply-To: <9ced7a06-5048-ad1a-3428-c8f943f7469c@linux.com>

> @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:

Can this check be specified as a constraint for a metavariable
in the initial SmPL rule?
Would you like to move it to an other place?

Regards,
Markus

      parent reply	other threads:[~2019-08-13 17:10 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       ` [PATCH] " Julia Lawall
2019-08-13  7:50   ` Markus Elfring [this message]

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=6168f58a-891c-1527-93ec-4d3778a59aa2@web.de \
    --to=markus.elfring@web.de \
    --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=julia.lawall@lip6.fr \
    --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).