netdev - Re: [PATCH net-next V0 18/21] mlx4_core: adjust catas operation for SRIOV mode

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]

Date:	Fri, 2 Dec 2011 09:07:09 -0800
From:	Roland Dreier <roland@...estorage.com>
To:	Yevgeny Petrilin <yevgenyp@...lanox.co.il>
Cc:	davem@...emloft.net, netdev@...r.kernel.org,
	linux-rdma@...r.kernel.org, liranl@...lanox.co.il,
	jackm@....mellanox.co.il
Subject: Re: [PATCH net-next V0 18/21] mlx4_core: adjust catas operation for
 SRIOV mode

On Fri, Dec 2, 2011 at 2:19 AM, Yevgeny Petrilin
<yevgenyp@...lanox.co.il> wrote:
> When running in SRIOV mode, driver should not automatically start/stop
> the mlx4_core upon sensing an HCA internal error -- doing this disables/enables
> sriov, which will cause the hypervisor to hang if there are running VMs with
> attached VFs.

Not sure I understand this -- what happens if the driver doesn't reset
the device
after a catastrophic error?  Surely all the VFs are pretty screwed at
that point?

Which hypervisor are we talking about here anyway?

 - R.
--
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