All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Neal Cardwell <ncardwell@google.com>
Cc: Vinson Lee <vlee@freedesktop.org>,
	stable@vger.kernel.org, Yuchung Cheng <ycheng@google.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [stable request 4.4] tcp: fix tcp_mark_head_lost to check skb len before fragmenting
Date: Thu, 13 Jul 2017 16:01:42 +0200	[thread overview]
Message-ID: <20170713140142.GA2215@kroah.com> (raw)
In-Reply-To: <CADVnQy=o3Hwo--2p5KbcJubwHkHp0JShFHqrc=2E8guDDzk6oQ@mail.gmail.com>

On Thu, Jul 06, 2017 at 03:02:16PM -0400, Neal Cardwell wrote:
> �Hi,
> 
> Yes, I can confirm that it would make sense to backport
> 
> � �d88270e ("tcp: fix tcp_mark_head_lost to check skb len before fragmenting")
> 
> to 4.4-stable. It should help address that warning shown in that stack trace.
> 
> Unfortunately we don't have a packetdrill test case for this, and it triggers
> quite rarely in our environment. But we have been running with this patch in
> our environment for over a year, and it works fine for us.

Thanks for the confirmation, will go apply it now.

greg k-h

  parent reply	other threads:[~2017-07-13 14:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 21:51 [stable request 4.4] tcp: fix tcp_mark_head_lost to check skb len before fragmenting Vinson Lee
2017-06-27 11:31 ` Greg KH
2017-07-06 17:23   ` Vinson Lee
     [not found]     ` <CADVnQy=o3Hwo--2p5KbcJubwHkHp0JShFHqrc=2E8guDDzk6oQ@mail.gmail.com>
2017-07-13 14:01       ` Greg KH [this message]
2017-07-13 14:06         ` Neal Cardwell

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=20170713140142.GA2215@kroah.com \
    --to=greg@kroah.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=ncardwell@google.com \
    --cc=stable@vger.kernel.org \
    --cc=vlee@freedesktop.org \
    --cc=ycheng@google.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 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.