From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: <alison.schofield@intel.com>
Cc: Ben Widawsky <ben.widawsky@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Ira Weiny <ira.weiny@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
<linux-cxl@vger.kernel.org>
Subject: Re: [PATCH v3 7/9] cxl/mbox: Move cxl_mem_command param to a local variable
Date: Fri, 25 Mar 2022 11:10:54 +0000 [thread overview]
Message-ID: <20220325111054.00004204@huawei.com> (raw)
In-Reply-To: <20220324011126.1144504-8-alison.schofield@intel.com>
On Wed, 23 Mar 2022 18:11:24 -0700
alison.schofield@intel.com wrote:
> From: Alison Schofield <alison.schofield@intel.com>
>
> cxl_validate_command_from_user() is now the single point of validation
> for mailbox commands coming from user space. Previously, it returned a
> a cxl_mem_command, but that was not sufficient when validation of the
> actual mailbox command became a requirement. Now, it returns a fully
> validated cxl_mbox_cmd.
>
> Remove the extraneous cxl_mem_command parameter. Define and use a
> local version only.
>
> Signed-off-by: Alison Schofield <alison.schofield@intel.com>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
> ---
> drivers/cxl/core/mbox.c | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
> index 0340399c7029..c323d6792405 100644
> --- a/drivers/cxl/core/mbox.c
> +++ b/drivers/cxl/core/mbox.c
> @@ -331,10 +331,9 @@ static int cxl_to_mem_cmd(struct cxl_dev_state *cxlds,
> }
>
> /**
> - * cxl_validate_cmd_from_user() - Check fields for CXL_MEM_SEND_COMMAND.
> + * cxl_validate_cmd_from_user() - Construct a valid cxl_mbox_cmd
> * @cxlds: The device data for the operation
> * @send_cmd: &struct cxl_send_command copied in from userspace.
> - * @out_cmd: Sanitized and populated &struct cxl_mem_command.
> * @mbox_cmd: Sanitized and populated &struct cxl_mbox_cmd.
> *
> * Return:
> @@ -345,16 +344,14 @@ static int cxl_to_mem_cmd(struct cxl_dev_state *cxlds,
> * * %-EPERM - Attempted to use a protected command.
> * * %-EBUSY - Kernel has claimed exclusive access to this opcode
> *
> - * The result of this command is a fully validated command in @out_cmd that is
> + * The result of this command is a fully validated command in @mbox_cmd that is
> * safe to send to the hardware.
> - *
> - * See handle_mailbox_cmd_from_user()
> */
> static int cxl_validate_cmd_from_user(struct cxl_dev_state *cxlds,
> const struct cxl_send_command *send_cmd,
> - struct cxl_mem_command *out_cmd,
> struct cxl_mbox_cmd *mbox_cmd)
> {
> + struct cxl_mem_command mem_cmd;
> int rc;
>
> if (send_cmd->id == 0 || send_cmd->id >= CXL_MEM_COMMAND_ID_MAX)
> @@ -370,16 +367,16 @@ static int cxl_validate_cmd_from_user(struct cxl_dev_state *cxlds,
>
> /* Sanitize and construct a cxl_mem_command */
> if (send_cmd->id == CXL_MEM_COMMAND_ID_RAW)
> - rc = cxl_to_mem_cmd_raw(cxlds, send_cmd, out_cmd);
> + rc = cxl_to_mem_cmd_raw(cxlds, send_cmd, &mem_cmd);
> else
> - rc = cxl_to_mem_cmd(cxlds, send_cmd, out_cmd);
> + rc = cxl_to_mem_cmd(cxlds, send_cmd, &mem_cmd);
>
> if (rc)
> return rc;
>
> /* Sanitize and construct a cxl_mbox_cmd */
> - rc = cxl_to_mbox_cmd(cxlds, mbox_cmd, out_cmd->opcode,
> - out_cmd->info.size_in, out_cmd->info.size_out,
> + rc = cxl_to_mbox_cmd(cxlds, mbox_cmd, mem_cmd.opcode,
> + mem_cmd.info.size_in, mem_cmd.info.size_out,
> send_cmd->in.payload);
>
> return rc;
> @@ -490,7 +487,6 @@ int cxl_send_cmd(struct cxl_memdev *cxlmd, struct cxl_send_command __user *s)
> struct cxl_dev_state *cxlds = cxlmd->cxlds;
> struct device *dev = &cxlmd->dev;
> struct cxl_send_command send;
> - struct cxl_mem_command c;
> struct cxl_mbox_cmd mbox_cmd;
> int rc;
>
> @@ -499,7 +495,7 @@ int cxl_send_cmd(struct cxl_memdev *cxlmd, struct cxl_send_command __user *s)
> if (copy_from_user(&send, s, sizeof(send)))
> return -EFAULT;
>
> - rc = cxl_validate_cmd_from_user(cxlmd->cxlds, &send, &c, &mbox_cmd);
> + rc = cxl_validate_cmd_from_user(cxlmd->cxlds, &send, &mbox_cmd);
> if (rc)
> return rc;
>
next prev parent reply other threads:[~2022-03-25 11:11 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 1:11 [PATCH v3 0/9] Do not allow set-partition immediate mode alison.schofield
2022-03-24 1:11 ` [PATCH v3 1/9] cxl/mbox: Move cxl_mem_command construction to helper funcs alison.schofield
2022-03-25 10:27 ` Jonathan Cameron
2022-03-26 0:01 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 2/9] cxl/mbox: Move raw command warning to raw command validation alison.schofield
2022-03-25 10:32 ` Jonathan Cameron
2022-03-24 1:11 ` [PATCH v3 3/9] cxl/mbox: Move build of user mailbox cmd to a helper function alison.schofield
2022-03-25 10:43 ` Jonathan Cameron
2022-03-24 1:11 ` [PATCH v3 4/9] cxl/mbox: Construct a users cxl_mbox_cmd in the validation path alison.schofield
2022-03-25 10:54 ` Jonathan Cameron
2022-03-26 0:37 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 5/9] cxl/mbox: Remove dependency on cxl_mem_command for a debug msg alison.schofield
2022-03-25 10:56 ` Jonathan Cameron
2022-03-26 0:26 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 6/9] cxl/mbox: Make handle_mailbox_cmd_from_user() use a mbox param alison.schofield
2022-03-25 11:04 ` Jonathan Cameron
2022-03-26 0:25 ` Alison Schofield
2022-03-29 10:50 ` Jonathan Cameron
2022-03-24 1:11 ` [PATCH v3 7/9] cxl/mbox: Move cxl_mem_command param to a local variable alison.schofield
2022-03-25 11:10 ` Jonathan Cameron [this message]
2022-03-24 1:11 ` [PATCH v3 8/9] cxl/mbox: Block immediate mode in SET_PARTITION_INFO command alison.schofield
2022-03-25 11:18 ` Jonathan Cameron
2022-03-26 0:31 ` Alison Schofield
2022-03-24 1:11 ` [PATCH v3 9/9] cxl/pmem: Remove CXL SET_PARTITION_INFO from exclusive_cmds list alison.schofield
2022-03-25 11:19 ` Jonathan Cameron
2022-03-25 10:34 ` [PATCH v3 0/9] Do not allow set-partition immediate mode Jonathan Cameron
2022-03-30 1:24 ` Dan Williams
2022-03-30 15:05 ` Jonathan Cameron
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=20220325111054.00004204@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=ben.widawsky@intel.com \
--cc=dan.j.williams@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--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 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.