linux-kernel - Re: [GIT PULL] gpio: updates for v5.17

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: <CAHk-=wg1RUc-41K=XTQavnkuLg2=oe8r8LWBocWWWXhM77=2gw@mail.gmail.com>
Date:   Tue, 11 Jan 2022 12:36:35 -0800
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] gpio: updates for v5.17

On Tue, Jan 11, 2022 at 7:53 AM Bartosz Golaszewski <brgl@...ev.pl> wrote:
>
> The gpio-sim module is back, this time without any changes to configfs. This
> results in a less elegant user-space interface but I never got any follow-up on
> the committable items and didn't want to delay this module for several more
> months.

Yeah, I think that was the right choice.

I actually did spend some time looking at the configfs code, and it
just worried me. It may have been clever, but there was no real
serious user that would have used it outside of this gpio use-case,
and the games it played with the dentry layer were scary. With no real
maintainer for configfs, and no VFS person willing to work on it, I
think it was a dead end. With that in mind, the fewer fancy configfs
users we have, and the fewer reasons to use it, the better.

            Linus