Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
In-Reply-To: <6cba215c-127e-f3eb-b525-773b6aed0eb7@c-s.fr>
References: <20180225172236.29650-1-malat@debian.org> <20180225172236.29650-7-malat@debian.org>
 <8862c1e1-d161-3410-1b2a-502ad06cef57@c-s.fr> <6cba215c-127e-f3eb-b525-773b6aed0eb7@c-s.fr>
From:   Mathieu Malaterre <malat@debian.org>
Date:   Mon, 26 Feb 2018 08:44:49 +0100
Message-ID: <CA+7wUswNE1ydgeESpG8Dqtz4SGFjZZJJiPp+SHN8Z1qtBtPLLQ@mail.gmail.com>
Subject: Re: [PATCH 06/21] powerpc: Avoid comparison of unsigned long >= 0 in __access_ok
To:     Christophe LEROY <christophe.leroy@c-s.fr>
Cc:     Michael Ellerman <mpe@ellerman.id.au>,
        LKML <linux-kernel@vger.kernel.org>,
        Paul Mackerras <paulus@samba.org>,
        Jiri Slaby <jslaby@suse.com>,
        linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Feb 26, 2018 at 7:50 AM, Christophe LEROY
<christophe.leroy@c-s.fr> wrote:
>
>
> Le 26/02/2018 =C3=A0 07:34, Christophe LEROY a =C3=A9crit :
>>
>>
>>
>> Le 25/02/2018 =C3=A0 18:22, Mathieu Malaterre a =C3=A9crit :
>>>
>>> Rewrite check size - 1 <=3D Y as size < Y since `size` is unsigned valu=
e.
>>> Fix warning (treated as error in W=3D1):
>>>
>>>    CC      arch/powerpc/kernel/signal_32.o
>>> In file included from ./include/linux/uaccess.h:14:0,
>>>                   from ./include/asm-generic/termios-base.h:8,
>>>                   from ./arch/powerpc/include/asm/termios.h:20,
>>>                   from ./include/uapi/linux/termios.h:6,
>>>                   from ./include/linux/tty.h:7,
>>>                   from arch/powerpc/kernel/signal_32.c:36:
>>> ./include/asm-generic/termios-base.h: In function
>>> =E2=80=98user_termio_to_kernel_termios=E2=80=99:
>>> ./arch/powerpc/include/asm/uaccess.h:52:35: error: comparison of unsign=
ed
>>> expression >=3D 0 is always true [-Werror=3Dtype-limits]
>>>     (((size) =3D=3D 0) || (((size) - 1) <=3D ((segment).seg - (addr))))=
)
>>>                                     ^
>>> ./arch/powerpc/include/asm/uaccess.h:58:3: note: in expansion of macro
>>> =E2=80=98__access_ok=E2=80=99
>>>     __access_ok((__force unsigned long)(addr), (size), get_fs()))
>>>     ^~~~~~~~~~~
>>> ./arch/powerpc/include/asm/uaccess.h:262:6: note: in expansion of macro
>>> =E2=80=98access_ok=E2=80=99
>>>    if (access_ok(VERIFY_READ, __gu_addr, (size)))   \
>>>        ^~~~~~~~~
>>> ./arch/powerpc/include/asm/uaccess.h:80:2: note: in expansion of macro
>>> =E2=80=98__get_user_check=E2=80=99
>>>    __get_user_check((x), (ptr), sizeof(*(ptr)))
>>>    ^~~~~~~~~~~~~~~~
>>> ./include/asm-generic/termios-base.h:36:6: note: in expansion of macro
>>> =E2=80=98get_user=E2=80=99
>>>    if (get_user(termios->c_line, &termio->c_line) < 0)
>>>        ^~~~~~~~
>>> [...]
>>> cc1: all warnings being treated as errors
>>>
>>> Signed-off-by: Mathieu Malaterre <malat@debian.org>
>>> ---
>>>   arch/powerpc/include/asm/uaccess.h | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/arch/powerpc/include/asm/uaccess.h
>>> b/arch/powerpc/include/asm/uaccess.h
>>> index 51bfeb8777f0..fadc406bd39d 100644
>>> --- a/arch/powerpc/include/asm/uaccess.h
>>> +++ b/arch/powerpc/include/asm/uaccess.h
>>> @@ -49,7 +49,7 @@
>>>   #define __access_ok(addr, size, segment)    \
>>>       (((addr) <=3D (segment).seg) &&        \
>>> -     (((size) =3D=3D 0) || (((size) - 1) <=3D ((segment).seg - (addr))=
)))
>>> +     (((size) =3D=3D 0) || ((size) < ((segment).seg - (addr)))))
>>
>>
>> IIUC, ((2 - 1) <=3D 1) is the same as (2 < 1) ?????
>

The whole series was pretty mediocre, but this one was actually pretty
destructive. Thanks for catching this.

>
> Note that I already try to submit a fix for this warning 3 years ago
> (https://patchwork.ozlabs.org/patch/418075/) and it was rejected with the
> following comment:
>
> Again, I don't think Linux enables this warning.  What did you do to
> produce this?  In any case, it's a bad warning that doesn't take macros
> into account, and the answer is not to make the code less clear by hiding
> the fact that zero is a special case.

Right. I'll try to see how to make W=3D1 run without error with an
alternate solution.

> Christophe
>
>
>>
>> Christophe
>>
>>>   #endif
>>>
>