Re: [PATCH 1/2] fuse: disable atomic_o_trunc if no_open is enabled

2021-09-08 Thread JeffleXu
On 9/7/21 4:34 PM, Miklos Szeredi wrote: > On Thu, 12 Aug 2021 at 07:46, Jeffle Xu wrote: >> >> From: Liu Bo >> >> When 'no_open' is used by virtiofsd, guest kernel won't send OPEN request >> any more. However, with atomic_o_trunc, SETATTR request is also omitted in >> OPEN(O_TRUNC) so that t

[PATCH 1/2] fuse: disable atomic_o_trunc if no_open is enabled

2021-08-11 Thread Jeffle Xu
From: Liu Bo When 'no_open' is used by virtiofsd, guest kernel won't send OPEN request any more. However, with atomic_o_trunc, SETATTR request is also omitted in OPEN(O_TRUNC) so that the backend file is not truncated. With a following GETATTR, inode size on guest side is updated to be same wit