netdev - RE: [net-next v2 13/15] i40e: limit WoL and link settings to partition 1

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] [day] [month] [year] [list]

Message-ID: <B5657A6538887040AD3A81F1008BEC63BC8FD3@avmb3.qlogic.org>
Date:	Mon, 19 Jan 2015 06:09:49 +0000
From:	Yuval Mintz <Yuval.Mintz@...gic.com>
To:	"Nelson, Shannon" <shannon.nelson@...el.com>,
	"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
	David Miller <davem@...emloft.net>
CC:	netdev <netdev@...r.kernel.org>,
	"nhorman@...hat.com" <nhorman@...hat.com>,
	"sassmann@...hat.com" <sassmann@...hat.com>,
	"jogreene@...hat.com" <jogreene@...hat.com>
Subject: RE: [net-next v2 13/15] i40e: limit WoL and link settings to
 partition 1

> > How can user be aware of this 'private' behavior?
> > via system logs? documentation?

> In this case, note that we have added a log message that
> says these are dependent on the initial partition of the port
> for setting control.  Also, the particular vendor using the 
> device in this configuration will supply and support the user documentation.

What I'm 'aiming' for is that this is a common problem;
I.e., having multiple PCI functions per a physical port is a constellation
which exists in several devices.

I think the community strives in such scenarios to uphold a unite front
for user experience - if the 'right' answer is that the network device
associated with the first PCI function is the configuration node in such
cases, then we should strive making it so for all drivers.

> > How does it interact with Physical Device Assignment of the first
> > partition?

> I'm not sure I understand this question, but I'll answer a different
> question: these multifunction ports show up as additional PCI
> functions, again, not unlike VF devices.

You can't refrain from user assigning the first partition to a VM.
In such a case, you receive quite a bizarre configuration when you
all a ~random device on some VM to control the physical port. 
--
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