On Sat, 20 Apr 2024 at 01:04, The 8472 <kernel@xxxxxxxxxxxxxxxxxx> wrote:
> If it is the official position that the whims of FUSE servers have
> primacy over current kernel API guarantees then please update
> the documentation of all affected syscalls and relax those
> guarantees, similar to the note on the write(2) manpage.
Which note are you referring to?
I can see some merit to both sides.
If it's an issue that can be fixed in the fuse server ("Doctor, it
hurts when I do this." "Then don't do that!”) adding complexity to the
fuse client is not warranted.
Obviously most fuse servers don't want to actively confuse caller, but
if such behavior can be used to exploit a weakness in an application,
then it becomes more than just a correctness issue. If you came up
with such a scenario, then this would turn into a serious bug.
Thanks,
Miklos
