Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] instruction traps on tcp_rcv - bug 360 regression - reopened
Date: Sun, 22 Dec 2013 22:26:33 +0000	[thread overview]
Message-ID: <52B76719.5070203@gmail.com> (raw)
In-Reply-To: <CAA93jw7d3WU5DXdTg3C5yuXPZ9BfzKx8FYN=3=rY8LjKgPt3Kw@mail.gmail.com>

On 22/12/13 21:35, Dave Taht wrote:
> http://www.bufferbloat.net/issues/360
>
> I would be very reluctant to take seriously any benchmarks going to
> the router until this one is quashed. Really bad behavior (I put a
> plot up on the bug)
>
> Stuff going through the router appears to be sane, but if you are monitoring
> the router at the same time (like via ssh or a web page) there are
> side effects visible at higher rates.
>
> I am hopefully getting setup to do ipv6 again soon so as to make sure
> all those bugs remain squashed too....
>

It looks like tcp_parse_aligned_timestamp() in net/ipv4/tcp_input.c has
acquired an if(*ptr) statement between 3.8 and 3.10.  That bug had been
annoying me for a while...

diff --git a/net/ipv4/tcp_input.c b/net/ipv4/tcp_input.c
index 3d67689..c6496eb 100644
--- a/net/ipv4/tcp_input.c
+++ b/net/ipv4/tcp_input.c
@@ -3632,7 +3632,7 @@ static bool tcp_parse_aligned_timestamp(struct
tcp_sock *tp, const struct tcphdr
                ++ptr;
                tp->rx_opt.rcv_tsval = get_unaligned_be32(ptr);
                ++ptr;
-               if (*ptr)
+               if (net_hdr_word(ptr))
                        tp->rx_opt.rcv_tsecr = get_unaligned_be32(ptr) -
                                               tp->tsoffset;
                else

-- 
Robert Bradley


      reply	other threads:[~2013-12-22 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-22 21:35 Dave Taht
2013-12-22 22:26 ` Robert Bradley [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

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52B76719.5070203@gmail.com \
    --to=robert.bradley1@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /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