From: Andrey Ryabinin <ryabinin.a.a@gmail.com>
To: Alexander Gordeev <agordeev@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Daniel Axtens <dja@axtens.net>, Harry Yoo <harry.yoo@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kasan-dev@googlegroups.com, linux-s390@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v8 0/1] kasan: Avoid sleepable page allocation from atomic context
Date: Tue, 13 May 2025 18:43:56 +0200 [thread overview]
Message-ID: <53a86990-0aa5-4816-a252-43287f3451b8@gmail.com> (raw)
In-Reply-To: <cover.1747149155.git.agordeev@linux.ibm.com>
On 5/13/25 5:21 PM, Alexander Gordeev wrote:
> Hi All,
>
> Chages since v7:
> - drop "unnecessary free pages" optimization
> - fix error path page leak
>
> Chages since v6:
> - do not unnecessary free pages across iterations
>
Have you looked at boot failure report from kernel test robot ?
https://lkml.kernel.org/r/202505121313.806a632c-lkp@intel.com
I think the report is for v6 version, but I don't see evidence that it was
addressed, so the v8 is probably affected as well?
> Chages since v5:
> - full error message included into commit description
>
> Chages since v4:
> - unused pages leak is avoided
>
> Chages since v3:
> - pfn_to_virt() changed to page_to_virt() due to compile error
>
> Chages since v2:
> - page allocation moved out of the atomic context
>
> Chages since v1:
> - Fixes: and -stable tags added to the patch description
>
> Thanks!
>
> Alexander Gordeev (1):
> kasan: Avoid sleepable page allocation from atomic context
>
> mm/kasan/shadow.c | 77 ++++++++++++++++++++++++++++++++++++++---------
> 1 file changed, 63 insertions(+), 14 deletions(-)
>
next prev parent reply other threads:[~2025-05-13 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 15:21 Alexander Gordeev
2025-05-13 15:21 ` [PATCH v8 1/1] " Alexander Gordeev
2025-05-13 16:43 ` Andrey Ryabinin [this message]
2025-05-15 10:41 ` [PATCH v8 0/1] " Alexander Gordeev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53a86990-0aa5-4816-a252-43287f3451b8@gmail.com \
--to=ryabinin.a.a@gmail.com \
--cc=agordeev@linux.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dja@axtens.net \
--cc=harry.yoo@oracle.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-s390@vger.kernel.org \
--cc=stable@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox