From: Joe Korty <joe.korty@concurrent-rt.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Daniel Wagner <dwagner@suse.de>,
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>
Subject: Re: [ANNOUNCE] v4.4.231-rt202
Date: Sat, 8 Aug 2020 10:06:38 -0400 [thread overview]
Message-ID: <20200808140638.GA26582@zipoli.concurrent-rt.com> (raw)
In-Reply-To: <20200727151033.7c37df2b@oasis.local.home>
Ping?
On Mon, Jul 27, 2020 at 03:10:33PM -0400, Steven Rostedt wrote:
> 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-08-08 14:07 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
2020-08-08 14:06 ` Joe Korty [this message]
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=20200808140638.GA26582@zipoli.concurrent-rt.com \
--to=joe.korty@concurrent-rt.com \
--cc=C.Emde@osadl.org \
--cc=bigeasy@linutronix.de \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=pavel@denx.de \
--cc=rostedt@goodmis.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.