Re: [PATCH] kasan: make depot_fetch_stack more robust

2016-07-04 Thread Kuthonuzo Luruo
On Mon, Jul 4, 2016 at 8:11 PM, Andrey Ryabinin wrote: > 2016-07-01 20:38 GMT+03:00 Dmitry Vyukov : >> I've hit a GPF in depot_fetch_stack when it was given >> bogus stack handle. I think it was caused by a distant >> out-of-bounds that hit a different

Re: [PATCH] kasan: make depot_fetch_stack more robust

2016-07-04 Thread Kuthonuzo Luruo
On Mon, Jul 4, 2016 at 8:11 PM, Andrey Ryabinin wrote: > 2016-07-01 20:38 GMT+03:00 Dmitry Vyukov : >> I've hit a GPF in depot_fetch_stack when it was given >> bogus stack handle. I think it was caused by a distant >> out-of-bounds that hit a different object, as the result >> we treated uninit

Re: [PATCH] kasan: make depot_fetch_stack more robust

2016-07-04 Thread Andrey Ryabinin
2016-07-01 20:38 GMT+03:00 Dmitry Vyukov : > I've hit a GPF in depot_fetch_stack when it was given > bogus stack handle. I think it was caused by a distant > out-of-bounds that hit a different object, as the result > we treated uninit garbage as stack handle. Maybe there is >

Re: [PATCH] kasan: make depot_fetch_stack more robust

2016-07-04 Thread Andrey Ryabinin
2016-07-01 20:38 GMT+03:00 Dmitry Vyukov : > I've hit a GPF in depot_fetch_stack when it was given > bogus stack handle. I think it was caused by a distant > out-of-bounds that hit a different object, as the result > we treated uninit garbage as stack handle. Maybe there is > something to fix in

Re: [PATCH] kasan: make depot_fetch_stack more robust

2016-07-03 Thread Joonsoo Kim
On Fri, Jul 01, 2016 at 07:38:18PM +0200, Dmitry Vyukov wrote: > I've hit a GPF in depot_fetch_stack when it was given > bogus stack handle. I think it was caused by a distant > out-of-bounds that hit a different object, as the result > we treated uninit garbage as stack handle. Maybe there is >

Re: [PATCH] kasan: make depot_fetch_stack more robust

2016-07-03 Thread Joonsoo Kim
On Fri, Jul 01, 2016 at 07:38:18PM +0200, Dmitry Vyukov wrote: > I've hit a GPF in depot_fetch_stack when it was given > bogus stack handle. I think it was caused by a distant > out-of-bounds that hit a different object, as the result > we treated uninit garbage as stack handle. Maybe there is >

[PATCH] kasan: make depot_fetch_stack more robust

2016-07-01 Thread Dmitry Vyukov
I've hit a GPF in depot_fetch_stack when it was given bogus stack handle. I think it was caused by a distant out-of-bounds that hit a different object, as the result we treated uninit garbage as stack handle. Maybe there is something to fix in KASAN logic, but I think it makes sense to make

[PATCH] kasan: make depot_fetch_stack more robust

2016-07-01 Thread Dmitry Vyukov
I've hit a GPF in depot_fetch_stack when it was given bogus stack handle. I think it was caused by a distant out-of-bounds that hit a different object, as the result we treated uninit garbage as stack handle. Maybe there is something to fix in KASAN logic, but I think it makes sense to make