All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: "Verma, Vishal L" <vishal.l.verma@intel.com>,
	"Schofield, Alison" <alison.schofield@intel.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"Cs, Abhi" <abhi.cs@intel.com>,
	"Weiny, Ira" <ira.weiny@intel.com>
Subject: Re: [PATCH] cxl/mbox: Fix missing variable payload checks in cmd size validation
Date: Tue, 28 Jun 2022 14:52:20 -0700	[thread overview]
Message-ID: <62bb7814e502f_1bc66e2945a@dwillia2-xfh.notmuch> (raw)
In-Reply-To: <bb3eea9a46c1cfb28d20c6f253ac5c8bd13e8412.camel@intel.com>

Verma, Vishal L wrote:
> On Tue, 2022-06-28 at 14:42 -0700, Alison Schofield wrote:
> > On Tue, Jun 28, 2022 at 01:04:27PM -0700, Vishal Verma wrote:
> > > The conversion of command sizes to unsigned missed a couple of
> > > checks
> > > against variable size payloads during command validation, which
> > > made all
> > > variable payload commands unconditionally fail. Add the checks back
> > > using
> > > the new CXL_VARIABLE_PAYLOAD scheme.
> > > 
> > > Reported-by: Abhi Cs <abhi.cs@intel.com>
> > > Fixes: 26f89535a5bb ("cxl/mbox: Use type __u32 for mailbox payload
> > > sizes")
> > > Cc: <stable@vger.kernel.org>
> > > Cc: Ira Weiny <ira.weiny@intel.com>
> > > Cc: Dan Williams <dan.j.williams@intel.com>
> > > Cc: Alison Schofield <alison.schofield@intel.com>
> > > Signed-off-by: Vishal Verma <vishal.l.verma@intel.com>
> > 
> > with one caveat below...
> > Reviewed-by: Alison Schofield <alison.schofield@intel.com>
> 
> Thanks for the review!
> 
> 
> > > ---
> > >  drivers/cxl/core/mbox.c | 10 ++++++----
> > >  1 file changed, 6 insertions(+), 4 deletions(-)
> > > 
> > > diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
> > > index 40e3ccb2bf3e..d929b89d12a7 100644
> > > --- a/drivers/cxl/core/mbox.c
> > > +++ b/drivers/cxl/core/mbox.c
> > > @@ -355,12 +355,14 @@ static int cxl_to_mem_cmd(struct
> > > cxl_mem_command *mem_cmd,
> > >                 return -EBUSY;
> > >  
> > >         /* Check the input buffer is the expected size */
> > > -       if (info->size_in != send_cmd->in.size)
> > > -               return -ENOMEM;
> > > +       if (info->size_in != CXL_VARIABLE_PAYLOAD)
> > > +               if (info->size_in != send_cmd->in.size)
> > > +                       return -ENOMEM;
> > 
> > We can leave it to Dan to arbitrate, but I don't think nested
> > if's without brackets follow kernel coding style.
> > 
> > However, Dan didn't like my nested if's with brackets either.
> > He'd prefer using &&
> 
> Ha funny - I had && originally, but then I spotted nested if () a few
> lines above in the same file in cxl_mbox_send_cmd(), and switched to
> the same style :)
> 
> I'd be happy to change to &&.

Yeah, lets go that route.

/me thanks Alison for catching it.

  reply	other threads:[~2022-06-28 21:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 20:04 [PATCH] cxl/mbox: Fix missing variable payload checks in cmd size validation Vishal Verma
2022-06-28 21:42 ` Alison Schofield
2022-06-28 21:46   ` Verma, Vishal L
2022-06-28 21:52     ` Dan Williams [this message]
2022-06-28 21:49 ` Dan Williams

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=62bb7814e502f_1bc66e2945a@dwillia2-xfh.notmuch \
    --to=dan.j.williams@intel.com \
    --cc=abhi.cs@intel.com \
    --cc=alison.schofield@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=stable@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.