From: Andrey Konovalov <andreyknvl@gmail.com>
To: Peter Collingbourne <pcc@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v3] mm: use compare-exchange operation to set KASAN page tag
Date: Mon, 24 Jan 2022 18:25:34 +0100 [thread overview]
Message-ID: <CA+fCnZfQ557MGc33jpSu9+ctUyXOaHR+tzsScPa3jZdkDiLjvA@mail.gmail.com> (raw)
In-Reply-To: <CA+fCnZeC5K+YoFbMg30Gasyq6AXp5WFCxagrsftkT+mJPuBZkQ@mail.gmail.com>
On Mon, Jan 24, 2022 at 6:22 PM Andrey Konovalov <andreyknvl@gmail.com> wrote:
>
> On Thu, Jan 20, 2022 at 3:02 AM Peter Collingbourne <pcc@google.com> wrote:
> >
> > It has been reported that the tag setting operation on newly-allocated
> > pages can cause the page flags to be corrupted when performed
> > concurrently with other flag updates as a result of the use of
> > non-atomic operations. Fix the problem by using a compare-exchange
> > loop to update the tag.
> >
> > Signed-off-by: Peter Collingbourne <pcc@google.com>
> > Link: https://linux-review.googlesource.com/id/I456b24a2b9067d93968d43b4bb3351c0cec63101
> > Fixes: 2813b9c02962 ("kasan, mm, arm64: tag non slab memory allocated via pagealloc")
> > Cc: stable@vger.kernel.org
> > ---
> > v3:
> > - use try_cmpxchg() as suggested by Peter Zijlstra on another
> > patch
> >
> > v2:
> > - use READ_ONCE()
> >
> > include/linux/mm.h | 17 ++++++++++++-----
> > 1 file changed, 12 insertions(+), 5 deletions(-)
> >
> > diff --git a/include/linux/mm.h b/include/linux/mm.h
> > index c768a7c81b0b..87473fe52c3f 100644
> > --- a/include/linux/mm.h
> > +++ b/include/linux/mm.h
> > @@ -1531,11 +1531,18 @@ static inline u8 page_kasan_tag(const struct page *page)
> >
> > static inline void page_kasan_tag_set(struct page *page, u8 tag)
> > {
> > - if (kasan_enabled()) {
> > - tag ^= 0xff;
> > - page->flags &= ~(KASAN_TAG_MASK << KASAN_TAG_PGSHIFT);
> > - page->flags |= (tag & KASAN_TAG_MASK) << KASAN_TAG_PGSHIFT;
> > - }
> > + unsigned long old_flags, flags;
> > +
> > + if (!kasan_enabled())
> > + return;
> > +
> > + tag ^= 0xff;
> > + old_flags = READ_ONCE(page->flags);
> > + do {
> > + flags = old_flags;
> > + flags &= ~(KASAN_TAG_MASK << KASAN_TAG_PGSHIFT);
> > + flags |= (tag & KASAN_TAG_MASK) << KASAN_TAG_PGSHIFT;
> > + } while (unlikely(!try_cmpxchg(&page->flags, &old_flags, flags)));
> > }
> >
> > static inline void page_kasan_tag_reset(struct page *page)
> > --
> > 2.34.1.703.g22d0c6ccf7-goog
> >
>
> Reviewed-by: Andrey Konovalov <andreyknvl@gmail.com>
>
> FWIW, try_cmpxchg() doesn't seem to be doing annotated atomic accesses
> when accessing old_flags, so using READ_ONCE() in page_kasan_tag_set()
> seems pointless after all.
Ah, nevermind. For a second I thought that try_cmpxchg() is actually
accessing page->flags through its second argument.
prev parent reply other threads:[~2022-01-24 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 2:01 Peter Collingbourne
2022-01-24 17:22 ` Andrey Konovalov
2022-01-24 17:25 ` 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+fCnZfQ557MGc33jpSu9+ctUyXOaHR+tzsScPa3jZdkDiLjvA@mail.gmail.com \
--to=andreyknvl@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pcc@google.com \
--cc=peterz@infradead.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