From: David Miller <davem@davemloft.net>
To: dcaratti@redhat.com
Cc: lkp@intel.com, john.hurley@netronome.com, kbuild-all@01.org,
lorenzo@kernel.org, netdev@vger.kernel.org,
xiyou.wangcong@gmail.com, simon.horman@netronome.com
Subject: Re: [PATCH net v2 0/2] net/sched: fix wrong behavior of MPLS push/pop action
Date: Tue, 15 Oct 2019 17:16:05 -0700 (PDT) [thread overview]
Message-ID: <20191015.171605.1926923209676909296.davem@davemloft.net> (raw)
In-Reply-To: <cover.1570878412.git.dcaratti@redhat.com>
From: Davide Caratti <dcaratti@redhat.com>
Date: Sat, 12 Oct 2019 13:55:05 +0200
> this series contains two fixes for TC 'act_mpls', that try to address
> two problems that can be observed configuring simple 'push' / 'pop'
> operations:
> - patch 1/2 avoids dropping non-MPLS packets that pass through the MPLS
> 'pop' action.
> - patch 2/2 fixes corruption of the L2 header that occurs when 'push'
> or 'pop' actions are configured in TC egress path.
>
> v2: - change commit message in patch 1/2 to better describe that the
> patch impacts only TC, thanks to Simon Horman
> - fix missing documentation of 'mac_len' in patch 2/2
Series applied and queued up for -stable, thanks!
prev parent reply other threads:[~2019-10-16 0:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-12 11:55 [PATCH net v2 0/2] net/sched: fix wrong behavior of MPLS push/pop action Davide Caratti
2019-10-12 11:55 ` [PATCH net v2 1/2] net: avoid errors when trying to pop MLPS header on non-MPLS packets Davide Caratti
2019-10-12 11:55 ` [PATCH net v2 2/2] net/sched: fix corrupted L2 header with MPLS 'push' and 'pop' actions Davide Caratti
2019-10-12 12:41 ` [PATCH net v2 0/2] net/sched: fix wrong behavior of MPLS push/pop action Simon Horman
2019-10-16 0:16 ` David Miller [this message]
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=20191015.171605.1926923209676909296.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=dcaratti@redhat.com \
--cc=john.hurley@netronome.com \
--cc=kbuild-all@01.org \
--cc=lkp@intel.com \
--cc=lorenzo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=simon.horman@netronome.com \
--cc=xiyou.wangcong@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).