pass open file to ->setattr()
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 7 lines · Miklos Szeredi
Quoted 5 lines
Quoted 3 lines
This is needed to be able to correctly implement open-unlink-fsetattr semantics in some filesystem such as sshfs, without having to resort to "silly-renaming".
How do you plan to do that?
Easy: the SFTP protocol has stateful opens and defines an FSTAT call.
Is it possible to reconnect without umounting? If yes, the unlinked files would be lost in spite of being opened, wouldn't they?
Signature · 8 lines
Top 100 things you don't want the sysadmin to say: 11. Can you get VMS for this Sparc thingy? Friß, Spammer: [email protected] [email protected] - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 9 lines
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
This is needed to be able to correctly implement open-unlink-fsetattr semantics in some filesystem such as sshfs, without having to resort to "silly-renaming".
How do you plan to do that?
Easy: the SFTP protocol has stateful opens and defines an FSTAT call.
Is it possible to reconnect without umounting?
Yes, but open files and in-progress requests are lost at reconnect.
Quoted 2 lines
If yes, the unlinked files would be lost in spite of being opened, wouldn't they?
Sure. Obviously one of the drawbacks of a stateful protocol is that the server state can't survive a reconnect.
But that sort of reliability has never been the goal of sshfs. And even if that was needed, it could probably be much better handled in a lower layer.
Miklos