On Mon, 8 Apr 2019, Thomas Gleixner wrote:
> On Mon, 8 Apr 2019, Andy Lutomirski wrote:
> > On Sun, Apr 7, 2019 at 11:46 PM Thomas Gleixner wrote:
> > >
> > > On Sun, 7 Apr 2019, Andy Lutomirski wrote:
> > > > On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner
> > > > wrote:
> > > > > Actually we h
On Mon, 8 Apr 2019, Andy Lutomirski wrote:
> On Sun, Apr 7, 2019 at 11:46 PM Thomas Gleixner wrote:
> >
> > On Sun, 7 Apr 2019, Andy Lutomirski wrote:
> > > On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote:
> > > > Actually we have: save_stack_trace()
> > > >
> > >
> > > Like I did here:
> >
On Mon, Apr 08, 2019 at 09:18:00AM -0700, Andy Lutomirski wrote:
> On Sun, Apr 7, 2019 at 11:46 PM Thomas Gleixner wrote:
> >
> > On Sun, 7 Apr 2019, Andy Lutomirski wrote:
> > > On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote:
> > > > Actually we have: save_stack_trace()
> > > >
> > >
> > >
On Sun, Apr 7, 2019 at 11:46 PM Thomas Gleixner wrote:
>
> On Sun, 7 Apr 2019, Andy Lutomirski wrote:
> > On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote:
> > > Actually we have: save_stack_trace()
> > >
> >
> > Like I did here:
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/luto/li
On Sun, 7 Apr 2019, Andy Lutomirski wrote:
> On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote:
> > Actually we have: save_stack_trace()
> >
>
> Like I did here:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git/log/?h=WIP.x86/stackguards
Kinda, but what that code wants is t
On Sun, Apr 7, 2019 at 3:44 PM Thomas Gleixner wrote:
>
> On Sat, 6 Apr 2019, Andy Lutomirski wrote:
> > On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
> > >
> > > From: Andy Lutomirski
> > >
> > > The IRQ stack lives in percpu space, so an IRQ handler that overflows it
> > > will overwri
On Sat, 6 Apr 2019, Andy Lutomirski wrote:
> On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
> >
> > From: Andy Lutomirski
> >
> > The IRQ stack lives in percpu space, so an IRQ handler that overflows it
> > will overwrite other data structures.
> >
> > Use vmap() to remap the IRQ stack so
> On Apr 7, 2019, at 2:34 AM, Thomas Gleixner wrote:
>
> On Sun, 7 Apr 2019, Andy Lutomirski wrote:
>>> On Apr 6, 2019, at 11:08 PM, Thomas Gleixner wrote:
>>>
> On Sat, 6 Apr 2019, Andy Lutomirski wrote:
> On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
>
> From: Andy
On Sun, 7 Apr 2019, Andy Lutomirski wrote:
> > On Apr 6, 2019, at 11:08 PM, Thomas Gleixner wrote:
> >
> >> On Sat, 6 Apr 2019, Andy Lutomirski wrote:
> >>> On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
> >>>
> >>> From: Andy Lutomirski
> >>>
> >>> The IRQ stack lives in percpu space,
> On Apr 6, 2019, at 11:08 PM, Thomas Gleixner wrote:
>
>> On Sat, 6 Apr 2019, Andy Lutomirski wrote:
>>> On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
>>>
>>> From: Andy Lutomirski
>>>
>>> The IRQ stack lives in percpu space, so an IRQ handler that overflows it
>>> will overwrite
On Sat, 6 Apr 2019, Andy Lutomirski wrote:
> On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
> >
> > From: Andy Lutomirski
> >
> > The IRQ stack lives in percpu space, so an IRQ handler that overflows it
> > will overwrite other data structures.
> >
> > Use vmap() to remap the IRQ stack so
On Fri, Apr 5, 2019 at 8:11 AM Thomas Gleixner wrote:
>
> From: Andy Lutomirski
>
> The IRQ stack lives in percpu space, so an IRQ handler that overflows it
> will overwrite other data structures.
>
> Use vmap() to remap the IRQ stack so that it will have the usual guard
> pages that vmap/vmalloc
From: Andy Lutomirski
The IRQ stack lives in percpu space, so an IRQ handler that overflows it
will overwrite other data structures.
Use vmap() to remap the IRQ stack so that it will have the usual guard
pages that vmap/vmalloc allocations have. With this the kernel will panic
immediately on an
13 matches
Mail list logo