Re: [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range

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

To: Ritesh Harjani <riteshh@xxxxxxxxxxxxx>
Subject: Re: [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 14 Jan 2020 08:37:02 -0800
Cc: linux-ext4@xxxxxxxxxxxxxxx, tytso@xxxxxxx, jack@xxxxxxx
In-reply-to: <27607a16327fe9664f32d09abe565af0d1ae56c9.1578907891.git.riteshh@linux.ibm.com>
References: <cover.1578907890.git.riteshh@linux.ibm.com> <27607a16327fe9664f32d09abe565af0d1ae56c9.1578907891.git.riteshh@linux.ibm.com>

Please add at very least the fsdevel and xfs lists to iomap patches.

Using i_dio_count for any kind of detection is bogus.  If you want to
pass flags to the writeback code please do so explicitly through
struct writeback_control.

Follow-Ups:
- Re: [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range
  - From: Jan Kara

References:
- [RFC 0/2] ext4: Fix stale data read exposure problem with DIO read/page_mkwrite
  - From: Ritesh Harjani
- [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range
  - From: Ritesh Harjani

Prev by Date: Making linkat() able to overwrite the target
Next by Date: Re: [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range
Previous by thread: Re: [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range
Next by thread: Re: [RFC 1/2] iomap: direct-io: Move inode_dio_begin before filemap_write_and_wait_range
Index(es):
- Date
- Thread

[Index of Archives] [Reiser Filesystem Development] [Ceph FS] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite National Park] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Device Mapper] [Linux Media]

Powered by Linux