linux-kernel - Re: [PATCH 1/7] platform_device: better support builtin boilerplate avoidance

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: <CACRpkda4U7k_Qh7VBOMXo0278bd_r2sn=ZvbOkCLkxs_wJZtsw@mail.gmail.com>
Date:	Wed, 10 Jun 2015 09:35:14 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Paul Gortmaker <paul.gortmaker@...driver.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH 1/7] platform_device: better support builtin boilerplate avoidance

On Wed, Jun 3, 2015 at 4:07 PM, Paul Gortmaker
<paul.gortmaker@...driver.com> wrote:
> On 15-06-02 05:19 AM, Linus Walleij wrote:

>> For example if this is a builtin regulator, clock, GPIO, DMA etc
>> driver, we want to suppress the binding/unbinding from userspace
>> too, since these drivers provide resources to others and
>> if you unbind them, nasty things happen. Unbinding/rebinding
>> is fine as long as noone else depend on you. However for
>> a large number of builtins, that is the case :P
>
> So, to summarize:
>
> 1) Currently drivers can unbind that really should not do so.
>
> 2) This is not a new issue, nor is it introduced by this series.
>
> 3) We can't set policy based on built in vs modular; the only
>    sane thing appears to be to let the driver decide itself.

Yeah I think you're right. If I wanted to fix this problem I
should come up with some patches to help driver authors
do it themselves in a simpler way.

Yours,
Linus Walleij
--
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/