From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, andreyknvl@gmail.com,
sfr@canb.auug.org.au, akpm@linux-foundation.org
Subject: [folded-merged] kasan-improve-vmalloc-tests-fix.patch removed from -mm tree
Date: Thu, 24 Mar 2022 17:33:09 -0700 [thread overview]
Message-ID: <20220325003310.16D54C340EC@smtp.kernel.org> (raw)
The patch titled
Subject: similar to "kasan: test: fix compatibility with FORTIFY_SOURCE"
has been removed from the -mm tree. Its filename was
kasan-improve-vmalloc-tests-fix.patch
This patch was dropped because it was folded into kasan-improve-vmalloc-tests.patch
------------------------------------------------------
From: Stephen Rothwell <sfr@canb.auug.org.au>
Subject: similar to "kasan: test: fix compatibility with FORTIFY_SOURCE"
Link: https://lkml.kernel.org/r/20220128144801.73f5ced0@canb.auug.org.au
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/test_kasan.c | 2 ++
1 file changed, 2 insertions(+)
--- a/lib/test_kasan.c~kasan-improve-vmalloc-tests-fix
+++ a/lib/test_kasan.c
@@ -1104,6 +1104,8 @@ static void vmalloc_oob(struct kunit *te
v_ptr = vmalloc(size);
KUNIT_ASSERT_NOT_ERR_OR_NULL(test, v_ptr);
+ OPTIMIZER_HIDE_VAR(v_ptr);
+
/*
* We have to be careful not to hit the guard page in vmalloc tests.
* The MMU will catch that and crash us.
_
Patches currently in -mm which might be from sfr@canb.auug.org.au are
kasan-improve-vmalloc-tests.patch
reply other threads:[~2022-03-25 0:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220325003310.16D54C340EC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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.