From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,vincenzo.frascino@arm.com,snovitoll@gmail.com,ryabinin.a.a@gmail.com,glider@google.com,elver@google.com,dvyukov@google.com,andreyknvl@gmail.com,akpm@linux-foundation.org,akpm@linux-foundation.org
Subject: [folded-merged] mm-kasan-kmsan-copy_from-to_kernel_nofault-fix.patch removed from -mm tree
Date: Sun, 03 Nov 2024 20:52:55 -0800 [thread overview]
Message-ID: <20241104045255.BC932C4CECE@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-kasan-kmsan-copy_from-to_kernel_nofault-fix
has been removed from the -mm tree. Its filename was
mm-kasan-kmsan-copy_from-to_kernel_nofault-fix.patch
This patch was dropped because it was folded into mm-kasan-kmsan-copy_from-to_kernel_nofault.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-kasan-kmsan-copy_from-to_kernel_nofault-fix
Date: Tue Oct 15 04:53:38 PM PDT 2024
fix comment layout, per checkpatch
Cc: Alexander Potapenko <glider@google.com>
Cc: Andrey Konovalov <andreyknvl@gmail.com>
Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
Cc: Dmitry Vyukov <dvyukov@google.com>
Cc: Marco Elver <elver@google.com>
Cc: Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Cc: Vincenzo Frascino <vincenzo.frascino@arm.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/kasan/kasan_test_c.c | 26 ++++++++++++++------------
1 file changed, 14 insertions(+), 12 deletions(-)
--- a/mm/kasan/kasan_test_c.c~mm-kasan-kmsan-copy_from-to_kernel_nofault-fix
+++ a/mm/kasan/kasan_test_c.c
@@ -1934,8 +1934,10 @@ static void copy_to_kernel_nofault_oob(s
char buf[128];
size_t size = sizeof(buf);
- /* This test currently fails with the HW_TAGS mode.
- * The reason is unknown and needs to be investigated. */
+ /*
+ * This test currently fails with the HW_TAGS mode. The reason is
+ * unknown and needs to be investigated.
+ */
KASAN_TEST_NEEDS_CONFIG_OFF(test, CONFIG_KASAN_HW_TAGS);
ptr = kmalloc(size - KASAN_GRANULE_SIZE, GFP_KERNEL);
@@ -1943,16 +1945,16 @@ static void copy_to_kernel_nofault_oob(s
OPTIMIZER_HIDE_VAR(ptr);
/*
- * We test copy_to_kernel_nofault() to detect corrupted memory that is
- * being written into the kernel. In contrast, copy_from_kernel_nofault()
- * is primarily used in kernel helper functions where the source address
- * might be random or uninitialized. Applying KASAN instrumentation to
- * copy_from_kernel_nofault() could lead to false positives.
- * By focusing KASAN checks only on copy_to_kernel_nofault(),
- * we ensure that only valid memory is written to the kernel,
- * minimizing the risk of kernel corruption while avoiding
- * false positives in the reverse case.
- */
+ * We test copy_to_kernel_nofault() to detect corrupted memory that is
+ * being written into the kernel. In contrast,
+ * copy_from_kernel_nofault() is primarily used in kernel helper
+ * functions where the source address might be random or uninitialized.
+ * Applying KASAN instrumentation to copy_from_kernel_nofault() could
+ * lead to false positives. By focusing KASAN checks only on
+ * copy_to_kernel_nofault(), we ensure that only valid memory is
+ * written to the kernel, minimizing the risk of kernel corruption
+ * while avoiding false positives in the reverse case.
+ */
KUNIT_EXPECT_KASAN_FAIL(test,
copy_to_kernel_nofault(&buf[0], ptr, size));
KUNIT_EXPECT_KASAN_FAIL(test,
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-page_alloc-keep-track-of-free-highatomic-fix.patch
mm-refactor-arch_calc_vm_flag_bits-and-arm64-mte-handling-fix.patch
mm-fix-__wp_page_copy_user-fallback-path-for-remote-mm-fix.patch
mm-memoryc-remove-stray-newline-at-top-of-file.patch
mm-kasan-kmsan-copy_from-to_kernel_nofault.patch
alloc_tag-load-module-tags-into-separate-contiguous-memory-fix-fix.patch
tools-mm-free-the-allocated-memory-fix.patch
memcg-v1-no-need-for-memcg-locking-for-mglru-fix.patch
mm-vma-the-pgoff-is-correct-if-can_merge_right-fix.patch
memcg-workingset-remove-folio_memcg_rcu-usage-fix.patch
bootmem-stop-using-page-index-fix.patch
vma-detect-infinite-loop-in-vma-tree-fix.patch
maple_tree-add-a-test-checking-storing-null-fix.patch
fs-proc-kcorec-fix-coccinelle-reported-error-instances-fix.patch
reply other threads:[~2024-11-04 4:52 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=20241104045255.BC932C4CECE@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=andreyknvl@gmail.com \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=mm-commits@vger.kernel.org \
--cc=ryabinin.a.a@gmail.com \
--cc=snovitoll@gmail.com \
--cc=vincenzo.frascino@arm.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.