From: Johannes Berg <johannes@sipsolutions•net>
To: Jeff Layton <jeff.layton@primarydata•com>
Cc: netdev@vger•kernel.org
Subject: Re: [ 2375.793397] WARNING: CPU: 0 PID: 1149 at net/netlink/genetlink.c:1037 genl_unbind+0xc0/0xd0()
Date: Thu, 15 Jan 2015 14:01:08 +0100 [thread overview]
Message-ID: <1421326868.1962.13.camel@sipsolutions.net> (raw)
In-Reply-To: <20150115074956.4e5617cd@tlielax.poochiereds.net> (sfid-20150115_134959_506751_D19674F4)
On Thu, 2015-01-15 at 07:49 -0500, Jeff Layton wrote:
> It may have. I just recently started playing with trinity, so I don't
> know much about what it does. I do see these sorts of messages in the
> logs that imply that it's opening netlink sockets:
>
> [main] fd[661] = domain:16 (PF_NETLINK) type:0x2 protocol:10
> [main] fd[675] = domain:16 (PF_NETLINK) type:0x2 protocol:0
>
> ...and then it does random I/Os on those fds.
Yes. We're looking for generic netlink, so one of these (protocol 16):
[main] fd[427] = domain:16 (PF_NETLINK) type:0x3 protocol:16
[main] fd[442] = domain:16 (PF_NETLINK) type:0x2 protocol:16
[main] fd[774] = domain:16 (PF_NETLINK) type:0x2 protocol:16
However, I didn't see much happening on these fds, and even if it
wouldn't have recorded the kind of messages.
OTOH, multicast group stuff is done with setsockopt() and/or bind, which
I didn't really find here?
> FWIW, it tries to call delete_module, but I was running this as an
> unprivileged user so I don't think that can succeed.
Ok.
johannes
prev parent reply other threads:[~2015-01-15 13:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 21:13 [ 2375.793397] WARNING: CPU: 0 PID: 1149 at net/netlink/genetlink.c:1037 genl_unbind+0xc0/0xd0() Jeff Layton
2015-01-14 22:48 ` Johannes Berg
2015-01-14 23:25 ` Johannes Berg
2015-01-15 2:20 ` Jeff Layton
2015-01-15 8:37 ` Johannes Berg
[not found] ` <20150115071426.563573e7@tlielax.poochiereds.net>
[not found] ` <1421324985.1962.5.camel@sipsolutions.net>
2015-01-15 12:49 ` Jeff Layton
2015-01-15 13:01 ` Johannes Berg [this message]
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=1421326868.1962.13.camel@sipsolutions.net \
--to=johannes@sipsolutions$(echo .)net \
--cc=jeff.layton@primarydata$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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