Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Pedro Tammela <pctammela@mojatatu.com>
To: gregkh@linuxfoundation.org, davem@davemloft.net,
	jhs@mojatatu.com, simon.horman@corigine.com
Cc: stable@vger.kernel.org
Subject: Re: Patch "net/sched: act_api: move TCA_EXT_WARN_MSG to the correct hierarchy" has been added to the 6.1-stable tree
Date: Mon, 19 Jun 2023 09:23:01 -0300	[thread overview]
Message-ID: <ecd5cd8c-66f8-0775-d509-32313bb4e70e@mojatatu.com> (raw)
In-Reply-To: <2023061951-existing-canned-81a5@gregkh>

On 19/06/2023 03:52, gregkh@linuxfoundation.org wrote:
> 
> This is a note to let you know that I've just added the patch titled
> 
>      net/sched: act_api: move TCA_EXT_WARN_MSG to the correct hierarchy
> 
> to the 6.1-stable tree which can be found at:
>      http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> 
> The filename of the patch is:
>       net-sched-act_api-move-tca_ext_warn_msg-to-the-correct-hierarchy.patch
> and it can be found in the queue-6.1 subdirectory.
> 
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
> 
> 
>  From 923b2e30dc9cd05931da0f64e2e23d040865c035 Mon Sep 17 00:00:00 2001
> From: Pedro Tammela <pctammela@mojatatu.com>
> Date: Fri, 24 Feb 2023 14:56:01 -0300
> Subject: net/sched: act_api: move TCA_EXT_WARN_MSG to the correct hierarchy
> 
> From: Pedro Tammela <pctammela@mojatatu.com>
> 
> commit 923b2e30dc9cd05931da0f64e2e23d040865c035 upstream.
> 
> TCA_EXT_WARN_MSG is currently sitting outside of the expected hierarchy
> for the tc actions code. It should sit within TCA_ACT_TAB.
> 
> Fixes: 0349b8779cc9 ("sched: add new attr TCA_EXT_WARN_MSG to report tc extact message")
> Reviewed-by: Jamal Hadi Salim <jhs@mojatatu.com>
> Signed-off-by: Pedro Tammela <pctammela@mojatatu.com>
> Reviewed-by: Simon Horman <simon.horman@corigine.com>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> ---
>   net/sched/act_api.c |    4 ++--
>   1 file changed, 2 insertions(+), 2 deletions(-)
> 
> --- a/net/sched/act_api.c
> +++ b/net/sched/act_api.c
> @@ -1603,12 +1603,12 @@ static int tca_get_fill(struct sk_buff *
>   	if (tcf_action_dump(skb, actions, bind, ref, false) < 0)
>   		goto out_nlmsg_trim;
>   
> -	nla_nest_end(skb, nest);
> -
>   	if (extack && extack->_msg &&
>   	    nla_put_string(skb, TCA_EXT_WARN_MSG, extack->_msg))
>   		goto out_nlmsg_trim;
>   
> +	nla_nest_end(skb, nest);
> +
>   	nlh->nlmsg_len = skb_tail_pointer(skb) - b;
>   
>   	return skb->len;
> 

Hi!
This commit is bogus. The correct one to pull is:
2f59823fe696 ("net/sched: act_api: add specific EXT_WARN_MSG for tc action")
If it's already in the queue then just removing this one is enough.

Thanks,
Pedro


       reply	other threads:[~2023-06-19 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2023061951-existing-canned-81a5@gregkh>
2023-06-19 12:23 ` Pedro Tammela [this message]
2023-06-19 12:31   ` Patch "net/sched: act_api: move TCA_EXT_WARN_MSG to the correct hierarchy" has been added to the 6.1-stable tree Greg KH

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=ecd5cd8c-66f8-0775-d509-32313bb4e70e@mojatatu.com \
    --to=pctammela@mojatatu.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jhs@mojatatu.com \
    --cc=simon.horman@corigine.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