From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: stable@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: stable fixes for nf_conncount 4.19.x
Date: Fri, 18 Jan 2019 09:14:17 +0100 [thread overview]
Message-ID: <20190118081417.GA6754@kroah.com> (raw)
In-Reply-To: <20190118065707.GA10207@kroah.com>
On Fri, Jan 18, 2019 at 07:57:07AM +0100, Greg Kroah-Hartman wrote:
> On Fri, Jan 18, 2019 at 02:24:14AM +0100, Pablo Neira Ayuso wrote:
> > Hi Greg,
> >
> > Could you cherry-pick the follow list of patches into -stable 4.19.x, please?
> >
> > a007232066f6 netfilter: nf_conncount: fix argument order to find_next_bit
> > c80f10bc973a netfilter: nf_conncount: speculative garbage collection on empty lists
> > 2f971a8f4255 netfilter: nf_conncount: move all list iterations under spinlock
> > df4a90250976 netfilter: nf_conncount: merge lookup and add functions
> > e8cfb372b38a netfilter: nf_conncount: restart search when nodes have been erased
> > f7fcc98dfc2d netfilter: nf_conncount: split gc in two phases
> > 4cd273bb91b3 netfilter: nf_conncount: don't skip eviction when age is negative
> > c78e7818f16f netfilter: nf_conncount: replace CONNCOUNT_LOCK_SLOTS with CONNCOUNT_SLOTS
> >
> > conncount infrastructure is not in good shape, for more details see:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=202013
>
> These should also go into 4.20.y as well, right? I don't want people to
> experience regressions moving from 4.19 to a newer kernel release.
I've queued them up to both now, thanks.
greg k-h
next prev parent reply other threads:[~2019-01-18 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 1:24 stable fixes for nf_conncount 4.19.x Pablo Neira Ayuso
2019-01-18 6:57 ` Greg Kroah-Hartman
2019-01-18 8:14 ` Greg Kroah-Hartman [this message]
2019-01-18 9:30 ` Reindl Harald
2019-01-18 12:41 ` Pablo Neira Ayuso
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=20190118081417.GA6754@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.org \
--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.