[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200630181928.GA7853@lst.de>
Date: Tue, 30 Jun 2020 20:19:28 +0200
From: Christoph Hellwig <hch@....de>
To: Jens Axboe <axboe@...nel.dk>
Cc: Christoph Hellwig <hch@....de>, dm-devel@...hat.com,
linux-kernel@...r.kernel.org, linux-m68k@...ts.linux-m68k.org,
linux-xtensa@...ux-xtensa.org, drbd-dev@...ts.linbit.com,
linuxppc-dev@...ts.ozlabs.org, linux-bcache@...r.kernel.org,
linux-raid@...r.kernel.org, linux-nvdimm@...ts.01.org,
linux-nvme@...ts.infradead.org, linux-s390@...r.kernel.org
Subject: Re: rename ->make_request_fn and move it to the
block_device_operations
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?
Powered by blists - more mailing lists