Re: [PATCH v2 0/2] gpio-cdev: Release IRQ used by gpio-cdev on gpio chip removal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Mar 2, 2024 at 10:00 AM Bartosz Golaszewski <brgl@xxxxxxxx> wrote:
> On Fri, Mar 1, 2024 at 9:15 PM Linus Walleij <linus.walleij@xxxxxxxxxx> wrote:

> > The problem is that I have never heard about a user unbinding/binding
> > a driver from sysfs for anything but debugging a drivers ability to
> > bind/unbind. Partly I feel that thing should just be moved
> > to debugfs given the usecase and because it just looks like a way for
> > attackers to provoke crashes given how some drivers look.
>
> That's not the only thing - device unbind can also be triggered by
> removing the module providing the driver which is a completely normal
> operation for user-space.

That is one thing, but every time I hear about "have you thought about
users going in and using bind/unbind in sysfs" it's for builtin bool
drivers.

I almost feel like bool drivers should have bind/unbind disabled by
default :/

The introduction of deferred probe has made the situation much better
because it tends to exercise the bind/unbind path a bit.

Yours,
Linus Walleij





[Index of Archives]     [Linux SPI]     [Linux Kernel]     [Linux ARM (vger)]     [Linux ARM MSM]     [Linux Omap]     [Linux Arm]     [Linux Tegra]     [Fedora ARM]     [Linux for Samsung SOC]     [eCos]     [Linux Fastboot]     [Gcc Help]     [Git]     [DCCP]     [IETF Announce]     [Security]     [Linux MIPS]     [Yosemite Campsites]

  Powered by Linux