netdev - Re: [PATCH net 2/2] net/mlx4_core: mlx4_init_slave() shouldn't access comm channel before PF is ready

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJZOPZLbmnaS_7mnOrMhp4ZrgehF+rgqnef0TEkJ3q8551OXDA@mail.gmail.com>
Date:	Thu, 6 Mar 2014 22:19:48 +0200
From:	Or Gerlitz <or.gerlitz@...il.com>
To:	David Miller <davem@...emloft.net>
Cc:	Amir Vadai <amirv@...lanox.com>,
	Or Gerlitz <ogerlitz@...lanox.com>,
	Yevgeny Petrilin <yevgenyp@...lanox.com>, Narendra_K@...l.com,
	Sreekanth_Reddy@...l.com,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH net 2/2] net/mlx4_core: mlx4_init_slave() shouldn't access
 comm channel before PF is ready

On Thu, Mar 6, 2014 at 10:12 PM, David Miller <davem@...emloft.net> wrote:
> From: Amir Vadai <amirv@...lanox.com>
> Date: Thu,  6 Mar 2014 18:28:17 +0200
> > @@ -150,6 +150,8 @@ struct mlx4_port_config {
> >       struct pci_dev *pdev;
> >  };
> >
> > +static atomic_t pf_loading = ATOMIC_INIT(0);
> > +
> >  int mlx4_check_port_params(struct mlx4_dev *dev,
> >                          enum mlx4_port_type *port_type)
> >  {
> > @@ -1407,6 +1409,11 @@ static int mlx4_init_slave(struct mlx4_dev *dev)
> >       u32 slave_read;
> >       u32 cmd_channel_ver;
> >
> > +     if (atomic_read(&pf_loading)) {
> > +             mlx4_warn(dev, "PF is not ready. Deferring probe\n");
> > +             return -EPROBE_DEFER;
> > +     }
> > +
>  ...
> > @@ -2319,7 +2326,11 @@ static int __mlx4_init_one(struct pci_dev *pdev, int pci_dev_data)
> >
> >               if (num_vfs) {
> >                       mlx4_warn(dev, "Enabling SR-IOV with %d VFs\n", num_vfs);
> > +
> > +                     atomic_inc(&pf_loading);
> >                       err = pci_enable_sriov(pdev, num_vfs);
> > +                     atomic_dec(&pf_loading);
> > +
>
> This synchronization scheme doesn't look right to me at all.
> It's global, so VF's for _any_ PF will probe defer while one is enabling SRIOV.
> It doesn't seem correct to cause unrelated VF's to defer the probe.

Hi Dave,

Can you please elaborate a bit why you find this approach to be
incorrect? basically, these nested VF probed are a bit headache
anyway, so we didn't find such global deferring to be problematic.

Or.

> You have absolutely have to maintain this state at least on a per-PF level.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html