On Thu, 2 Nov 2017, Linus Torvalds wrote:
> On Thu, Nov 2, 2017 at 11:40 AM, Thomas Gleixner wrote:
> >
> > Hmm. Not sure. IIRC you need to be able to read it to figure out where the
> > entry points are. They are at fixed offsets, but there is some voodoo out
> > there
On Thu, 2 Nov 2017, Linus Torvalds wrote:
> On Thu, Nov 2, 2017 at 11:40 AM, Thomas Gleixner wrote:
> >
> > Hmm. Not sure. IIRC you need to be able to read it to figure out where the
> > entry points are. They are at fixed offsets, but there is some voodoo out
> > there which reads the 'elf' to
On Thu, Nov 2, 2017 at 11:40 AM, Thomas Gleixner wrote:
>
> Hmm. Not sure. IIRC you need to be able to read it to figure out where the
> entry points are. They are at fixed offsets, but there is some voodoo out
> there which reads the 'elf' to get to them.
That would actually
On Thu, Nov 2, 2017 at 11:40 AM, Thomas Gleixner wrote:
>
> Hmm. Not sure. IIRC you need to be able to read it to figure out where the
> entry points are. They are at fixed offsets, but there is some voodoo out
> there which reads the 'elf' to get to them.
That would actually be really painful.
On Thu, 2 Nov 2017, Linus Torvalds wrote:
> On Thu, Nov 2, 2017 at 11:19 AM, Andy Lutomirski wrote:
> >
> > We'd have to force NONE, and Linus won't like it.
>
> Oh, I think it's fine for the kaiser case.
>
> I am not convinced anybody will actually use it, but if you do
On Thu, 2 Nov 2017, Linus Torvalds wrote:
> On Thu, Nov 2, 2017 at 11:19 AM, Andy Lutomirski wrote:
> >
> > We'd have to force NONE, and Linus won't like it.
>
> Oh, I think it's fine for the kaiser case.
>
> I am not convinced anybody will actually use it, but if you do use it,
> I suspect
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> > On Nov 2, 2017, at 5:38 PM, Dave Hansen wrote:
> >
> >> On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
> >> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
> >> CONFIG_KAISER=y and be done with
On Thu, Nov 2, 2017 at 11:19 AM, Andy Lutomirski wrote:
>
> We'd have to force NONE, and Linus won't like it.
Oh, I think it's fine for the kaiser case.
I am not convinced anybody will actually use it, but if you do use it,
I suspect "the legacy vsyscall page no longer
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> > On Nov 2, 2017, at 5:38 PM, Dave Hansen wrote:
> >
> >> On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
> >> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
> >> CONFIG_KAISER=y and be done with it.
> >
> > Just to be
On Thu, Nov 2, 2017 at 11:19 AM, Andy Lutomirski wrote:
>
> We'd have to force NONE, and Linus won't like it.
Oh, I think it's fine for the kaiser case.
I am not convinced anybody will actually use it, but if you do use it,
I suspect "the legacy vsyscall page no longer works" is the least of
> On Nov 2, 2017, at 5:38 PM, Dave Hansen wrote:
>
>> On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
>> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
>> CONFIG_KAISER=y and be done with it.
>
> Just to be clear, are we suggesting to just
> On Nov 2, 2017, at 5:38 PM, Dave Hansen wrote:
>
>> On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
>> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
>> CONFIG_KAISER=y and be done with it.
>
> Just to be clear, are we suggesting to just disable
>
On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
> CONFIG_KAISER=y and be done with it.
Just to be clear, are we suggesting to just disable
LEGACY_VSYSCALL_NATIVE if KAISER=y, and allow LEGACY_VSYSCALL_EMULATE?
Or, do we
On 11/02/2017 04:33 AM, Thomas Gleixner wrote:
> So for the problem at hand, I'd suggest we disable the vsyscall stuff if
> CONFIG_KAISER=y and be done with it.
Just to be clear, are we suggesting to just disable
LEGACY_VSYSCALL_NATIVE if KAISER=y, and allow LEGACY_VSYSCALL_EMULATE?
Or, do we
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> > On Nov 2, 2017, at 12:33 PM, Thomas Gleixner wrote:
> > Fair enough. I enabled function tracing with emulate_vsyscall as the filter
> > on a couple of machines and so far I have no hit at all. Though I found a
> > VM with a real
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> > On Nov 2, 2017, at 12:33 PM, Thomas Gleixner wrote:
> > Fair enough. I enabled function tracing with emulate_vsyscall as the filter
> > on a couple of machines and so far I have no hit at all. Though I found a
> > VM with a real old user space
> On Nov 2, 2017, at 12:33 PM, Thomas Gleixner wrote:
>
>> On Thu, 2 Nov 2017, Andy Lutomirski wrote:
>>> On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
On Wed, 1 Nov 2017, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 2:52 PM, Dave
> On Nov 2, 2017, at 12:33 PM, Thomas Gleixner wrote:
>
>> On Thu, 2 Nov 2017, Andy Lutomirski wrote:
>>> On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
On Wed, 1 Nov 2017, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
> wrote:
>> On 11/01/2017
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
> > On Wed, 1 Nov 2017, Linus Torvalds wrote:
> >> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
> >> wrote:
> >> > On 11/01/2017 02:28 PM, Thomas
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
> > On Wed, 1 Nov 2017, Linus Torvalds wrote:
> >> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
> >> wrote:
> >> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> >> >> On Wed, 1 Nov 2017, Andy
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> On Wed, Nov 1, 2017 at 2:28 PM, Thomas Gleixner wrote:
> > On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> >
> >> On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
> >> > On Tue, 31 Oct 2017, Dave Hansen
On Thu, 2 Nov 2017, Andy Lutomirski wrote:
> On Wed, Nov 1, 2017 at 2:28 PM, Thomas Gleixner wrote:
> > On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> >
> >> On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
> >> > On Tue, 31 Oct 2017, Dave Hansen wrote:
> >> >
> >> >>
> >> >> init_mm is for
On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Linus Torvalds wrote:
>> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
>> wrote:
>> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
>> >> On Wed, 1 Nov 2017, Andy
On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Linus Torvalds wrote:
>> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
>> wrote:
>> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
>> >> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>> >>> The vsyscall page is _PAGE_USER
On Wed, Nov 1, 2017 at 2:28 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>
>> On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
>> > On Tue, 31 Oct 2017, Dave Hansen wrote:
>> >
>> >>
>> >> init_mm is for kernel-exclusive
On Wed, Nov 1, 2017 at 2:28 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>
>> On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
>> > On Tue, 31 Oct 2017, Dave Hansen wrote:
>> >
>> >>
>> >> init_mm is for kernel-exclusive use. If someone is allocating page
>> >>
On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Linus Torvalds wrote:
>> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
>> wrote:
>> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
>> >> On Wed, 1 Nov 2017, Andy
On Wed, Nov 1, 2017 at 3:20 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Linus Torvalds wrote:
>> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
>> wrote:
>> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
>> >> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>> >>> The vsyscall page is _PAGE_USER
On Wed, 1 Nov 2017, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
> wrote:
> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> >> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> >>> The vsyscall page is _PAGE_USER and lives in init_mm via the
On Wed, 1 Nov 2017, Linus Torvalds wrote:
> On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen
> wrote:
> > On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> >> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> >>> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
> >>
> >> Groan, forgot
On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen wrote:
> On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
>> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>>> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
>>
>> Groan, forgot about that abomination, but
On Wed, Nov 1, 2017 at 2:52 PM, Dave Hansen wrote:
> On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
>> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>>> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
>>
>> Groan, forgot about that abomination, but still there is no point in
On Wed, 1 Nov 2017, Dave Hansen wrote:
> On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> > On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> >> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
> >
> > Groan, forgot about that abomination, but still there is no point in having
> >
On Wed, 1 Nov 2017, Dave Hansen wrote:
> On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> > On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> >> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
> >
> > Groan, forgot about that abomination, but still there is no point in having
> >
On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
>
> Groan, forgot about that abomination, but still there is no point in having
> it marked PAGE_USER in the init_mm at all, kaiser
On 11/01/2017 02:28 PM, Thomas Gleixner wrote:
> On Wed, 1 Nov 2017, Andy Lutomirski wrote:
>> The vsyscall page is _PAGE_USER and lives in init_mm via the fixmap.
>
> Groan, forgot about that abomination, but still there is no point in having
> it marked PAGE_USER in the init_mm at all, kaiser
On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
> > On Tue, 31 Oct 2017, Dave Hansen wrote:
> >
> >>
> >> init_mm is for kernel-exclusive use. If someone is allocating page
> >> tables in it, do not set _PAGE_USER on them.
On Wed, 1 Nov 2017, Andy Lutomirski wrote:
> On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
> > On Tue, 31 Oct 2017, Dave Hansen wrote:
> >
> >>
> >> init_mm is for kernel-exclusive use. If someone is allocating page
> >> tables in it, do not set _PAGE_USER on them. This ensures that
>
On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
> On Tue, 31 Oct 2017, Dave Hansen wrote:
>
>>
>> init_mm is for kernel-exclusive use. If someone is allocating page
>> tables in it, do not set _PAGE_USER on them. This ensures that
>> we do *not* set NX on these page
On Wed, Nov 1, 2017 at 2:11 PM, Thomas Gleixner wrote:
> On Tue, 31 Oct 2017, Dave Hansen wrote:
>
>>
>> init_mm is for kernel-exclusive use. If someone is allocating page
>> tables in it, do not set _PAGE_USER on them. This ensures that
>> we do *not* set NX on these page tables in the KAISER
On Tue, 31 Oct 2017, Dave Hansen wrote:
>
> init_mm is for kernel-exclusive use. If someone is allocating page
> tables in it, do not set _PAGE_USER on them. This ensures that
> we do *not* set NX on these page tables in the KAISER code.
This changelog is confusing at best.
Why is this a
On Tue, 31 Oct 2017, Dave Hansen wrote:
>
> init_mm is for kernel-exclusive use. If someone is allocating page
> tables in it, do not set _PAGE_USER on them. This ensures that
> we do *not* set NX on these page tables in the KAISER code.
This changelog is confusing at best.
Why is this a
init_mm is for kernel-exclusive use. If someone is allocating page
tables in it, do not set _PAGE_USER on them. This ensures that
we do *not* set NX on these page tables in the KAISER code.
Signed-off-by: Dave Hansen
Cc: Moritz Lipp
init_mm is for kernel-exclusive use. If someone is allocating page
tables in it, do not set _PAGE_USER on them. This ensures that
we do *not* set NX on these page tables in the KAISER code.
Signed-off-by: Dave Hansen
Cc: Moritz Lipp
Cc: Daniel Gruss
Cc: Michael Schwarz
Cc: Andy Lutomirski
44 matches
Mail list logo