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
| ||
|
Message-ID: <20140714202531.GA24877@laptop.dumpdata.com> Date: Mon, 14 Jul 2014 16:25:31 -0400 From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> To: Sander Eikelenboom <linux@...elenboom.it> Cc: konrad@...nel.org, xen-devel@...ts.xenproject.org, boris.ostrovsky@...cle.com, david.vrabel@...rix.com, linux-kernel@...r.kernel.org Subject: Re: [Xen-devel] [PATCH v4] PCI back fixes for 3.17. > >> > Thank you for reporting it and helping me with the XenStore output to > >> > narrow down the culprit! > >> > >> The thing i don't understand then is: > >> How is it different for the last (or all ) device(s) ? > >> (since the last device (or removing all devices) before doing the > >> assignable-remove doesn't trigger the warning) > >> > >> Or does the complete removal of the pci-part of the tree in xenstore trigger something ? > > > Yup. It removes the whole 'pci' directory in XenStore which triggers > > in Xen pciback the code to deal with that. > So that essentially needs to be changed to watch the individual devices in the > xenstore tree instead of the whole pci stuff. Correct. Thought instead of watching it will just compare with what it had assigned to a guest and what it currently has exposed in XenStore. And then whatever is not on the list (exposed in XenStore) is going to be reaped. > Then it all makes sense :-) Until you find another bug :-) > > >> You know if you got a patch cooked up, i'm more than happy to test ! > > > Hehe! > >> > >> -- > >> Sander > >> > > -- 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