From: William Tu <u9012063@gmail.com>
To: Linux Kernel Network Developers <netdev@vger.kernel.org>
Cc: chrism@mellanox.com, David Ahern <dsahern@gmail.com>
Subject: help on iproute2 hangs
Date: Thu, 1 Mar 2018 09:29:59 -0800 [thread overview]
Message-ID: <CALDO+SaXQtxLkdsWM=5StJzTbnUEKBuRT+9nJRgziY9ZA3CBEg@mail.gmail.com> (raw)
Hi,
We're running commands below on kernel 4.15.0:
1) ip netns add at_ns0
2) ip link add p0 type veth peer name ovs-p0
3) ip link set p0 netns at_ns0
4) ip link set dev ovs-p0 up
However, it always hangs at creating veth peer, command (2) when we
run above commands in GNU autotest. Running the same commands in a
bash script works fine.
Running bisect on iproute2, the first bad commit is
commit 72a2ff3916e59d2132a7d613d9e8f5eb372ba43e
Author: Chris Mi <chrism@mellanox.com>
Date: Fri Jan 12 14:13:15 2018 +0900
lib/libnetlink: Add a new function rtnl_talk_iov
rtnl_talk can only send a single message to kernel. Add a new function
rtnl_talk_iov that can send multiple messages to kernel.
rtnl_talk_iov takes struct iovec * and iovlen as arguments.
GDB shows it hangs on
#0 0x00007f9c92e6b330 in recvmsg () from /lib/x86_64-linux-gnu/libc.so.6
#1 0x000000000044eac6 in __rtnl_recvmsg ()
#2 0x000000000044eb95 in rtnl_recvmsg ()
#3 0x000000000044ed46 in __rtnl_talk_iov ()
#4 0x000000000044fbb8 in rtnl_talk ()
#5 0x0000000000422554 in iplink_modify ()
Any suggestion about how to debug this?
Thanks
William
next reply other threads:[~2018-03-01 17:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 17:29 William Tu [this message]
2018-03-01 18:36 ` help on iproute2 hangs David Ahern
2018-03-01 18:51 ` William Tu
2018-03-01 21:38 ` David Ahern
2018-03-01 22:13 ` William Tu
2018-03-01 22:14 ` David Ahern
2018-03-01 22:24 ` William Tu
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='CALDO+SaXQtxLkdsWM=5StJzTbnUEKBuRT+9nJRgziY9ZA3CBEg@mail.gmail.com' \
--to=u9012063@gmail.com \
--cc=chrism@mellanox.com \
--cc=dsahern@gmail.com \
--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 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).