Re: [PATCH v7 03/14] x86/cet/ibt: Add IBT legacy code bitmap setup function
From: Yu-cheng Yu
Date: Fri Jun 14 2019 - 17:47:15 EST
On Fri, 2019-06-14 at 13:57 -0700, Dave Hansen wrote:
> On 6/14/19 10:13 AM, Yu-cheng Yu wrote:
> > On Fri, 2019-06-14 at 09:13 -0700, Dave Hansen wrote:
> > > On 6/14/19 8:25 AM, Yu-cheng Yu wrote:
> > > > The bitmap is very big.
> > >
> > > Really? It's actually, what, 8*4096=32k, so 1/32,768th of the size of
> > > the libraries legacy libraries you load? Do our crash dumps really not
> > > know how to represent or deal with sparse mappings?
> > Ok, even the core dump is not physically big, its size still looks odd,
> > right?
> Hell if I know.
> Could you please go try this in practice so that we're designing this
> thing fixing real actual problems instead of phantoms that we're
> > Could this also affect how much time for GDB to load it.
> I don't know. Can you go find out for sure, please?
> > I have a related question:
> > Do we allow the application to read the bitmap, or any fault from the
> > application on bitmap pages?
> We have to allow apps to read it. Otherwise they can't execute
What I meant was, if an app executes some legacy code that results in bitmap
lookup, but the bitmap page is not yet populated, and if we then populate that
page with all-zero, a #CP should follow. So do we even populate that zero page
I think we should; a #CP is more obvious to the user at least.
> We don't have to allow them to (popuating) fault on it. But, if we
> don't, we need some kind of kernel interface to avoid the faults.
The plan is:
* Move STACK_TOP (and vdso) down to give space to the bitmap.
* Reserve the bitmap space from (mm->start_stack + PAGE_SIZE) to cover a code
size of TASK_SIZE_LOW, which is (TASK_SIZE_LOW / PAGE_SIZE / 8).
* Mmap the space only when the app issues the first mark-legacy prctl. This
avoids the core-dump issue for most apps and the accounting problem that
MAP_NORESERVE probably won't solve completely.
* The bitmap is read-only. The kernel sets the bitmap with
get_user_pages_fast(FOLL_WRITE) and user_access_begin()/user_addess_end().
I will send out a RFC patch.