From: Greg KH <gregkh@linuxfoundation.org>
To: Jane Chu <jane.chu@oracle.com>
Cc: tj@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/kernfs: raise sb->maxbytes to MAX_LFS_FILESIZE
Date: Mon, 24 Nov 2025 17:17:02 +0100 [thread overview]
Message-ID: <2025112410-carnivore-anemia-e6eb@gregkh> (raw)
In-Reply-To: <20251111202606.1505437-1-jane.chu@oracle.com>
On Tue, Nov 11, 2025 at 01:26:06PM -0700, Jane Chu wrote:
> On an ARM64 A1 system, it's possible to have physical memory span
> up to the 64T boundary, like below
>
> $ lsmem -b -r -n -o range,size
> 0x0000000080000000-0x00000000bfffffff 1073741824
> 0x0000080000000000-0x000008007fffffff 2147483648
> 0x00000800c0000000-0x0000087fffffffff 546534588416
> 0x0000400000000000-0x00004000bfffffff 3221225472
> 0x0000400100000000-0x0000407fffffffff 545460846592
>
> So it's time to extend /sys/kernel/mm/page_idle/bitmap to be able
> to account for >2G number of pages, by raising the kernfs file size
> limit.
Wait, we are having sysfs files that are bigger than >2G? Which files
exactly?
> Signed-off-by: Jane Chu <jane.chu@oracle.com>
> ---
> fs/kernfs/mount.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/fs/kernfs/mount.c b/fs/kernfs/mount.c
> index 76eaf64b9d9e..3ac52e141766 100644
> --- a/fs/kernfs/mount.c
> +++ b/fs/kernfs/mount.c
> @@ -298,6 +298,7 @@ static int kernfs_fill_super(struct super_block *sb, struct kernfs_fs_context *k
> if (info->root->flags & KERNFS_ROOT_SUPPORT_EXPORTOP)
> sb->s_export_op = &kernfs_export_ops;
> sb->s_time_gran = 1;
> + sb->s_maxbytes = MAX_LFS_FILESIZE;
What is the default setting for s_maxbytes today?
thanks,
greg k-h
next prev parent reply other threads:[~2025-11-24 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 20:26 [PATCH] fs/kernfs: raise sb->maxbytes to MAX_LFS_FILESIZE Jane Chu
2025-11-24 16:17 ` Greg KH [this message]
2025-11-24 17:06 ` jane.chu
2025-11-24 17:27 ` Greg KH
2025-11-24 17:54 ` jane.chu
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=2025112410-carnivore-anemia-e6eb@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jane.chu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox