From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@davemloft.net>
Cc: xiyou.wangcong@gmail.com, netdev@vger.kernel.org,
jiri@mellanox.com, code@rkapl.cz, fli4l@franke-prem.de,
stable@vger.kernel.org
Subject: Re: [Patch 4.14 0/4] net_sched: backport tc filter fixes to 4.14
Date: Fri, 2 Mar 2018 09:22:54 +0100 [thread overview]
Message-ID: <20180302082254.GA9281@kroah.com> (raw)
In-Reply-To: <20180301.205617.1833479492339800297.davem@davemloft.net>
On Thu, Mar 01, 2018 at 08:56:17PM -0500, David Miller wrote:
> From: Cong Wang <xiyou.wangcong@gmail.com>
> Date: Thu, 1 Mar 2018 13:46:35 -0800
>
> > This patchset backports 4 important bug fixes for tc filter to
> > 4.14 stable branch. Due to some big changes between 4.14 and 4.15,
> > the backports are not trivial, I have to adjust and fix the conflicts
> > manually.
> >
> > Thanks to Roland for reporting the kernel warning and testing
> > the patches.
> >
> > Reported-by: Roland Franke <fli4l@franke-prem.de>
> > Tested-by: Roland Franke <fli4l@franke-prem.de>
> > Cc: Jiri Pirko <jiri@mellanox.com>
> > Cc: Roman Kapl <code@rkapl.cz>
> > Cc: David S. Miller <davem@davemloft.net>
> > Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
>
> Greg, please queue up this series for -stable.
All now applied, thanks.
greg k-h
prev parent reply other threads:[~2018-03-02 8:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 21:46 [Patch 4.14 0/4] net_sched: backport tc filter fixes to 4.14 Cong Wang
2018-03-01 21:46 ` [Patch 4.14 1/4] net: sched: fix crash when deleting secondary chains Cong Wang
2018-03-01 21:46 ` [Patch 4.14 2/4] net: sched: crash on blocks with goto chain action Cong Wang
2018-03-01 21:46 ` [Patch 4.14 3/4] net_sched: get rid of rcu_barrier() in tcf_block_put_ext() Cong Wang
2018-03-01 21:46 ` [Patch 4.14 4/4] net: sched: fix use-after-free in tcf_block_put_ext Cong Wang
2018-03-02 1:56 ` [Patch 4.14 0/4] net_sched: backport tc filter fixes to 4.14 David Miller
2018-03-02 8:22 ` Greg KH [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=20180302082254.GA9281@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=code@rkapl.cz \
--cc=davem@davemloft.net \
--cc=fli4l@franke-prem.de \
--cc=jiri@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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).