From: Ido Schimmel <idosch@idosch.org>
To: "Mahesh Bandewar (महेश बंडेवार)" <maheshb@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>, Petr Machata <petrm@nvidia.com>,
Jian Yang <jianyang.kernel@gmail.com>,
David Miller <davem@davemloft.net>,
linux-netdev <netdev@vger.kernel.org>,
Jian Yang <jianyang@google.com>
Subject: Re: [PATCH net-next v3] net-loopback: set lo dev initial state to UP
Date: Tue, 9 Feb 2021 21:06:27 +0200 [thread overview]
Message-ID: <20210209190627.GA267182@shredder.lan> (raw)
In-Reply-To: <CAF2d9jj3x9CbPbB6u3gQyW=80WqXxwqnk2bbk1pEmkP6K_Wasg@mail.gmail.com>
On Tue, Feb 09, 2021 at 10:49:23AM -0800, Mahesh Bandewar (महेश बंडेवार) wrote:
> On Tue, Feb 9, 2021 at 8:23 AM Jakub Kicinski <kuba@kernel.org> wrote:
> >
> > On Tue, 9 Feb 2021 12:54:59 +0100 Petr Machata wrote:
> > > Jian Yang <jianyang.kernel@gmail.com> writes:
> > >
> > > > From: Jian Yang <jianyang@google.com>
> > > >
> > > > Traditionally loopback devices come up with initial state as DOWN for
> > > > any new network-namespace. This would mean that anyone needing this
> > > > device would have to bring this UP by issuing something like 'ip link
> > > > set lo up'. This can be avoided if the initial state is set as UP.
> > >
> > > This will break user scripts, and it fact breaks kernel's very own
> > > selftest. We currently have this internally:
> > >
> > > diff --git a/tools/testing/selftests/net/fib_nexthops.sh b/tools/testing/selftests/net/fib_nexthops.sh
> > > index 4c7d33618437..bf8ed24ab3ba 100755
> > > --- a/tools/testing/selftests/net/fib_nexthops.sh
> > > +++ b/tools/testing/selftests/net/fib_nexthops.sh
> > > @@ -121,8 +121,6 @@ create_ns()
> > > set -e
> > > ip netns add ${n}
> > > ip netns set ${n} $((nsid++))
> > > - ip -netns ${n} addr add 127.0.0.1/8 dev lo
> > > - ip -netns ${n} link set lo up
> > >
> > > ip netns exec ${n} sysctl -qw net.ipv4.ip_forward=1
> > > ip netns exec ${n} sysctl -qw net.ipv4.fib_multipath_use_neigh=1
> > >
> > > This now fails because the ip commands are run within a "set -e" block,
> > > and kernel rejects addition of a duplicate address.
> >
> > Thanks for the report, could you send a revert with this explanation?
> Rather than revert, shouldn't we just fix the self-test in that regard?
I reviewed such a patch internally and asked Petr to report it as a
regression instead. At the time the new behavior was added under a
sysctl, but nobody had examples for behavior that will break, so the
sysctl was removed. Now we have such an example, so the revert / sysctl
are needed.
next prev parent reply other threads:[~2021-02-09 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 23:34 [PATCH net-next v3] net-loopback: set lo dev initial state to UP Jian Yang
2021-02-05 3:00 ` patchwork-bot+netdevbpf
2021-02-09 11:54 ` Petr Machata
2021-02-09 16:23 ` Jakub Kicinski
2021-02-09 17:19 ` Petr Machata
2021-02-09 18:49 ` Mahesh Bandewar (महेश बंडेवार)
2021-02-09 19:04 ` Jakub Kicinski
2021-02-09 19:18 ` Mahesh Bandewar (महेश बंडेवार)
2021-02-09 19:43 ` Jakub Kicinski
2021-02-09 19:06 ` Ido Schimmel [this message]
2021-02-09 19:19 ` Mahesh Bandewar (महेश बंडेवार)
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=20210209190627.GA267182@shredder.lan \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=jianyang.kernel@gmail.com \
--cc=jianyang@google.com \
--cc=kuba@kernel.org \
--cc=maheshb@google.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@nvidia.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).