Re: [PATCH 4/4] kasan: Prevent deadlock in kasan reporting

From: Andrey Ryabinin
Date: Thu Sep 03 2015 - 05:15:57 EST


On 09/03/2015 10:54 AM, Aneesh Kumar K.V wrote:
> We we end up calling kasan_report in real mode, our shadow mapping

s/We we/We

> for even spinlock variable will show poisoned. This will result
> in us calling kasan_report_error with lock_report spin lock held.
> To prevent this disable kasan reporting when we are priting

s/priting/printing

> error w.r.t kasan.
>
> Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@xxxxxxxxxxxxxxxxxx>
> ---
> mm/kasan/report.c | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>

Reviewed-by: Andrey Ryabinin <ryabinin.a.a@xxxxxxxxx>
--
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/