linux-4.14.55: Allow to trace nfsd v4 operations #921
Merged
+979
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
From time to time our nfs file servers are overloaded and it is quite
challenging for the admins to track down the source of the problem.
Add a patch to the kernels nfsd module which enables it to log all nfs4
operations via the kernel event trace utility.
This will give us the oportunity to write simple users-space tools
to track down nfs load.
Also rebuild nvidia_linux-4.14.55 for the new kernel.
Patch Description:
Add trace events to all v4 operations. Record client ip for ipv4
clients. Record uid from request credentials.
For READ and WRITE ops, additionally record offset and length request
arguments and device, inode and filename of the affected file.
Prove of concept:
tested on dose, sigchld, claptrap