All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: devel@driverdev.osuosl.org, samuel@sortiz.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org, lkp@01.org,
	davem@davemloft.net
Subject: Re: [lkp-robot] [irda]  66d98e78e4: BUG:unable_to_handle_kernel
Date: Wed, 30 Aug 2017 08:12:15 +0200	[thread overview]
Message-ID: <20170830061215.GA3682@kroah.com> (raw)
In-Reply-To: <20170830060410.GX30390@yexl-desktop>

On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
> 
> commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to drivers/staging/irda/net/")
> url: https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816
> 
> 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):
> 
> +-----------------------------------------------------+------------+------------+
> |                                                     | 89ff9d58e6 | 66d98e78e4 |
> +-----------------------------------------------------+------------+------------+
> | boot_successes                                      | 0          | 0          |
> | boot_failures                                       | 10         | 12         |
> | IP-Config:Auto-configuration_of_network_failed      | 8          |            |
> | WARNING:at_arch/x86/mm/dump_pagetables.c:#note_page | 2          |            |
> | EIP:note_page                                       | 2          |            |
> | BUG:unable_to_handle_kernel                         | 0          | 12         |
> | Oops:#[##]                                          | 0          | 12         |
> | EIP:dev_add_pack                                    | 0          | 12         |
> | Kernel_panic-not_syncing:Fatal_exception            | 0          | 12         |
> +-----------------------------------------------------+------------+------------+
> 
> [    0.227015] BUG: unable to handle kernel NULL pointer dereference at 00000004
> [    0.228000] IP: dev_add_pack+0x37/0x80

Didn't you report this yesterday as well?  Anyway, am working on it,
give me a few hours to wake up and test...

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel
Date: Wed, 30 Aug 2017 08:12:15 +0200	[thread overview]
Message-ID: <20170830061215.GA3682@kroah.com> (raw)
In-Reply-To: <20170830060410.GX30390@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 2101 bytes --]

On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote:
> FYI, we noticed the following commit:
> 
> commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to drivers/staging/irda/net/")
> url: https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816
> 
> 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):
> 
> +-----------------------------------------------------+------------+------------+
> |                                                     | 89ff9d58e6 | 66d98e78e4 |
> +-----------------------------------------------------+------------+------------+
> | boot_successes                                      | 0          | 0          |
> | boot_failures                                       | 10         | 12         |
> | IP-Config:Auto-configuration_of_network_failed      | 8          |            |
> | WARNING:at_arch/x86/mm/dump_pagetables.c:#note_page | 2          |            |
> | EIP:note_page                                       | 2          |            |
> | BUG:unable_to_handle_kernel                         | 0          | 12         |
> | Oops:#[##]                                          | 0          | 12         |
> | EIP:dev_add_pack                                    | 0          | 12         |
> | Kernel_panic-not_syncing:Fatal_exception            | 0          | 12         |
> +-----------------------------------------------------+------------+------------+
> 
> [    0.227015] BUG: unable to handle kernel NULL pointer dereference at 00000004
> [    0.228000] IP: dev_add_pack+0x37/0x80

Didn't you report this yesterday as well?  Anyway, am working on it,
give me a few hours to wake up and test...

thanks,

greg k-h

  reply	other threads:[~2017-08-30  6:12 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-27 15:03 [PATCH 0/4] irda: move it to drivers/staging so we can delete it Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 1/4] irda: move net/irda/ to drivers/staging/irda/net/ Greg Kroah-Hartman
2017-08-27 15:03   ` Greg Kroah-Hartman
2017-08-30  6:04   ` [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel kernel test robot
2017-08-30  6:04     ` kernel test robot
2017-08-30  6:12     ` Greg Kroah-Hartman [this message]
2017-08-30  6:12       ` Greg Kroah-Hartman
2017-08-30  6:19       ` Ye Xiaolong
2017-08-30  6:19         ` Ye Xiaolong
2017-08-27 15:03 ` [PATCH 2/4] irda: move drivers/net/irda to drivers/staging/irda/drivers Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 3/4] irda: move include/net/irda into staging subdirectory Greg Kroah-Hartman
2017-08-27 15:03 ` [PATCH 4/4] staging: irda: add a TODO file Greg Kroah-Hartman
2017-08-27 15:35 ` [PATCH 0/4] irda: move it to drivers/staging so we can delete it Joe Perches
2017-08-27 16:13   ` Greg Kroah-Hartman
2017-08-27 16:13     ` Greg Kroah-Hartman
2017-08-27 16:19     ` Joe Perches
2017-08-27 16:19       ` Joe Perches
2017-08-27 16:53       ` Greg Kroah-Hartman
2017-08-27 16:53         ` Greg Kroah-Hartman
2017-08-27 23:15         ` Joe Perches
2017-08-28 23:42 ` David Miller
2017-08-28 23:42   ` David Miller
2017-08-28 23:46   ` Joe Perches
2017-08-29  5:06     ` Greg KH
2017-08-29  5:06       ` Greg KH
2017-08-29 21:32   ` Ondrej Zary
2017-08-31  4:30     ` Greg KH
2017-08-31  4:30       ` Greg KH
2017-08-31  7:31       ` Ondrej Zary
2017-08-31  7:31         ` Ondrej Zary
2017-08-29 10:59 ` Geert Uytterhoeven
2017-08-29 11:11   ` Stefano Brivio
2017-08-29 11:11     ` Stefano Brivio
2017-08-29 11:28     ` Greg Kroah-Hartman
2017-08-29 12:11       ` Geert Uytterhoeven
2017-08-29 14:48         ` Greg Kroah-Hartman
2017-08-29 16:49           ` David Miller
2017-08-29 16:49             ` David Miller
2017-08-29 16:38   ` 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=20170830061215.GA3682@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=davem@davemloft.net \
    --cc=devel@driverdev.osuosl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=netdev@vger.kernel.org \
    --cc=samuel@sortiz.org \
    --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 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.