All of lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 14 Jan 2015 23:48:20 +0100	[thread overview]
Message-ID: <1421275700.1950.34.camel@sipsolutions.net> (raw)
In-Reply-To: <20150114161334.28acf5fc@tlielax.poochiereds.net>

On Wed, 2015-01-14 at 16:13 -0500, Jeff Layton wrote:
> While running the trinity fuzzer in a KVM guest, I ^C'ed it at an
> (apparent) inopportune moment, and saw a bunch of these WARN_ONs pop:

A bunch?!

> [ 2375.793396] ------------[ cut here ]------------
> [ 2375.793397] WARNING: CPU: 0 PID: 1149 at net/netlink/genetlink.c:1037 genl_unbind+0xc0/0xd0()

This warning is supposed to happen only when you somehow manage to
unsubscribe from a generic netlink group that doesn't actually exist, or
so.

Do you have any sort of log/trace of what trinity actually did at/before
this point?

johannes

  reply	other threads:[~2015-01-14 22:48 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 [this message]
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

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=1421275700.1950.34.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jeff.layton@primarydata.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 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.