Netdev List
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: Sabrina Dubroca <sd@queasysnail.net>, netdev@vger.kernel.org
Cc: Stefano Brivio <sbrivio@redhat.com>
Subject: Re: [PATCH net-next 2/3] selftests: pmtu: extend MTU parsing helper to locked MTU
Date: Mon, 8 Oct 2018 11:35:40 -0600	[thread overview]
Message-ID: <db3a8c81-cf50-9b4e-9141-d37a48b96648@gmail.com> (raw)
In-Reply-To: <99a5ccbf8aa2b8dae9955d14a8562f4de6ad2152.1539001627.git.sd@queasysnail.net>

On 10/8/18 6:37 AM, Sabrina Dubroca wrote:
> The mtu_parse helper introduced in commit f2c929feeccd ("selftests:
> pmtu: Factor out MTU parsing helper") can only handle "mtu 1234", but
> not "mtu lock 1234". Extend it, so that we can do IPv4 tests with PMTU
> smaller than net.ipv4.route.min_pmtu
> 
> Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
> ---
>  tools/testing/selftests/net/pmtu.sh | 2 ++
>  1 file changed, 2 insertions(+)
> 

Reviewed-by: David Ahern <dsahern@gmail.com>

  reply	other threads:[~2018-10-09  0:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-08 12:37 [PATCH net-next 0/3] selftests: add more PMTU tests Sabrina Dubroca
2018-10-08 12:37 ` [PATCH net-next 1/3] selftests: pmtu: Introduce check_pmtu_value() Sabrina Dubroca
2018-10-08 17:35   ` David Ahern
2018-10-08 12:37 ` [PATCH net-next 2/3] selftests: pmtu: extend MTU parsing helper to locked MTU Sabrina Dubroca
2018-10-08 17:35   ` David Ahern [this message]
2018-10-08 12:37 ` [PATCH net-next 3/3] selftests: pmtu: add basic IPv4 and IPv6 PMTU tests Sabrina Dubroca
2018-10-08 17:36   ` David Ahern
2018-10-08 18:00 ` [PATCH net-next 0/3] selftests: add more " David Miller

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=db3a8c81-cf50-9b4e-9141-d37a48b96648@gmail.com \
    --to=dsahern@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sbrivio@redhat.com \
    --cc=sd@queasysnail.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