linux-kernel - Re: [PATCH] Revert "driver core: synchronize device shutdown"

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: <CAG4TOxONSsyokdy9Sw+fT21QA7E-uY572ZDoNf3V9f7D1ytyxQ@mail.gmail.com>
Date:	Tue, 4 Mar 2014 20:15:36 -0800
From:	Roland Dreier <roland@...nel.org>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arjan van de Ven <arjan@...radead.org>, shli@...nel.org
Subject: Re: [PATCH] Revert "driver core: synchronize device shutdown"

> Hm, no one seems to have said anything for the past 5 years about this.

It definitely is hard to hit -- you have to do "shutdown" or "reboot"
right as something schedules async work.  In our case we have some
systems with a large and slightly flaky SAS fabric, so there's a
constant level of re-probing SCSI disks, and we occasionally see
reboots hanging due to waiting for never-finishing sd probe async
work.

AFAICT the synchronization does nothing useful and is just a remnant
of a patch series where the real meat didn't get applied.  But of
course it would be great if Shaohua could confirm my understanding.

Thanks,
  Roland
--
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/