Re: [harry:kmalloc-no-objext-rfc-v1r1] [mm/slab] 6bc21472e7: BUG:kernel_NULL_pointer_dereference,address

Harry Yoo <[email protected]> Fri, 10 Jul 2026 19:04:50 +0900
Newsgroups dev.linux.lists.oe-lkp,org.kvack.linux-mm
Message-ID <[email protected]>
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--------------V6m3WAHSMa9Jv1iiktisZNM2
Content-Type: multipart/mixed; boundary="------------iPxkI0pAlY3tmBSQs0WgtLW5";
 protected-headers="v1"
From: Harry Yoo <[email protected]>
To: Oliver Sang <[email protected]>
Cc: [email protected], [email protected],
 Danielle Constantino <[email protected]>,
 Shakeel Butt <[email protected]>, [email protected]
Message-ID: <[email protected]>
Subject: Re: [harry:kmalloc-no-objext-rfc-v1r1] [mm/slab] 6bc21472e7:
 BUG:kernel_NULL_pointer_dereference,address
References: <[email protected]>
 <[email protected]>
 <alCddXaJ4HkjZNXi@xsang-OptiPlex-9020>
In-Reply-To: <alCddXaJ4HkjZNXi@xsang-OptiPlex-9020>

--------------iPxkI0pAlY3tmBSQs0WgtLW5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable



On 7/10/26 4:21 PM, Oliver Sang wrote:
> hi, Harry Yoo,

Hi Oliver,

> On Thu, Jul 09, 2026 at 06:26:54PM +0900, Harry Yoo wrote:
>> On 7/9/26 5:48 PM, kernel test robot wrote:
>>>
>>>
>>> Hello,
>>>
>>> kernel test robot noticed "BUG:kernel_NULL_pointer_dereference,addres=
s" on:
>>>
>>> commit: 6bc21472e7eb9f8c771ffdf86266aa6d9dcb1dac ("mm/slab: prevent u=
nbounded recursion due to obj_exts in free path")
>>> https://git.kernel.org/cgit/linux/kernel/git/harry/linux.git kmalloc-=
no-objext-rfc-v1r1
>>
>> This is v1r1, and I posted v1r3, because it was bootstrapping sheaves
>> for normal kmalloc only. This crashed the kernel but was fixed in v1r2=
=2E
>>
>> Apologies for the confusion, I discovered bugs after exposing it in my=

>> tree (force pushing isn't great, you know...) I should probably have
>> deleted that broken one, though. :)
>>
>> Will be posting v2 that fixes false warnings w/ memalloc profiling
>> debug shortly.
>=20
> thanks a lot for information! sorry that our bot still cannot analyze b=
ranch
> version so far.

No worries :)

Is there any way to tell the bot that a branch is broken,
e.g.) deleting a broken branch from the repository?

> we will check the latest branch in your repo before reporting
> in the future.

Thanks!

--=20
Cheers,
Harry / Hyeonggon

--------------iPxkI0pAlY3tmBSQs0WgtLW5--

--------------V6m3WAHSMa9Jv1iiktisZNM2
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEARYKAB0WIQQQ1ub6gR5ogjaKRmOGXBN6rc5S1gUCalDDwgAKCRCGXBN6rc5S
1rNtAQDsPHuMpYN3I8TXdZ/lV71OWDWJ+P6u+SAkNGwh1T3ITAEAw/YZZDhQB4jz
0g+m/gEmAqFtRBolTTJBFnGyh55RIw8=
=ppkB
-----END PGP SIGNATURE-----

--------------V6m3WAHSMa9Jv1iiktisZNM2--