From: NeilBrown <neilb@suse.com>
To: kernel test robot <fengguang.wu@intel.com>
Cc: devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [staging] 184ecc5ceb: BUG:unable_to_handle_kernel
Date: Tue, 20 Mar 2018 13:34:09 +1100 [thread overview]
Message-ID: <87h8pba31a.fsf@notabene.neil.brown.name> (raw)
In-Reply-To: <20180319091931.gt6ijdw7ahkbtvrq@inn>
[-- Attachment #1.1: Type: text/plain, Size: 1842 bytes --]
On Mon, Mar 19 2018, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-6):
>
> commit: 184ecc5ceb379b43b29fc373f497fca88c73ad38 ("staging: lustre: allow monolithic builds")
> https://git.kernel.org/cgit/linux/kernel/git/gregkh/staging.git staging-testing
>
> in testcase: trinity
> with following parameters:
>
> runtime: 300s
>
> test-description: Trinity is a linux system call fuzz tester.
> test-url: http://codemonkey.org.uk/projects/trinity/
>
>
> on test machine: qemu-system-i386 -enable-kvm -smp 2 -m 320M
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +------------------------------------------+------------+------------+
> | | 26f7a294e5 | 184ecc5ceb |
> +------------------------------------------+------------+------------+
> | boot_successes | 14 | 4 |
> | boot_failures | 0 | 12 |
> | BUG:unable_to_handle_kernel | 0 | 12 |
> | Oops:#[##] | 0 | 12 |
> | EIP:cfs_cpt_spread_node | 0 | 12 |
> | Kernel_panic-not_syncing:Fatal_exception | 0 | 12 |
> +------------------------------------------+------------+------------+
>
>
>
> [ 123.548190] BUG: unable to handle kernel NULL pointer dereference at 00000008
> [ 123.551023] IP: cfs_cpt_spread_node+0x31/0x100
Thanks.
This happens when both USERIO and LNET are built into the kernel
drivers/staging/lustre/TODO says
LNET_MINOR conflicts with USERIO_MINOR
I'll add a Kconfig rule preventing them from being built together until
this is resolved properly.
I'll also lok into making the module init routine more robust.
Thanks,
NeilBrown
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 169 bytes --]
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
prev parent reply other threads:[~2018-03-20 2:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 9:19 [staging] 184ecc5ceb: BUG:unable_to_handle_kernel kernel test robot
2018-03-20 2:34 ` NeilBrown [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=87h8pba31a.fsf@notabene.neil.brown.name \
--to=neilb@suse.com \
--cc=devel@driverdev.osuosl.org \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox