linux-kernel - Re: [PATCH v8 2/3] pinctrl: pinctrl-microchip-sgpio: Add pinctrl driver for Microsemi Serial GPIO

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: <20201109152748.GA1691943@piout.net>
Date:   Mon, 9 Nov 2020 16:27:48 +0100
From:   Alexandre Belloni <alexandre.belloni@...tlin.com>
To:     Andy Shevchenko <andy.shevchenko@...il.com>
Cc:     Lars Povlsen <lars.povlsen@...rochip.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        Microchip Linux Driver Support <UNGLinuxDriver@...rochip.com>,
        devicetree <devicetree@...r.kernel.org>,
        "open list:GPIO SUBSYSTEM" <linux-gpio@...r.kernel.org>,
        linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v8 2/3] pinctrl: pinctrl-microchip-sgpio: Add pinctrl
 driver for Microsemi Serial GPIO

On 09/11/2020 17:16:49+0200, Andy Shevchenko wrote:
> On Mon, Nov 9, 2020 at 4:32 PM Alexandre Belloni
> <alexandre.belloni@...tlin.com> wrote:
> > On 09/11/2020 16:17:40+0200, Andy Shevchenko wrote:
> > > > +       if (input != bank->is_input) {
> > >
> > > > +               dev_err(pctldev->dev, "Pin %d direction as %s is not possible\n",
> > > > +                       pin, input ? "input" : "output");
> > >
> > > Do we need this noise? Isn't user space getting a proper error code as
> > > per doc and can handle this?
> >
> > Why would userspace get the error code?
> 
> Huh?! Why it shouldn't. How will users know if they are doing something wrong?
> 
> > Userspace should never have to
> > handle gpios directly or you are doing something wrong.
> 
> This is true, but check how error codes are propagated to the user space.
> 

your point is to remove an error message because the error may be
propagated to userspace. My point is that userspace should never use
gpios and the kernel has to be the consumer. I don't see how your answer
is relevant here. Did you already check all the call sites from the
kernel too?

-- 
Alexandre Belloni, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com