linux-kernel - Re: gpiochip_lock_as_irq on pins without FLAG

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:   Mon, 28 Jun 2021 16:42:20 +0300
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Vincent Pelletier <plr.vincent@...il.com>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        Bartosz Golaszewski <bgolaszewski@...libre.com>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: gpiochip_lock_as_irq on pins without FLAG_REQUESTED: bug or
 feature ?

On Mon, Jun 28, 2021 at 4:40 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Mon, Jun 28, 2021 at 6:37 AM Vincent Pelletier <plr.vincent@...il.com> wrote:

> > While trying to debug an IRQ handling issue on a sifive-unmatched board
> > (which is a very recent board on a recent architecture, so I would not
> > be overly surprised if there were bugs in hiding), I realised that I was able
> > to claim via sysfs GPIO pins which are being actively used as IRQ sources.

And one important note: do NOT use sysfs GPIO interface. Use a GPIO
character device instead.

-- 
With Best Regards,
Andy Shevchenko