Query regards to expose client-pid to fuse process

[Mohit Agrawal <moagrawa@xxxxxxxxxx>]

Hi,

  I have a query specific to authenticate a client based on the PID (client-pid).
  It can break the bricks xlator functionality, Usually, on the brick side we take a decision about the 

   source of fop request based on PID.If PID value is -ve xlator considers the request has come from an internal 

  client otherwise it has come from an external client.

  If a user has mounted the volume through fuse after provide --client-pid to command line argument similar to internal client PID 

  in that case brick_xlator consider external fop request also as an internal and it will break functionality.

  We are checking pid in (lease, posix-lock, worm, trash) xlator to know about the source of the fops.
  Even there are other brick xlators also we are checking specific PID value for all internal
  clients that can be break if the external client has the same pid.
   

  My query is why we need to expose client-pid as an argument to the fuse process?
   I think we need to resolve it. Please share your view on the same.

  

Thanks,
Mohit Agrawal

_______________________________________________

Community Meeting Calendar:

APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/118564314

NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/118564314

Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel