[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240111161522.GB16626@lst.de>
Date: Thu, 11 Jan 2024 17:15:22 +0100
From: Christoph Hellwig <hch@....de>
To: John Garry <john.g.garry@...cle.com>
Cc: Christoph Hellwig <hch@....de>, "Darrick J. Wong" <djwong@...nel.org>,
Dave Chinner <david@...morbit.com>, axboe@...nel.dk,
kbusch@...nel.org, sagi@...mberg.me, jejb@...ux.ibm.com,
martin.petersen@...cle.com, viro@...iv.linux.org.uk,
brauner@...nel.org, dchinner@...hat.com, jack@...e.cz,
linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org, linux-xfs@...r.kernel.org,
linux-fsdevel@...r.kernel.org, tytso@....edu, jbongio@...gle.com,
linux-scsi@...r.kernel.org, ming.lei@...hat.com, bvanassche@....org,
ojaswin@...ux.ibm.com
Subject: Re: [PATCH v2 00/16] block atomic writes
On Thu, Jan 11, 2024 at 04:11:38PM +0000, John Garry wrote:
> Could we just error the SETXATTR ioctl when FS_XFLAG_FORCEALIGN is not set
> (and it is required)? The problem is that ioctl reports -EINVAL for any
> such errors, so hard for the user to know the issue...
Sure. Pick a good unique error code, though.
Powered by blists - more mailing lists