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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <432fb484-eecf-8203-c457-9092b48a0528@gmail.com>
Date:   Wed, 30 Mar 2022 13:50:13 +0700
From:   Bagas Sanjaya <bagasdotme@...il.com>
To:     Alexey Khoroshilov <khoroshilov@...ras.ru>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
        torvalds@...ux-foundation.org, stable@...r.kernel.org
Cc:     lwn@....net, jslaby@...e.cz
Subject: Re: Stable release process proposal (Was: Linux 5.10.109)

On 30/03/22 06.49, Alexey Khoroshilov wrote:
> The problem will be fixed in 5.10.110, but we still have a couple oddities:
> - we have a release that should not be recommended for use
> - we have a commit message misleading users when says:
> 
>      Tested-by: Pavel Machek (CIP) <pavel@...x.de>
>      Tested-by: Fox Chen <foxhlchen@...il.com>
>      Tested-by: Florian Fainelli <f.fainelli@...il.com>
>      Tested-by: Shuah Khan <skhan@...uxfoundation.org>
>      Tested-by: Bagas Sanjaya <bagasdotme@...il.com>
>      Tested-by: Salvatore Bonaccorso <carnil@...ian.org>
>      Tested-by: Linux Kernel Functional Testing <lkft@...aro.org>
>      Tested-by: Sudip Mukherjee <sudip.mukherjee@...ethink.co.uk>
>      Tested-by: Guenter Roeck <linux@...ck-us.net>
> 
> but actually nobody tested that version.

I think you missed the point of having Tested-by in stable releases here.
The tag is used to indicate that the entity (individuals, organizations,
or bots) had successfully tested the release candidate (stable-rc). The
degree of testing can vary. For example, I only did cross-compile test [1],
then I offered Tested-by in my name.

[1]: https://lore.kernel.org/stable/2b3af5d1-8233-45a6-7a44-a19f7010cd6b@gmail.com/

On the other hand, Naresh Kamboju (LKFT) did full testing as indicated on
[2].

[2]: https://lore.kernel.org/stable/CA+G9fYu9CjYCQwM3EO5eguRC0rq00HMuE7cEAG4E68shzw4OHA@mail.gmail.com/

Regardless of how testing is done by entities involved, the point of having
Tested-by is to give kernel users confidence to upgrade to more recent
release, as almost all sufferings of testing is represented by Tested-by
entities.

-- 
An old man doll... just what I always wanted! - Clara

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ