On Tue, Aug 12, 2014 at 09:33:26AM +0000, Emmanuel Dreyfus wrote: > A possible solution would be to turn into an (int *) the a_mode in VOP_OPEN(), > and fmode invn_open(), so that ths method implementing OPEN in FS > (here puffs_vnop_open) can change the flags and have the new value > propagated to file_t's f_flags. But that is a heavy change and it modify > the VFS interface.
Or I can add ant int *new_a_mode / int *new_fmode as an additionnal argument to those fonctions. If passed NULL, behavior is unaltered. If passed != NULL, the upper layer gets the new fmode value from filesystem. Thoughts? -- Emmanuel Dreyfus [email protected]
