All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: David Sauerwein <dssauerw@amazon.de>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.10.y] fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats
Date: Sun, 13 Apr 2025 12:46:45 -0400	[thread overview]
Message-ID: <20250412095109-13b29e5a284c2d53@stable.kernel.org> (raw)
In-Reply-To: <20250411154758.57959-1-dssauerw@amazon.de>

[ Sasha's backport helper bot ]

Hi,

✅ All tests passed successfully. No issues detected.
No action required from the submitter.

The upstream commit SHA1 provided is correct: 7601df8031fd67310af891897ef6cc0df4209305

WARNING: Author mismatch between patch and upstream commit:
Backport author: David Sauerwein<dssauerw@amazon.de>
Commit author: Oleg Nesterov<oleg@redhat.com>

Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.13.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 3820b0fac773)
6.1.y | Present (different SHA1: cf4b8c39b9a0)
5.15.y | Not found

Note: The patch differs from the upstream commit:
---
1:  7601df8031fd6 < -:  ------------- fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats
-:  ------------- > 1:  9205eb3b53ba2 fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats
---

Results of testing on various branches:

| Branch                    | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.10.y       |  Success    |  Success   |

      reply	other threads:[~2025-04-13 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 15:47 [PATCH 5.10.y] fs/proc: do_task_stat: use sig->stats_lock to gather the threads/children stats David Sauerwein
2025-04-13 16:46 ` Sasha Levin [this message]

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=20250412095109-13b29e5a284c2d53@stable.kernel.org \
    --to=sashal@kernel.org \
    --cc=dssauerw@amazon.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 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.