Debugging enhancements for inode/entry lks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi,
From discussions with avati, we are thinking of addressing the following issues in locks xlator. At the moment to find which mount performed inode/entry lks, the process needs to be attached to gdb and the connection address needs to be de-referenced to figure out the actual owner. We need to move away from this model to a model which prints a free form string which contains information about the mount which performed the inode/entry lk in state-dumps. We also want to print a free-form string which captures brief info of the fop that issued the lock.

        Please feel free to add any suggestions you have.

Pranith.



[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux