Re: Is there a reason why REQ_OP_READ has to be 0?

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

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: Is there a reason why REQ_OP_READ has to be 0?
From: David Howells <dhowells@xxxxxxxxxx>
Date: Mon, 16 Jan 2023 16:17:34 +0000
Cc: dhowells@xxxxxxxxxx, Jens Axboe <axboe@xxxxxxxxx>, linux-block@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <Y8V1n4e/eeOd4n8/@infradead.org>
Organization: Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903
References: <Y8V1n4e/eeOd4n8/@infradead.org> <2117829.1673884910@warthog.procyon.org.uk>

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

References:
- Re: Is there a reason why REQ_OP_READ has to be 0?
  - From: Christoph Hellwig
- Is there a reason why REQ_OP_READ has to be 0?
  - From: David Howells

Prev by Date: Re: [PATCH] block: check disk flag before setting scan bit
Next by Date: RE: [PATCH] block: don't allow multiple bios for IOCB_NOWAIT issue
Previous by thread: Re: Is there a reason why REQ_OP_READ has to be 0?
Next by thread: Re: [PATCH] block: check disk flag before setting scan bit
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]

Powered by Linux