Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Daniel Wagner <dwagner@suse.de>
Subject: [ANNOUNCE] 4.4.262-rt219
Date:   Sat, 20 Mar 2021 16:25:35 -0000
Message-ID: <161625753552.20205.6230905513724868931@beryllium>
To:     LKML <linux-kernel@vger.kernel.org>,
        linux-rt-users <linux-rt-users@vger.kernel.org>,
        Steven Rostedt <rostedt@goodmis.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        Carsten Emde <C.Emde@osadl.org>,
        John Kacur <jkacur@redhat.com>,
        Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
        Tom Zanussi <tom.zanussi@linux.intel.com>,
        Clark Williams <williams@redhat.com>,
        Pavel Machek <pavel@denx.de>
Precedence: bulk

Hello RT-list!

I'm pleased to announce the 4.4.262-rt219 stable release.

This is just an update to the latest stable release. No RT
specific changes.

I tried to fix the locking self failures I reported last time. As it
turns out the test setup was somehow broken. After redoing all the
test just using 'defconfig + kvmconfig + locking_selftest' all worked
fine. I also tested older v4.4-rt releases and there was no failures.

Furthermore, the cyclicdeadline fails again, which I probably a good
thing; I don't believe in self healing capabilities of the -rt patchset.
Anyway, I think my build/test setup was just broken.

Known issue:

  - locktorture reports a might_sleep warning for spin_locks test

You can get this release via the git tree at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git

  branch: v4.4-rt
  Head SHA1: d18d08f6afe25c27207d26a9811e23abf7ef36b8

Or to build 4.4.262-rt219 directly, the following patches should be applied:

  https://www.kernel.org/pub/linux/kernel/v4.x/linux-4.4.tar.xz

  https://www.kernel.org/pub/linux/kernel/v4.x/patch-4.4.262.xz

  https://www.kernel.org/pub/linux/kernel/projects/rt/4.4/patch-4.4.262-rt219.patch.xz

Enjoy!
Daniel