mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: Eric Van Hensbergen <ericvh@kernel.org>,
	Dominique Martinet <asmadeus@codewreck.org>,
	Christian Schoenebeck <linux_oss@crudebyte.com>,
	v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
	regressions@lists.linux.dev
Subject: Re: [PATCH] 9p: Avoid creating multiple slab caches with the same name
Date: Fri, 18 Oct 2024 14:28:04 -0300	[thread overview]
Message-ID: <20241018172804.GA2151929@nvidia.com> (raw)
In-Reply-To: <20240807094725.2193423-1-pedro.falcato@gmail.com>

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?

It is causing regressions in my environment

#regzbot introduced: 4c39529663b9

Thanks,
Jason

  reply	other threads:[~2024-10-18 17:28 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 [this message]
2024-10-18 18:36   ` Pedro Falcato
2024-10-18 18:54     ` Thorsten Leemhuis
2024-10-18 21:38       ` Vlastimil Babka
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=20241018172804.GA2151929@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=asmadeus@codewreck.org \
    --cc=ericvh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_oss@crudebyte.com \
    --cc=pedro.falcato@gmail.com \
    --cc=regressions@lists.linux.dev \
    --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®