[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211124065938.GB7229@lst.de>
Date: Wed, 24 Nov 2021 07:59:38 +0100
From: Christoph Hellwig <hch@....de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Christoph Hellwig <hch@....de>, Mike Snitzer <snitzer@...hat.com>,
Ira Weiny <ira.weiny@...el.com>,
device-mapper development <dm-devel@...hat.com>,
linux-xfs <linux-xfs@...r.kernel.org>,
Linux NVDIMM <nvdimm@...ts.linux.dev>,
linux-s390 <linux-s390@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
linux-erofs@...ts.ozlabs.org,
linux-ext4 <linux-ext4@...r.kernel.org>,
virtualization@...ts.linux-foundation.org
Subject: Re: [PATCH 25/29] dax: return the partition offset from
fs_dax_get_by_bdev
On Tue, Nov 23, 2021 at 06:56:29PM -0800, Dan Williams wrote:
> On Tue, Nov 9, 2021 at 12:34 AM Christoph Hellwig <hch@....de> wrote:
> >
> > Prepare from removing the block_device from the DAX I/O path by returning
>
> s/from removing/for the removal of/
Fixed.
> > td->dm_dev.bdev = bdev;
> > - td->dm_dev.dax_dev = fs_dax_get_by_bdev(bdev);
> > + td->dm_dev.dax_dev = fs_dax_get_by_bdev(bdev, &part_off);
>
> Perhaps allow NULL as an argument for callers that do not care about
> the start offset?
All callers currently care, dm just has another way to get at the
information. So for now I'd like to not add the NULL special case,
but we can reconsider that as needed if/when more callers show up.
Powered by blists - more mailing lists