[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bb7c50da-1ee2-4ba1-9f54-8e98dff14b6d@oracle.com>
Date: Wed, 13 Dec 2023 11:02:36 +0000
From: John Garry <john.g.garry@...cle.com>
To: Jan Kara <jack@...e.cz>
Cc: axboe@...nel.dk, kbusch@...nel.org, hch@....de, sagi@...mberg.me,
jejb@...ux.ibm.com, martin.petersen@...cle.com, djwong@...nel.org,
viro@...iv.linux.org.uk, brauner@...nel.org, dchinner@...hat.com,
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,
jaswin@...ux.ibm.com, bvanassche@....org,
Prasad Singamsetty <prasad.singamsetty@...cle.com>
Subject: Re: [PATCH v2 03/16] fs/bdev: Add atomic write support info to statx
On 13/12/2023 10:24, Jan Kara wrote:
>> Signed-off-by: Prasad Singamsetty<prasad.singamsetty@...cle.com>
>> Signed-off-by: John Garry<john.g.garry@...cle.com>
> Just some nits below.
>
>> +#define BDEV_STATX_SUPPORTED_MSK (STATX_DIOALIGN | STATX_WRITE_ATOMIC)
> ^^^
> I believe saving one letter here is not
> really beneficial so just spell out MASK here...
ok
>
>> /*
>> - * Handle STATX_DIOALIGN for block devices.
>> - *
>> - * Note that the inode passed to this is the inode of a block device node file,
>> - * not the block device's internal inode. Therefore it is*not* valid to use
>> - * I_BDEV() here; the block device has to be looked up by i_rdev instead.
>> + * Handle STATX_{DIOALIGN, WRITE_ATOMIC} for block devices.
>> */
> Please keep "Note ..." from the above comment (or you can move the note in
> front of blkdev_get_no_open() if you want).
ok, fine, I think that moving it to in front of blkdev_get_no_open() may
be best.
Thanks,
John
Powered by blists - more mailing lists