Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp4643128ybe; Mon, 16 Sep 2019 16:08:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqyxU/OQWQlxJNoEFrcoMubnY3tTH5b+Mg2Mho3AkYSOW9bfw/mYT5OoN8BOLaM8WP/YT8+r X-Received: by 2002:a17:906:a40b:: with SMTP id l11mr2203610ejz.307.1568675297049; Mon, 16 Sep 2019 16:08:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1568675297; cv=none; d=google.com; s=arc-20160816; b=g4I4Sguah5L+4lHjZnpocCdvhm4detKzmp/xr1d3Jvkdp9S9CWjEKXuEgsDVb89Lj/ x671iDxPH3UKXdWnlBfiN0ZrvEdqsXEV35nsUcgau5+A094hnR7R9go99PIyykXZ9JR6 gKWSciceJESYIXDKUHSzwNPPVSMNTJaDjGmXzcExR8gDSeQ1vY985lNzlr3eavn79DGP +ew9dRrxQ733cHn2UXs76w60OihAOGPDC+EeDP/vuf5hIEcW0n7aoP6lkiVaEOgFHuxA vPbu5d8rvDtxySbJ+uldlVbSLyGFG0Dq0HTShxtXHRzurk+WERncnxS7fDdCima0uVwX XVuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:subject:to:from:date; bh=AG3THxer5QQIirHTNHyqRGeiWRn4KOkF2NIqAEDDnH4=; b=EkTL9yBgcnxLsRWnMzFnN9Pc378GA2P/2qgN5o9pQAvERg9z0pVg9HQm9YMbOJg7BT z89PJ/AEmB3AMQtp9VS9pwVVDZOkXrEFMpSAGAroV2Q5OHnWunI/XmfMZRyojsKz3zs3 NIPFA9qlzcNpcJEPOnmuA9cLre5x/33pMvhhIWqw2WWA74HOW/l4/S0e9dKixDocDq+K 6judEpQ2qR5/s7VshQY2ltdppcmNIu2N/5NgaULy43KCLzSpfKs5S4fWIkjQEf6rrn41 vJbvAKzG30vFHHiV4xYO2ebA2H0+m4nCJ0dnYlogtcoF96zC21ZO3m1x8VfmXuNzdKUy NkBQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b24si192276eje.85.2019.09.16.16.07.47; Mon, 16 Sep 2019 16:08:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728386AbfIPVjY (ORCPT + 99 others); Mon, 16 Sep 2019 17:39:24 -0400 Received: from mail.kernel.org ([198.145.29.99]:43144 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726125AbfIPVjY (ORCPT ); Mon, 16 Sep 2019 17:39:24 -0400 Received: from gandalf.local.home (cpe-66-24-58-225.stny.res.rr.com [66.24.58.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9F0D220644; Mon, 16 Sep 2019 21:39:22 +0000 (UTC) Date: Mon, 16 Sep 2019 17:39:21 -0400 From: Steven Rostedt To: LKML , linux-rt-users , Thomas Gleixner , Carsten Emde , John Kacur , Sebastian Andrzej Siewior , Julia Cartwright , Daniel Wagner , tom.zanussi@linux.intel.com Subject: [ANNOUNCE] 4.19.72-rt25 Message-ID: <20190916173921.6368cd62@gandalf.local.home> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear RT Folks, I'm pleased to announce the 4.19.72-rt25 stable release. **** **** As you probably have noticed, it has been a long time since I released a stable 4.19-rt. The reason for this delay is that one of my tests failed after merging with the latest stable upstream. I refuse to push releases with a known bug in it, so I figured I would find the bug before releasing. I only spend around 4 to 6 hours a week on upstream stable RT as I have other responsibilities, and I could not debug this bug during that time (after several weeks of trying). The bug is a random NULL pointer dereference that only happens with lockdep enabled and on 32bit x86. I also found that this bug existed before the latest stable pull release but now it is much easier to trigger. I have not been able to trigger this bug in the 64 bit kernel, and as I rather do a release than waste more time on this bug and postpone the release further, I am now doing that. As a consequence, I am no longer supporting 32bit x86, as it is known to have this bug. If you are interested in this, I am willing to send out the config I am using and one of the dmesg crashes. Just ask. **** **** This release is just an update to the new stable 4.19.72 version and no RT specific changes have been made. 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: 9cd04ab6a9a162ac4189a80032261d243563ff45 Or to build 4.19.72-rt25 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.72.xz http://www.kernel.org/pub/linux/kernel/projects/rt/4.19/patch-4.19.72-rt25.patch.xz Enjoy, -- Steve