diff for duplicates of <YuY6Wc39DbL3YmGi@feng-skl> diff --git a/a/1.txt b/N1/1.txt index 2d9e7a8..733782a 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -10,7 +10,7 @@ On Sun, Jul 31, 2022 at 02:53:17PM +0800, Sang, Oliver wrote: > commit: 3616799128612e04ed919579e2c7b0dccf6bcb00 ("[PATCH v3 3/3] mm/slub: extend redzone check to cover extra allocated kmalloc space than requested") > url: https://github.com/intel-lab-lkp/linux/commits/Feng-Tang/mm-slub-some-debug-enhancements/20220727-151318 > base: git://git.kernel.org/cgit/linux/kernel/git/vbabka/slab.git for-next -> patch link: https://lore.kernel.org/linux-mm/20220727071042.8796-4-feng.tang(a)intel.com +> patch link: https://lore.kernel.org/linux-mm/20220727071042.8796-4-feng.tang@intel.com > > in testcase: boot > @@ -66,7 +66,7 @@ On Sun, Jul 31, 2022 at 02:53:17PM +0800, Sang, Oliver wrote: Thanks for the report! ->From the log it happened when kasan is enabled, and my first guess is +From the log it happened when kasan is enabled, and my first guess is the data processing from kmalloc redzone handling had some conflict with kasan's in allocation path (though I tested some kernel config with KASAN enabled) diff --git a/a/content_digest b/N1/content_digest index ccfc7b9..47fa510 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,28 @@ + "ref\020220727071042.8796-4-feng.tang@intel.com\0" "ref\0YuYm3dWwpZwH58Hu@xsang-OptiPlex-9020\0" "From\0Feng Tang <feng.tang@intel.com>\0" - "Subject\0Re: [mm/slub] 3616799128: BUG_kmalloc-#(Not_tainted):kmalloc_Redzone_overwritten\0" + "Subject\0Re: [mm/slub] 3616799128: BUG_kmalloc-#(Not_tainted):kmalloc_Redzone_overwritten\0" "Date\0Sun, 31 Jul 2022 16:16:25 +0800\0" - "To\0lkp@lists.01.org\0" - "\01:1\0" + "To\0Sang" + " Oliver <oliver.sang@intel.com>\0" + "Cc\0lkp <lkp@intel.com>" + Vlastimil Babka <vbabka@suse.cz> + LKML <linux-kernel@vger.kernel.org> + linux-mm@kvack.org <linux-mm@kvack.org> + lkp@lists.01.org <lkp@lists.01.org> + Andrew Morton <akpm@linux-foundation.org> + Christoph Lameter <cl@linux.com> + Pekka Enberg <penberg@kernel.org> + David Rientjes <rientjes@google.com> + Joonsoo Kim <iamjoonsoo.kim@lge.com> + Roman Gushchin <roman.gushchin@linux.dev> + Hyeonggon Yoo <42.hyeyoo@gmail.com> + Hansen + Dave <dave.hansen@intel.com> + Robin Murphy <robin.murphy@arm.com> + John Garry <john.garry@huawei.com> + " Kefeng Wang <wangkefeng.wang@huawei.com>\0" + "\00:1\0" "b\0" "Hi Oliver,\n" "\n" @@ -17,7 +36,7 @@ "> commit: 3616799128612e04ed919579e2c7b0dccf6bcb00 (\"[PATCH v3 3/3] mm/slub: extend redzone check to cover extra allocated kmalloc space than requested\")\n" "> url: https://github.com/intel-lab-lkp/linux/commits/Feng-Tang/mm-slub-some-debug-enhancements/20220727-151318\n" "> base: git://git.kernel.org/cgit/linux/kernel/git/vbabka/slab.git for-next\n" - "> patch link: https://lore.kernel.org/linux-mm/20220727071042.8796-4-feng.tang(a)intel.com\n" + "> patch link: https://lore.kernel.org/linux-mm/20220727071042.8796-4-feng.tang@intel.com\n" "> \n" "> in testcase: boot\n" "> \n" @@ -73,7 +92,7 @@ "\n" "Thanks for the report!\n" "\n" - ">From the log it happened when kasan is enabled, and my first guess is\n" + "From the log it happened when kasan is enabled, and my first guess is\n" "the data processing from kmalloc redzone handling had some conflict\n" "with kasan's in allocation path (though I tested some kernel config\n" "with KASAN enabled)\n" @@ -107,4 +126,4 @@ "> 0-DAY CI Kernel Test Service\n" > https://01.org/lkp -766e9d8defd114f16b484c28aba575cbe361744df6c9d36c39d4d82630cce2b5 +78daaffdf382cc176a9a6f02ea7e7e40ba973ef399fb73c92bb9a09ab5401410
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.