From: Joe Korty <joe.korty@concurrent-rt.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Mark Gross <markgross@kernel.org>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux RT users <linux-rt-users@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [RT BUG] Mismatched get_uid/free_uid usage in signals in some rts (2nd try)
Date: Thu, 18 Aug 2022 12:31:26 -0400 [thread overview]
Message-ID: <20220818163126.GA47319@zipoli.concurrent-rt.com> (raw)
In-Reply-To: <Yv5j8NQ72KXu60nL@linutronix.de>
On Thu, Aug 18, 2022 at 06:08:16PM +0200, Sebastian Andrzej Siewior wrote:
> On 2022-06-26 08:30:19 [-0400], Joe Korty wrote:
> > Hi Mark,
> > Absent an actual test of your port of a99e09659e6c to 4.9-rt, I just
> > eye-verified that the change it makes to sigqueue_free_current looks
> > correct. In detail,
> >
> > matches the same change the Linus patch makes to __sigqueue_free (ie,
> > to the routine that sigqueue_free_current is a copy of).
> >
> > That the new variable 'up', in sigqueue_free_current, is being used
> > in the patch (some variants of this fix do not have 'up'), and that
> > variable is present in 4.9's version of sigqueue_free_current.
> >
> > That atomic_dec_and_test, rather than the refcounting version of that
> > some function, is being used (some versions of this patch are refcounted
> > instead).
>
> What is the status here? Is this still needed?
Hi Sebastian,
I just verified that 4.9.319-rt195 has this fix.
Regards,
Joe
next prev parent reply other threads:[~2022-08-18 16:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 15:16 [RT BUG] Mismatched get_uid/free_uid usage in signals in some rts (2nd try) Joe Korty
2022-06-24 16:58 ` Mark Gross
2022-06-24 18:44 ` Joe Korty
2022-06-26 12:30 ` Joe Korty
2022-08-18 16:08 ` Sebastian Andrzej Siewior
2022-08-18 16:31 ` Joe Korty [this message]
2022-08-18 16:33 ` Sebastian Andrzej Siewior
2022-08-18 16:58 ` Joe Korty
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=20220818163126.GA47319@zipoli.concurrent-rt.com \
--to=joe.korty@concurrent-rt.com \
--cc=bigeasy@linutronix.de \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.