All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Eric Dumazet <edumazet@google.com>,
	Andrey Konovalov <andreyknvl@google.com>,
	"David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	James Morris <jmorris@namei.org>,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	Patrick McHardy <kaber@trash.net>,
	netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Kostya Serebryany <kcc@google.com>,
	syzkaller <syzkaller@googlegroups.com>
Subject: Re: net/tcp: warning in tcp_try_coalesce/skb_try_coalesce
Date: Thu, 02 Feb 2017 05:40:12 -0800	[thread overview]
Message-ID: <1486042812.13103.27.camel@edumazet-glaptop3.roam.corp.google.com> (raw)
In-Reply-To: <CACT4Y+Z8uSWJaW+QXSOr7dCo5fSNrMu6fHxPcDBxL08qQUvRMw@mail.gmail.com>

On Thu, 2017-02-02 at 13:59 +0100, Dmitry Vyukov wrote:

> 
> Right, I can confirm that this is not happening on net-next tip
> (62e13097c46c69dbd7544ab2cd585ccf48f360a4).
> I reproduced it on a random month old commit on net-next, though
> (23a8ed4a624324dc696c328f09bd502c4a3816f0). Let's consider that this
> is accidentally fixed by something in that range.

This also might depend on the .config 

I tried 23a8ed4a624324dc696c328f09bd502c4a3816f0 and could not trigger
the warning .

Thanks.

  reply	other threads:[~2017-02-02 13:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-31 13:17 net/tcp: warning in tcp_try_coalesce/skb_try_coalesce Andrey Konovalov
2017-01-31 14:27 ` Eric Dumazet
2017-02-02  9:05   ` Dmitry Vyukov
2017-02-02 12:20     ` Eric Dumazet
2017-02-02 12:59       ` Dmitry Vyukov
2017-02-02 13:40         ` Eric Dumazet [this message]
2017-02-02 13:56           ` Dmitry Vyukov
2017-02-02 14:03             ` Dmitry Vyukov
2017-02-02 17:34               ` Dmitry Vyukov
2017-04-26 12:08 ` Andrey Konovalov
2017-04-26 14:16   ` Eric Dumazet

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=1486042812.13103.27.camel@edumazet-glaptop3.roam.corp.google.com \
    --to=eric.dumazet@gmail.com \
    --cc=andreyknvl@google.com \
    --cc=davem@davemloft.net \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=jmorris@namei.org \
    --cc=kaber@trash.net \
    --cc=kcc@google.com \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=syzkaller@googlegroups.com \
    --cc=yoshfuji@linux-ipv6.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.