From: Vlastimil Babka <vbabka@suse.cz>
To: Thorsten Leemhuis <regressions@leemhuis.info>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dominique Martinet <asmadeus@codewreck.org>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
Christian Schoenebeck <linux_oss@crudebyte.com>,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, Jason Gunthorpe <jgg@nvidia.com>,
Pedro Falcato <pedro.falcato@gmail.com>
Subject: Re: [PATCH] 9p: Avoid creating multiple slab caches with the same name
Date: Fri, 18 Oct 2024 23:38:04 +0200 [thread overview]
Message-ID: <b6852c2d-3371-47a4-bfeb-049f4048e88a@suse.cz> (raw)
In-Reply-To: <1cb07628-269c-4d6c-9936-f3a2b233165f@leemhuis.info>
On 10/18/24 8:54 PM, Thorsten Leemhuis wrote:
> [reinserting a bit of quotation below for Linus]
>
> TLDR: Linus, I wonder if it would be best if you could merge the patch
> at the start of this thread
> (https://lore.kernel.org/all/20240807094725.2193423-1-pedro.falcato@gmail.com/
> ), which can also be found as 79efebae4afc22 in -next if you prefer to
> cherry-pick it from there. Either now or after 24 to 36 hours, which
> would give Eric a chance to ACK/NACK this if he sees this mail.
>
> For details see below.
>
> On 18.10.24 20:36, Pedro Falcato wrote:
>> On Fri, Oct 18, 2024 at 6:28 PM Jason Gunthorpe <jgg@nvidia.com> wrote:
>>>
>>> On Wed, Aug 07, 2024 at 10:47:25AM +0100, Pedro Falcato wrote:
>>>> In the spirit of [1], avoid creating multiple slab caches with the same
>>>> name. Instead, add the dev_name into the mix.
>>>>
>>>> [1]: https://lore.kernel.org/all/20240807090746.2146479-1-pedro.falcato@gmail.com/
>>>>
>>>> Signed-off-by: Pedro Falcato <pedro.falcato@gmail.com>
>>>> ---
>>>> net/9p/client.c | 10 +++++++++-
>>>> 1 file changed, 9 insertions(+), 1 deletion(-)
>>>
>>> Can this get picked up to rc4 please?
>
> Eric apparently has not much time or upstream work currently (but
> recently showed up in a discussion about another regression:
> https://lore.kernel.org/all/Zw-J0DdrCFLYpT5y@codewreck.org/ ).
>
>>> It is causing regressions in my environment
>>> #regzbot introduced: 4c39529663b9
>
> If anyone wonders, that is 4c39529663b931 ("slab: Warn on duplicate
> cache names when DEBUG_VM=y") [v6.12-rc1]. That's also why I'm CCing
> Vlastimil, so he knows about this.
>
>> FWIW, seems to have been picked up into 9pfs-next
>> (https://github.com/martinetd/linux/commit/79efebae4afc2221fa814c3cae001bede66ab259).
>> Seems like we're just missing a PR to Linus?
If was Dominique, not Eric, see:
https://lore.kernel.org/all/ZvBIl8b9RRK9jgtJ@codewreck.org/
Can you send it as mentioned in the email? :)
> In that case: Linus, given the circumstances I wonder if it would be
> best if you could merge the patch at the start of this thread
> (https://lore.kernel.org/all/20240807094725.2193423-1-pedro.falcato@gmail.com/
> ) directly, which can also be found as 79efebae4afc22 in -next if you
> prefer to cherry-pick it from there Either now or after 24 to 36 hours,
> which would give Eric a chance to ACK/NACK this if he sees this mail.
>
> Ciao, Thorsten
next prev parent reply other threads:[~2024-10-18 21:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 9:47 Pedro Falcato
2024-10-18 17:28 ` Jason Gunthorpe
2024-10-18 18:36 ` Pedro Falcato
2024-10-18 18:54 ` Thorsten Leemhuis
2024-10-18 21:38 ` Vlastimil Babka [this message]
2024-10-19 0:02 ` Dominique Martinet
2024-10-21 8:42 ` Vlastimil Babka
2024-10-21 18:37 ` Omar Sandoval
2024-10-21 18:57 ` Linus Torvalds
2024-10-21 20:06 ` Omar Sandoval
2024-10-21 23:00 ` Linus Torvalds
2024-10-21 20:18 ` Vlastimil Babka
2024-10-19 5:28 ` Linux regression tracking (Thorsten Leemhuis)
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=b6852c2d-3371-47a4-bfeb-049f4048e88a@suse.cz \
--to=vbabka@suse.cz \
--cc=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=jgg@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=pedro.falcato@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=v9fs@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®