From: Mike Snitzer <snitzer@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
linux-bcache@vger.kernel.org
Subject: Re: [PATCH 2/3] dm: remove the make_request_fn check in device_area_is_invalid
Date: Tue, 28 Apr 2020 14:38:13 -0400 [thread overview]
Message-ID: <20200428183812.GA17609@redhat.com> (raw)
In-Reply-To: <20200425075336.721021-3-hch@lst.de>
On Sat, Apr 25 2020 at 3:53am -0400,
Christoph Hellwig <hch@lst.de> wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Think it'd be useful to add a commit message like you did for revert
commit f01b411f41f91fc3196eae4317cf8b4d872830a6 , e.g.:
We can't have queues without a make_request_fn any more (and the loop
device uses blk-mq these days anyway..).
But that aside:
Acked-by: Mike Snitzer <snitzer@redhat.com>
Thanks.
> ---
> drivers/md/dm-table.c | 17 -----------------
> 1 file changed, 17 deletions(-)
>
> diff --git a/drivers/md/dm-table.c b/drivers/md/dm-table.c
> index 0a2cc197f62b4..8277b959e00bd 100644
> --- a/drivers/md/dm-table.c
> +++ b/drivers/md/dm-table.c
> @@ -279,7 +279,6 @@ static struct dm_dev_internal *find_device(struct list_head *l, dev_t dev)
> static int device_area_is_invalid(struct dm_target *ti, struct dm_dev *dev,
> sector_t start, sector_t len, void *data)
> {
> - struct request_queue *q;
> struct queue_limits *limits = data;
> struct block_device *bdev = dev->bdev;
> sector_t dev_size =
> @@ -288,22 +287,6 @@ static int device_area_is_invalid(struct dm_target *ti, struct dm_dev *dev,
> limits->logical_block_size >> SECTOR_SHIFT;
> char b[BDEVNAME_SIZE];
>
> - /*
> - * Some devices exist without request functions,
> - * such as loop devices not yet bound to backing files.
> - * Forbid the use of such devices.
> - */
> - q = bdev_get_queue(bdev);
> - if (!q || !q->make_request_fn) {
> - DMWARN("%s: %s is not yet initialised: "
> - "start=%llu, len=%llu, dev_size=%llu",
> - dm_device_name(ti->table->md), bdevname(bdev, b),
> - (unsigned long long)start,
> - (unsigned long long)len,
> - (unsigned long long)dev_size);
> - return 1;
> - }
> -
> if (!dev_size)
> return 0;
>
> --
> 2.26.1
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2020-04-28 18:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 7:53 avoid the ->make_request_fn indirect for blk-mq drivers Christoph Hellwig
2020-04-25 7:53 ` [PATCH 1/3] bcache: remove a duplicate ->make_request_fn assignment Christoph Hellwig
2020-04-26 9:35 ` Coly Li
2020-04-25 7:53 ` [PATCH 2/3] dm: remove the make_request_fn check in device_area_is_invalid Christoph Hellwig
2020-04-28 18:38 ` Mike Snitzer [this message]
2020-04-25 7:53 ` [PATCH 3/3] block: bypass ->make_request_fn for blk-mq drivers Christoph Hellwig
2020-04-28 18:40 ` Mike Snitzer
2020-04-25 15:45 ` avoid the ->make_request_fn indirect " Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200428183812.GA17609@redhat.com \
--to=snitzer@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).