Re: vvar, gup && coredump
From: Oleg Nesterov
Date: Thu Mar 12 2015 - 13:41:03 EST
On 03/12, Andy Lutomirski wrote:
> On Thu, Mar 12, 2015 at 9:54 AM, Oleg Nesterov <oleg@xxxxxxxxxx> wrote:
> > On 03/12, Andy Lutomirski wrote:
> > As for 32-bit applications. Yes, this can't work because 32-bit simply
> > can't access this "high" memory. But you know, it would be very nice to
> > have the fixmap-like "global" area in init_mm which is also visible to
> > compat applications. If we had it, uprobes could work without xol vma's.
> It could work for 32-bit native, but not for 32-bit compat.
Yes, yes, I meant 32-bit compat apps. Once again, it would be nice if we
had the "low" fixmaps in init_mm. But unlikely this is possible...
> On a related note, I'm hoping to rework the mm part pretty heavily:
OK... not that I really understand this email.
Well. Speaking of vdso. I understand that unlikely we can do this, but
for uprobes it would be nice to have a anon-inode file behind this mapping,
so that vma_interval_tree_foreach() could work, etc. OK, this is completely
off-topic, please forget.
And I noticed that I didn't read your previous email carefully enough...
> That sounds reasonable to me. I'll write the patch later today.
Sure, please send a patch if you want to do this.
> gdb will still need changes, though, right?
This is up to gdb developers. To me, it should simply skip this
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/