From: Jakub Kicinski <kuba@kernel.org>
To: Ido Schimmel <idosch@idosch.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"netdev-driver-reviewers@vger.kernel.org"
<netdev-driver-reviewers@vger.kernel.org>
Subject: Re: [TEST] bridge tests (was: net-next is OPEN)
Date: Thu, 1 Feb 2024 16:16:19 -0800 [thread overview]
Message-ID: <20240201161619.0d248e4e@kernel.org> (raw)
In-Reply-To: <20240201073025.04cc760f@kernel.org>
On Thu, 1 Feb 2024 07:30:25 -0800 Jakub Kicinski wrote:
> On Thu, 1 Feb 2024 15:46:23 +0200 Ido Schimmel wrote:
> > > selftests-net/test-bridge-neigh-suppress-sh
> > > - fails across all, so must be the OS rather than the "speed"
> >
> > Yes, it's something related to the OS. From the log below:
> >
> > ```
> > COMMAND: ip netns exec h1-n8Aaip ndisc6 -q -r 1 -s 2001:db8:1::1 -w 5000 2001:db8:1::2 eth0.10
> > Raw IPv6 socket: Operation not permitted
> > TEST: ndisc6 [FAIL]
> > rc=1, expected 0
> > ```
> >
> > The test is supposed to be run as root so I'm not sure what this error
> > is about. Do you have something like AppArmor or SELinux running? The
> > program creates an IPv6 raw socket and requires CAP_NET_RAW.
>
> Ah, ugh, sorry for the misdirection, you're right.
Confirmed, with the SUID cleared test-bridge-neigh-suppress-sh now
passes on everything with the exception of metal+debug kernel.
next prev parent reply other threads:[~2024-02-02 0:16 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 17:16 [ANN] net-next is OPEN Jakub Kicinski
2024-01-22 20:54 ` Simon Horman
2024-01-23 8:45 ` Hangbin Liu
2024-01-23 15:20 ` Jakub Kicinski
2024-01-23 16:51 ` David Ahern
2024-01-23 21:39 ` Jakub Kicinski
2024-01-24 5:20 ` David Ahern
2024-01-24 8:22 ` Paolo Abeni
2024-01-24 15:07 ` Jakub Kicinski
2024-01-24 16:19 ` Jakub Kicinski
2024-01-24 16:35 ` David Ahern
2024-01-24 16:59 ` Jakub Kicinski
2024-01-24 21:48 ` David Ahern
2024-01-27 0:56 ` David Ahern
2024-01-27 1:13 ` Jakub Kicinski
2024-01-28 4:26 ` David Ahern
2024-01-29 9:23 ` Paolo Abeni
2024-01-29 15:03 ` Jakub Kicinski
2024-01-29 15:32 ` David Ahern
2024-01-29 16:53 ` Jakub Kicinski
2024-01-24 15:59 ` Willem de Bruijn
2024-01-24 16:22 ` Jakub Kicinski
2024-01-24 17:01 ` Jakub Kicinski
2024-01-24 18:35 ` Matthieu Baerts
2024-01-24 19:00 ` Jakub Kicinski
2024-01-24 19:18 ` [netfilter-core] " Pablo Neira Ayuso
2024-02-06 18:31 ` Matthieu Baerts
2024-02-07 9:49 ` Pablo Neira Ayuso
2024-02-07 11:33 ` Matthieu Baerts
2024-02-16 15:38 ` Pablo Neira Ayuso
2024-02-16 15:51 ` Matthieu Baerts
2024-01-24 19:16 ` Pablo Neira Ayuso
2024-01-24 19:40 ` Jakub Kicinski
2024-01-24 20:02 ` Pablo Neira Ayuso
2024-01-24 20:13 ` Jakub Kicinski
2024-01-25 5:07 ` Jakub Kicinski
2024-01-25 8:52 ` Florian Westphal
2024-01-25 17:30 ` Jakub Kicinski
2024-01-25 9:29 ` Pablo Neira Ayuso
2024-01-25 17:34 ` Jakub Kicinski
2024-01-24 17:42 ` Willem de Bruijn
2024-01-24 17:49 ` Jakub Kicinski
2024-01-24 18:23 ` Willem de Bruijn
2024-01-24 18:31 ` Paolo Abeni
2024-01-23 9:55 ` Petr Machata
2024-01-23 12:42 ` Matthias May
2024-01-23 13:38 ` Petr Machata
2024-01-23 15:30 ` Jakub Kicinski
2024-01-23 16:05 ` Petr Machata
2024-01-23 16:33 ` Jakub Kicinski
2024-01-23 15:34 ` Jakub Kicinski
2024-01-23 17:04 ` Petr Machata
2024-01-23 17:38 ` Jakub Kicinski
2024-01-24 11:06 ` Petr Machata
2024-01-29 12:43 ` Ido Schimmel
2024-01-29 12:46 ` Ido Schimmel
2024-01-29 15:00 ` Jakub Kicinski
2024-01-29 17:00 ` Ido Schimmel
2024-01-29 17:18 ` Jakub Kicinski
2024-01-31 13:23 ` Ido Schimmel
2024-01-31 14:16 ` Heiner Kallweit
2024-01-31 16:01 ` [TEST] bridge tests (was: net-next is OPEN) Jakub Kicinski
2024-02-01 13:46 ` Ido Schimmel
2024-02-01 15:30 ` Jakub Kicinski
2024-02-02 0:16 ` Jakub Kicinski [this message]
2024-02-08 16:21 ` Ido Schimmel
2024-02-08 17:26 ` Jakub Kicinski
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=20240201161619.0d248e4e@kernel.org \
--to=kuba@kernel.org \
--cc=idosch@idosch.org \
--cc=netdev-driver-reviewers@vger.kernel.org \
--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.