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
| ||
|
Date: Thu, 3 Jun 2010 11:11:21 +0800 From: Frank Pan <frankpzh@...il.com> To: "Williams, Mitch A" <mitch.a.williams@...el.com> Cc: Greg KH <greg@...ah.com>, Andrew Morton <akpm@...ux-foundation.org>, Jesse Barnes <jbarnes@...tuousgeek.org>, Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>, Yu Zhao <yu.zhao@...el.com>, Chris Wright <chrisw@...s-sol.org>, "Rafael J. Wysocki" <rjw@...k.pl>, "David S. Miller" <davem@...emloft.net>, Matt Carlson <mcarlson@...adcom.com>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: Add a helper function in PCI IOV to get VF device > So, when VF has no interface, this path is also unavailable. That's > why I say given vf's bdf, one cannot infer pf's. Sorry I just missed something. Userspace can find pf's bdf by physfn. So, the motivation is provide some information about vf from pf driver by sysfs. I cannot avoid to create one directory for each vf, like vf0, vf1, etc. Although userspace can find these directories, but it has no idea about which one to use. Userspace just knows vf's bdf, it won't care about/know vf's id. So I have the issue to create a symlink from each vf's /sys/bus/pci/devices/xxxx/ to their corresponding directories. And then comes the issue: PF cannot get VF's bdf in kernel space. This is not a strange issue, hacking every SR-IOV device can met. Thanks. -- Frank Pan Computer Science and Technology Tsinghua University -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists