16c00db4bb
Pull AFS fixes from David Howells:
"Here's a set of patches that fix a number of bugs in the in-kernel AFS
client, including:
- Fix directory locking to not use individual page locks for
directory reading/scanning but rather to use a semaphore on the
afs_vnode struct as the directory contents must be read in a single
blob and data from different reads must not be mixed as the entire
contents may be shuffled about between reads.
- Fix address list parsing to handle port specifiers correctly.
- Only give up callback records on a server if we actually talked to
that server (we might not be able to access a server).
- Fix some callback handling bugs, including refcounting,
whole-volume callbacks and when callbacks actually get broken in
response to a CB.CallBack op.
- Fix some server/address rotation bugs, including giving up if we
can't probe a server; giving up if a server says it doesn't have a
volume, but there are more servers to try.
- Fix the decoding of fetched statuses to be OpenAFS compatible.
- Fix the handling of server lookups in Cache Manager ops (such as
CB.InitCallBackState3) to use a UUID if possible and to handle no
server being found.
- Fix a bug in server lookup where not all addresses are compared.
- Fix the non-encryption of calls that prevents some servers from
being accessed (this also requires an AF_RXRPC patch that has
already gone in through the net tree).
There's also a patch that adds tracepoints to log Cache Manager ops
that don't find a matching server, either by UUID or by address"
* tag 'afs-fixes-20180514' of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs:
afs: Fix the non-encryption of calls
afs: Fix CB.CallBack handling
afs: Fix whole-volume callback handling
afs: Fix afs_find_server search loop
afs: Fix the handling of an unfound server in CM operations
afs: Add a tracepoint to record callbacks from unlisted servers
afs: Fix the handling of CB.InitCallBackState3 to find the server by UUID
afs: Fix VNOVOL handling in address rotation
afs: Fix AFSFetchStatus decoder to provide OpenAFS compatibility
afs: Fix server rotation's handling of fileserver probe failure
afs: Fix refcounting in callback registration
afs: Fix giving up callbacks on server destruction
afs: Fix address list parsing
afs: Fix directory page locking
69 lines
1.7 KiB
Text
69 lines
1.7 KiB
Text
perf-inject(1)
|
|
==============
|
|
|
|
NAME
|
|
----
|
|
perf-inject - Filter to augment the events stream with additional information
|
|
|
|
SYNOPSIS
|
|
--------
|
|
[verse]
|
|
'perf inject <options>'
|
|
|
|
DESCRIPTION
|
|
-----------
|
|
perf-inject reads a perf-record event stream and repipes it to stdout. At any
|
|
point the processing code can inject other events into the event stream - in
|
|
this case build-ids (-b option) are read and injected as needed into the event
|
|
stream.
|
|
|
|
Build-ids are just the first user of perf-inject - potentially anything that
|
|
needs userspace processing to augment the events stream with additional
|
|
information could make use of this facility.
|
|
|
|
OPTIONS
|
|
-------
|
|
-b::
|
|
--build-ids=::
|
|
Inject build-ids into the output stream
|
|
-v::
|
|
--verbose::
|
|
Be more verbose.
|
|
-i::
|
|
--input=::
|
|
Input file name. (default: stdin)
|
|
-o::
|
|
--output=::
|
|
Output file name. (default: stdout)
|
|
-s::
|
|
--sched-stat::
|
|
Merge sched_stat and sched_switch for getting events where and how long
|
|
tasks slept. sched_switch contains a callchain where a task slept and
|
|
sched_stat contains a timeslice how long a task slept.
|
|
|
|
--kallsyms=<file>::
|
|
kallsyms pathname
|
|
|
|
--itrace::
|
|
Decode Instruction Tracing data, replacing it with synthesized events.
|
|
Options are:
|
|
|
|
include::itrace.txt[]
|
|
|
|
--strip::
|
|
Use with --itrace to strip out non-synthesized events.
|
|
|
|
-j::
|
|
--jit::
|
|
Process jitdump files by injecting the mmap records corresponding to jitted
|
|
functions. This option also generates the ELF images for each jitted function
|
|
found in the jitdumps files captured in the input perf.data file. Use this option
|
|
if you are monitoring environment using JIT runtimes, such as Java, DART or V8.
|
|
|
|
-f::
|
|
--force::
|
|
Don't complain, do it.
|
|
|
|
SEE ALSO
|
|
--------
|
|
linkperf:perf-record[1], linkperf:perf-report[1], linkperf:perf-archive[1]
|