Skip to content

Commit

Permalink
Add fix for chromium saving files to FUSE filesys
Browse files Browse the repository at this point in the history
Chromium 130 won't save to our filesystem if we don't return a
max filename length.

Dummy parameters were tried for inode counts, but these do not seem to
be necessary. Not also that btrfs foes not return values for these
fields.
  • Loading branch information
matt335672 committed Nov 11, 2024
1 parent 5dc4fdb commit e3b62fd
Showing 1 changed file with 9 additions and 0 deletions.
9 changes: 9 additions & 0 deletions sesman/chansrv/devredir.c
Original file line number Diff line number Diff line change
Expand Up @@ -2441,6 +2441,15 @@ devredir_proc_cid_statfs_resp(IRP *irp,
fss.f_blocks = TotalAllocationUnits;
fss.f_bfree = ActualAvailableAllocationUnits;
fss.f_bavail = CallerAvailableAllocationUnits;
// Following values do not seem to be needed by
// any applications. btrfs also returns 0 for these
//fss.f_files = ???;
//fss.f_ffree = ???;
//fss.f_favail = fss.f_ffree;
// Chromium 130 needs this set, or the user can't save
// to our filesystem
fss.f_namemax = XFS_MAXFILENAMELEN;

}
}
}
Expand Down

0 comments on commit e3b62fd

Please sign in to comment.