From: kernel test robot <lkp@intel.com>
To: Hyesoo Yu <hyesoo.yu@samsung.com>
Cc: oe-kbuild-all@lists.linux.dev, janghyuck.kim@samsung.com,
Hyesoo Yu <hyesoo.yu@samsung.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: slub: Panic if the object corruption is checked.
Date: Tue, 21 Jan 2025 20:46:57 +0800 [thread overview]
Message-ID: <202501212026.lUnLNhv6-lkp@intel.com> (raw)
In-Reply-To: <20250120082908.4162780-1-hyesoo.yu@samsung.com>
Hi Hyesoo,
kernel test robot noticed the following build warnings:
[auto build test WARNING on akpm-mm/mm-everything]
url: https://github.com/intel-lab-lkp/linux/commits/Hyesoo-Yu/mm-slub-Panic-if-the-object-corruption-is-checked/20250120-163233
base: https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/r/20250120082908.4162780-1-hyesoo.yu%40samsung.com
patch subject: [PATCH] mm: slub: Panic if the object corruption is checked.
config: mips-randconfig-r111-20250121 (https://download.01.org/0day-ci/archive/20250121/202501212026.lUnLNhv6-lkp@intel.com/config)
compiler: mips-linux-gcc (GCC) 14.2.0
reproduce: (https://download.01.org/0day-ci/archive/20250121/202501212026.lUnLNhv6-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202501212026.lUnLNhv6-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> mm/slub.c:1308:9: sparse: sparse: cast from restricted slab_flags_t
mm/slub.c:1394:17: sparse: sparse: cast from restricted slab_flags_t
mm/slub.c:4440:47: sparse: sparse: context imbalance in '__slab_free' - unexpected unlock
vim +1308 mm/slub.c
1273
1274 /* Check the pad bytes at the end of a slab page */
1275 static pad_check_attributes void
1276 slab_pad_check(struct kmem_cache *s, struct slab *slab)
1277 {
1278 u8 *start;
1279 u8 *fault;
1280 u8 *end;
1281 u8 *pad;
1282 int length;
1283 int remainder;
1284
1285 if (!(s->flags & SLAB_POISON))
1286 return;
1287
1288 start = slab_address(slab);
1289 length = slab_size(slab);
1290 end = start + length;
1291 remainder = length % s->size;
1292 if (!remainder)
1293 return;
1294
1295 pad = end - remainder;
1296 metadata_access_enable();
1297 fault = memchr_inv(kasan_reset_tag(pad), POISON_INUSE, remainder);
1298 metadata_access_disable();
1299 if (!fault)
1300 return;
1301 while (end > fault && end[-1] == POISON_INUSE)
1302 end--;
1303
1304 slab_err(s, slab, "Padding overwritten. 0x%p-0x%p @offset=%tu",
1305 fault, end - 1, fault - start);
1306 print_section(KERN_ERR, "Padding ", pad, remainder);
1307
> 1308 BUG_ON(s->flags & SLAB_CORRUPTION_PANIC);
1309
1310 restore_bytes(s, "slab padding", POISON_INUSE, fault, end);
1311 }
1312
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-01-21 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250120083041epcas2p30d61ee801c1db5a7ebdf26fdc642883f@epcas2p3.samsung.com>
2025-01-20 8:28 ` [PATCH] mm: slub: Panic if the object corruption is checked Hyesoo Yu
2025-01-20 15:36 ` Matthew Wilcox
2025-01-21 0:40 ` Hyesoo Yu
2025-01-21 10:27 ` Vlastimil Babka
2025-01-20 15:41 ` Hyeonggon Yoo
2025-01-21 0:54 ` Hyesoo Yu
2025-01-21 1:48 ` Hyeonggon Yoo
2025-01-21 2:32 ` Hyesoo Yu
2025-01-21 10:28 ` Vlastimil Babka
2025-01-21 12:46 ` kernel test robot [this message]
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=202501212026.lUnLNhv6-lkp@intel.com \
--to=lkp@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=hyesoo.yu@samsung.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=janghyuck.kim@samsung.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
/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.