From: Florian Westphal <fw@strlen.de>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [test_rhashtable] c1bd3689a7: WARNING:at_lib/debugobjects.c:#__debug_object_init
Date: Wed, 20 Sep 2017 10:44:28 +0200 [thread overview]
Message-ID: <20170920084428.GA15946@breakpoint.cc> (raw)
In-Reply-To: <20170920015457.GA30213@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
kernel test robot <xiaolong.ye@intel.com> wrote:
> FYI, we noticed the following commit:
>
> commit: c1bd3689a70d1ba1a2f7c6781770920087166018 ("test_rhashtable: add test case for rhl_table interface")
> url: https://github.com/0day-ci/linux/commits/Florian-Westphal/test_rhashtable-add-test-case-for-rhl-table/20170919-135550
>
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -smp 2 -m 512M
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +---------------------------------------------------------+------------+------------+
> [ 15.235031] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:328 __debug_object_init+0x794/0x930
[..]
This is with v1 of the patch where the rhltable struct was allocated on
stack, v2 is fine.
WARNING: multiple messages have this Message-ID (diff)
From: Florian Westphal <fw@strlen.de>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Florian Westphal <fw@strlen.de>, netdev@vger.kernel.org, lkp@01.org
Subject: Re: [lkp-robot] [test_rhashtable] c1bd3689a7: WARNING:at_lib/debugobjects.c:#__debug_object_init
Date: Wed, 20 Sep 2017 10:44:28 +0200 [thread overview]
Message-ID: <20170920084428.GA15946@breakpoint.cc> (raw)
In-Reply-To: <20170920015457.GA30213@yexl-desktop>
kernel test robot <xiaolong.ye@intel.com> wrote:
> FYI, we noticed the following commit:
>
> commit: c1bd3689a70d1ba1a2f7c6781770920087166018 ("test_rhashtable: add test case for rhl_table interface")
> url: https://github.com/0day-ci/linux/commits/Florian-Westphal/test_rhashtable-add-test-case-for-rhl-table/20170919-135550
>
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -smp 2 -m 512M
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +---------------------------------------------------------+------------+------------+
> [ 15.235031] WARNING: CPU: 0 PID: 1 at lib/debugobjects.c:328 __debug_object_init+0x794/0x930
[..]
This is with v1 of the patch where the rhltable struct was allocated on
stack, v2 is fine.
next prev parent reply other threads:[~2017-09-20 8:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 21:07 [PATCH net-next 0/4] test_rhashtable: add test case for rhl table Florian Westphal
2017-09-18 21:07 ` [PATCH net-next 1/4] test_rhashtable: don't allocate huge static array Florian Westphal
2017-09-18 21:07 ` [PATCH net-next 2/4] test_rhashtable: don't use global entries variable Florian Westphal
2017-09-18 21:07 ` [PATCH net-next 3/4] test_rhashtable: add a check for max_size Florian Westphal
2017-09-18 21:07 ` [PATCH net-next 4/4] test_rhashtable: add test case for rhl_table interface Florian Westphal
2017-09-19 14:59 ` kbuild test robot
2017-09-20 1:54 ` [lkp-robot] [test_rhashtable] c1bd3689a7: WARNING:at_lib/debugobjects.c:#__debug_object_init kernel test robot
2017-09-20 1:54 ` kernel test robot
2017-09-20 8:44 ` Florian Westphal [this message]
2017-09-20 8:44 ` Florian Westphal
2017-09-19 21:03 ` [PATCH net-next 0/4] test_rhashtable: add test case for rhl table David Miller
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=20170920084428.GA15946@breakpoint.cc \
--to=fw@strlen.de \
--cc=lkp@lists.01.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.