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

hi, Harry Yoo,

On Fri, Jul 10, 2026 at 07:04:50PM +0900, Harry Yoo wrote:
> 
> 
> 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?

yeah, deleting the broken branch could be a simple approach.
bot checks if the branch still exists before final reporting.

thanks!

> 
> > we will check the latest branch in your repo before reporting
> > in the future.
> 
> Thanks!
> 
> -- 
> Cheers,
> Harry / Hyeonggon