linux-kernel - Re: [ANNOUNCE] 5.10.162-rt79

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]

Date:   Thu, 23 Feb 2023 15:33:56 +0100
From:   Daniel Wagner <wagi@...om.org>
To:     Florian Bezdeka <florian.bezdeka@...mens.com>
Cc:     "Luis Claudio R. Goncalves" <lgoncalv@...hat.com>,
        LKML <linux-kernel@...r.kernel.org>,
        linux-rt-users <linux-rt-users@...r.kernel.org>,
        stable-rt <stable-rt@...r.kernel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Carsten Emde <C.Emde@...dl.org>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Daniel Wagner <daniel.wagner@...e.com>,
        Tom Zanussi <tom.zanussi@...ux.intel.com>,
        Clark Williams <williams@...hat.com>,
        Mark Gross <markgross@...nel.org>,
        Pavel Machek <pavel@...x.de>,
        Jeff Brady <jeffreyjbrady@...il.com>,
        Salvatore Bonaccorso <carnil@...ian.org>,
        Mark Rutland <mark.rutland@....com>,
        Jan Kiszka <jan.kiszka@...mens.com>
Subject: Re: [ANNOUNCE] 5.10.162-rt79

Hi Florian,

On Thu, Jan 26, 2023 at 06:41:27PM +0100, Florian Bezdeka wrote:
> From the CIP projects perspective we would like to improve the
> situation.
> 
> From my perspective the following could be done:
> 
>   - Instead of (or in addition to) building and testing released -rt
>     branches enable testing of -rt release candidates
>   - Make sure the build results get back to the maintainers
> 
> I'm not sure if every -rt branch has a -rc branch. I'm not familiar
> with the -rt release process yet.

The process so far is, that every stable maintainer updates his tree (merges the
stable tree) and does a local build and local tests. Usually when merging latest
upstream stable release there are no or little fallouts. When the maintainer is
happy he does the release by pushing the changes to the usptream branch. The
release candiates come only into play when there is something the maintainer is
not sure how to handle or -rt patches are backported which need some more eyes
to look on. That means Sebastian's approval :)

IIRC, I did give a presentation on the workflow some time ago...

https://lpc.events/event/4/contributions/293/attachments/237/416/maintaining-out-of-tree-patches-over-the-long-term.pdf
https://www.youtube.com/watch?v=2ab4Knwlmo4

When we started with this process kernelci didn't build these branches but that
is long time ago.

Personally, I don't mind doing an official -rc for every release and getting
some additional builds and tests run by kernelci.

Though just piping the results back is the easy thing, the time consuming task
is to fix those problems. Do you plan to help out here?

Thanks,
Daniel