[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4a2adc33-ef38-6a5f-65ee-8fcfaa0948a9@infradead.org>
Date: Thu, 14 Mar 2019 16:49:28 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Jens Axboe <axboe@...nel.dk>,
linux-block <linux-block@...r.kernel.org>
Cc: LKML <linux-kernel@...r.kernel.org>, Tim Waugh <tim@...erelk.net>,
linux-parport@...ts.infradead.org
Subject: Re: paride/pf.c: blk-mq use-after-free (kernel v5.0)
On 3/14/19 4:43 PM, Jens Axboe wrote:
> On 3/13/19 5:09 PM, Randy Dunlap wrote:
>> On 3/11/19 6:34 PM, Randy Dunlap wrote:
>>> On 3/11/19 6:25 PM, Randy Dunlap wrote:
>>>> [Has this already been addressed/fixed?]>>
>>>
>>> Same bug occurs with paride/pcd.c driver.
>>
>> This still happens (in blk-mq) in v5.0-11053-gebc551f2b8f9 of Mar. 12, 2019,
>> around 4pm PT. [caused by paride: pf.c and pcd.c)
>
> I'll take a look at this, been busy with other stuff. How are you
> reproducing this? I'm assuming you don't actually have any hardware :-)
Right. I just load the module (pf or pcd), unload it, and
then load it again.
--
~Randy
Powered by blists - more mailing lists