All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shannon Nelson <shannon.nelson@oracle.com>
To: Anders Roxell <anders.roxell@linaro.org>
Cc: Networking <netdev@vger.kernel.org>, David Miller <davem@davemloft.net>
Subject: Re: [PATCH net-next 0/2] fixes for ipsec selftests
Date: Wed, 20 Jun 2018 15:26:08 -0700	[thread overview]
Message-ID: <cd0832a6-0d65-b9de-35b4-fdcb72d6003d@oracle.com> (raw)
In-Reply-To: <CADYN=9+7DDh6UwT8oY1g61QkjoKpFwhRdDBcMdwDq8gX7sTbjw@mail.gmail.com>

On 6/20/2018 12:09 PM, Anders Roxell wrote:
> On Wed, 20 Jun 2018 at 07:42, Shannon Nelson <shannon.nelson@oracle.com> wrote:
>>
>> 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
>>
>>   tools/testing/selftests/net/rtnetlink.sh | 11 +++++++----
>>   1 file changed, 7 insertions(+), 4 deletions(-)
>>
>> --
>> 2.7.4
>>
> 
> Hi Shannon,
> 
> With this patches applied and my config patch.
> 
> I still get this error when I run the ipsec test:
> 
> FAIL: can't add fou port 7777, skipping test
> RTNETLINK answers: Operation not supported
> FAIL: can't add macsec interface, skipping test
> RTNETLINK answers: Protocol not supported
> RTNETLINK answers: No such process
> RTNETLINK answers: No such process
> FAIL: ipsec

One of the odd things I noticed about this script is that there really 
aren't any diagnosis messages, just PASS or FAIL.  I followed this 
custom when I added the ipsec tests, but I think this is something that 
should change so we can get some idea of what breaks.

I'm curious about the "RTNETLINK answers" messages and where they might 
be coming from, especially "RTNETLINK answers: Protocol not supported". 
What version of iproute2 are you using?  Is it older than iproute2-ss130716?

What distro and kernel are you running?

What are the XFRM and AES settings in your kernel config - what is the 
output from
	egrep -i "xfrm|_aes" .config

I did also notice that the ipsec test should set ret=0 at its start. 
Can you either add this or comment out all the other tests in 
kci_test_rtnl() so that only the kci_test_ipsec is run and send me the 
output?

Thanks,
sln


> 
> Can you please cc the kselftest list when sending patches to
> tools/testing/selftests/ ?
> 
> Cheers,
> Anders
> 

  reply	other threads:[~2018-06-20 22:26 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 [this message]
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
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=cd0832a6-0d65-b9de-35b4-fdcb72d6003d@oracle.com \
    --to=shannon.nelson@oracle.com \
    --cc=anders.roxell@linaro.org \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.