On Thu, May 28, 2020 at 05:34:13PM +0100, Catalin Marinas wrote:
> On Thu, May 28, 2020 at 12:05:09PM +0100, Szabolcs Nagy wrote:
> > The 05/28/2020 10:14, Catalin Marinas wrote:
> > > On Wed, May 27, 2020 at 11:57:39AM -0700, Peter Collingbourne wrote:
[...]
Just jumping in on this point:
> > > > Should the userspace stack always be mapped as if with PROT_MTE if the
> > > > hardware supports it? Such a change would be invisible to non-MTE
> > > > aware userspace since it would already need to opt in to tag checking
> > > > via prctl. This would let userspace avoid a complex stack
> > > > initialization sequence when running with stack tagging enabled on the
> > > > main thread.
> > >
> > > I don't think the stack initialisation is that difficult. On program
> > > startup (can be the dynamic loader). Something like (untested):
> > >
> > > register unsigned long stack asm ("sp");
> > > unsigned long page_sz = sysconf(_SC_PAGESIZE);
> > >
> > > mprotect((void *)(stack & ~(page_sz - 1)), page_sz,
> > > PROT_READ | PROT_WRITE | PROT_MTE | PROT_GROWSDOWN);
> > >
> > > (the essential part it PROT_GROWSDOWN so that you don't have to specify
> > > a stack lower limit)
> >
> > does this work even if the currently mapped stack is more than page_sz?
> > determining the mapped main stack area is i think non-trivial to do in
> > userspace (requires parsing /proc/self/maps or similar).
>
> Because of PROT_GROWSDOWN, the kernel adjusts the start of the range
> down automatically. It is potentially problematic if the top of the
> stack is more than a page away and you want the whole stack coloured. I
> haven't run a test but my reading of the kernel code is that the stack
> vma would be split in this scenario, so the range beyond sp+page_sz
> won't have PROT_MTE set.
>
> My assumption is that if you do this during program start, the stack is
> smaller than a page. Alternatively, could we use argv or envp to
> determine the top of the user stack (the bottom is taken care of by the
> kernel)?
I don't think you can easily know when the stack ends, but perhaps it
doesn't matter.
>From memory, the initial stack looks like:
argv/env strings
AT_NULL
auxv
NULL
env
NULL
argv
argc <--- sp
If we don't care about tagging the strings correctly, we could step to
the end of auxv and tag down from there.
If we do care about tagging the strings, there's probably no good way
to find the end of the string area, other than looking up sp in
/proc/self/maps. I'm not sure we should trust all past and future
kernels to spit out the strings in a predictable order.
Assuming that the last env string has the highest address does not
sounds like a good idea to me. It would be easy for someone to break
that assumption later without realising.
If we're concerned about this, and reading /proc/self/auxv is deemed
unacceptable (likely: some binaries need to work before /proc is
mounted) then we could perhaps add a new auxv entry to report the stack
base address to the user startup code.
I don't think it matters if all this is "hard" for userspace: only the
C library / runtime should be doing this. After libc startup, it's
generally too late to do this kind of thing safely.
[...]
Cheers
---Dave
