| 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: Tue, 1 May 2012 22:10:27 -0700 From: Greg KH <gregkh@...uxfoundation.org> To: Jiang Liu <liuj97@...il.com> Cc: Yinghai Lu <yinghai@...nel.org>, Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>, Bjorn Helgaas <bhelgaas@...gle.com>, Don Dutile <ddutile@...hat.com>, Jiang Liu <jiang.liu@...wei.com>, Keping Chen <chenkeping@...wei.com>, linux-kernel@...r.kernel.org, linux-pci@...r.kernel.org Subject: Re: [PATCH v2 06/19] PCI: prepare for serializing hotplug operations triggered by pciehp driver On Fri, Apr 27, 2012 at 11:16:47PM +0800, Jiang Liu wrote: > From: Jiang Liu <jiang.liu@...wei.com> > > Split pciehp_wq into two workqueues to avoid possible deadlock issues > when using PCI hotplug lock to serialize hotplug operations triggered > by pciehp driver. Why two workqueues? What is deadlocking? And why name one "power" and one "event"? What do they now do differently? How are you serializing events across the workqueues as they can be doing the same thing at the same time to the same hardware now, right? What am I missing? Ick, I said I wasn't going to read anymore, I'm really stopping now. Sorry, it's like watching a train-wreck, you just can't turn away... greg k-h -- 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