Re: [harry:kmalloc-no-objext-rfc-v1r3] [mm/slab] d6967566f4: RIP:mark_obj_codetag_empty

Harry Yoo <[email protected]> Thu, 16 Jul 2026 19:32:56 +0900
Newsgroups dev.linux.lists.oe-lkp
Message-ID <[email protected]>
Hi Oliver,

On 7/16/26 4:47 PM, Oliver Sang wrote:
> hi, Harry,
> 
> On Thu, Jul 16, 2026 at 11:27:11AM +0900, Harry Yoo wrote:
>>
>> Thanks for reporting!
>>
>> Indeed I've seen this false warning and it was fixed in v2.
>>
> 
> thanks a lot for information!
> 
> I remember I checked if the branch is latest when reporting, now I check again:
> 
>   kmalloc-no-objext-rfc-v1r2
>   kmalloc-no-objext-rfc-v1r3
>   kmalloc-no-objext-v2r1    <-----
>   kmalloc-no-objext-v2r2
>   kmalloc-no-objext-v3r1
> 
> oh, I guess kmalloc-no-objext-v* is the following version to kmalloc-no-objext-rfc-v*,
> am I right?

That's correct.

It usually starts w/ RFC, then at some point I drop RFC and
advance the version number.

For example,

<name>-rfc-v1r1,
<name>-rfc-v2r1
<name>-rfc-v2r2 # drop RFC in the next version
<name>-v3r1,
<name>-v4r1,
<name>-v4r2,

[...]

> will be more careful in the future. sorry for noise.

No worries, and thanks for testing, as always!

-- 
Cheers,
Harry / Hyeonggon