[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6f9d84c118e0067f335ff0d65837d3bf34a6d39.camel@redhat.com>
Date: Wed, 27 Feb 2019 10:26:04 +0100
From: Paolo Abeni <pabeni@...hat.com>
To: Willem de Bruijn <willemdebruijn.kernel@...il.com>
Cc: Network Development <netdev@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Willem de Bruijn <willemb@...gle.com>
Subject: Re: [PATCH net] selftests: fixes for UDP GRO
Hi,
On Tue, 2019-02-26 at 13:38 -0500, Willem de Bruijn wrote:
> On Tue, Feb 26, 2019 at 9:28 AM Paolo Abeni <pabeni@...hat.com> wrote:
> > The current implementation for UDP GRO tests is racy: the receiver
> > may flush the RX queue while the sending is still transmitting and
> > incorrectly report RX errors, with a wrong number of packet received.
> >
> > Add explicit timeouts to the receiver for both connection activation
> > (first packet received for UDP) and reception completion, so that
> > in the above critical scenario the receiver will wait for the
> > transfer completion.
> >
> > Fixes: 3327a9c46352 ("selftests: add functionals test for UDP GRO")
> > Signed-off-by: Paolo Abeni <pabeni@...hat.com>
>
> Acked-by: Willem de Bruijn <willemb@...gle.com>
Thanks for reviewing.
> ---
>
> This is because of that "force termination after the second poll()"?
Yes, exactly.
> Could perhaps also just extend do_recv to wait while (!interrupted &&
> tnow < tstart + 2000) and avoid the explicit arguments.
I thought about that, but then UDP GRO self-tests would take a bit more
and the binary helper would be less re-usable for future test cases.
Cheers,
Paolo
Powered by blists - more mailing lists