linux-kernel - Re: [PATCH v2] ver_linux: add missing software to checklist

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:   Tue, 31 Jan 2023 13:07:42 -0700
From:   Shuah Khan <skhan@...uxfoundation.org>
To:     Alexander Kapshuk <alexander.kapshuk@...il.com>
Cc:     linux-kernel@...r.kernel.org,
        Shuah Khan <skhan@...uxfoundation.org>
Subject: Re: [PATCH v2] ver_linux: add missing software to checklist

On 1/26/23 01:02, Alexander Kapshuk wrote:
> On Tue, Jan 24, 2023 at 11:04 PM Shuah Khan <skhan@...uxfoundation.org> wrote:
>>
>> Update to add missing software checks to bring it in sync with the
>> Documentation/Changes list. Make improvements to the output with
>> separator between different sections.
>>
>> Signed-off-by: Shuah Khan <skhan@...uxfoundation.org>
>> ---
>> Changes since v1: addressed review comments
>>
>>   scripts/ver_linux | 28 ++++++++++++++++++++++++----
>>   1 file changed, 24 insertions(+), 4 deletions(-)
>>
>> diff --git a/scripts/ver_linux b/scripts/ver_linux
>> index 1a8ee4ff0e32..2daee7e88c45 100755
>> --- a/scripts/ver_linux
>> +++ b/scripts/ver_linux
>> @@ -6,20 +6,29 @@
>>   # differ on your system.
>>
>>   BEGIN {
>> -       usage = "If some fields are empty or look unusual you may have an old version.\n"
>> -       usage = usage "Compare to the current minimal requirements in Documentation/Changes.\n"
>> +       usage = "Minimum required software versions to build and run current kernel version.\n"
>> +       usage = usage "If some fields are empty or look unusual you may have an old version.\n"
>> +       usage = usage "Compare with the current minimal requirements in Documentation/Changes.\n"
>>          print usage
> 
> The usage message is followed by three new line characters, the 1st is
> embedded in the last line of the usage message, the second is output
> by the print function, and the third by the leading new line character
> in the separator string.
> All other sections use two trailing new line characters instead.
> If the formatting of this section is desired to be consistent with all
> the other sections, this print function may be substituted with the
> printf function, which does not append a new line character to its
> argument.
> 

> 
> Other than that, LGTM. Thanks.

Thanks for checking this. Make sense to keep it consistent. Will
fix it in the next version.

thanks,
-- Shuah