From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Alexey Panov <apanov@astralinux.ru>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1 2/2] erofs: fix PSI memstall accounting
Date: Fri, 28 Feb 2025 23:20:35 -0500 [thread overview]
Message-ID: <20250228185254-bfcc3535c1953e85@stable.kernel.org> (raw)
In-Reply-To: <20250228165103.26775-3-apanov@astralinux.ru>
[ 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: 1a2180f6859c73c674809f9f82e36c94084682ba
WARNING: Author mismatch between patch and upstream commit:
Backport author: Alexey Panov<apanov@astralinux.ru>
Commit author: Gao Xiang<hsiangkao@linux.alibaba.com>
Status in newer kernel trees:
6.13.y | Present (exact SHA1)
6.12.y | Present (different SHA1: 0653fa6ee045)
6.6.y | Present (different SHA1: 14f030a807dd)
Note: The patch differs from the upstream commit:
---
1: 1a2180f6859c7 < -: ------------- erofs: fix PSI memstall accounting
-: ------------- > 1: 63f49db1d3fb4 erofs: fix PSI memstall accounting
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-6.1.y | Success | Success |
next prev parent reply other threads:[~2025-03-01 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 16:51 [PATCH 6.1 0/2] erofs: handle overlapped pclusters out of crafted images properly Alexey Panov
2025-02-28 16:51 ` [PATCH 6.1 1/2] " Alexey Panov
2025-03-01 4:21 ` Sasha Levin
2025-03-02 10:56 ` Fedor Pchelkin
2025-03-02 17:41 ` Gao Xiang
2025-03-02 17:56 ` Gao Xiang
2025-03-02 18:13 ` Fedor Pchelkin
2025-03-03 0:31 ` Gao Xiang
2025-03-03 9:19 ` Fedor Pchelkin
2025-03-04 11:18 ` Алексей Панов
2025-02-28 16:51 ` [PATCH 6.1 2/2] erofs: fix PSI memstall accounting Alexey Panov
2025-03-01 4:20 ` Sasha Levin [this message]
2025-03-01 2:52 ` [PATCH 6.1 0/2] erofs: handle overlapped pclusters out of crafted images properly Gao Xiang
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=20250228185254-bfcc3535c1953e85@stable.kernel.org \
--to=sashal@kernel.org \
--cc=apanov@astralinux.ru \
--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