public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: Fengguang Wu <fengguang.wu@intel.com>, Thomas Graf <tgraf@suug.ch>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, LKP <lkp@01.org>
Subject: Re: [rhashtable] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:301 __debug_object_init()
Date: Tue, 14 Jul 2015 10:50:26 +0200	[thread overview]
Message-ID: <55A4CD52.5060104@iogearbox.net> (raw)
In-Reply-To: <20150714052136.GA20251@wfg-t540p.sh.intel.com>

On 07/14/2015 07:21 AM, Fengguang Wu wrote:
> Sorry please ignore -- this no longer happen in linux-next, so should be fine.

Seen this before, this fixed it back then:

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/lib/test_rhashtable.c?id=b7f5e5c7f8cedf6b69c9702d448cdf78ffc45c7b

  reply	other threads:[~2015-07-14  8:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14  5:19 [rhashtable] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:301 __debug_object_init() Fengguang Wu
2015-07-14  5:21 ` Fengguang Wu
2015-07-14  8:50   ` Daniel Borkmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-01-12 23:22 Fengguang Wu

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=55A4CD52.5060104@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=netdev@vger.kernel.org \
    --cc=tgraf@suug.ch \
    /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