Linux CXL
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.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 8/9] cxl/mbox: Block immediate mode in SET_PARTITION_INFO command
Date: Fri, 25 Mar 2022 17:31:01 -0700	[thread overview]
Message-ID: <20220326003101.GA1153706@alison-desk> (raw)
In-Reply-To: <20220325111816.00005cf8@huawei.com>

On Fri, Mar 25, 2022 at 11:18:16AM +0000, Jonathan Cameron wrote:
> On Wed, 23 Mar 2022 18:11:25 -0700
> alison.schofield@intel.com wrote:
> 
> > From: Alison Schofield <alison.schofield@intel.com>
> > 
> > User space may send the SET_PARTITION_INFO mailbox command using
> > the IOCTL interface. Inspect the input payload and fail if the
> > immediate flag is set.
> > 
> > This is the first instance of the driver inspecting an input payload
> > from user space. Assume there will be more such cases and implement
> > with an extensible helper.
> > 
> > In order for the kernel to react to an immediate partition change it
> > needs to assert that the change will not affect any active decode. At
> > a minimum this requires validating that the device is using HDM
> > decoders instead of the CXL DVSEC for decode, and that none of the
> > active HDM decoders are affected by the partition change. For now,
> > just fail until that support arrives.
> > 
> > Signed-off-by: Alison Schofield <alison.schofield@intel.com>
> 
> Follow on comment from one in earlier patch on the use of a goto
> to skip the input payload case... Otherwise,
> 
> Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
snip
> >  static int cxl_to_mbox_cmd(struct cxl_dev_state *cxlds,
> >  			   struct cxl_mbox_cmd *mbox, u16 opcode,
> >  			   size_t in_size, size_t out_size, u64 in_payload)
> > @@ -235,6 +269,13 @@ static int cxl_to_mbox_cmd(struct cxl_dev_state *cxlds,
> >  	if (!mbox->payload_in)
> >  		return PTR_ERR(mbox->payload_in);
> >  
> > +	if (!cxl_payload_from_user_allowed(opcode, mbox->payload_in)) {
> > +		dev_dbg(cxlds->dev, "%s: input payload not allowed\n",
> > +			cxl_mem_opcode_to_name(opcode));
> > +		kvfree(mbox->payload_in);
> > +		return -EBUSY;
> > +	}
> 
> Ah. This is making the block before the label larger. I'm still doubtful that
> the code is more readable with the goto though rather than just having
> it indented one more tab.
> 
You remembered my goto from a few patches back and still don't
appreciate it ;)
Will redo.
Thanks for the reviews Jonathan!


  reply	other threads:[~2022-03-26  0:28 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
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 [this message]
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=20220326003101.GA1153706@alison-desk \
    --to=alison.schofield@intel.com \
    --cc=Jonathan.Cameron@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox