stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
	"David S . Miller" <davem@davemloft.net>,
	linux-kernel@vger.kernel.org, Michal Kubecek <mkubecek@suse.cz>,
	Jiri Bohac <jbohac@suse.cz>
Subject: Re: [PATCH 4.4.y] tcp: Fix missing range_truesize enlargement in the backport
Date: Wed, 15 Aug 2018 14:15:07 +0200	[thread overview]
Message-ID: <s5hin4b7rn8.wl-tiwai@suse.de> (raw)
In-Reply-To: <20180815111121.GA17583@kroah.com>

On Wed, 15 Aug 2018 13:11:21 +0200,
Greg Kroah-Hartman wrote:
> 
> On Wed, Aug 15, 2018 at 11:58:46AM +0200, Takashi Iwai wrote:
> > The 4.4.y stable backport dc6ae4dffd65 for the upstream commit
> > 3d4bf93ac120 ("tcp: detect malicious patterns in
> > tcp_collapse_ofo_queue()") missed a line that enlarges the
> > range_truesize value, which broke the whole check.
> > 
> > Fixes: dc6ae4dffd65 ("tcp: detect malicious patterns in tcp_collapse_ofo_queue()")
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> > 
> > Greg, this is a fix-up specific to 4.4.y stable backport that had a
> > slightly different form from upstream fix.  I haven't looked at the
> > older trees, but 4.9.y and later took the upstream fix as is, so this
> > patch isn't needed for them.
> > 
> > The patch hasn't been tested with the real test case, though; let me
> > know if the current code is intended.  Thanks!
> 
> Hm, I did the initial backport, and then Eric showed what I got wrong
> and fixed that up, so being still wrong is not inconceivable at all :)
> 
> Have you tried testing this with the reproducer?  That might be the best
> verification here.  If your testing proves to be good, I'll gladly take
> this patch, thanks!

No, I haven't tested it, just followed from the thread in the past
(and hope that our QA team will test that sooner or later :)
Will let you know if we find any issues in the current tree.

And, if the current code works as intended, it's great, of course.


thanks,

Takashi

  reply	other threads:[~2018-08-15 15:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-15  9:58 [PATCH 4.4.y] tcp: Fix missing range_truesize enlargement in the backport Takashi Iwai
2018-08-15 11:11 ` Greg Kroah-Hartman
2018-08-15 12:15   ` Takashi Iwai [this message]
2018-08-15 20:02   ` Michal Kubecek
2018-08-16 15:16     ` Greg Kroah-Hartman

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=s5hin4b7rn8.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbohac@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mkubecek@suse.cz \
    --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;
as well as URLs for NNTP newsgroup(s).