mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: "Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	axboe@kernel.dk, brauner@kernel.org, djwong@kernel.org,
	viro@zeniv.linux.org.uk, jack@suse.cz, dchinner@redhat.com,
	hch@lst.de, cem@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	hare@suse.de, martin.petersen@oracle.com,
	catherine.hoang@oracle.com, mcgrof@kernel.org,
	ojaswin@linux.ibm.com
Subject: Re: [PATCH v10 7/8] xfs: Validate atomic writes
Date: Sun, 20 Oct 2024 12:09:31 +0100	[thread overview]
Message-ID: <c4edb568-6fac-4c30-9ca3-12fbefc761e2@oracle.com> (raw)
In-Reply-To: <87plnvglck.fsf@gmail.com>

On 20/10/2024 10:44, Ritesh Harjani (IBM) wrote:
>> +	if (iocb->ki_flags & IOCB_ATOMIC) {
>> +		/*
>> +		 * Currently only atomic writing of a single FS block is
>> +		 * supported. It would be possible to atomic write smaller than
>> +		 * a FS block, but there is no requirement to support this.
>> +		 * Note that iomap also does not support this yet.
>> +		 */
>> +		if (ocount != ip->i_mount->m_sb.sb_blocksize)
>> +			return -EINVAL;
> Shouldn't we "return -ENOTSUPP" ?
> Given we are later going to add support for ocount > sb_blocksize.

So far we have been reporting -EINVAL for an invalid atomic write size 
(according to atomic write unit min and max reported for that inode).

-ENOTSUPP is used for times when we just don't support atomic writes, 
like non-DIO.

Thanks,
John

  reply	other threads:[~2024-10-20 11:09 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-19 12:51 [PATCH v10 0/8] block atomic writes for xfs John Garry
2024-10-19 12:51 ` [PATCH v10 1/8] block/fs: Pass an iocb to generic_atomic_write_valid() John Garry
2024-10-19 12:51 ` [PATCH v10 2/8] fs/block: Check for IOCB_DIRECT in generic_atomic_write_valid() John Garry
2024-10-19 12:51 ` [PATCH v10 3/8] block: Add bdev atomic write limits helpers John Garry
2024-10-19 12:51 ` [PATCH v10 4/8] fs: Export generic_atomic_write_valid() John Garry
2024-10-19 12:51 ` [PATCH v10 5/8] fs: iomap: Atomic write support John Garry
2024-10-20  8:21   ` Ritesh Harjani
2024-10-20 11:21     ` John Garry
2024-10-20 11:37       ` Ritesh Harjani
2024-10-19 12:51 ` [PATCH v10 6/8] xfs: Support atomic write for statx John Garry
2024-10-19 12:51 ` [PATCH v10 7/8] xfs: Validate atomic writes John Garry
2024-10-20  9:44   ` Ritesh Harjani
2024-10-20 11:09     ` John Garry [this message]
2024-10-20 11:41       ` Ritesh Harjani
2024-10-19 12:51 ` [PATCH v10 8/8] xfs: Support setting FMODE_CAN_ATOMIC_WRITE John Garry
2024-10-19 22:49 ` (subset) [PATCH v10 0/8] block atomic writes for xfs Jens Axboe
2024-10-19 22:50   ` Jens Axboe
2024-10-23 12:42     ` John Garry
2024-10-23 12:50       ` Carlos Maiolino
2024-10-24  6:32 ` Ojaswin Mujoo

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=c4edb568-6fac-4c30-9ca3-12fbefc761e2@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=brauner@kernel.org \
    --cc=catherine.hoang@oracle.com \
    --cc=cem@kernel.org \
    --cc=dchinner@redhat.com \
    --cc=djwong@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=mcgrof@kernel.org \
    --cc=ojaswin@linux.ibm.com \
    --cc=ritesh.list@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    /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®