linux-kernel - [RFC PATCH 0/1] FUSE: allow drivers to increase readahead.

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-next>] [day] [month] [year] [list]

Date:   Wed,  2 Mar 2022 10:18:15 -0700
From:   Kevin Vigor <kvigor@...il.com>
To:     miklos@...redi.hu
Cc:     linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        Kevin Vigor <kvigor@...il.com>
Subject: [RFC PATCH 0/1] FUSE: allow drivers to increase readahead.

Summary:

Allow FUSE drivers to increase readahead setting.

Details:

FUSE drivers can set a max_readahead value in the fuse_init_out value.

However, this value can currently only decrease the readahead setting
from the default, which is set to VM_READAHEAD_PAGES in bdi_alloc().

Add a flag which causes the kernel driver to accept whatever
max_readahead value the user provides in fuse_init_out. Note that
read_ahead_kb_store() similarly allows users to set arbitrary ra_pages
values.

Kevin Vigor (1):
  FUSE: Add FUSE_TRUST_MAX_RA flag enabling readahead settings >128KB.

 fs/fuse/inode.c           | 8 ++++++--
 include/uapi/linux/fuse.h | 3 +++
 2 files changed, 9 insertions(+), 2 deletions(-)

-- 
2.33.1