From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: jianqi.ren.cn@windriver.com, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 6.1.y v2] net/sched: act_mirred: don't override retval if we already lost the skb
Date: Tue, 29 Apr 2025 08:50:23 -0400 [thread overview]
Message-ID: <20250429003113-2d1e50f66a422c0d@stable.kernel.org> (raw)
In-Reply-To: <20250428080103.4158144-1-jianqi.ren.cn@windriver.com>
[ 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: 166c2c8a6a4dc2e4ceba9e10cfe81c3e469e3210
WARNING: Author mismatch between patch and upstream commit:
Backport author: <jianqi.ren.cn@windriver.com>
Commit author: Jakub Kicinski<kuba@kernel.org>
Status in newer kernel trees:
6.14.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (different SHA1: 28cdbbd38a44)
Note: The patch differs from the upstream commit:
---
1: 166c2c8a6a4dc < -: ------------- net/sched: act_mirred: don't override retval if we already lost the skb
-: ------------- > 1: 799e00a9644fe net/sched: act_mirred: don't override retval if we already lost the skb
---
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-04-29 12:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 8:01 [PATCH 6.1.y v2] net/sched: act_mirred: don't override retval if we already lost the skb jianqi.ren.cn
2025-04-28 11:46 ` Greg KH
2025-04-29 2:07 ` Ren, Jianqi (Jacky) (CN)
2025-04-29 5:26 ` Greg KH
2025-04-29 12:50 ` Sasha Levin [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-04-28 7:45 jianqi.ren.cn
2025-04-28 7:52 ` Ren, Jianqi (Jacky) (CN)
2025-04-29 12:50 ` 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=20250429003113-2d1e50f66a422c0d@stable.kernel.org \
--to=sashal@kernel.org \
--cc=jianqi.ren.cn@windriver.com \
--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