[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <78791260-c029-4ce8-d44a-61f3a9b392d1@acm.org>
Date: Wed, 7 Nov 2018 18:26:12 -0800
From: Bart Van Assche <bvanassche@....org>
To: kernel test robot <rong.a.chen@...el.com>
Cc: Lee Duncan <lduncan@...e.com>, Hannes Reinecke <hare@...e.com>,
Luis Chamberlain <mcgrof@...nel.org>,
Johannes Thumshirn <jthumshirn@...e.de>,
Christoph Hellwig <hch@....de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Bart Van Assche <bart.vanassche@...disk.com>, lkp@...org
Subject: Re: [LKP] [drivers/base] 1431aa42b3:
WARNING:at_drivers/base.c:#device_bind_driver
On 11/7/18 4:24 PM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 1431aa42b3afc1dd50b292abcc68ccdc3193da63 ("drivers/base: Verify struct device locking requirements at runtime")
> https://github.com/bvanassche/linux for-next
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu IvyBridge -smp 2 -m 2G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> [ ... ]
A fix has already been pushed out, so I think this report can be ignored.
Bart.
Powered by blists - more mailing lists