public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Gross <markgross@kernel.org>
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@archiver.kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	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: Fri, 24 Jun 2022 09:58:07 -0700	[thread overview]
Message-ID: <YrXtH1z2JSmwLS7W@T470> (raw)
In-Reply-To: <VI1PR09MB358214376379A2D6B024A689A0B39@VI1PR09MB3582.eurprd09.prod.outlook.com>

On Tue, Jun 21, 2022 at 03:16:39PM +0000, Joe Korty wrote:
> Mismatched get_uid/free_uid usage in signals in 4.9.312-rt193
> 
>      [  First attempt using mutt did not show up on the mailing lists.
>         Trying again with office365 Outlook.   Also added the 4.9-rt
>         maintainers. ]
> 
> The 4.19-rt patch,
> 
>    0329-signal-Prevent-double-free-of-user-struct.patch
> 
> needs to be ported to LAG 4.9-rt, as that release now has the Linus commit,
What does LAG stand for?

FWIW the cherry-pick within the RT-stable tree worked without conflict.
    (cherry picked from commit a99e09659e6cd4b633c3689f2c3aa5f8a816fe5b)
It compiles.
See 58a584ee59b2 signal: Prevent double-free of user struct in 
linux-stable-rt.git/v4.9-rt-next

> 
>    fda31c50292a ("signal: avoid double atomic counter increments for user accounting")
>
This was added to 4.9.y on March 20, 2020.
commit 4306259ff6b8b682322d9aeb0c12b27c61c4a548 in linux-stable.

How did you find this issue?  What is missing from my testing?

Do you have a test case that I can conferm my cherry-pick works?
Could you test the v4.9-rt-next branch to see if it fixes you issue?

--mark

> which breaks the longstanding rt patch,
> 
>    0259-signals-Allow-rt-tasks-to-cache-one-sigqueue-struct.patch
> 
> Current application status:
> 
>    4.4.302-rt232        OK      has both Linus's patch and the fix needed for rt.
>    4.9.312-rt193        BROKE   has Linus's patch but not the fix.
>    4.14.87-rt50         OK      does NOT have either Linus's patch nor its rt fix.
>    4.19.246-rt110       OK      has both Linus's patch and the fix needed for rt.
>    5.4.193-rt74         OK	has both Linus's patch and the fix needed for rt.
>    5.10.120-rt70        OK	has both Linus's patch and the fix needed for rt.
>    5.15.44-rt46         UNKNOWN no get_uid/free_uid usage in kernel/signal.c anymore.
> 
> Regards,
> Joe

  reply	other threads:[~2022-06-24 16:58 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 [this message]
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
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=YrXtH1z2JSmwLS7W@T470 \
    --to=markgross@kernel.org \
    --cc=Joe.Korty@concurrent-rt.com \
    --cc=bigeasy@linutronix.de \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@archiver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox