[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10486098-fee5-4f66-afe0-f0120e134e97@oracle.com>
Date: Wed, 12 Mar 2025 08:21:41 +0000
From: John Garry <john.g.garry@...cle.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: brauner@...nel.org, djwong@...nel.org, cem@...nel.org,
linux-xfs@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org, ojaswin@...ux.ibm.com,
ritesh.list@...il.com, martin.petersen@...cle.com
Subject: Re: [PATCH v5 02/10] xfs: Switch atomic write size check in
xfs_file_write_iter()
On 12/03/2025 07:17, Christoph Hellwig wrote:
>> +void
>> +xfs_get_atomic_write_attr(
>> + struct xfs_inode *ip,
>> + unsigned int *unit_min,
>> + unsigned int *unit_max)
>> +{
>> + if (!xfs_inode_can_atomicwrite(ip)) {
>> + *unit_min = *unit_max = 0;
>> + return;
>> + }
>> +
>> + *unit_min = *unit_max = ip->i_mount->m_sb.sb_blocksize;
>
> This is a rather ugly interface. Why not have separate helpers for
> the min and max values that can just return the actual values?
>
ok, I can make that change.
Thanks,
John
Powered by blists - more mailing lists