mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "jiale yao" <19888972804@163.com>
To: liubaolin <liubaolin12138@163.com>
Cc: "Namjae Jeon" <linkinjeon@kernel.org>,
	"Sungjong Seo" <sj1557.seo@samsung.com>,
	"Yuezhang Mo" <yuezhang.mo@sony.com>, "Jan Kara" <jack@suse.com>,
	"Hyunchul Lee" <hyc.lee@gmail.com>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	"Darrick J. Wong" <djwong@kernel.org>,
	exfat@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-ext4@vger.kernel.org, ntfs@lists.linux.dev
Subject: Re:Re: [PATCH 2/3] ntfs: drain in-flight DIO before buffered write fallback
Date: Thu, 24 Sep 2026 20:20:47 +0800 (CST)	[thread overview]
Message-ID: <7e97a16e.9bac.1a0d35c76c2.Coremail.19888972804@163.com> (raw)
In-Reply-To: <b51a2ffa-5778-4075-a679-84cd3acf419a@163.com>

Hi Baolin,

You're right. NTFS advertises FMODE_NOWAIT, and clearing IOCB_DIRECT
does not make it valid to block in inode_dio_wait().

I will check IOCB_NOWAIT before entering the buffered fallback. If
iomap_dio_rw() has not written any data, the path will return -EAGAIN.
If it completed a partial write, it will return the positive short-write
result without entering the potentially blocking fallback.

I will address this in v2, after 24h.

Thanks,
Jiale

  reply	other threads:[~2026-09-24 12:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24 11:05 [PATCH 0/3] fs: " Jiale Yao
2026-09-24 11:05 ` [PATCH 1/3] ext2: " Jiale Yao
2026-09-24 11:05 ` [PATCH 2/3] ntfs: " Jiale Yao
2026-09-24 12:04   ` liubaolin
2026-09-24 12:20     ` jiale yao [this message]
2026-09-24 11:05 ` [PATCH 3/3] exfat: " Jiale Yao

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=7e97a16e.9bac.1a0d35c76c2.Coremail.19888972804@163.com \
    --to=19888972804@163.com \
    --cc=djwong@kernel.org \
    --cc=exfat@lists.linux.dev \
    --cc=hyc.lee@gmail.com \
    --cc=jack@suse.com \
    --cc=linkinjeon@kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liubaolin12138@163.com \
    --cc=ntfs@lists.linux.dev \
    --cc=ritesh.list@gmail.com \
    --cc=sj1557.seo@samsung.com \
    --cc=yuezhang.mo@sony.com \
    /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
all inboxes | Powered by JetHome®