All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] IB/mlx5: add checking for "vf" from do_setvfinfo()
Date: Mon, 15 Apr 2019 09:32:31 +0000	[thread overview]
Message-ID: <20190415093231.GN6095@kadam> (raw)
In-Reply-To: <20190412175504.GA20857@kadam>

On Fri, Apr 12, 2019 at 08:25:05PM +0000, Parav Pandit wrote:
> 
> 
> > -----Original Message-----
> > From: linux-rdma-owner@vger.kernel.org <linux-rdma-
> > owner@vger.kernel.org> On Behalf Of Dan Carpenter
> > Sent: Friday, April 12, 2019 12:55 PM
> > To: Leon Romanovsky <leon@kernel.org>; Eli Cohen <eli@mellanox.com>
> > Cc: Doug Ledford <dledford@redhat.com>; Jason Gunthorpe <jgg@ziepe.ca>;
> > linux-rdma@vger.kernel.org; kernel-janitors@vger.kernel.org
> > Subject: [PATCH] IB/mlx5: add checking for "vf" from do_setvfinfo()
> > 
> > My static checker complains that these "vf" variables come from the user in
> > do_setvfinfo() and haven't been checked to make sure they're valid.
> > 
> > Fixes: eff901d30e6c ("IB/mlx5: Implement callbacks for manipulating VFs")
> > Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
> > ---
> > Untested static checker stuff.  Please review carefully.
> > 
> >  drivers/infiniband/hw/mlx5/ib_virt.c | 6 ++++++
> >  1 file changed, 6 insertions(+)
> > 
> > diff --git a/drivers/infiniband/hw/mlx5/ib_virt.c
> > b/drivers/infiniband/hw/mlx5/ib_virt.c
> > index 649a3364f838..9a8eebe3d462 100644
> > --- a/drivers/infiniband/hw/mlx5/ib_virt.c
> > +++ b/drivers/infiniband/hw/mlx5/ib_virt.c
> > @@ -56,6 +56,9 @@ int mlx5_ib_get_vf_config(struct ib_device *device, int
> > vf, u8 port,
> >  	struct mlx5_hca_vport_context *rep;
> >  	int err;
> > 
> > +	if (vf < 0 || vf >= pci_sriov_get_totalvfs(mdev->pdev))
> > +		return -EINVAL;
> > +
> I traced back ndo_get_vf_config and friend functions. vf number is u32 from user space.
> 
> And all the VF operations at ndo ops level and at driver level should be changed from int to u32.
> After that vf < 0 check is not needed.
> 
> >  	rep = kzalloc(sizeof(*rep), GFP_KERNEL);
> >  	if (!rep)
> >  		return -ENOMEM;
> > @@ -99,6 +102,9 @@ int mlx5_ib_set_vf_link_state(struct ib_device *device,
> > int vf,
> >  	struct mlx5_vf_context *vfs_ctx = mdev->priv.sriov.vfs_ctx;
> >  	int err;
> > 
> > +	if (vf < 0 || vf >= pci_sriov_get_totalvfs(mdev->pdev))
> > +		return -EINVAL;
> > +
> We are currently working on a patch to post in mid-May to not have access to pdev in this file.
> If the vf > desired value, HCA firmware should be failing this command too.

I'm not sure what you want me to do with this information.  :P

regards,
dan carpenter

  parent reply	other threads:[~2019-04-15  9:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-12 17:55 [PATCH] IB/mlx5: add checking for "vf" from do_setvfinfo() Dan Carpenter
2019-04-12 20:25 ` Parav Pandit
2019-04-15  9:32 ` Dan Carpenter [this message]
2019-04-15  9:46 ` Dan Carpenter
2019-04-15 20:04 ` Parav Pandit
2019-04-16  8:21 ` Dan Carpenter
2019-04-16 22:54 ` Parav Pandit
2019-04-22  8:08 ` Dan Carpenter
2019-04-22 15:09 ` Parav Pandit
2019-04-23 15:49 ` Dan Carpenter
2019-04-23 22:32 ` Parav Pandit
2019-04-24 14:08   ` Dan Carpenter
2019-04-24 14:08     ` Dan Carpenter
2019-04-24 14:24     ` Jason Gunthorpe
2019-04-24 14:24       ` Jason Gunthorpe
2019-04-24 22:12       ` Parav Pandit
2019-04-25  0:36     ` Jakub Kicinski
2019-04-25  0:36       ` Jakub Kicinski
2019-04-25  6:15     ` Parav Pandit
2019-09-24  9:21       ` Dan Carpenter
2019-09-24  9:21         ` Dan Carpenter
2019-09-25 17:14         ` Parav Pandit

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=20190415093231.GN6095@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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.