Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230420165454.9517-1-jorge.lopez2@hp.com> <20230420165454.9517-9-jorge.lopez2@hp.com>
 <ca74121b-bb78-4093-8625-13359c324c28@t-8ch.de> <CAOOmCE_MpCBFOHd6QtzD5ufcwEz_FhJvqevj68pVeY_JS+V=Rg@mail.gmail.com>
 <462b5d12-0430-4fbe-8c26-7b6126556ec8@t-8ch.de> <CAOOmCE8iBfeuodTO7C=0EUOkqv16008h7vsZO2hhBZPuLoLECw@mail.gmail.com>
 <152fb7c0-1075-4718-bca1-c2083c425788@t-8ch.de>
In-Reply-To: <152fb7c0-1075-4718-bca1-c2083c425788@t-8ch.de>
From:   Jorge Lopez <jorgealtxwork@gmail.com>
Date:   Fri, 28 Apr 2023 11:19:04 -0500
Message-ID: <CAOOmCE-KK3AYmjaDO=qV7WzpsgeZ6d7U1Ep9a9=dcu9CEmohLQ@mail.gmail.com>
Subject: Re: [PATCH v11 08/14] HP BIOSCFG driver - bioscfg-h
To:     =?UTF-8?Q?Thomas_Wei=C3=9Fschuh?= <thomas@t-8ch.de>
Cc:     hdegoede@redhat.com, platform-driver-x86@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Fri, Apr 28, 2023 at 11:09=E2=80=AFAM Thomas Wei=C3=9Fschuh <thomas@t-8c=
h.de> wrote:
>
> On 2023-04-28 11:03:56-0500, Jorge Lopez wrote:
> > On Fri, Apr 28, 2023 at 10:36=E2=80=AFAM Thomas Wei=C3=9Fschuh <thomas@=
t-8ch.de> wrote:
> > >
> > > On 2023-04-28 10:24:40-0500, Jorge Lopez wrote:
> > > > On Sun, Apr 23, 2023 at 7:01=E2=80=AFAM Thomas Wei=C3=9Fschuh <thom=
as@t-8ch.de> wrote:
> > > > >
> > > > > On 2023-04-20 11:54:48-0500, Jorge Lopez wrote:
> > > > > > ---
> > > > > >  drivers/platform/x86/hp/hp-bioscfg/bioscfg.h | 613 +++++++++++=
++++++++
> > > > > >  1 file changed, 613 insertions(+)
> > > > > >  create mode 100644 drivers/platform/x86/hp/hp-bioscfg/bioscfg.=
h
>
> <snip>
>
> > > > > > +#define ATTRIBUTE_PROPERTY_STORE(curr_val, type)              =
       \
> > > > > > +     static ssize_t curr_val##_store(struct kobject *kobj,    =
       \
> > > > > > +                                     struct kobj_attribute *at=
tr,    \
> > > > > > +                                     const char *buf, size_t c=
ount)  \
> > > > > > +     {                                                        =
       \
> > > > > > +             char *p =3D NULL;                                =
         \
> > > > > > +             char *attr_value =3D NULL;                       =
         \
> > > > > > +             int i;                                           =
       \
> > > > > > +             int ret =3D -EIO;                                =
         \
> > > > > > +                                                              =
       \
> > > > > > +             attr_value =3D kstrdup(buf, GFP_KERNEL);         =
         \
> > > > > > +             if (!attr_value)                                 =
       \
> > > > > > +                     return -ENOMEM;                          =
       \
> > > > > > +                                                              =
       \
> > > > > > +             p =3D memchr(attr_value, '\n', count);           =
         \
> > > > > > +             if (p !=3D NULL)                                 =
         \
> > > > > > +                     *p =3D '\0';                             =
         \
> > > > >
> > > > > This can also truncate the string if there is data after the newl=
ine.
> > > >
> > > > This is a expected behavior as described by Hans in a later email
> > >
> > > I'm fine with stripping a trailing newline.
> > >
> > > But this truncates the string at the first newline.
> > >
> > > "foo\nbar" -> "foo"
> > > "\nfoo" -> ""
> > >
> > All inputs expected by this driver and respectively by BIOS are a
> > single line.  For this reason, '\n' will cause the string to be
> > truncated.
> > I propose reporting a warning message indicating that the data entered
> > has a '\n' character and will be truncated in addition to failing the
> > operation with -EINVAL
>
> EINVAL sounds good, but a warning is overkill IMO.
>
> Whoever put in the garbage value will see the error.
>
> Stripping a trailing newline still seems fine though.

So. should the driver return an -EINVAL error or truncate the line,
report a warning message, and allow it to proceed.?
Please advice

> This would be a very good candidate for a helper function.