From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Alok Tiwari <alok.a.tiwari@oracle.com>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y] RDMA/srpt: Support specifying the srpt_service_guid parameter
Date: Thu, 3 Apr 2025 12:13:51 -0400 [thread overview]
Message-ID: <20250403115342-4427a17a0370402b@stable.kernel.org> (raw)
In-Reply-To: <20250403125955.2553106-1-alok.a.tiwari@oracle.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: fdfa083549de5d50ebf7f6811f33757781e838c0
WARNING: Author mismatch between patch and upstream commit:
Backport author: Alok Tiwari<alok.a.tiwari@oracle.com>
Commit author: Bart Van Assche<bvanassche@acm.org>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: fe2a73d57319)
6.1.y | Present (different SHA1: aee4dcfe1721)
5.15.y | Present (different SHA1: 989af2f29342)
5.10.y | Present (different SHA1: 5a5c039dac1b)
Note: The patch differs from the upstream commit:
---
1: fdfa083549de5 ! 1: f0d286e4cef27 RDMA/srpt: Support specifying the srpt_service_guid parameter
@@ Metadata
## Commit message ##
RDMA/srpt: Support specifying the srpt_service_guid parameter
+ [ Upstream commit fdfa083549de5d50ebf7f6811f33757781e838c0 ]
+
Make loading ib_srpt with this parameter set work. The current behavior is
that setting that parameter while loading the ib_srpt kernel module
triggers the following kernel crash:
@@ Commit message
Signed-off-by: Bart Van Assche <bvanassche@acm.org>
Link: https://lore.kernel.org/r/20240205004207.17031-1-bvanassche@acm.org
Signed-off-by: Leon Romanovsky <leon@kernel.org>
+ Signed-off-by: Sasha Levin <sashal@kernel.org>
+ [Alok: Backport to 5.4.y since the commit has already been backported to
+ 5.15y, 5.10.y, and 4.19.y]
+ Signed-off-by: Alok Tiwari <alok.a.tiwari@oracle.com>
## drivers/infiniband/ulp/srpt/ib_srpt.c ##
@@ drivers/infiniband/ulp/srpt/ib_srpt.c: module_param(srpt_srq_size, int, 0444);
@@ drivers/infiniband/ulp/srpt/ib_srpt.c: module_param(srpt_srq_size, int, 0444);
+}
static int srpt_get_u64_x(char *buffer, const struct kernel_param *kp)
{
- return sprintf(buffer, "0x%016llx\n", *(u64 *)kp->arg);
+ return sprintf(buffer, "0x%016llx", *(u64 *)kp->arg);
}
-module_param_call(srpt_service_guid, NULL, srpt_get_u64_x, &srpt_service_guid,
- 0444);
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.4.y | Success | Success |
next prev parent reply other threads:[~2025-04-03 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-03 12:59 [PATCH 5.4.y] RDMA/srpt: Support specifying the srpt_service_guid parameter Alok Tiwari
2025-04-03 16:13 ` Sasha Levin [this message]
2025-04-04 13:40 ` Zhu Yanjun
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=20250403115342-4427a17a0370402b@stable.kernel.org \
--to=sashal@kernel.org \
--cc=alok.a.tiwari@oracle.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.