From: Jens Axboe <axboe@kernel.dk>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
kernel test robot <xiaolong.ye@intel.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, linux-scsi@vger.kernel.org, tglx@linutronix.de,
linux-block@vger.kernel.org
Subject: Re: [lkp-robot] [rcu] b332151a29: kernel_BUG_at_mm/slab.c
Date: Fri, 20 Jan 2017 08:09:36 -0800 [thread overview]
Message-ID: <32585b54-c2fd-66ea-e636-bdbd387133c1@kernel.dk> (raw)
In-Reply-To: <20170120160123.z4llgm4qaaemkp52@linutronix.de>
On 01/20/2017 08:01 AM, Sebastian Andrzej Siewior wrote:
> On 2017-01-19 09:02:16 [+0800], kernel test robot wrote:
>> test-description: Trinity is a linux system call fuzz tester.
>
> you don't even get to fire up trinity. With and without the patch you
> crash very early.
>
>> +-----------------------------------------------------+------------+------------+
>> | | d5f6ab9c11 | b332151a29 |
>> +-----------------------------------------------------+------------+------------+
>> | boot_successes | 0 | 0 |
>> | boot_failures | 6 | 8 |
>> | WARNING:at_include/linux/kref.h:#kobject_get | 6 | 8 |
>> | WARNING:at_arch/x86/mm/dump_pagetables.c:#note_page | 2 | 2 |
>> | kernel_BUG_at_mm/slab.c | 0 | 4 |
>> | invalid_opcode:#[##]PREEMPT_SMP | 0 | 4 |
>> | Kernel_panic-not_syncing:Fatal_exception | 0 | 6 |
>> | BUG:unable_to_handle_kernel | 0 | 2 |
>> | Oops | 0 | 2 |
>> +-----------------------------------------------------+------------+------------+
>
> There is no successful boot. The pattern changes with patch in question
> applied.
>
>> [ 8.044624] sd 0:0:0:0: [sda] Synchronizing SCSI cache
>> [ 8.055721] slab: double free detected in cache 'kmalloc-32', objp 8af558c0
>> [ 8.057138] ------------[ cut here ]------------
>> [ 8.058085] kernel BUG at mm/slab.c:2624!
>> [ 8.059255] invalid opcode: 0000 [#1] PREEMPT SMP
Is there a full trace of this?
> yes. With and without the patch there is a lot of wrong stuff like
> complains about a kobject initialized again. This leads to a double free
> at some point.
And what patch are we talking about? I don't mind being CC'ed into a thread,
but some context and background would be immensely helpful here...
--
Jens Axboe
next prev parent reply other threads:[~2017-01-20 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 1:02 [lkp-robot] [rcu] b332151a29: kernel_BUG_at_mm/slab.c kernel test robot
2017-01-20 16:01 ` Sebastian Andrzej Siewior
2017-01-20 16:09 ` Jens Axboe [this message]
2017-01-20 16:23 ` Sebastian Andrzej Siewior
2017-01-20 16:32 ` Jens Axboe
2017-01-20 17:09 ` Sebastian Andrzej Siewior
2017-01-20 17:15 ` Jens Axboe
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=32585b54-c2fd-66ea-e636-bdbd387133c1@kernel.dk \
--to=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@01.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=xiaolong.ye@intel.com \
/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