From: Cloud User <rajeevm@hpe.com>
To: Cloud User <rajeevm@hpe.com>, Yu Kuai <yukuai1@huaweicloud.com>,
ming.lei@redhat.com, hch@infradead.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yi.zhang@huawei.com, yangerkun@huawei.com,
johnny.chenyi@huawei.com, yukuai <yukuai3@huawei.com>
Subject: Re: [PATCH v5] fixed the blok file statx issue
Date: Tue, 26 Aug 2025 02:58:13 +0000 [thread overview]
Message-ID: <20250826025815.3715160-1-rajeevm@hpe.com> (raw)
In-Reply-To: <a118e156-36a2-6612-517a-ba22c11fbd1d@huaweicloud.com>
Hi,
在 2025/08/26 6:17, Cloud User 写道:
> This fixes the statx issue which caused multiple test issue
>
> Rajeev Mishra (2):
> loop: Rename and merge get_size/get_loop_size to lo_calculate_size
> loop: use vfs_getattr_nosec for accurate file size
>
> drivers/block/loop.c | 43 +++++++++++++++++++++++++------------------
> 1 file changed, 25 insertions(+), 18 deletions(-)
>
There is no need, to late for this now. :(
>>> Thanks Kuai for your continued support. I just want to make sure the original
>>>> fix which calls vfs_getattr_nosec in lo_calculate_size is not getting
>>> discarded. Again thanks for your quick response
Thanks,
Kuai
prev parent reply other threads:[~2025-08-26 2:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-25 22:17 Cloud User
2025-08-25 22:17 ` [PATCH 1/2] loop: Rename and merge get_size/get_loop_size to lo_calculate_size Cloud User
2025-08-25 22:17 ` [PATCH 2/2] loop: use vfs_getattr_nosec for accurate file size Cloud User
2025-08-26 0:49 ` [PATCH v5] fixed the blok file statx issue Yu Kuai
2025-08-26 2:58 ` Cloud User [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=20250826025815.3715160-1-rajeevm@hpe.com \
--to=rajeevm@hpe.com \
--cc=hch@infradead.org \
--cc=johnny.chenyi@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yangerkun@huawei.com \
--cc=yi.zhang@huawei.com \
--cc=yukuai1@huaweicloud.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
all inboxes | Powered by JetHome®