From: Christoph Hellwig <hch@infradead.org>
To: Joanne Chang <joannechien@google.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>,
linux-f2fs-devel@lists.sourceforge.net, Chao Yu <chao@kernel.org>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v1] generic/735: disable for f2fs
Date: Fri, 19 Dec 2025 03:10:18 -0800 [thread overview]
Message-ID: <aUUymqMO4RfK8thK@infradead.org> (raw)
In-Reply-To: <CACQK4XCmq2_nSJA7jLz+TWiTgyZpVwnZZmG-NbNOkB2JjrCSeA@mail.gmail.com>
On Fri, Dec 19, 2025 at 04:53:04PM +0800, Joanne Chang wrote:
> Thanks for the reply. To clarify, I meant testing the architectural
> limit of blocks per file, not the current free blocks. Sorry for any
> confusion in my previous reply.
>
> The limit is indeed the maximum file size. However, since both the F2FS
> file size limit and the test's requirements are calculated as
> (block_number * block_size), I believe it is simpler to just test the
> block number.
Well, for the file size you can test by doing a truncate to the expected
size and _notrun if not supported. I can't really think of a way that
easy to directly check for the number of supported blocks.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Joanne Chang <joannechien@google.com>
Cc: Zorro Lang <zlang@kernel.org>,
fstests@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, Jaegeuk Kim <jaegeuk@kernel.org>
Subject: Re: [f2fs-dev] [PATCH v1] generic/735: disable for f2fs
Date: Fri, 19 Dec 2025 03:10:18 -0800 [thread overview]
Message-ID: <aUUymqMO4RfK8thK@infradead.org> (raw)
In-Reply-To: <CACQK4XCmq2_nSJA7jLz+TWiTgyZpVwnZZmG-NbNOkB2JjrCSeA@mail.gmail.com>
On Fri, Dec 19, 2025 at 04:53:04PM +0800, Joanne Chang wrote:
> Thanks for the reply. To clarify, I meant testing the architectural
> limit of blocks per file, not the current free blocks. Sorry for any
> confusion in my previous reply.
>
> The limit is indeed the maximum file size. However, since both the F2FS
> file size limit and the test's requirements are calculated as
> (block_number * block_size), I believe it is simpler to just test the
> block number.
Well, for the file size you can test by doing a truncate to the expected
size and _notrun if not supported. I can't really think of a way that
easy to directly check for the number of supported blocks.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-12-19 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-18 7:17 [PATCH v1] generic/735: disable for f2fs Joanne Chang
2025-12-18 7:17 ` [f2fs-dev] " Joanne Chang via Linux-f2fs-devel
2025-12-18 7:33 ` Christoph Hellwig
2025-12-18 7:33 ` [f2fs-dev] " Christoph Hellwig
2025-12-18 12:02 ` Joanne Chang
2025-12-18 12:02 ` [f2fs-dev] " Joanne Chang via Linux-f2fs-devel
2025-12-19 5:30 ` Christoph Hellwig
2025-12-19 5:30 ` [f2fs-dev] " Christoph Hellwig
2025-12-19 8:53 ` Joanne Chang
2025-12-19 8:53 ` [f2fs-dev] " Joanne Chang via Linux-f2fs-devel
2025-12-19 11:10 ` Christoph Hellwig [this message]
2025-12-19 11:10 ` Christoph Hellwig
2025-12-22 2:48 ` Joanne Chang
2025-12-22 2:48 ` [f2fs-dev] " Joanne Chang via Linux-f2fs-devel
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=aUUymqMO4RfK8thK@infradead.org \
--to=hch@infradead.org \
--cc=chao@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=jaegeuk@kernel.org \
--cc=joannechien@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zlang@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.