public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Christian Simon <simon@swine.de>
Cc: stable@vger.kernel.org, regressions@lists.linux.dev, jolsa@kernel.org
Subject: Re: [6.1.y][6.6.y] uprobes: Fix race in uprobe_free_utask
Date: Wed, 5 Mar 2025 15:05:24 +0100	[thread overview]
Message-ID: <2025030550-last-fit-9d20@gregkh> (raw)
In-Reply-To: <f32da38f-d313-48ed-9ca6-7da210b08f8b@swine.de>

On Tue, Mar 04, 2025 at 10:33:24AM +0000, Christian Simon wrote:
> Dear stable team,
> 
> I noticed that cfa7f3d2c526 ("perf,x86: avoid missing caller address in stack traces captured in uprobe"), got backported into 6.1.113 and 6.6.55, but it contains a race condition which Jiri Olsa has fixed in mainline b583ef82b671 ("uprobes: Fix race in uprobe_free_utask"). I think this should be backported into those stable branches.
> 
> #regzbot title: uprobes: Fix race in uprobe_free_utask
> #regzbot introduced: cfa7f3d2c526
> #regzbot link: https://lore.kernel.org/all/20250109141440.2692173-1-jolsa@kernel.org/
> 
> Link: https://lore.kernel.org/all/20250109141440.2692173-1-jolsa@kernel.org/
> 
> Note: Sorry if I am using the wrong process/form/format, I tried to follow "Option 2" from the stable-kernel-rules.html.

As the patch does not apply cleanly to those kernels, how did you test
this?

Can you provide some working, and tested, patches for this?  We'll be
glad to queue them up if so.

thanks,

greg k-h

  reply	other threads:[~2025-03-05 14:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 10:33 [6.1.y][6.6.y] uprobes: Fix race in uprobe_free_utask Christian Simon
2025-03-05 14:05 ` Greg KH [this message]
2025-03-05 18:27   ` [PATCH 6.6.y] " Christian Simon
2025-03-06 19:11     ` Sasha Levin
2025-03-06  9:24   ` [PATCH 6.1.y] " Christian Simon
2025-03-06 19:11     ` Sasha Levin
2025-03-06 13:38   ` [PATCH 6.12.y] " Christian Simon
2025-03-06 19:11     ` Sasha Levin

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=2025030550-last-fit-9d20@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=jolsa@kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=simon@swine.de \
    --cc=stable@vger.kernel.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