linux-kernel - Re: [RFC] gpio: remove gpio

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: <CAAVeFu+fsgG86b8iYVeHNmGqtb2m_P6esF1QFrbsMhwTh+P7Aw@mail.gmail.com>
Date:	Tue, 4 Nov 2014 18:10:16 +0900
From:	Alexandre Courbot <gnurou@...il.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Alexandre Courbot <acourbot@...dia.com>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC] gpio: remove gpio_descs global array

On Mon, Nov 3, 2014 at 11:11 PM, Linus Walleij <linus.walleij@...aro.org> wrote:
> On Sat, Nov 1, 2014 at 8:03 AM, Alexandre Courbot <acourbot@...dia.com> wrote:
>
>> The issue with this patch is its use of kzalloc() in gpiochip_add(), a
>> function potentially called during early boot, before kzalloc() becomes
>> usable. Hence its [RFC] status until we can find a solution for this or
>> agree that this issue is actually never ran into (from which point can
>> one use kzalloc()?)
>
> So which driver requires that the gpiochip be statically defined...
> I heard about early call but not *that* early.

Let me know if you feel adventurous - in that case I will submit a
proper version of this patch to put in -next, and we'll see if people
complain... :)
--
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/