diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2017-05-27 09:02:41 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-05-27 09:02:41 -0700 |
commit | fac3fcae3244d6d8af61f04d2c10b4fd5ee03933 (patch) | |
tree | 6852f921b0ec8a75a93cf8c4b6911e70a7abb7ff /tools/include | |
parent | 805f286907ace68bef37db20bbdfa8f4a1908ed9 (diff) | |
parent | 6e30437bd42c4d4e9cfc4c40efda00eb83a11cde (diff) | |
download | op-kernel-dev-fac3fcae3244d6d8af61f04d2c10b4fd5ee03933.zip op-kernel-dev-fac3fcae3244d6d8af61f04d2c10b4fd5ee03933.tar.gz |
Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull perf tooling fixes from Thomas Gleixner:
- Synchronization of tools and kernel headers
- A series of fixes for perf report addressing various failures:
* Handle invalid maps proper
* Plug a memory leak
* Handle frames and callchain order correctly
- Fixes for handling inlines and children mode
* 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
tools/include: Sync kernel ABI headers with tooling headers
perf tools: Put caller above callee in --children mode
perf report: Do not drop last inlined frame
perf report: Always honor callchain order for inlined nodes
perf script: Add --inline option for debugging
perf report: Fix off-by-one for non-activation frames
perf report: Fix memory leak in addr2line when called by addr2inlines
perf report: Don't crash on invalid maps in `-g srcline` mode
Diffstat (limited to 'tools/include')
-rw-r--r-- | tools/include/uapi/linux/stat.h | 8 |
1 files changed, 2 insertions, 6 deletions
diff --git a/tools/include/uapi/linux/stat.h b/tools/include/uapi/linux/stat.h index d538897..17b1030 100644 --- a/tools/include/uapi/linux/stat.h +++ b/tools/include/uapi/linux/stat.h @@ -48,17 +48,13 @@ * tv_sec holds the number of seconds before (negative) or after (positive) * 00:00:00 1st January 1970 UTC. * - * tv_nsec holds a number of nanoseconds before (0..-999,999,999 if tv_sec is - * negative) or after (0..999,999,999 if tv_sec is positive) the tv_sec time. - * - * Note that if both tv_sec and tv_nsec are non-zero, then the two values must - * either be both positive or both negative. + * tv_nsec holds a number of nanoseconds (0..999,999,999) after the tv_sec time. * * __reserved is held in case we need a yet finer resolution. */ struct statx_timestamp { __s64 tv_sec; - __s32 tv_nsec; + __u32 tv_nsec; __s32 __reserved; }; |