[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YT+EStsWldSp76HX@slm.duckdns.org>
Date: Mon, 13 Sep 2021 07:03:06 -1000
From: Tejun Heo <tj@...nel.org>
To: Marco Elver <elver@...gle.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Shuah Khan <skhan@...uxfoundation.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
Andrey Konovalov <andreyknvl@...il.com>,
Walter Wu <walter-zh.wu@...iatek.com>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
Thomas Gleixner <tglx@...utronix.de>,
Andrey Ryabinin <ryabinin.a.a@...il.com>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
Vijayanand Jitta <vjitta@...eaurora.org>,
Vinayak Menon <vinmenon@...eaurora.org>,
"Gustavo A. R. Silva" <gustavoars@...nel.org>,
kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, Aleksandr Nogikh <nogikh@...gle.com>,
Taras Madan <tarasmadan@...gle.com>
Subject: Re: [PATCH v2 6/6] workqueue, kasan: avoid alloc_pages() when
recording stack
On Mon, Sep 13, 2021 at 01:26:09PM +0200, Marco Elver wrote:
> While there is an increased risk of failing to insert the stack trace,
> this is typically unlikely, especially if the same insertion had already
> succeeded previously (stack depot hit). For frequent calls from the same
> location, it therefore becomes extremely unlikely that
> kasan_record_aux_stack_noalloc() fails.
>
> Link: https://lkml.kernel.org/r/20210902200134.25603-1-skhan@linuxfoundation.org
> Reported-by: Shuah Khan <skhan@...uxfoundation.org>
> Signed-off-by: Marco Elver <elver@...gle.com>
> Tested-by: Shuah Khan <skhan@...uxfoundation.org>
> Acked-by: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Acked-by: Tejun Heo <tj@...nel.org>
Please feel free to route with the rest of series or if you want me to take
these through the wq tree, please let me know.
Thanks.
--
tejun
Powered by blists - more mailing lists