All of lore.kernel.org
 help / color / mirror / Atom feed
From: Harry Yoo <harry@kernel.org>
To: Oliver Sang <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com,
	Danielle Constantino <dconstantino@meta.com>,
	Shakeel Butt <shakeel.butt@linux.dev>,
	linux-mm@kvack.org
Subject: Re: [harry:kmalloc-no-objext-rfc-v1r1] [mm/slab] 6bc21472e7: BUG:kernel_NULL_pointer_dereference,address
Date: Fri, 10 Jul 2026 19:04:50 +0900	[thread overview]
Message-ID: <292ffec0-6a6b-451d-8977-3a5217c65d2c@kernel.org> (raw)
In-Reply-To: <alCddXaJ4HkjZNXi@xsang-OptiPlex-9020>


[-- Attachment #1.1: Type: text/plain, Size: 1323 bytes --]



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,address" on:
>>>
>>> commit: 6bc21472e7eb9f8c771ffdf86266aa6d9dcb1dac ("mm/slab: prevent unbounded 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.
>>
>> 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.
> 
> thanks a lot for information! sorry that our bot still cannot analyze branch
> 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!

-- 
Cheers,
Harry / Hyeonggon

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-07-10 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-09  8:48 [harry:kmalloc-no-objext-rfc-v1r1] [mm/slab] 6bc21472e7: BUG:kernel_NULL_pointer_dereference,address kernel test robot
2026-07-09  9:26 ` Harry Yoo
2026-07-10  7:21   ` Oliver Sang
2026-07-10 10:04     ` Harry Yoo [this message]
2026-07-12  8:14       ` Oliver Sang

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=292ffec0-6a6b-451d-8977-3a5217c65d2c@kernel.org \
    --to=harry@kernel.org \
    --cc=dconstantino@meta.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=oliver.sang@intel.com \
    --cc=shakeel.butt@linux.dev \
    /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.