From: Peter Collingbourne <pcc@google.com>
To: catalin.marinas@arm.com, andreyknvl@gmail.com
Cc: Peter Collingbourne <pcc@google.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
Subject: [PATCH v3 0/2] kasan: bugfix and cleanup
Date: Tue, 28 Feb 2023 16:35:43 -0800 [thread overview]
Message-ID: <20230301003545.282859-1-pcc@google.com> (raw)
Hi,
This patch series reverts a cleanup patch that turned out to introduce
a bug, and does some cleanup of its own by removing some flags that I
realized were redundant while investigating the bug.
Peter
Peter Collingbourne (2):
Revert "kasan: drop skip_kasan_poison variable in free_pages_prepare"
kasan: remove PG_skip_kasan_poison flag
include/linux/gfp_types.h | 30 ++++++------
include/linux/page-flags.h | 9 ----
include/trace/events/mmflags.h | 12 +----
mm/kasan/hw_tags.c | 2 +-
mm/page_alloc.c | 84 +++++++++++++---------------------
mm/vmalloc.c | 2 +-
6 files changed, 49 insertions(+), 90 deletions(-)
--
2.39.2.722.g9855ee24e9-goog
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Peter Collingbourne <pcc@google.com>
To: catalin.marinas@arm.com, andreyknvl@gmail.com
Cc: Peter Collingbourne <pcc@google.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
Subject: [PATCH v3 0/2] kasan: bugfix and cleanup
Date: Tue, 28 Feb 2023 16:35:43 -0800 [thread overview]
Message-ID: <20230301003545.282859-1-pcc@google.com> (raw)
Hi,
This patch series reverts a cleanup patch that turned out to introduce
a bug, and does some cleanup of its own by removing some flags that I
realized were redundant while investigating the bug.
Peter
Peter Collingbourne (2):
Revert "kasan: drop skip_kasan_poison variable in free_pages_prepare"
kasan: remove PG_skip_kasan_poison flag
include/linux/gfp_types.h | 30 ++++++------
include/linux/page-flags.h | 9 ----
include/trace/events/mmflags.h | 12 +----
mm/kasan/hw_tags.c | 2 +-
mm/page_alloc.c | 84 +++++++++++++---------------------
mm/vmalloc.c | 2 +-
6 files changed, 49 insertions(+), 90 deletions(-)
--
2.39.2.722.g9855ee24e9-goog
next reply other threads:[~2023-03-01 0:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 0:35 Peter Collingbourne [this message]
2023-03-01 0:35 ` [PATCH v3 0/2] kasan: bugfix and cleanup Peter Collingbourne
2023-03-01 0:35 ` [PATCH v3 1/2] Revert "kasan: drop skip_kasan_poison variable in free_pages_prepare" Peter Collingbourne
2023-03-01 0:35 ` Peter Collingbourne
2023-03-09 1:46 ` Andrew Morton
2023-03-09 1:46 ` Andrew Morton
2023-03-09 21:36 ` Peter Collingbourne
2023-03-09 21:36 ` Peter Collingbourne
2023-03-01 0:35 ` [PATCH v3 2/2] kasan: remove PG_skip_kasan_poison flag Peter Collingbourne
2023-03-01 0:35 ` Peter Collingbourne
2023-03-01 0:57 ` Andrey Konovalov
2023-03-01 0:57 ` Andrey Konovalov
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=20230301003545.282859-1-pcc@google.com \
--to=pcc@google.com \
--cc=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=ryabinin.a.a@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.