From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Daniel Wagner <wagi@monom.org>
Cc: Matt Fleming <matt@codeblueprint.co.uk>,
linux-rt@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RT] signal: Prevent double-free of user struct
Date: Thu, 16 Apr 2020 10:05:05 +0200 [thread overview]
Message-ID: <20200416080505.ec4m4yifgyfti4kf@linutronix.de> (raw)
In-Reply-To: <f8152ef5-f71d-b8b6-fe9e-6a8678930775@monom.org>
On 2020-04-15 21:05:14 [+0200], Daniel Wagner wrote:
> Hi Sebastian,
Hi Daniel,
> This can be triggered by running sigwaittest.
>
> # sigwaittest -t -a -p 98
>
> a few seconds should be enough to get the splat.
thank you.
> > This is v5.6 only, correct?
>
> I've seen this also with a frankstein version of 5.2-rt...v5-4-rt :)
…
> Thanks,
> Daniel
Sebastian
next prev parent reply other threads:[~2020-04-16 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 9:54 [PATCH RT] signal: Prevent double-free of user struct Matt Fleming
2020-04-15 16:46 ` Sebastian Andrzej Siewior
2020-04-15 19:05 ` Daniel Wagner
2020-04-16 8:05 ` Sebastian Andrzej Siewior [this message]
2020-04-07 14:45 Markus Elfring
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=20200416080505.ec4m4yifgyfti4kf@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=wagi@monom.org \
/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).