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-next>] [day] [month] [year] [list]
Message-Id: <201412041206.sB4C6XVQ009497@userz7022.oracle.com>
Date:	Thu, 04 Dec 2014 07:06:24 -0500
From:	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To:	David Vrabel <david.vrabel@...rix.com>
Cc:	Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	linux-pci@...r.kernel.org, xen-devel@...ts.xenproject.org,
	linux-kernel@...r.kernel.org, bhelgaas@...gle.com
Subject: Re: [PATCH v5 9/9] xen/pciback: Implement PCI reset slot or bus
 with 'do_flr' SysFS attribute


On Dec 4, 2014 6:30 AM, David Vrabel <david.vrabel@...rix.com> wrote:
>
> On 03/12/14 21:40, Konrad Rzeszutek Wilk wrote: 
> > 
> > Instead of doing all this complex dance, we depend on the toolstack 
> > doing the right thing. As such implement the 'do_flr' SysFS attribute 
> > which 'xl' uses when a device is detached or attached from/to a guest. 
> > It bypasses the need to worry about the PCI lock. 
>
> No.  Get pciback to add its own "reset" sysfs file (as I have repeatedly 
> proposed). 
>

Which does not work as the kobj will complain (as there is already an 'reset' associated with the PCI device).

Unless you mean an different name (reset2).

> David 

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ