Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1220954 > unrolled thread

Re: [PATCH 1/2] dax: fix O_DIRECT I/O to the last block of a blockdev

Started byLinda Knippers <linda.knippers@hpe.com>
First post2015-09-08 18:20 +0200
Last post2015-09-08 18:30 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [PATCH 1/2] dax: fix O_DIRECT I/O to the last block of a blockdev Linda Knippers <linda.knippers@hpe.com> - 2015-09-08 18:20 +0200
    Re: [PATCH 1/2] dax: fix O_DIRECT I/O to the last block of a blockdev Dan Williams <dan.j.williams@intel.com> - 2015-09-08 18:30 +0200

#1220954 — Re: [PATCH 1/2] dax: fix O_DIRECT I/O to the last block of a blockdev

FromLinda Knippers <linda.knippers@hpe.com>
Date2015-09-08 18:20 +0200
SubjectRe: [PATCH 1/2] dax: fix O_DIRECT I/O to the last block of a blockdev
Message-ID<q6tMJ-Vo-13@gated-at.bofh.it>
This patch and the 2/2 patch don't seem to have gone anywhere.
Willy?  or Ross?

-- ljk

On 8/14/2015 4:53 PM, Linda Knippers wrote:
> On 8/14/2015 4:15 PM, Jeff Moyer wrote:
>> commit bbab37ddc20b (block: Add support for DAX reads/writes to
>> block devices) caused a regression in mkfs.xfs.  That utility
>> sets the block size of the device to the logical block size
>> using the BLKBSZSET ioctl, and then issues a single sector read
>> from the last sector of the device.  This results in the dax_io
>> code trying to do a page-sized read from 512 bytes from the end
>> of the device.  The result is -ERANGE being returned to userspace.
>>
>> The fix is to align the block to the page size before calling
>> get_block.
>>
>> Thanks to willy for simplifying my original patch.
>>
>> Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
> 
> Tested-by:  Linda Knippers <linda.knippers@hp.com>
> 
>> ---
>>  fs/dax.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/dax.c b/fs/dax.c
>> index a7f77e1..ef35a20 100644
>> --- a/fs/dax.c
>> +++ b/fs/dax.c
>> @@ -116,7 +116,8 @@ static ssize_t dax_io(struct inode *inode, struct iov_iter *iter,
>>  		unsigned len;
>>  		if (pos == max) {
>>  			unsigned blkbits = inode->i_blkbits;
>> -			sector_t block = pos >> blkbits;
>> +			long page = pos >> PAGE_SHIFT;
>> +			sector_t block = page << (PAGE_SHIFT - blkbits);
>>  			unsigned first = pos - (block << blkbits);
>>  			long size;
>>  
>>
> 

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

[toc] | [next] | [standalone]


#1220962

FromDan Williams <dan.j.williams@intel.com>
Date2015-09-08 18:30 +0200
Message-ID<q6tWr-16N-29@gated-at.bofh.it>
In reply to#1220954
On Tue, Sep 8, 2015 at 9:10 AM, Linda Knippers <linda.knippers@hpe.com> wrote:
> This patch and the 2/2 patch don't seem to have gone anywhere.
> Willy?  or Ross?
>

Yes, these should have gone into 4.2, The nvdimm.git tree will pick
them up after 4.3-rc1 and tag them for -stable.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web