From: David Miller <davem@davemloft.net>
To: marcelo.leitner@gmail.com
Cc: netdev@vger.kernel.org, eric.dumazet@gmail.com,
jmaxwell37@gmail.com, markus@trippelsdorf.de
Subject: Re: [PATCH net] tcp: minimize false-positives on TCP/GRO check
Date: Mon, 03 Apr 2017 18:44:56 -0700 (PDT) [thread overview]
Message-ID: <20170403.184456.724166144761742945.davem@davemloft.net> (raw)
In-Reply-To: <47c94077ffa8988118a19514389b42fccdc2f6ef.1491054871.git.marcelo.leitner@gmail.com>
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Date: Sat, 1 Apr 2017 11:00:21 -0300
> Markus Trippelsdorf reported that after commit dcb17d22e1c2 ("tcp: warn
> on bogus MSS and try to amend it") the kernel started logging the
> warning for a NIC driver that doesn't even support GRO.
>
> It was diagnosed that it was possibly caused on connections that were
> using TCP Timestamps but some packets lacked the Timestamps option. As
> we reduce rcv_mss when timestamps are used, the lack of them would cause
> the packets to be bigger than expected, although this is a valid case.
>
> As this warning is more as a hint, getting a clean-cut on the
> threshold is probably not worth the execution time spent on it. This
> patch thus alleviates the false-positives with 2 quick checks: by
> accounting for the entire TCP option space and also checking against the
> interface MTU if it's available.
>
> These changes, specially the MTU one, might mask some real positives,
> though if they are really happening, it's possible that sooner or later
> it will be triggered anyway.
>
> Reported-by: Markus Trippelsdorf <markus@trippelsdorf.de>
> Cc: Eric Dumazet <eric.dumazet@gmail.com>
> Signed-off-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
Applied, thanks Marcelo.
prev parent reply other threads:[~2017-04-04 1:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-01 14:00 [PATCH net] tcp: minimize false-positives on TCP/GRO check Marcelo Ricardo Leitner
2017-04-04 1:44 ` David Miller [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=20170403.184456.724166144761742945.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jmaxwell37@gmail.com \
--cc=marcelo.leitner@gmail.com \
--cc=markus@trippelsdorf.de \
--cc=netdev@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).