On Sep 2, 2016 9:20 PM, "Dmitry Torokhov" wrote:
>
> Like what? Some devices do need to have firmware loaded so we know
> their capabilities, so we really can't push the firmware loading into
> "open".
So you
(a) document that
(b) make the driver only build as a module
(c) make sure the module an
On Fri, Sep 02, 2016 at 05:52:16PM +0530, Aneesh Kumar K.V wrote:
>
> Hi Paul,
>
> Really nice catch. Was this found by code analysis or do we have any
> reported issue around this ?
I found it by code analysis.
I haven't been able to find any really bad consequence, beyond leaking
some informa
On 3 September 2016 06:26:08 GMT+10:00, Linus Torvalds
wrote:
>On Fri, Sep 2, 2016 at 1:06 PM, Arnd Bergmann wrote:
>>
>> When I once looked, I thought all drivers using NO_IRQ were specific
>> to powerpc or one of the less common architectures.
>
>powerpc definitely does seem to be the bigges
On Fri, Sep 02, 2016 at 09:41:18PM -0700, Linus Torvalds wrote:
> On Sep 2, 2016 9:20 PM, "Dmitry Torokhov" wrote:
> >
> > Like what? Some devices do need to have firmware loaded so we know
> > their capabilities, so we really can't push the firmware loading into
> > "open".
>
> So you
> (a) docu
On Sat, Sep 3, 2016 at 10:49 AM, Dmitry Torokhov
wrote:
>
> Unfortunately module loading and availability of firmware is very
> loosely coupled.
The whole "let's add a new magical proc entry to say that all
filesystems are mounted" is all about the user space coupling them.
I'm just saying that
On Sat, Sep 3, 2016 at 11:01 AM, Linus Torvalds
wrote:
> On Sat, Sep 3, 2016 at 10:49 AM, Dmitry Torokhov
> wrote:
>>
>> Unfortunately module loading and availability of firmware is very
>> loosely coupled.
>
> The whole "let's add a new magical proc entry to say that all
> filesystems are mounte
On Wed, Aug 17, 2016 at 03:15:09PM +0800, Fam Zheng wrote:
> Previously after device_add_disk returns, the KOBJ_ADD uevent is already
> emitted. Adding attributes after that is a poor usage of kobject, and
> in practice may result in race conditions with userspace, for
> example udev checks availab