From: David Howells <dhowells@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: dhowells@redhat.com, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: Is there a reason why REQ_OP_READ has to be 0?
Date: Mon, 16 Jan 2023 16:17:34 +0000 [thread overview]
Message-ID: <2127557.1673885854@warthog.procyon.org.uk> (raw)
In-Reply-To: <Y8V1n4e/eeOd4n8/@infradead.org>
Aha!
The problem is that whilst aio, io_uring and cachefiles set IOCB_WRITE when
giving a write op to the VFS, the write() syscall does not...
David
prev parent reply other threads:[~2023-01-16 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 16:01 Is there a reason why REQ_OP_READ has to be 0? David Howells
2023-01-16 16:04 ` Christoph Hellwig
2023-01-16 16:06 ` Jens Axboe
2023-01-16 16:17 ` David Howells [this message]
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=2127557.1673885854@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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