From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Matt Fleming <matt@readmodwrite.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] net/mlx5: unique names for per device caches
Date: Wed, 11 Dec 2024 11:32:23 -0500 [thread overview]
Message-ID: <20241211080902-2e0f0ddb7bde5096@stable.kernel.org> (raw)
In-Reply-To: <20241210210723.3227571-1-mfleming@cloudflare.com>
[ Sasha's backport helper bot ]
Hi,
The upstream commit SHA1 provided is correct: 25872a079bbbe952eb660249cc9f40fa75623e68
WARNING: Author mismatch between patch and upstream commit:
Backport author: Matt Fleming <matt@readmodwrite.com>
Commit author: Sebastian Ott <sebott@redhat.com>
Status in newer kernel trees:
6.12.y | Not found
Note: The patch differs from the upstream commit:
---
1: 25872a079bbbe ! 1: 48fb546e12d61 net/mlx5: unique names for per device caches
@@ Metadata
## Commit message ##
net/mlx5: unique names for per device caches
+ [ Upstream commit 25872a079bbbe952eb660249cc9f40fa75623e68 ]
+
Add the device name to the per device kmem_cache names to
ensure their uniqueness. This fixes warnings like this:
"kmem_cache of name 'mlx5_fs_fgs' already exists".
+ Fixes: 4c39529663b9 ("slab: Warn on duplicate cache names when DEBUG_VM=y")
Signed-off-by: Sebastian Ott <sebott@redhat.com>
Reviewed-by: Breno Leitao <leitao@debian.org>
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>
Link: https://patch.msgid.link/20241023134146.28448-1-sebott@redhat.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+ Signed-off-by: Matt Fleming <mfleming@cloudflare.com>
## drivers/net/ethernet/mellanox/mlx5/core/fs_core.c ##
@@ drivers/net/ethernet/mellanox/mlx5/core/fs_core.c: void mlx5_fs_core_free(struct mlx5_core_dev *dev)
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.12.y | Success | Success |
| stable/linux-6.6.y | Success | Success |
| stable/linux-6.1.y | Success | Success |
| stable/linux-5.15.y | Failed | N/A |
| stable/linux-5.10.y | Failed | N/A |
| stable/linux-5.4.y | Failed | N/A |
next prev parent reply other threads:[~2024-12-11 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 21:07 [PATCH] net/mlx5: unique names for per device caches Matt Fleming
2024-12-11 16:32 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-20 14:33 Sebastian Ott
2024-09-20 16:32 ` Parav Pandit
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=20241211080902-2e0f0ddb7bde5096@stable.kernel.org \
--to=sashal@kernel.org \
--cc=matt@readmodwrite.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.