Re: [PATCH 4/6] block: stop setting ->direct_IO

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Christoph Hellwig <hch@xxxxxx>
Subject: Re: [PATCH 4/6] block: stop setting ->direct_IO
From: Al Viro <viro@xxxxxxxxxxxxxxxxxx>
Date: Tue, 29 Aug 2023 03:13:37 +0100
Cc: Jens Axboe <axboe@xxxxxxxxx>, "Darrick J. Wong" <djwong@xxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Matthew Wilcox <willy@xxxxxxxxxxxxx>, Christian Brauner <christian@xxxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxxxxxx, linux-mm@xxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Luis Chamberlain <mcgrof@xxxxxxxxxx>, Hannes Reinecke <hare@xxxxxxx>, Johannes Thumshirn <johannes.thumshirn@xxxxxxx>
In-reply-to: <20230801172201.1923299-5-hch@lst.de>

On Tue, Aug 01, 2023 at 07:21:59PM +0200, Christoph Hellwig wrote:
> Direct I/O on block devices now nevers goes through aops->direct_IO.
> Stop setting it and set the FMODE_CAN_ODIRECT in ->open instead.

s/nevers/never/

References:
- allow building a kernel without buffer_heads v3
  - From: Christoph Hellwig
- [PATCH 4/6] block: stop setting ->direct_IO
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH 3/6] block: open code __generic_file_write_iter for blkdev writes
Next by Date: Re: [RFC PATCH v11 12/29] KVM: Add KVM_CREATE_GUEST_MEMFD ioctl() for guest-specific backing memory
Previous by thread: [PATCH 4/6] block: stop setting ->direct_IO
Next by thread: [PATCH 5/6] block: use iomap for writes to block devices
Index(es):
- Date
- Thread

[Index of Archives] [Linux Ext4 Filesystem] [Union Filesystem] [Filesystem Testing] [Ceph Users] [Ecryptfs] [NTFS 3] [AutoFS] [Kernel Newbies] [Share Photos] [Security] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux Cachefs] [Reiser Filesystem] [Linux RAID] [NTFS 3] [Samba] [Device Mapper] [CEPH Development]

Powered by Linux