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
49 lines
1.3 KiB
Text
49 lines
1.3 KiB
Text
|
|
1) perf build
|
|
=============
|
|
The perf build process consists of several separated building blocks,
|
|
which are linked together to form the perf binary:
|
|
- libperf library (static)
|
|
- perf builtin commands
|
|
- traceevent library (static)
|
|
- GTK ui library
|
|
|
|
Several makefiles govern the perf build:
|
|
|
|
- Makefile
|
|
top level Makefile working as a wrapper that calls the main
|
|
Makefile.perf with a -j option to do parallel builds.
|
|
|
|
- Makefile.perf
|
|
main makefile that triggers build of all perf objects including
|
|
installation and documentation processing.
|
|
|
|
- tools/build/Makefile.build
|
|
main makefile of the build framework
|
|
|
|
- tools/build/Build.include
|
|
build framework generic definitions
|
|
|
|
- Build makefiles
|
|
makefiles that defines build objects
|
|
|
|
Please refer to tools/build/Documentation/Build.txt for more
|
|
information about build framework.
|
|
|
|
|
|
2) perf build
|
|
=============
|
|
The Makefile.perf triggers the build framework for build objects:
|
|
perf, libperf, gtk
|
|
|
|
resulting in following objects:
|
|
$ ls *-in.o
|
|
gtk-in.o libperf-in.o perf-in.o
|
|
|
|
Those objects are then used in final linking:
|
|
libperf-gtk.so <- gtk-in.o libperf-in.o
|
|
perf <- perf-in.o libperf-in.o
|
|
|
|
|
|
NOTE this description is omitting other libraries involved, only
|
|
focusing on build framework outcomes
|