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
44 lines
No EOL
2 KiB
JSON
44 lines
No EOL
2 KiB
JSON
[
|
|
{
|
|
"EventCode": "0x5C",
|
|
"UMask": "0x1",
|
|
"BriefDescription": "Unhalted core cycles when the thread is in ring 0",
|
|
"Counter": "0,1,2,3",
|
|
"EventName": "CPL_CYCLES.RING0",
|
|
"PublicDescription": "This event counts the unhalted core cycles during which the thread is in the ring 0 privileged mode.",
|
|
"SampleAfterValue": "2000003",
|
|
"CounterHTOff": "0,1,2,3,4,5,6,7"
|
|
},
|
|
{
|
|
"EdgeDetect": "1",
|
|
"EventCode": "0x5C",
|
|
"UMask": "0x1",
|
|
"BriefDescription": "Number of intervals between processor halts while thread is in ring 0",
|
|
"Counter": "0,1,2,3",
|
|
"EventName": "CPL_CYCLES.RING0_TRANS",
|
|
"CounterMask": "1",
|
|
"PublicDescription": "This event counts when there is a transition from ring 1,2 or 3 to ring0.",
|
|
"SampleAfterValue": "100007",
|
|
"CounterHTOff": "0,1,2,3,4,5,6,7"
|
|
},
|
|
{
|
|
"EventCode": "0x5C",
|
|
"UMask": "0x2",
|
|
"BriefDescription": "Unhalted core cycles when thread is in rings 1, 2, or 3",
|
|
"Counter": "0,1,2,3",
|
|
"EventName": "CPL_CYCLES.RING123",
|
|
"PublicDescription": "This event counts unhalted core cycles during which the thread is in rings 1, 2, or 3.",
|
|
"SampleAfterValue": "2000003",
|
|
"CounterHTOff": "0,1,2,3,4,5,6,7"
|
|
},
|
|
{
|
|
"EventCode": "0x63",
|
|
"UMask": "0x1",
|
|
"BriefDescription": "Cycles when L1 and L2 are locked due to UC or split lock",
|
|
"Counter": "0,1,2,3",
|
|
"EventName": "LOCK_CYCLES.SPLIT_LOCK_UC_LOCK_DURATION",
|
|
"PublicDescription": "This event counts cycles in which the L1 and L2 are locked due to a UC lock or split lock. A lock is asserted in case of locked memory access, due to noncacheable memory, locked operation that spans two cache lines, or a page walk from the noncacheable page table. L1D and L2 locks have a very high performance penalty and it is highly recommended to avoid such access.",
|
|
"SampleAfterValue": "2000003",
|
|
"CounterHTOff": "0,1,2,3,4,5,6,7"
|
|
}
|
|
] |