From: Ilia Kolominsky <ikolomin@amazon.com>
To: <jgg@nvidia.com>, <leon@kernel.org>, <linux-rdma@vger.kernel.org>
Cc: <sleybo@amazon.com>, <matua@amazon.com>, <gal.pressman@linux.dev>,
"Michael Margolin" <mrgolin@amazon.com>,
Yonatan Nachum <ynachum@amazon.com>
Subject: [PATCH for-next 2/3] RDMA/efa: Report the admin RESOURCE_BUSY status as EBUSY
Date: Mon, 9 Nov 2026 08:13:48 +0000 [thread overview]
Message-ID: <20261109081349.27316-3-ikolomin@amazon.com> (raw)
In-Reply-To: <20261109081349.27316-1-ikolomin@amazon.com>
The device completes a command with RESOURCE_BUSY when the object it
targets is still in use, for example a destroy of an object that other
objects still reference. Map that status to EBUSY instead of the generic
EINVAL so that callers can tell the two apart.
Reviewed-by: Michael Margolin <mrgolin@amazon.com>
Reviewed-by: Yonatan Nachum <ynachum@amazon.com>
Signed-off-by: Ilia Kolominsky <ikolomin@amazon.com>
---
drivers/infiniband/hw/efa/efa_com.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/infiniband/hw/efa/efa_com.c b/drivers/infiniband/hw/efa/efa_com.c
index 9c59d127e..e8045b43f 100644
--- a/drivers/infiniband/hw/efa/efa_com.c
+++ b/drivers/infiniband/hw/efa/efa_com.c
@@ -584,6 +584,8 @@ static int efa_com_comp_status_to_errno(u8 comp_status)
case EFA_ADMIN_ILLEGAL_PARAMETER:
case EFA_ADMIN_UNKNOWN_ERROR:
return -EINVAL;
+ case EFA_ADMIN_RESOURCE_BUSY:
+ return -EBUSY;
default:
return -EINVAL;
}
--
2.47.3
next prev parent reply other threads:[~2026-11-09 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 8:13 [PATCH for-next 0/3] RDMA/efa: Add Completion Actions support Ilia Kolominsky
2026-11-09 8:13 ` [PATCH for-next 1/3] RDMA/efa: Update device interface Ilia Kolominsky
2026-11-09 8:17 ` sashiko-bot
2026-11-09 8:13 ` Ilia Kolominsky [this message]
2026-11-09 8:19 ` [PATCH for-next 2/3] RDMA/efa: Report the admin RESOURCE_BUSY status as EBUSY sashiko-bot
2026-11-09 8:13 ` [PATCH for-next 3/3] RDMA/efa: Add Completion Actions support Ilia Kolominsky
2026-11-09 8:26 ` sashiko-bot
2026-11-12 11:06 ` [PATCH for-next 0/3] " Ilia Kolominsky
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=20261109081349.27316-3-ikolomin@amazon.com \
--to=ikolomin@amazon.com \
--cc=gal.pressman@linux.dev \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@amazon.com \
--cc=sleybo@amazon.com \
--cc=ynachum@amazon.com \
/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