From: Richard Cheng <icheng@nvidia.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: dave@stgolabs.net, jic23@kernel.org, alison.schofield@intel.com,
vishal.l.verma@intel.com, iweiny@kernel.org,
ming.li@zohomail.com, gourry@gourry.net, rrichter@amd.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
kees@kernel.org, newtonl@nvidia.com, kristinc@nvidia.com,
kaihengf@nvidia.com, kobak@nvidia.com
Subject: Re: [PATCH v6 7/7] cxl/fwctl: Propagate feature RPC delivery errors
Date: Fri, 28 Aug 2026 16:38:07 +0800 [thread overview]
Message-ID: <apFIzMv83ZpPm6MJ@MWDK4CY14F> (raw)
In-Reply-To: <e3447007-4bc7-46f5-9bd5-f59b84d6113e@intel.com>
On Thu, Aug 27, 2026 at 03:11:09PM +0800, Dave Jiang wrote:
>
>
> On 8/25/26 6:45 PM, Richard Cheng wrote:
> > FWCTL_RPC requires delivery failures to be returned as ioctl errors,
> > while device errors are reported in the output. Get and Set Feature
> > instead converted all failures into normal responses, sometimes with a
> > SUCCESS device status.
> >
> > Initialize the return code to SUCCESS. When the helper fails without a
> > device error code, return its errno. Continue reporting actual device
> > errors through rpc_out->retval.
> >
> > Fixes: 5908f3ed6dc2 ("cxl: Add support to handle user feature commands for get feature")
> > Fixes: eb5dfcb9e36d ("cxl: Add support to handle user feature commands for set feature")
> > Signed-off-by: Richard Cheng <icheng@nvidia.com>
> > ---
> > Changelog:
> >
> > v1 -> v2:
> > - Remove redundant CXL_MBOX_CMD_RC_SUCCESS assignments. (Dave Jiang)
> >
> > ---
> > drivers/cxl/core/features.c | 14 +++++++-------
> > 1 file changed, 7 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/cxl/core/features.c b/drivers/cxl/core/features.c
> > index 8d44ce829497..28b326df3398 100644
> > --- a/drivers/cxl/core/features.c
> > +++ b/drivers/cxl/core/features.c
> > @@ -232,7 +232,7 @@ ssize_t cxl_get_feature(struct cxl_mailbox *cxl_mbox, const uuid_t *feat_uuid,
> > int rc;
> >
> > if (return_code)
> > - *return_code = CXL_MBOX_CMD_RC_INPUT;
> > + *return_code = CXL_MBOX_CMD_RC_SUCCESS;
> >
> > if (!feat_out || !feat_out_size)
> > return -EINVAL;
> > @@ -267,9 +267,6 @@ ssize_t cxl_get_feature(struct cxl_mailbox *cxl_mbox, const uuid_t *feat_uuid,
> > data_rcvd_size += mbox_cmd.size_out;
> > } while (data_rcvd_size < feat_out_size);
> >
> > - if (return_code)
> > - *return_code = CXL_MBOX_CMD_RC_SUCCESS;
> > -
> > return data_rcvd_size;
> > }
> >
> > @@ -289,7 +286,7 @@ int cxl_set_feature(struct cxl_mailbox *cxl_mbox,
> > size_t hdr_size;
> >
> > if (return_code)
> > - *return_code = CXL_MBOX_CMD_RC_INPUT;
> > + *return_code = CXL_MBOX_CMD_RC_SUCCESS;
> >
> > if (feat_data_size > U16_MAX - offset)
> > return -EINVAL;
> > @@ -341,8 +338,6 @@ int cxl_set_feature(struct cxl_mailbox *cxl_mbox,
> >
> > data_sent_size += data_in_size;
> > if (data_sent_size >= feat_data_size) {
> > - if (return_code)
> > - *return_code = CXL_MBOX_CMD_RC_SUCCESS;
> > return 0;
> > }
>
> Minor. the {} can now go.
>
Ahh sure, thanks, I'll remove it in v7.
Best regards,
Richard Cheng.
> >
> > @@ -492,6 +487,9 @@ static void *cxlctl_get_feature(struct cxl_features_state *cxlfs,
> > data_size = cxl_get_feature(cxl_mbox, &feat_in->uuid,
> > feat_in->selection, rpc_out->payload,
> > count, offset, &return_code);
> > + if (data_size < 0 &&
>
> Do we need to handle the 'data_size == 0' case here?
>
> > + return_code == CXL_MBOX_CMD_RC_SUCCESS)
> > + return ERR_PTR(data_size);
> > *out_len = sizeof(struct fwctl_rpc_cxl_out);
> > if (data_size <= 0) {
> > rpc_out->size = 0;
> > @@ -544,6 +542,8 @@ static void *cxlctl_set_feature(struct cxl_features_state *cxlfs,
> > rc = cxl_set_feature(cxl_mbox, &feat_in->uuid,
> > feat_in->version, feat_in->feat_data,
> > data_size, flags, offset, &return_code);
> > + if (rc && return_code == CXL_MBOX_CMD_RC_SUCCESS)
> > + return ERR_PTR(rc);
> > *out_len = sizeof(*rpc_out);
> > if (rc) {
> > rpc_out->retval = return_code;
>
>
> We may also need to add something like this because of the change of default return code. The code segment is similar to cxl_xfer_log().
>
> diff --git a/drivers/cxl/core/features.c b/drivers/cxl/core/features.c
> index 28b326df3398..2e62f3720072 100644
> --- a/drivers/cxl/core/features.c
> +++ b/drivers/cxl/core/features.c
> @@ -259,6 +259,17 @@ ssize_t cxl_get_feature(struct cxl_mailbox *cxl_mbox, const uuid_t *feat_uuid,
> .min_out = data_to_rd_size,
> };
> rc = cxl_internal_send_cmd(cxl_mbox, &mbox_cmd);
> + /*
> + * Per CXL r4.0 8.2.10.6.2, when Offset + Count runs past the
> + * end of the Feature the device returns only the bytes up to
> + * the Feature size. cxl_internal_send_cmd() reports that as
> + * -EIO with a short payload, so stop and return what arrived.
> + */
> + if (rc == -EIO && mbox_cmd.size_out &&
> + mbox_cmd.size_out < data_to_rd_size) {
> + data_rcvd_size += mbox_cmd.size_out;
> + break;
> + }
> if (rc < 0 || !mbox_cmd.size_out) {
> if (return_code)
> *return_code = mbox_cmd.return_code;
prev parent reply other threads:[~2026-08-28 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 1:45 [PATCH v6 0/7] cxl: Sashiko bug fixes Richard Cheng
2026-08-26 1:45 ` [PATCH v6 1/7] cxl/features: Reject feature offset that overflows 16-bit field Richard Cheng
2026-08-27 22:55 ` Dave Jiang
2026-08-26 1:45 ` [PATCH v6 2/7] cxl/region: Scan all partitions for unmapped poison Richard Cheng
2026-08-26 1:57 ` sashiko-bot
2026-08-26 1:45 ` [PATCH v6 3/7] cxl/region: Don't leak tolerated RAM -EFAULT from unmapped poison scan Richard Cheng
2026-08-26 1:45 ` [PATCH v6 4/7] cxl/region: Start unmapped poison scan at the committed decoder boundary Richard Cheng
2026-08-28 17:56 ` Alison Schofield
2026-08-26 1:45 ` [PATCH v6 5/7] cxl/memdev: Don't overwrite the error from an earlier partition poison query Richard Cheng
2026-08-26 1:56 ` sashiko-bot
2026-08-26 1:45 ` [PATCH v6 6/7] cxl/region: Reject poison scan for decoder without a partition Richard Cheng
2026-08-26 1:57 ` sashiko-bot
2026-08-26 1:45 ` [PATCH v6 7/7] cxl/fwctl: Propagate feature RPC delivery errors Richard Cheng
2026-08-27 22:11 ` Dave Jiang
2026-08-28 8:38 ` Richard Cheng [this message]
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=apFIzMv83ZpPm6MJ@MWDK4CY14F \
--to=icheng@nvidia.com \
--cc=alison.schofield@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=kaihengf@nvidia.com \
--cc=kees@kernel.org \
--cc=kobak@nvidia.com \
--cc=kristinc@nvidia.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=newtonl@nvidia.com \
--cc=rrichter@amd.com \
--cc=vishal.l.verma@intel.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