From: Andrey Konovalov <andreyknvl@gmail.com>
To: Peter Collingbourne <pcc@google.com>
Cc: catalin.marinas@arm.com, linux-mm@kvack.org,
kasan-dev@googlegroups.com, ryabinin.a.a@gmail.com,
linux-arm-kernel@lists.infradead.org, vincenzo.frascino@arm.com,
will@kernel.org, eugenis@google.com, stable@vger.kernel.org
Subject: Re: [PATCH] Revert "kasan: drop skip_kasan_poison variable in free_pages_prepare"
Date: Mon, 27 Feb 2023 01:16:06 +0100 [thread overview]
Message-ID: <CA+fCnZepwNj2OXqHHeztOuZQ7UGp5i0M=SBkzQpTSnnMGL0dvA@mail.gmail.com> (raw)
In-Reply-To: <20230224061550.177541-1-pcc@google.com>
On Fri, Feb 24, 2023 at 7:16 AM Peter Collingbourne <pcc@google.com> wrote:
>
> This reverts commit 487a32ec24be819e747af8c2ab0d5c515508086a.
>
> The should_skip_kasan_poison() function reads the PG_skip_kasan_poison
> flag from page->flags. However, this line of code in free_pages_prepare():
>
> page->flags &= ~PAGE_FLAGS_CHECK_AT_PREP;
>
> clears most of page->flags, including PG_skip_kasan_poison, before calling
> should_skip_kasan_poison(), which meant that it would never return true
> as a result of the page flag being set. Therefore, fix the code to call
> should_skip_kasan_poison() before clearing the flags, as we were doing
> before the reverted patch.
>
> Signed-off-by: Peter Collingbourne <pcc@google.com>
> Fixes: 487a32ec24be ("kasan: drop skip_kasan_poison variable in free_pages_prepare")
> Cc: <stable@vger.kernel.org> # 6.1
> Link: https://linux-review.googlesource.com/id/Ic4f13affeebd20548758438bb9ed9ca40e312b79
> ---
> mm/page_alloc.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index ac1fc986af44..7136c36c5d01 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1398,6 +1398,7 @@ static __always_inline bool free_pages_prepare(struct page *page,
> unsigned int order, bool check_free, fpi_t fpi_flags)
> {
> int bad = 0;
> + bool skip_kasan_poison = should_skip_kasan_poison(page, fpi_flags);
> bool init = want_init_on_free();
>
> VM_BUG_ON_PAGE(PageTail(page), page);
> @@ -1470,7 +1471,7 @@ static __always_inline bool free_pages_prepare(struct page *page,
> * With hardware tag-based KASAN, memory tags must be set before the
> * page becomes unavailable via debug_pagealloc or arch_free_page.
> */
> - if (!should_skip_kasan_poison(page, fpi_flags)) {
> + if (!skip_kasan_poison) {
> kasan_poison_pages(page, order, init);
>
> /* Memory is already initialized if KASAN did it internally. */
> --
> 2.39.2.637.g21b0678d19-goog
>
Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
Thank you for fixing this, Peter!
prev parent reply other threads:[~2023-02-27 0:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 6:15 Peter Collingbourne
2023-02-27 0:16 ` Andrey Konovalov [this message]
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='CA+fCnZepwNj2OXqHHeztOuZQ7UGp5i0M=SBkzQpTSnnMGL0dvA@mail.gmail.com' \
--to=andreyknvl@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=eugenis@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=ryabinin.a.a@gmail.com \
--cc=stable@vger.kernel.org \
--cc=vincenzo.frascino@arm.com \
--cc=will@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