linux-kernel - QA: Monitor Linux log messages as port of release (candidate) testing

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

Message-ID: <458e0604-1fe9-bed0-d22f-84540b05ffb1@molgen.mpg.de>
Date:   Tue, 7 Sep 2021 10:40:31 +0200
From:   Paul Menzel <pmenzel@...gen.mpg.de>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: QA: Monitor Linux log messages as port of release (candidate) testing

Dear Guenter,

Thank you for testing release candidates and releases [1]. Is your test 
setup documented somewhere?

If not happening already, could the Linux messages (at least up to log 
level warning) also be monitored? For example, in Linux 5.14, a new 
warning snuck in by cefc7ca462 (ACPI: PRM: implement OperationRegion 
handler for the PlatformRtMechanism subtype) [2], which could have been 
caught early on, and fixed before the release.

The test summaries would then also notify about possible behavior change.

Kind regards,

Paul

[1]: https://lkml.org/lkml/2021/7/11/326
[2]: 
https://lore.kernel.org/linux-acpi/54b6f8cb-4714-587c-b2d0-98134473293d@linux.intel.com/T/#m3f54733714381765c8bb5bfa5b2aa3969407931e