From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org, skulkarni@mvista.com
Cc: Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH 5.4.y 8/8] act_mirred: use the backlog for nested calls to mirred ingress
Date: Fri, 25 Jul 2025 21:01:37 -0400 [thread overview]
Message-ID: <1753464140-e7196da4@stable.kernel.org> (raw)
In-Reply-To: <20250724192619.217203-9-skulkarni@mvista.com>
[ Sasha's backport helper bot ]
Hi,
Summary of potential issues:
ℹ️ This is part 8/8 of a series
⚠️ Found follow-up fixes in mainline
The upstream commit SHA1 provided is correct: ca22da2fbd693b54dc8e3b7b54ccc9f7e9ba3640
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: 4c8fc3fe28e4)
5.15.y | Present (different SHA1: 169a41073993)
5.10.y | Present (different SHA1: 532451037863)
Found fixes commits:
5e8670610b93 selftests: forwarding: tc_actions: Use ncat instead of nc
Note: Could not generate a diff with upstream commit:
---
Note: Could not generate diff - patch failed to apply for comparison
---
NOTE: These results are for this patch alone. Full series testing will be
performed when all parts are received.
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| 5.4 | Success | Success |
next prev parent reply other threads:[~2025-07-26 1:01 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
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 [this message]
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=1753464140-e7196da4@stable.kernel.org \
--to=sashal@kernel.org \
--cc=skulkarni@mvista.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 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.