linux-kernel - Re: [PATCH v2] kbuild: replace LANG=C with LC

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] [day] [month] [year] [list]

Date:   Mon, 24 May 2021 10:03:37 -0600
From:   Shuah Khan <skhan@...uxfoundation.org>
To:     Masahiro Yamada <masahiroy@...nel.org>,
        patchwork-bot+linux-kselftest@...nel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH v2] kbuild: replace LANG=C with LC_ALL=C

On 5/21/21 8:22 PM, Masahiro Yamada wrote:
> On Sat, May 22, 2021 at 11:14 AM Masahiro Yamada <masahiroy@...nel.org> wrote:
>>
>> On Sat, May 22, 2021 at 3:34 AM
>> <patchwork-bot+linux-kselftest@...nel.org> wrote:
>>>
>>> Hello:
>>>
>>> This patch was applied to shuah/linux-kselftest.git (refs/heads/next):
>>>
>>> On Fri, 30 Apr 2021 10:56:27 +0900 you wrote:
>>>> LANG gives a weak default to each LC_* in case it is not explicitly
>>>> defined. LC_ALL, if set, overrides all other LC_* variables.
>>>>
>>>>    LANG  <  LC_CTYPE, LC_COLLATE, LC_MONETARY, LC_NUMERIC, ...  <  LC_ALL
>>>>
>>>> This is why documentation such as [1] suggests to set LC_ALL in build
>>>> scripts to get the deterministic result.
>>>>
>>>> [...]
>>>
>>> Here is the summary with links:
>>>    - [v2] kbuild: replace LANG=C with LC_ALL=C
>>>      https://git.kernel.org/shuah/linux-kselftest/c/77a88274dc1a
>>>
>>> You are awesome, thank you!
>>> --
>>
>>
>> Huh?
>>
>> This patch exists in Linus' tree.
>>
>> Why is this going to the kselftest tree
>> in the first place?
> 
> 
> Sorry, I misunderstood it.
> 
> I think this notification was unneeded
> because the commit was not actually
> applied to kselftest tree.
> 

When I rebase kselftest tree, patchwork-bot generates this unnecessary
notification. I have been procrastinating looking into how to disable
this. This confusion is a good enough reason to get to it asap. :)

thanks,
-- Shuah