From: Yu Kuai <yukuai1@huaweicloud.com>
To: Christoph Hellwig <hch@infradead.org>, Ming Lei <ming.lei@redhat.com>
Cc: Yu Kuai <yukuai1@huaweicloud.com>,
axboe@kernel.dk, rajeevm@hpe.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org, yi.zhang@huawei.com,
yangerkun@huawei.com, johnny.chenyi@huawei.com,
linux-fsdevel@vger.kernel.org, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] loop: fix zero sized loop for block special file
Date: Mon, 25 Aug 2025 17:36:02 +0800 [thread overview]
Message-ID: <eb572576-89f4-c192-09ab-b4585d09b75a@huaweicloud.com> (raw)
In-Reply-To: <aKwqUVmX-yH6_lZy@infradead.org>
Hi,
在 2025/08/25 17:18, Christoph Hellwig 写道:
> On Mon, Aug 25, 2025 at 04:56:55PM +0800, Ming Lei wrote:
>> `stat $BDEV_PATH` never works for getting bdev size, so it looks wrong
>> to call vfs_getattr_nosec() with bdev path for retrieving bdev's size.
>
> Exactly.
>
Ok.
>> So just wondering why not take the following more readable way?
>>
>> /* vfs_getattr() never works for retrieving bdev size */
>> if (S_ISBLK(stat.mode)) {
>> loopsize = i_size_read(file->f_mapping->host);
>> } else {
>> ret = vfs_getattr_nosec(&file->f_path, &stat, STATX_SIZE, 0);
>> if (ret)
>> return 0;
>> loopsize = stat.size;
>> }
Just we can't use stat.mode here, I'll replace it with:
S_ISBLK(file_inode(file)->i_mode)
Thanks,
Kuai
>>
>> Also the above looks like how application reads file size in case of bdev
>> involved.
>
> That's not just more readable, but simply the way to go. Maybe split
> it into a helper for readability, though.
> .
>
prev parent reply other threads:[~2025-08-25 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250825062300.2485281-1-yukuai1@huaweicloud.com>
2025-08-25 8:56 ` [PATCH] loop: fix zero sized loop for block special file Ming Lei
2025-08-25 9:18 ` Christoph Hellwig
2025-08-25 9:36 ` Yu Kuai [this message]
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=eb572576-89f4-c192-09ab-b4585d09b75a@huaweicloud.com \
--to=yukuai1@huaweicloud.com \
--cc=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=rajeevm@hpe.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.com \
/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;
as well as URLs for NNTP newsgroup(s).