From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y 7/8] net/sched: act_mirred: better wording on protection against excessive stack growth
Date: Fri, 25 Jul 2025 20:25:00 -0400 [thread overview]
Message-ID: <1753464062-3c61abde@stable.kernel.org> (raw)
In-Reply-To: <20250724192619.217203-8-skulkarni@mvista.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: 78dcdffe0418ac8f3f057f26fe71ccf4d8ed851f
WARNING: Author mismatch between patch and upstream commit:
Backport author: <skulkarni@mvista.com>
Commit author: Davide Caratti <dcaratti@redhat.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.12.y | Present (exact SHA1)
6.6.y | Present (exact SHA1)
6.1.y | Present (different SHA1: e0c12b9bfffc)
5.15.y | Present (different SHA1: 5b347652aebd)
5.10.y | Present (different SHA1: f5bf8e3ca13e)
Note: Could not generate a diff with upstream commit:
---
Note: Could not generate diff - patch failed to apply for comparison
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 5.4 | Success | Success |
next prev parent reply other threads:[~2025-07-26 0:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 19:26 [PATCH 5.4.y 0/8] Backport CVE-2022-4269 fix to stable kernel v5.4.y skulkarni
2025-07-24 19:26 ` [PATCH 5.4.y 1/8] net: sched: extract common action counters update code into function skulkarni
2025-07-25 23:26 ` Sasha Levin
2025-07-24 19:26 ` [PATCH 5.4.y 2/8] net: sched: extract bstats " skulkarni
2025-07-25 23:24 ` Sasha Levin
2025-07-24 19:26 ` [PATCH 5.4.y 3/8] net: sched: extract qstats update code into functions skulkarni
2025-07-26 0:24 ` Sasha Levin
2025-07-24 19:26 ` [PATCH 5.4.y 4/8] net: sched: don't expose action qstats to skb_tc_reinsert() skulkarni
2025-07-26 1:01 ` Sasha Levin
2025-07-24 19:26 ` [PATCH 5.4.y 5/8] selftests: forwarding: tc_actions.sh: add matchall mirror test skulkarni
2025-07-25 23:26 ` Sasha Levin
2025-07-24 19:26 ` [PATCH 5.4.y 6/8] net/sched: act_mirred: refactor the handle of xmit skulkarni
2025-07-25 23:26 ` Sasha Levin
2025-07-24 19:26 ` [PATCH 5.4.y 7/8] net/sched: act_mirred: better wording on protection against excessive stack growth skulkarni
2025-07-26 0:25 ` Sasha Levin [this message]
2025-07-24 19:26 ` [PATCH 5.4.y 8/8] act_mirred: use the backlog for nested calls to mirred ingress skulkarni
2025-07-26 1:01 ` Sasha Levin
2025-07-28 5:26 ` skulkarni
2025-07-30 9:11 ` Greg KH
2025-07-30 12:17 ` Shubham Kulkarni
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=1753464062-3c61abde@stable.kernel.org \
--to=sashal@kernel.org \
--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