linux-kernel - Re: Linux 5.14

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

Message-ID: <CAHk-=wjz+RhR8rr4rAZBPf-mxZXvn2RQe-XTQcL8X+HXBAFxBA@mail.gmail.com>
Date:   Mon, 30 Aug 2021 08:17:04 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 5.14

On Mon, Aug 30, 2021 at 2:12 AM Sudip Mukherjee
<sudipm.mukherjee@...il.com> wrote:
>
> We were recently working on openqa based testing and is a very basic
> testing for now.. Build the kernel for x86_64 and arm64, boot it on
> qemu and rpi4 and test that the desktop environment is working. And,
> it now tests mainline branch every night. So, last night it tested
> "5.14.0-7d2a07b76933" and both tests were ok.

Thanks. The more the merrier, and if you do this every night, having a
fairly low-latency "it stopped working" will be good.

Of course, if you can find some other slightly more oddball
configuration that you would also like to test, that it would be even
better.

Because while it's lovely to have more automated testing, if
_everybody_ only tests x86-64 and arm64, the less common cases get
little to no testing.

No big deal, but I thought I'd just mention it in case you go "Yeah, I
know XYZ is entirely irrelevant, but I happen to like it, so I could
easily add that to the testing too".

               Linus