Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 18 Aug 2022 18:08:16 +0200
From:   Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To:     Joe Korty <joe.korty@concurrent-rt.com>
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)
Message-ID: <Yv5j8NQ72KXu60nL@linutronix.de>
References: <VI1PR09MB358214376379A2D6B024A689A0B39@VI1PR09MB3582.eurprd09.prod.outlook.com>
 <YrXtH1z2JSmwLS7W@T470>
 <20220624184431.GA4386@zipoli.concurrent-rt.com>
 <20220626123019.GA51149@zipoli.concurrent-rt.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20220626123019.GA51149@zipoli.concurrent-rt.com>
Precedence: bulk

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?

> Regards,
> Joe

Sebastian