From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, zhongjubin@huawei.com,
wangbing6@huawei.com, nixiaoming@huawei.com,
huangshaobo6@huawei.com, glider@google.com, elver@google.com,
dvyukov@google.com, chenzefeng2@huawei.com,
akpm@linux-foundation.org, akpm@linux-foundation.org
Subject: [folded-merged] kfence-enable-check-kfence-canary-on-panic-via-boot-param-fix.patch removed from -mm tree
Date: Mon, 09 May 2022 18:05:24 -0700 [thread overview]
Message-ID: <20220510010524.CC72BC385C2@smtp.kernel.org> (raw)
The quilt patch titled
Subject: kfence-enable-check-kfence-canary-on-panic-via-boot-param-fix
has been removed from the -mm tree. Its filename was
kfence-enable-check-kfence-canary-on-panic-via-boot-param-fix.patch
This patch was dropped because it was folded into kfence-enable-check-kfence-canary-on-panic-via-boot-param.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: kfence-enable-check-kfence-canary-on-panic-via-boot-param-fix
add __read_mostly, per Marco
Cc: Alexander Potapenko <glider@google.com>
Cc: chenzefeng <chenzefeng2@huawei.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: huangshaobo <huangshaobo6@huawei.com>
Cc: Jubin Zhong <zhongjubin@huawei.com>
Cc: Marco Elver <elver@google.com>
Cc: Wangbing <wangbing6@huawei.com>
Cc: Xiaoming Ni <nixiaoming@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/kfence/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/kfence/core.c~kfence-enable-check-kfence-canary-on-panic-via-boot-param-fix
+++ a/mm/kfence/core.c
@@ -102,7 +102,7 @@ static bool kfence_deferrable __read_mos
module_param_named(deferrable, kfence_deferrable, bool, 0444);
/* If true, check all canary bytes on panic. */
-static bool kfence_check_on_panic;
+static bool kfence_check_on_panic __read_mostly;
module_param_named(check_on_panic, kfence_check_on_panic, bool, 0444);
/* The pool of pages used for guard pages and objects. */
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-check-against-orig_pte-for-finish_fault-fix-checkpatch-fixes.patch
mm-hugetlb-only-drop-uffd-wp-special-pte-if-required-fix-fix.patch
kfence-enable-check-kfence-canary-on-panic-via-boot-param.patch
lib-kstrtoxc-add-false-true-support-to-kstrtobool-fix.patch
mm-vmscan-not-necessary-to-re-init-the-list-for-each-iteration-fix.patch
mm-make-minimum-slab-alignment-a-runtime-property-fix.patch
proc-fix-dentry-inode-overinstantiating-under-proc-pid-net-checkpatch-fixes.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
mm-oom_killc-fix-vm_oom_kill_table-ifdeffery.patch
reply other threads:[~2022-05-10 1:05 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=20220510010524.CC72BC385C2@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=chenzefeng2@huawei.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=huangshaobo6@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=nixiaoming@huawei.com \
--cc=wangbing6@huawei.com \
--cc=zhongjubin@huawei.com \
/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.