linux-kernel - Re: [PATCH 0/3] firmware: Fix usermodehelper deadlock at 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: <s5hip2twk0e.wl%tiwai@suse.de>
Date:	Wed, 08 May 2013 17:48:01 +0200
From:	Takashi Iwai <tiwai@...e.de>
To:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org, Ming Lei <ming.lei@...onical.com>
Subject: Re: [PATCH 0/3] firmware: Fix usermodehelper deadlock at shutdown

At Wed, 8 May 2013 08:42:16 -0700,
Greg Kroah-Hartman wrote:
> 
> On Wed, May 08, 2013 at 08:56:34AM +0200, Takashi Iwai wrote:
> > Hi,
> > 
> > this is a series of patches for the issue we faced in the firmware
> > loader code during debugging the problem with dell_rbu driver with
> > 3.9 kernel.
> > 
> > The original problem was that the shutdown gets stuck when DELL BIOS
> > update is performed.  This turned out to be a problem in the firmware
> > loader.  Although the reason of dell_rbu driver breakage is still
> > unclear, we should fix the firmware loader side, at least, not to
> > stall during shutdown.
> 
> This is the second time this has been sent, right?  Any differences from
> the first set?

Ah, sorry, you received it already.

I noticed that the patches via git-send-email weren't sent out
properly to some places (like LKML) because of my bad setup of email
(totally forgotten after the fresh installation), so I resent them
again yesterday.

I should have mentioned it in the cover page.  Sorry for confusion.

> I'll get to these after 3.10-rc1 is out, thanks.

OK, thanks!


Takashi
--
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/