From: David Miller <davem@davemloft.net>
To: shannon.nelson@oracle.com
Cc: netdev@vger.kernel.org, anders.roxell@linaro.org
Subject: Re: [PATCH net-next 0/2] fixes for ipsec selftests
Date: Fri, 22 Jun 2018 13:49:13 +0900 (KST) [thread overview]
Message-ID: <20180622.134913.2049651808540037401.davem@davemloft.net> (raw)
In-Reply-To: <1529473363-4036-1-git-send-email-shannon.nelson@oracle.com>
From: Shannon Nelson <shannon.nelson@oracle.com>
Date: Tue, 19 Jun 2018 22:42:41 -0700
> A couple of bad behaviors in the ipsec selftest were pointed out
> by Anders Roxell <anders.roxell@linaro.org> and are addressed here.
>
> Shannon Nelson (2):
> selftests: rtnetlink: hide complaint from terminated monitor
> selftests: rtnetlink: use a local IP address for IPsec tests
Series applied, but I wonder about patch #2.
The idea is that we don't make modifications to the actual system
networking configuration and therefore make changes that can't
possibly disrupt connectivity for the system under test.
Using a configured local IP address seems to subvert that.
next prev parent reply other threads:[~2018-06-22 4:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 5:42 [PATCH net-next 0/2] fixes for ipsec selftests Shannon Nelson
2018-06-20 5:42 ` [PATCH net-next 1/2] selftests: rtnetlink: hide complaint from terminated monitor Shannon Nelson
2018-06-20 5:42 ` [PATCH net-next 2/2] selftests: rtnetlink: use a local IP address for IPsec tests Shannon Nelson
2018-06-20 19:09 ` [PATCH net-next 0/2] fixes for ipsec selftests Anders Roxell
2018-06-20 22:26 ` Shannon Nelson
2018-06-20 23:18 ` Anders Roxell
2018-06-21 0:32 ` Shannon Nelson
2018-06-21 16:56 ` Anders Roxell
2018-06-21 17:25 ` Shannon Nelson
2018-06-22 4:49 ` David Miller [this message]
2018-06-22 6:50 ` Shannon Nelson
2018-06-22 7:27 ` 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=20180622.134913.2049651808540037401.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=anders.roxell@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=shannon.nelson@oracle.com \
/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).