[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20220414142457.d22ce3a11920dc943001d737@linux-foundation.org>
Date: Thu, 14 Apr 2022 14:24:57 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Aleksandr Nogikh <nogikh@...gle.com>
Cc: kasan-dev@...glegroups.com, linux-kernel@...r.kernel.org,
dvyukov@...gle.com, andreyknvl@...il.com, elver@...gle.com,
glider@...gle.com, tarasmadan@...gle.com, bigeasy@...utronix.de
Subject: Re: [PATCH v3] kcov: don't generate a warning on vm_insert_page()'s
failure
On Fri, 1 Apr 2022 18:25:12 +0000 Aleksandr Nogikh <nogikh@...gle.com> wrote:
> vm_insert_page()'s failure is not an unexpected condition, so don't do
> WARN_ONCE() in such a case.
>
> Instead, print a kernel message and just return an error code.
(hm, I thought I asked this before but I can't find it)
Under what circumstances will this failure occur?
Why do we emit a message at all? What action can the user take upon
seeing the message?
Do we have a Fixes: for this?
>From the info provided thus far I'm unable to determine whether a
-stable backport is needed. What are your thoughts on this?
Powered by blists - more mailing lists