From: Andreas Schwab <schwab@linux-m68k.org>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: linux-riscv@lists.infradead.org,
Javier Jardon <javier.jardon@codethink.co.uk>,
Terry Hu <kejia.hu@codethink.co.uk>,
syzbot+e74b94fe601ab9552d69@syzkaller.appspotmail.com,
Arnd Bergman <arnd@arndb.de>,
dvyukov@google.com, paul.walmsley@sifive.com,
palmer@dabbelt.com, alex@ghiti.fr,
linux-kernel@lists.codethink.co.uk, hch@infradead.org
Subject: Re: [PATCH] riscv: evaluate put_user() argument before enabling user access
Date: Mon, 22 Mar 2021 14:12:39 +0100 [thread overview]
Message-ID: <87o8fbmiwo.fsf@igel.home> (raw)
In-Reply-To: <20210322120935.391973-1-ben.dooks@codethink.co.uk> (Ben Dooks's message of "Mon, 22 Mar 2021 12:09:35 +0000")
On Mär 22 2021, Ben Dooks wrote:
> + * to the result of dereferencing @ptr. The @x is copied inside the macro
The value of @x
> + * to avoid code re-ordering where @x gets evaulated within the block that
> + * enables user-space access (thus possibly bypassing some of the protection
> + * this feautre provides).
feature
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2021-03-22 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:09 [PATCH] riscv: evaluate put_user() argument before enabling user access Ben Dooks
2021-03-22 13:12 ` Andreas Schwab [this message]
2021-03-22 16:53 ` Ben Dooks
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=87o8fbmiwo.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=alex@ghiti.fr \
--cc=arnd@arndb.de \
--cc=ben.dooks@codethink.co.uk \
--cc=dvyukov@google.com \
--cc=hch@infradead.org \
--cc=javier.jardon@codethink.co.uk \
--cc=kejia.hu@codethink.co.uk \
--cc=linux-kernel@lists.codethink.co.uk \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=syzbot+e74b94fe601ab9552d69@syzkaller.appspotmail.com \
/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