linux-kernel - Re:[PATCH] fuse: Replace hardcoded 4096 with PAGE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20250819132215.861-1-luochunsheng@ustc.edu>
Date: Tue, 19 Aug 2025 21:22:15 +0800
From: Chunsheng Luo <luochunsheng@...c.edu>
To: luochunsheng@...c.edu
Cc: linux-fsdevel@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	miklos@...redi.hu
Subject: Re:[PATCH] fuse: Replace hardcoded 4096 with PAGE_SIZE

Hi everyone,

I have a question about the historical use of hardcoded 4096 values for 
max_read and max_write defaults in FUSE code, rather than using PAGE_SIZE.

fc->max_read = max_t(unsigned, arg->max_read, 4096);
fc->max_write = max_t(unsigned, arg->max_write, 4096); 

Is there any historical reason or compatibility concern for keeping the
hardcoded 4096? Would it make sense to use PAGE_SIZE?

Any insights would be appreciated.

Thanks
Chunsheng Luo