linux-kernel - Re: [PATCH] ACPIPHP: fix device destroying order issue in handling dock notification

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

Message-ID: <CAN_LGv3iwgp_8dkt1ouCD-FFGau3h7L25ORUW2J-rz30_4ZYTA@mail.gmail.com>
Date:	Tue, 11 Jun 2013 22:51:59 +0600
From:	"Alexander E. Patrakov" <patrakov@...il.com>
To:	Jiang Liu <liuj97@...il.com>
Cc:	Jiang Liu <jiang.liu@...wei.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Yinghai Lu <yinghai@...nel.org>,
	"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
	linux-pci@...r.kernel.org,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ACPIPHP: fix device destroying order issue in handling
 dock notification

2013/6/11 Jiang Liu <liuj97@...il.com>:
> Hi Alexander,
>     This is much more harder issue to resolve.  Let's first work around
> this
> issue and check whether other things are OK. The patch below is just a
> prove of concept, could you please help to try it?

In the initially-undocked case it passes the "dock and undock three
times, verify lspci output at each step" test.

In the initially-docked case, it exhibits the following problem: when
I press the undock button, only one PCI device disappears, and the
"docked" LED does not turn off. Additionally, there is a hung task.

Both dmesgs are attached.

-- 
Alexander E. Patrakov

View attachment "dmesg-initially-docked.txt" of type "text/plain" (91763 bytes)

View attachment "dmesg-initially-undocked.txt" of type "text/plain" (99965 bytes)