mbox series

[v3,0/2] fuse: Increase FUSE_NAME_MAX limit

Message ID 20241216-fuse_name_max-limit-6-13-v3-0-b4b04966ecea@ddn.com (mailing list archive)
Headers show
Series fuse: Increase FUSE_NAME_MAX limit | expand

Message

Bernd Schubert Dec. 16, 2024, 9:14 p.m. UTC 
First patch switches fuse_notify_inval_entry and fuse_notify_delete
to allocate name buffers to the actual file name size and not
FUSE_NAME_MAX anymore. 
Second patch increases the FUSE_NAME_MAX limit.

Signed-off-by: Bernd Schubert <bschubert@ddn.com>
---
Changes in v3:
- New variable fc->name_max that is initialized to FUSE_NAME_LOW_MAX
  (1024B). The FUSE_NAME_MAX (PATH_MAX - 1) is only used when
  fuse server set max_pages > 1 in FUSE_INIT reply.
- Link to v2: https://lore.kernel.org/r/20241213-fuse_name_max-limit-6-13-v2-0-39fec5253632@ddn.com

Changes in v2:
- Switch to PATH_MAX (Jingbo)
- Add -1 to handle the terminating null
- Link to v1: https://lore.kernel.org/r/20241212-fuse_name_max-limit-6-13-v1-0-92be52f01eca@ddn.com

---
Bernd Schubert (2):
      fuse: Allocate only namelen buf memory in fuse_notify_
      fuse: Increase FUSE_NAME_MAX to PATH_MAX

 fs/fuse/dev.c    | 30 ++++++++++++++++--------------
 fs/fuse/dir.c    |  2 +-
 fs/fuse/fuse_i.h | 11 +++++++++--
 fs/fuse/inode.c  |  8 ++++++++
 4 files changed, 34 insertions(+), 17 deletions(-)
---
base-commit: f92f4749861b06fed908d336b4dee1326003291b
change-id: 20241212-fuse_name_max-limit-6-13-18582bd39dd4

Best regards,