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]
Date:	Tue, 16 Aug 2011 16:38:50 -0500
From:	Linas Vepstas <linasvepstas@...il.com>
To:	Tejun Heo <tj@...nel.org>
Cc:	Oleg Nesterov <oleg@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Paul Mackerras <paulus@...ba.org>,
	Matt Fleming <matt@...sole-pimps.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] powerpc/eeh: remove eeh_event_handler()->daemonize()

On 16 August 2011 14:29, Tejun Heo <tj@...nel.org> wrote:
> Hello,
>
> On Tue, Aug 16, 2011 at 02:24:12PM -0500, Linas Vepstas wrote:
>> BTW, if someone wants to tackle a big, difficult project, one would be
>> to untangle the mess that happens when the hardware underneath an
>> active block device dies.  Currently, the kernel will deadlock in
>> umpteen zillion places waiting for blocks and files that will never
>> arrive.
>
> Umm... that has been working fine for SCSI and ATA for years now.
> Just aborting pending commands and freeing the device should do it.
> Drivers need to take care of driver specific resources (per-req and
> per-dev) but that's not different from aborting timed out commands.
> What's missing for your use case?

Sorry, I guess I'm out-of-date; its been far more than a few years since
I last tried this :-) The use case was eeh recovery, where the hardware was
so hosed that it wouldn't recover.  The test cases were whatever it was that
the test team could throw at the system.

--linas

--linas
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ