[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3122b34e-7a9e-8d81-da01-99ff23b6e3e1@kernel.dk>
Date: Tue, 30 Jun 2020 12:55:49 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Christoph Hellwig <hch@....de>
Cc: linux-bcache@...r.kernel.org, linux-xtensa@...ux-xtensa.org,
linux-nvdimm@...ts.01.org, linux-s390@...r.kernel.org,
dm-devel@...hat.com, linux-nvme@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-raid@...r.kernel.org,
linux-m68k@...ts.linux-m68k.org, linuxppc-dev@...ts.ozlabs.org,
drbd-dev@...ts.linbit.com
Subject: Re: rename ->make_request_fn and move it to the
block_device_operations
On 6/30/20 12:21 PM, Jens Axboe wrote:
> On 6/30/20 12:19 PM, Christoph Hellwig wrote:
>> On Tue, Jun 30, 2020 at 09:43:31AM -0600, Jens Axboe wrote:
>>> On 6/30/20 7:57 AM, Jens Axboe wrote:
>>>> On 6/29/20 1:39 PM, Christoph Hellwig wrote:
>>>>> Hi Jens,
>>>>>
>>>>> this series moves the make_request_fn method into block_device_operations
>>>>> with the much more descriptive ->submit_bio name. It then also gives
>>>>> generic_make_request a more descriptive name, and further optimize the
>>>>> path to issue to blk-mq, removing the need for the direct_make_request
>>>>> bypass.
>>>>
>>>> Looks good to me, and it's a nice cleanup as well. Applied.
>>>
>>> Dropped, insta-crashes with dm:
>>
>> Hmm. Can you send me what is at "submit_bio_noacct+0x1f6" from gdb?
>> Or your .config?
>
> I'd have to apply and compile again. But it's a bad RIP, so I'm guessing
> it's ->submit_bio == NULL. Let me know if you really need it, and I can
> re-generate the OOPS and have the vmlinux too.
Here's the .config
--
Jens Axboe
View attachment "qemu-config" of type "text/plain" (81287 bytes)
Powered by blists - more mailing lists