From: Greg KH <gregkh@linuxfoundation.org>
To: skulkarni@mvista.com
Cc: sashal@kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 5.4.y 8/8] act_mirred: use the backlog for nested calls to mirred ingress
Date: Wed, 30 Jul 2025 11:11:35 +0200 [thread overview]
Message-ID: <2025073030-thrash-negative-6089@gregkh> (raw)
In-Reply-To: <20250728052618.171895-1-skulkarni@mvista.com>
On Mon, Jul 28, 2025 at 10:56:18AM +0530, skulkarni@mvista.com wrote:
> My apologies for sending the HTML content in the previous email/reply which was rejected by the stable mailing list.
> Here is a resend without HTML part:
> ---
>
> Hello Sasha/Greg,
>
> For the "found follow-up fixes in mainline warning" for this patch:
> "Found fixes commits:
> 5e8670610b93 selftests: forwarding: tc_actions: Use ncat instead of nc"
>
> While analysing the patches, I actually had noticed that the commit 5e867061 is a follow up i.e. "fixes" commit. But this commit 5e867061 is not part of the next stable kernel v5.10.y and as per my understanding, we are not allowed to backport a commit which is not in the next stable kernel version. Thus I haven't included that commit/patch here.
>
> I am new to the process & learning the rules. Can you please let me know if any action is required from my side for this patchset here?
You need to submit all of the needed fixes for anything you have
backported as well. As you are introducing a "problem", that would not
be good.
But, as you say, this is not in the 5.10.y tree yet, so please submit a
version for that as well, then there should not be any problem.
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-30 9:11 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
2025-07-28 5:26 ` skulkarni
2025-07-30 9:11 ` Greg KH [this message]
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=2025073030-thrash-negative-6089@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox