From: Steven Rostedt <rostedt@goodmis.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Tom Zanussi <tom.zanussi@linux.intel.com>,
Clark Williams <williams@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Pavel Machek <pavel@denx.de>,
Joe Korty <joe.korty@concurrent-rt.com>
Subject: Re: [ANNOUNCE] v4.4.231-rt202
Date: Mon, 27 Jul 2020 15:10:33 -0400 [thread overview]
Message-ID: <20200727151033.7c37df2b@oasis.local.home> (raw)
In-Reply-To: <3732c1c4-36d4-2cdc-677a-cb58a9507df1@suse.de>
On Sun, 26 Jul 2020 13:55:12 +0200
Daniel Wagner <dwagner@suse.de> wrote:
> Hi,
>
> On 24.07.20 15:41, Daniel Wagner wrote:
> > Known issues:
> >
> > sigwaittest with hackbench as workload is able to trigger a crash on x86_64,
> > the same as reported for the v4.4.220-rt196 release. As it turns
> > out it was not triggered by BPF.
> > https://paste.opensuse.org/view/raw/58939248
>
> Joe pointed out [1] that v4.4-rt is missing 9567db2ebe56 ("signal:
> Prevent double-free of user struct") from devel-rt. With this
> patch all my tests pass.
>
> @stable-rt team: Can you please add it to the missing trees?
Good catch,
I'll pull this in on Friday.
-- Steve
>
> Thanks,
> Daniel
>
> [1]
> https://lore.kernel.org/linux-rt-users/20200626130544.GA37967@zipoli.concurrent-rt.com/
next prev parent reply other threads:[~2020-07-27 19:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 13:41 [ANNOUNCE] v4.4.231-rt202 Daniel Wagner
2020-07-26 11:55 ` Daniel Wagner
2020-07-27 19:10 ` Steven Rostedt [this message]
2020-08-08 14:06 ` Joe Korty
2020-08-10 13:29 ` Steven Rostedt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727151033.7c37df2b@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=joe.korty@concurrent-rt.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=williams@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).