[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Mon, 10 Oct 2016 14:34:56 -0500
From: Rob Herring <robh@...nel.org>
To: CAI Qian <caiqian@...hat.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: kasan inline + CONFIG_DEBUG_TEST_DRIVER_REMOVE kernel panic
On Mon, Oct 10, 2016 at 1:22 PM, CAI Qian <caiqian@...hat.com> wrote:
>
>
> ----- Original Message -----
>> From: "Rob Herring" <robh@...nel.org>
>> To: "Greg Kroah-Hartman" <gregkh@...uxfoundation.org>
>> Cc: "CAI Qian" <caiqian@...hat.com>, "linux-kernel" <linux-kernel@...r.kernel.org>
>> Sent: Monday, October 10, 2016 2:15:29 PM
>> Subject: Re: kasan inline + CONFIG_DEBUG_TEST_DRIVER_REMOVE kernel panic
>>
>> On Mon, Oct 10, 2016 at 12:20 PM, Greg Kroah-Hartman
>> <gregkh@...uxfoundation.org> wrote:
>> > On Mon, Oct 10, 2016 at 11:37:27AM -0400, CAI Qian wrote:
>> >> Not sure if anyone reported this before. With this kernel config, it is
>> >> 100% kernel panic so far with today's
>> >> mainline master HEAD.
>> >>
>> >> http://people.redhat.com/qcai/tmp/config-kasan-remove
>> >
>> > Oh it breaks things with kasan disabled as well :)
>> >
>> > See Laszlo's bug report already a few hours ago, Rob is on it...
>>
>> I think this one is different though. It has a remove() hook.
> FYI, this can also be reproduced without kasan.
Is the backtrace the same in that case?
Rob
Powered by blists - more mailing lists