linux-kernel - Re: [PATCH post 2.6.28] firewire: core: fix sleep in atomic context due to driver core change

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:	Fri, 9 Jan 2009 21:17:18 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
Cc:	linux1394-devel@...ts.sourceforge.net,
	Kay Sievers <kay.sievers@...y.org>,
	linux-kernel@...r.kernel.org, Jay Fenlason <fenlason@...hat.com>,
	Greg Kroah-Hartman <gregkh@...e.de>
Subject: Re: [PATCH post 2.6.28] firewire: core: fix sleep in atomic context
 due to driver core change

On Fri, 9 Jan 2009 20:49:37 +0100 (CET)
Stefan Richter <stefanr@...6.in-berlin.de> wrote:

> Due to commit 2831fe6f9cc4e16c103504ee09a47a084297c0f3, "driver core:
> create a private portion of struct device", device_initialize() can no
> longer be called from atomic contexts.

I don't see why this is neccessary or appropriate - the original commit
needs to be pulled and the private area allocation rethought.
--
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/