From: Greg KH <gregkh@linuxfoundation.org>
To: David Miller <davem@redhat.com>
Cc: fw@strlen.de, david@unsolicited.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, pablo@netfilter.org,
stable@vger.kernel.org
Subject: Re: iptables problem upgrading kernel from 3.18.8 to 3.19.1
Date: Mon, 16 Mar 2015 14:54:14 +0100 [thread overview]
Message-ID: <20150316135414.GA25978@kroah.com> (raw)
In-Reply-To: <20150312.154756.1175332873553032640.davem@redhat.com>
On Thu, Mar 12, 2015 at 03:47:56PM -0400, David Miller wrote:
> From: Florian Westphal <fw@strlen.de>
> Date: Sun, 8 Mar 2015 18:55:53 +0100
>
> > David R <david@unsolicited.net> wrote:
> >
> > [ CC Pablo & stable@ ]
> >
> >> I've just had an exception to my "uneventful kernel upgrade" monotony.
> >>
> >> My boot scripts failed when setting up the firewall due to this :-
> >>
> >> xt_recent: hitcount (1) is larger than packets to be remembered (1)
> >> for table xxxx
> >>
> >> This is a completely straightforward
> >>
> >> iptables -A yyyy -j REJECT -p tcp --reject-with tcp-reset -m recent
> >> --set --name xxxx --rsource
> >>
> >> Looking at the history for xt_recent.c it looks like this was introduced
> >> in abc86d0f99242b7f142b7cb8f90e30081dd3c256 but maybe corrected in
> >> cef9ed86ed62eeffcd017882278bbece32001f86 ?
> >
> > Right. I would recommend to revert abc86d0f99242b7f142b7cb8f90e30081dd3c256
> > in 3.19.y series rather than applying cef9ed86ed62, though.
>
> Greg, please queue up a revert of abc86d0f99242b7f142b7cb8f90e30081dd3c256 for
> 3.19.x -stable, if you haven't done so already.
Now done, thanks.
greg k-h
prev parent reply other threads:[~2015-03-16 13:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-08 10:12 iptables problem upgrading kernel from 3.18.8 to 3.19.1 David R
2015-03-08 17:55 ` Florian Westphal
2015-03-12 19:47 ` David Miller
2015-03-16 13:54 ` 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=20150316135414.GA25978@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=davem@redhat.com \
--cc=david@unsolicited.net \
--cc=fw@strlen.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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.