From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] syscalls: Restore address limit after a syscall
Date: Thu, 9 Mar 2017 15:21:45 +0000 [thread overview]
Message-ID: <20170309152144.GA11966@leverpostej> (raw)
In-Reply-To: <20170309134456.GI21222@n2100.armlinux.org.uk>
On Thu, Mar 09, 2017 at 01:44:56PM +0000, Russell King - ARM Linux wrote:
> On Thu, Mar 09, 2017 at 12:09:55PM +0000, Mark Rutland wrote:
> > On Wed, Mar 08, 2017 at 05:24:53PM -0800, Thomas Garnier wrote:
> > It would be simpler to wrap the call entirely, e.g. have:
> >
> > #ifdef CONFIG_WHATEVER
> > static inline void verify_pre_usermode_state(void)
> > {
> > if (segment_eq(get_fs(), USER_DS))
> > __verify_pre_usermode_state();
> > }
> > #else
> > static inline void verify_pre_usermode_state(void) { }
> > #endif
>
> That's utterly pointless - you've missed a detail.
>
> > > @@ -199,7 +215,10 @@ extern struct trace_event_functions exit_syscall_print_funcs;
> > > asmlinkage long SyS##name(__MAP(x,__SC_LONG,__VA_ARGS__)); \
> > > asmlinkage long SyS##name(__MAP(x,__SC_LONG,__VA_ARGS__)) \
> > > { \
> > > + bool user_caller = has_user_ds(); \
> > > long ret = SYSC##name(__MAP(x,__SC_CAST,__VA_ARGS__)); \
> > > + if (user_caller) \
> > > + verify_pre_usermode_state(); \
> >
> > ... then we can unconditionally use verify_pre_usermode_state() here ...
>
> Look at this closely. has_user_ds() is called _before_ the syscall code
> is invoked. It's checking what conditions the syscall was entered from.
> If the syscall was entered with the user segment selected, then we run
> a check on the system state _after_ the syscall code has returned.
Indeed; I clearly did not consider this correctly.
Sorry for the noise.
Thanks,
Mark.
next prev parent reply other threads:[~2017-03-09 15:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170309012456.5631-1-thgarnie@google.com>
2017-03-09 8:42 ` [PATCH v2 1/4] syscalls: Restore address limit after a syscall Borislav Petkov
2017-03-09 15:48 ` Thomas Garnier
2017-03-09 12:09 ` Mark Rutland
2017-03-09 13:44 ` Russell King - ARM Linux
2017-03-09 15:21 ` Mark Rutland [this message]
2017-03-09 15:54 ` Thomas Garnier
2017-03-09 15:52 ` Thomas Garnier
[not found] ` <20170309012456.5631-4-thgarnie@google.com>
2017-03-09 12:23 ` [PATCH v2 4/4] arm64/syscalls: Specific usage of verify_pre_usermode_state Mark Rutland
2017-03-09 15:56 ` Thomas Garnier
2017-03-09 16:05 ` Mark Rutland
2017-03-09 16:19 ` Thomas Garnier
2017-03-09 16:26 ` Russell King - ARM Linux
2017-03-09 16:35 ` Thomas Garnier
2017-03-09 17:05 ` Russell King - ARM Linux
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=20170309152144.GA11966@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).