linux-kernel - Re: [PATCH v7] NVMe: conversion to blk-mq

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <5397636F.9050209@fb.com>
Date:	Tue, 10 Jun 2014 13:58:39 -0600
From:	Jens Axboe <axboe@...com>
To:	Keith Busch <keith.busch@...el.com>
CC:	Matias Bjørling <m@...rling.me>,
	"willy@...ux.intel.com" <willy@...ux.intel.com>,
	"sbradshaw@...ron.com" <sbradshaw@...ron.com>,
	"tom.leiming@...il.com" <tom.leiming@...il.com>,
	"hch@...radead.org" <hch@...radead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>
Subject: Re: [PATCH v7] NVMe: conversion to blk-mq

On 06/10/2014 01:29 PM, Keith Busch wrote:
> On Tue, 10 Jun 2014, Jens Axboe wrote:
>>> On Jun 10, 2014, at 9:52 AM, Keith Busch <keith.busch@...el.com> wrote:
>>>
>>>> On Tue, 10 Jun 2014, Matias Bjørling wrote:
>>>> This converts the current NVMe driver to utilize the blk-mq layer.
>>>
>>> I'd like to run xfstests on this, but it is failing mkfs.xfs. I honestly
>>> don't know much about this area, but I think this may be from the recent
>>> chunk sectors patch causing a __bio_add_page to reject adding a new
>>> page.
>>
>> Gah, yes that's a bug in the chunk patch. It must always allow a
>> single page
>> at any offset. I'll test and send out a fix.
> 
> I have two devices, one formatted 4k, the other 512. The 4k is used as
> the TEST_DEV and 512 is used as SCRATCH_DEV. I'm always hitting a BUG when
> unmounting the scratch dev in xfstests generic/068. The bug looks like
> nvme was trying to use an SGL that doesn't map correctly to a PRP.

I'm guessing it's some of the coalescing settings, since the driver is
now using the generic block rq mapping.

> Also, it doesn't look like this driver can recover from an unresponsive
> device, leaving tasks in uniterruptible sleep state forever. Still looking
> into that one though; as far as I can tell the device is perfectly fine,
> but lots of "Cancelling I/O"  messages are getting logged.

If the task is still stuck, some of the IOs must not be getting cancelled.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/