linux-kernel - [ANNOUNCE] 4.19.50-rt22

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

Message-ID: <20190614205241.2ad1d103@gandalf.local.home>
Date:   Fri, 14 Jun 2019 20:52:41 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     LKML <linux-kernel@...r.kernel.org>,
        linux-rt-users <linux-rt-users@...r.kernel.org>
Cc:     Thomas Gleixner <tglx@...utronix.de>,
        Carsten Emde <C.Emde@...dl.org>,
        John Kacur <jkacur@...hat.com>,
        Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
        Julia Cartwright <julia@...com>,
        Daniel Wagner <wagi@...om.org>,
        Tom Zanussi <tom.zanussi@...ux.intel.com>
Subject: [ANNOUNCE] 4.19.50-rt22

Dear RT Folks,

I'm pleased to announce the 4.19.50-rt22 stable release.

This release is just an update to the new stable 4.19.50 version
and no RT specific changes have been made.

*** NOTE ***

The 4.19 stable fixed a "use after free" bug in kernel/irq/manage.c,
which was the use case of implementing a new work queue and removing
the old one. But if the old one was in transit, the data could be used
after it was freed. This was fixed in stable by canceling the work
before freeing it. The problem is that RT uses swork instead of the
normal work queues, and swork does not implement a cancel operation.

I simply kept the bug in as is (no regressions, it will fail just like
it has always done ;-). Then I will need to backport the rt-devel code
which makes it possible to use normal work queues in interrupt context.
But that change was too big for a "stable merge" release.

************

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.19-rt
  Head SHA1: 858848641fbecd42437e36adc9291b0ce5db379e

Or to build 4.19.50-rt22 directly, the following patches should be
applied:

  http://www.kernel.org/pub/linux/kernel/v4.x/linux-4.19.tar.xz

  http://www.kernel.org/pub/linux/kernel/v4.x/patch-4.19.50.xz

  http://www.kernel.org/pub/linux/kernel/projects/rt/4.19/patch-4.19.50-rt22.patch.xz

Enjoy,

-- Steve