From: Vlastimil Babka <vbabka@suse.cz>
To: Xiongwei Song <sxwbruce@gmail.com>, Sasha Levin <sashal@kernel.org>
Cc: brauner@kernel.org, viro@zeniv.linux.org.uk,
Linus Torvalds <torvalds@linux-foundation.org>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: Re: [GIT PULL] slab updates for 6.13
Date: Sun, 17 Nov 2024 22:01:57 +0100 [thread overview]
Message-ID: <d7d5fa1f-f696-44f7-8384-6ba982bff8ec@suse.cz> (raw)
In-Reply-To: <CALy5rjW-rOAUDuFVVL67yRXhyVUjWa_9saE2HBTGbyAfUV53kA@mail.gmail.com>
On 11/17/24 13:56, Xiongwei Song wrote:
> It seems there is a conflict between fc0eac57d08c ("slab: pull kmem_cache_open()
> into do_kmem_cache_create()") and 543c5bde72e9 ("mm/slab: Allow cache creation
> to proceed even if sysfs registration fails"). The err is initialized
No conflict, commit fc0eac57d08c is from 6.12-rc1, there's no merge here.
I've introduced the bug by trying to improve Hyeonggon's patch and he
quickly corrected me [1] so the buggy version never even made it to -next.
But here I managed to resurrect it before the git pull.
[1] https://lore.kernel.org/all/195242b4-5471-419a-a350-08fd246973f0@suse.cz/
> to -EINVAL in
> the entry of do_kmem_cache_create(), sysfs_slab_add() call can assign
> a value to
> err normally, but the assignment to err variable has been removed in
> Hyeonggon's
> patch, so do_kmem_cache_create() returns -EINVAL normally. We probably can do
> the following fix:
>
> diff --git a/mm/slub.c b/mm/slub.c
> index 73eea67a306b..19630a2da8e1 100644
> --- a/mm/slub.c
> +++ b/mm/slub.c
> @@ -6199,9 +6199,11 @@ int do_kmem_cache_create(struct kmem_cache *s,
> const char *name,
> if (!alloc_kmem_cache_cpus(s))
> goto out;
>
> + /* The error code is not needed any more. */
> + err = 0;
> +
> /* Mutex is not taken during early boot */
> if (slab_state <= UP) {
> - err = 0;
That was indeed the fix.
> goto out;
> }
>
> Regards,
> Xiongwei
>
> On Sun, Nov 17, 2024 at 11:42 AM Sasha Levin <sashal@kernel.org> wrote:
>>
>> On Sat, Nov 16, 2024 at 09:43:07PM +0100, Vlastimil Babka wrote:
>> >On 11/16/24 16:35, Sasha Levin wrote:
>> >> [ Obviously I fat-fingered it and didn't add Christian or Al ]
>> >
>> >I have found the problem and looks like I managed to force push an older
>> >broken version of a branch, possibly due to switching between two computers.
>> >Serves me well for amending in some last minute R-b tags. Doing git diff
>> >@{u} to check for unexpected suprirses before pushing the result didn't help
>> >this time, either I forgot or was blind.
>> >
>> >I have deleted the slab-for-6.13 signed tag and pushed the fixed branch only
>> >to -next. Thanks a lot Sasha for catching this early and please drop the
>> >merge from the for-linus tree.
>>
>> I've dropped the merge and tests are passing now, thanks!
>>
>> --
>> Thanks,
>> Sasha
>>
prev parent reply other threads:[~2024-11-17 21:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 14:22 Vlastimil Babka
2024-11-16 15:32 ` Sasha Levin
2024-11-16 15:35 ` Sasha Levin
2024-11-16 20:43 ` Vlastimil Babka
2024-11-17 3:41 ` Sasha Levin
2024-11-17 12:56 ` Xiongwei Song
2024-11-17 21:01 ` Vlastimil Babka [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=d7d5fa1f-f696-44f7-8384-6ba982bff8ec@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=sashal@kernel.org \
--cc=sxwbruce@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox