tracing: Fixes for 5.10-rc6
Subsystems (7)
Steven Rostedt
maintainercover tracing: Fixes for 5.10-rc6
Andrea Righi (1):
ring-buffer: Set the right timestamp in the slow path of __rb_reserve_next()
Masami Hiramatsu (4):
tools/bootconfig: Fix errno reference after printf() tools/bootconfig: Fix to check the write failure correctly tools/bootconfig: Align the bootconfig applied initrd image size to 4
docs: bootconfig: Update file format on initrd image
Minchan Kim (1):
tracing: Fix alignment of static buffer
Naveen N. Rao (2):
ftrace: Fix updating FTRACE_FL_TRAMP
ftrace: Fix DYNAMIC_FTRACE_WITH_DIRECT_CALLS dependency
Sami Tolvanen (1):
samples/ftrace: Mark my_tramp[12]? global
Steven Rostedt (VMware) (2):
ring-buffer: Update write stamp with the correct ts
ring-buffer: Always check to put back before stamp when crossing pages
Vasily Averin (1):
tracing: Remove WARN_ON in start_thread()
----
Documentation/admin-guide/bootconfig.rst | 18 +++-- include/linux/bootconfig.h | 3 + kernel/trace/Kconfig | 2 +- kernel/trace/ftrace.c | 22 +++++- kernel/trace/ring_buffer.c | 20 +++-- kernel/trace/trace.c | 2 +- kernel/trace/trace_hwlat.c | 2 +- samples/ftrace/ftrace-direct-modify.c | 2 + samples/ftrace/ftrace-direct-too.c | 1 + samples/ftrace/ftrace-direct.c | 1 + tools/bootconfig/main.c | 121 ++++++++++++++++++++----------- tools/bootconfig/test-bootconfig.sh | 6 +- 12 files changed, 138 insertions(+), 62 deletions(-)
Steven Rostedt
maintainerPATCH 1/12 tools/bootconfig: Fix errno reference after printf()
From: Masami Hiramatsu <[email protected]>
Fix not to refer the errno variable as the result of previous libc functions after printf() because printf() can change the errno.
--- tools/bootconfig/main.c | 52 +++++++++++++++++++++++------------------ 1 file changed, 29 insertions(+), 23 deletions(-)
tools/bootconfig/main.c +29 -23
@@ -147,6 +147,12 @@ static int load_xbc_file(const char *path, char **buf)return ret; } +static int pr_errno (const char *msg,int err) +{ +pr_err ("%s: %d\n" , msg, err); +return err; +} +static int load_xbc_from_initrd (int fd,char **buf) {struct stat stat;
@@ -162,26 +168,24 @@ static int load_xbc_from_initrd(int fd, char **buf)if (stat.st_size <8 +BOOTCONFIG_MAGIC_LEN )return 0 ; -if (lseek (fd, -BOOTCONFIG_MAGIC_LEN ,SEEK_END ) <0 ) { -pr_err ("Failed to lseek: %d\n" , -errno); -return -errno; - } +if (lseek (fd, -BOOTCONFIG_MAGIC_LEN ,SEEK_END ) <0 ) +return pr_errno ("Failed to lseek for magic" , -errno); +if (read (fd, magic,BOOTCONFIG_MAGIC_LEN ) <0 ) -return -errno; +return pr_errno ("Failed to read" , -errno); +/* Check the bootconfig magic bytes */ if (memcmp (magic,BOOTCONFIG_MAGIC ,BOOTCONFIG_MAGIC_LEN ) !=0 )return 0 ; -if (lseek (fd, -(8 +BOOTCONFIG_MAGIC_LEN ),SEEK_END ) <0 ) { -pr_err ("Failed to lseek: %d\n" , -errno); -return -errno; - } +if (lseek (fd, -(8 +BOOTCONFIG_MAGIC_LEN ),SEEK_END ) <0 ) +return pr_errno ("Failed to lseek for size" , -errno);if (read (fd, &size,sizeof (u32)) <0 ) -return -errno; +return pr_errno ("Failed to read size" , -errno);if (read (fd, &csum,sizeof (u32)) <0 ) -return -errno; +return pr_errno ("Failed to read checksum" , -errno);/* Wrong size error */ if (stat.st_size < size +8 +BOOTCONFIG_MAGIC_LEN ) {
@@ -190,10 +194,8 @@ static int load_xbc_from_initrd(int fd, char **buf) }if (lseek (fd, stat.st_size - (size +8 +BOOTCONFIG_MAGIC_LEN ), -SEEK_SET ) <0 ) { -pr_err ("Failed to lseek: %d\n" , -errno); -return -errno; - } +SEEK_SET ) <0 ) +return pr_errno ("Failed to lseek" , -errno); ret =load_xbc_fd (fd, buf, size);if (ret <0 )
@@ -262,14 +264,16 @@ static int show_xbc(const char *path, bool list) ret =stat (path, &st);if (ret <0 ) { -pr_err ("Failed to stat %s: %d\n" , path, -errno); -return -errno; + ret = -errno; +pr_err ("Failed to stat %s: %d\n" , path, ret); +return ret; } fd =open (path,O_RDONLY );if (fd <0 ) { -pr_err ("Failed to open initrd %s: %d\n" , path, fd); -return -errno; + ret = -errno; +pr_err ("Failed to open initrd %s: %d\n" , path, ret); +return ret; } ret =load_xbc_from_initrd (fd, &buf);
@@ -307,8 +311,9 @@ static int delete_xbc(const char *path) fd =open (path,O_RDWR );if (fd <0 ) { -pr_err ("Failed to open initrd %s: %d\n" , path, fd); -return -errno; + ret = -errno; +pr_err ("Failed to open initrd %s: %d\n" , path, ret); +return ret; } size =load_xbc_from_initrd (fd, &buf);
@@ -383,9 +388,10 @@ static int apply_xbc(const char *path, const char *xbc_path)/* Apply new one */ fd =open (path,O_RDWR |O_APPEND );if (fd <0 ) { -pr_err ("Failed to open %s: %d\n" , path, fd); + ret = -errno; +pr_err ("Failed to open %s: %d\n" , path, ret);free (data); -return fd; +return ret; }/* TODO: Ensure the @path is initramfs/initrd image */ ret =write (fd, data, size +8 );
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 2/12 tools/bootconfig: Fix to check the write failure correctly
In reply to Steven RostedtFrom: Masami Hiramatsu <[email protected]>
Fix to check the write(2) failure including partial write correctly and try to rollback the partial write, because if there is no BOOTCONFIG_MAGIC string, we can not remove it.
--- tools/bootconfig/main.c | 30 ++++++++++++++++++++++++++---- 1 file changed, 26 insertions(+), 4 deletions(-)
tools/bootconfig/main.c +26 -4
@@ -337,6 +337,7 @@ static int delete_xbc(const char *path)static int apply_xbc (const char *path,const char *xbc_path) { +struct stat stat;u32 size, csum;char *buf, *data;int ret, fd;
@@ -394,16 +395,26 @@ static int apply_xbc(const char *path, const char *xbc_path)return ret; }/* TODO: Ensure the @path is initramfs/initrd image */ +if (fstat (fd, &stat) <0 ) { +pr_err ("Failed to get the size of %s\n" , path); + goto out; + } ret =write (fd, data, size +8 ); -if (ret <0 ) { +if (ret < size +8 ) { +if (ret <0 ) + ret = -errno;pr_err ("Failed to apply a boot config: %d\n" , ret); - goto out; +if (ret <0 ) + goto out; + goto out_rollback; }/* Write a magic word of the bootconfig */ ret =write (fd,BOOTCONFIG_MAGIC ,BOOTCONFIG_MAGIC_LEN ); -if (ret <0 ) { +if (ret <BOOTCONFIG_MAGIC_LEN ) { +if (ret <0 ) + ret = -errno;pr_err ("Failed to apply a boot config magic: %d\n" , ret); - goto out; + goto out_rollback; } ret =0 ; out:
@@ -411,6 +422,17 @@ static int apply_xbc(const char *path, const char *xbc_path)free (data);return ret; + +out_rollback: +/* Map the partial write to -ENOSPC */ +if (ret >=0 ) + ret = -ENOSPC ; +if (ftruncate (fd, stat.st_size) <0 ) { + ret = -errno; +pr_err ("Failed to rollback the write error: %d\n" , ret); +pr_err ("The initrd %s may be corrupted. Recommend to rebuild.\n" , path); + } + goto out; }static int usage (void )
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 3/12 tools/bootconfig: Align the bootconfig applied initrd image size to 4
In reply to Steven RostedtFrom: Masami Hiramatsu <[email protected]>
Align the bootconfig applied initrd image size to 4. To fill the gap, the bootconfig command uses null characters in between the bootconfig data and the footer. This will expands the footer size but don't change the checksum.
Thus the block image of the initrd file with bootconfig is as follows.
[initrd][bootconfig][(pad)][size][csum]["#BOOTCONFIG\n"]
--- include/linux/bootconfig.h | 3 ++ tools/bootconfig/main.c | 57 +++++++++++++++++------------ tools/bootconfig/test-bootconfig.sh | 6 ++- 3 files changed, 42 insertions(+), 24 deletions(-)
include/linux/bootconfig.h +3 -0
@@ -12,6 +12,9 @@#define BOOTCONFIG_MAGIC "#BOOTCONFIG\n"#define BOOTCONFIG_MAGIC_LEN 12 +#define BOOTCONFIG_ALIGN_SHIFT 2 +#define BOOTCONFIG_ALIGN (1 << BOOTCONFIG_ALIGN_SHIFT) +#define BOOTCONFIG_ALIGN_MASK (BOOTCONFIG_ALIGN - 1)/* XBC tree node */ struct xbc_node {
tools/bootconfig/main.c +34 -23
83 lines not on this page · raw message
tools/bootconfig/test-bootconfig.sh +5 -1
@@ -9,6 +9,7 @@ else TESTDIR=. fi BOOTCONF=${TESTDIR}/bootconfig +ALIGN=4 INITRD=`mktemp ${TESTDIR}/initrd-XXXX` TEMPCONF=`mktemp ${TESTDIR}/temp-XXXX.bconf`
@@ -59,7 +60,10 @@ echo "Show command test" xpass $BOOTCONF $INITRD echo "File size check" -xpass test $new_size -eq $(expr $bconf_size + $initrd_size + 9 + 12) +total_size=$(expr $bconf_size + $initrd_size + 9 + 12 + $ALIGN - 1 ) +total_size=$(expr $total_size / $ALIGN) +total_size=$(expr $total_size \* $ALIGN) +xpass test $new_size -eq $total_size echo "Apply command repeat test" xpass $BOOTCONF -a $TEMPCONF $INITRD
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 4/12 docs: bootconfig: Update file format on initrd image
In reply to Steven RostedtFrom: Masami Hiramatsu <[email protected]>
To align the total file size, add padding null character when appending the bootconfig to initrd image.
--- Documentation/admin-guide/bootconfig.rst | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-)
Documentation/admin-guide/bootconfig.rst +13 -5
@@ -137,15 +137,22 @@ Boot Kernel With a Boot Config ============================== Since the boot configuration file is loaded with initrd, it will be added -to the end of the initrd (initramfs) image file with size, checksum and -12-byte magic word as below. +to the end of the initrd (initramfs) image file with padding, size, +checksum and 12-byte magic word as below. -[initrd][bootconfig][size(u32)][checksum(u32)][#BOOTCONFIG\n] +[initrd][bootconfig][padding][size(u32)][checksum(u32)][#BOOTCONFIG\n] + +When the boot configuration is added to the initrd image, the total +file size is aligned to 4 bytes. To fill the gap, null characters +(``\0``) will be added. Thus the ``size`` is the length of the bootconfig +file + padding bytes. The Linux kernel decodes the last part of the initrd image in memory to get the boot configuration data. Because of this "piggyback" method, there is no need to change or -update the boot loader and the kernel image itself. +update the boot loader and the kernel image itself as long as the boot +loader passes the correct initrd file size. If by any chance, the boot +loader passes a longer size, the kernel feils to find the bootconfig data. To do this operation, Linux kernel provides "bootconfig" command under tools/bootconfig, which allows admin to apply or delete the config file
@@ -176,7 +183,8 @@ up to 512 key-value pairs. If keys contains 3 words in average, it can contain 256 key-value pairs. In most cases, the number of config items will be under 100 entries and smaller than 8KB, so it would be enough. If the node number exceeds 1024, parser returns an error even if the file -size is smaller than 32KB. +size is smaller than 32KB. (Note that this maximum size is not including +the padding null characters.) Anyway, since bootconfig command verifies it when appending a boot config to initrd image, user can notice it before boot.
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 5/12 ring-buffer: Update write stamp with the correct ts
In reply to Steven RostedtFrom: "Steven Rostedt (VMware)" <[email protected]>
The write stamp, used to calculate deltas between events, was updated with the stale "ts" value in the "info" structure, and not with the updated "ts" variable. This caused the deltas between events to be inaccurate, and when crossing into a new sub buffer, had time go backwards.
--- kernel/trace/ring_buffer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/ring_buffer.c +1 -1
@@ -3291,7 +3291,7 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,/* Nothing came after this event between C and E */ info->delta = ts - info->after; (void )rb_time_cmpxchg (&cpu_buffer->write_stamp, - info->after, info->ts); + info->after, ts); info->ts = ts; }else {/*
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 6/12 ring-buffer: Set the right timestamp in the slow path of __rb_reserve_next()
In reply to Steven RostedtFrom: Andrea Righi <[email protected]>
In the slow path of __rb_reserve_next() a nested event(s) can happen between evaluating the timestamp delta of the current event and updating write_stamp via local_cmpxchg(); in this case the delta is not valid anymore and it should be set to 0 (same timestamp as the interrupting event), since the event that we are currently processing is not the last event in the buffer.
--- kernel/trace/ring_buffer.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
kernel/trace/ring_buffer.c +3 -3
@@ -3287,11 +3287,11 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer, ts =rb_time_stamp (cpu_buffer->buffer);barrier ();/*E*/ if (write == (local_read (&tail_page->write) &RB_WRITE_MASK ) && - info->after < ts) { + info->after < ts && +rb_time_cmpxchg (&cpu_buffer->write_stamp, + info->after, ts)) {/* Nothing came after this event between C and E */ info->delta = ts - info->after; - (void )rb_time_cmpxchg (&cpu_buffer->write_stamp, - info->after, ts); info->ts = ts; }else {/*
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 7/12 samples/ftrace: Mark my_tramp[12]? global
In reply to Steven RostedtFrom: Sami Tolvanen <[email protected]>
my_tramp[12]? are declared as global functions in C, but they are not marked global in the inline assembly definition. This mismatch confuses Clang's Control-Flow Integrity checking. Fix the definitions by adding .globl.
--- samples/ftrace/ftrace-direct-modify.c | 2 ++ samples/ftrace/ftrace-direct-too.c | 1 + samples/ftrace/ftrace-direct.c | 1 + 3 files changed, 4 insertions(+)
samples/ftrace/ftrace-direct-modify.c +2 -0
@@ -21,6 +21,7 @@ static unsigned long my_ip = (unsigned long)schedule; asm (" .pushsection .text, \"ax\", @progbits\n" " .type my_tramp1, @function\n" +" .globl my_tramp1\n" " my_tramp1:" " pushq %rbp\n" " movq %rsp, %rbp\n"
@@ -29,6 +30,7 @@ asm (" .size my_tramp1, .-my_tramp1\n" " ret\n" " .type my_tramp2, @function\n" +" .globl my_tramp2\n" " my_tramp2:" " pushq %rbp\n" " movq %rsp, %rbp\n"
samples/ftrace/ftrace-direct-too.c +1 -0
@@ -16,6 +16,7 @@ extern void my_tramp(void *); asm (" .pushsection .text, \"ax\", @progbits\n" " .type my_tramp, @function\n" +" .globl my_tramp\n" " my_tramp:" " pushq %rbp\n" " movq %rsp, %rbp\n"
samples/ftrace/ftrace-direct.c +1 -0
@@ -14,6 +14,7 @@ extern void my_tramp(void *); asm (" .pushsection .text, \"ax\", @progbits\n" " .type my_tramp, @function\n" +" .globl my_tramp\n" " my_tramp:" " pushq %rbp\n" " movq %rsp, %rbp\n"
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 8/12 tracing: Remove WARN_ON in start_thread()
In reply to Steven RostedtFrom: Vasily Averin <[email protected]>
This patch reverts commit 978defee11a5 ("tracing: Do a WARN_ON()
if start_thread() in hwlat is called when thread exists")
.start hook can be legally called several times if according tracer is stopped
screen window 1
[root@localhost ~]# echo 1 > /sys/kernel/tracing/events/kmem/kfree/enable [root@localhost ~]# echo 1 > /sys/kernel/tracing/options/pause-on-trace [root@localhost ~]# less -F /sys/kernel/tracing/trace
screen window 2
[root@localhost ~]# cat /sys/kernel/debug/tracing/tracing_on
0
[root@localhost ~]# echo hwlat > /sys/kernel/debug/tracing/current_tracer [root@localhost ~]# echo 1 > /sys/kernel/debug/tracing/tracing_on [root@localhost ~]# cat /sys/kernel/debug/tracing/tracing_on
0
[root@localhost ~]# echo 2 > /sys/kernel/debug/tracing/tracing_on
triggers warning in dmesg:
WARNING: CPU: 3 PID: 1403 at kernel/trace/trace_hwlat.c:371 hwlat_tracer_start+0xc9/0xd0
--- kernel/trace/trace_hwlat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/trace_hwlat.c +1 -1
@@ -368,7 +368,7 @@ static int start_kthread(struct trace_array *tr)struct task_struct *kthread;int next_cpu; -if (WARN_ON (hwlat_kthread)) +if (hwlat_kthread)return 0 ;/* Just pick the first CPU on first iteration */
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 9/12 tracing: Fix alignment of static buffer
In reply to Steven RostedtFrom: Minchan Kim <[email protected]>
With 5.9 kernel on ARM64, I found ftrace_dump output was broken but it had no problem with normal output "cat /sys/kernel/debug/tracing/trace".
With investigation, it seems coping the data into temporal buffer seems to break the align binary printf expects if the static buffer is not aligned with 4-byte. IIUC, get_arg in bstr_printf expects that args has already right align to be decoded and seq_buf_bprintf says ``the arguments are saved in a 32bit word array that is defined by the format string constraints``. So if we don't keep the align under copy to temporal buffer, the output will be broken by shifting some bytes.
This patch fixes it.
--- kernel/trace/trace.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/trace.c +1 -1
@@ -3534,7 +3534,7 @@ __find_next_entry(struct trace_iterator *iter, int *ent_cpu, }#define STATIC_TEMP_BUF_SIZE 128 -static char static_temp_buf[STATIC_TEMP_BUF_SIZE ]; +static char static_temp_buf[STATIC_TEMP_BUF_SIZE ]__aligned(4) ;/* Find the next real entry, without updating the iterator itself */ struct trace_entry *trace_find_next_entry(struct trace_iterator *iter,
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 10/12 ftrace: Fix updating FTRACE_FL_TRAMP
In reply to Steven RostedtFrom: "Naveen N. Rao" <[email protected]>
On powerpc, kprobe-direct.tc triggered FTRACE_WARN_ON() in ftrace_get_addr_new() followed by the below message:
Bad trampoline accounting at: 000000004222522f (wake_up_process+0xc/0x20) (f0000001)
The set of steps leading to this involved:
- modprobe ftrace-direct-too
- enable_probe
- modprobe ftrace-direct
- rmmod ftrace-direct <-- trigger
The problem turned out to be that we were not updating flags in the ftrace record properly. From the above message about the trampoline accounting being bad, it can be seen that the ftrace record still has FTRACE_FL_TRAMP set though ftrace-direct module is going away. This happens because we are checking if any ftrace_ops has the FTRACE_FL_TRAMP flag set _before_ updating the filter hash.
The fix for this is to look for any _other_ ftrace_ops that also needs FTRACE_FL_TRAMP.
--- kernel/trace/ftrace.c | 22 +++++++++++++++++++++- 1 file changed, 21 insertions(+), 1 deletion(-)
kernel/trace/ftrace.c +21 -1
@@ -1629,6 +1629,8 @@ static bool test_rec_ops_needs_regs(struct dyn_ftrace *rec)static struct ftrace_ops *ftrace_find_tramp_ops_any (struct dyn_ftrace *rec);static struct ftrace_ops * +ftrace_find_tramp_ops_any_other (struct dyn_ftrace *rec,struct ftrace_ops *op_exclude); +static struct ftrace_ops *ftrace_find_tramp_ops_next (struct dyn_ftrace *rec,struct ftrace_ops *ops); static bool __ftrace_hash_rec_update(struct ftrace_ops *ops,
@@ -1778,7 +1780,7 @@ static bool __ftrace_hash_rec_update(struct ftrace_ops *ops,* to it. */ if (ftrace_rec_count (rec) ==1 && -ftrace_find_tramp_ops_any (rec)) +ftrace_find_tramp_ops_any_other (rec, ops)) rec->flags |=FTRACE_FL_TRAMP ;else rec->flags &= ~FTRACE_FL_TRAMP ;
@@ -2244,6 +2246,24 @@ ftrace_find_tramp_ops_any(struct dyn_ftrace *rec)return NULL ; } +static struct ftrace_ops * +ftrace_find_tramp_ops_any_other (struct dyn_ftrace *rec,struct ftrace_ops *op_exclude) +{ +struct ftrace_ops *op; +unsigned long ip = rec->ip; + +do_for_each_ftrace_op (op, ftrace_ops_list) { + +if (op == op_exclude || !op->trampoline) +continue ; + +if (hash_contains_ip (ip, op->func_hash)) +return op; + }while_for_each_ftrace_op (op); + +return NULL ; +} +static struct ftrace_ops *ftrace_find_tramp_ops_next (struct dyn_ftrace *rec,struct ftrace_ops *op)
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 11/12 ftrace: Fix DYNAMIC_FTRACE_WITH_DIRECT_CALLS dependency
In reply to Steven RostedtFrom: "Naveen N. Rao" <[email protected]>
DYNAMIC_FTRACE_WITH_DIRECT_CALLS should depend on DYNAMIC_FTRACE_WITH_REGS since we need ftrace_regs_caller().
--- kernel/trace/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/trace/Kconfig +1 -1
@@ -202,7 +202,7 @@ config DYNAMIC_FTRACE_WITH_REGS config DYNAMIC_FTRACE_WITH_DIRECT_CALLS def_bool y - depends on DYNAMIC_FTRACE + depends on DYNAMIC_FTRACE_WITH_REGS depends on HAVE_DYNAMIC_FTRACE_WITH_DIRECT_CALLS config FUNCTION_PROFILER
Signature · 1 line
2.28.0
Steven Rostedt
maintainerPATCH 12/12 ring-buffer: Always check to put back before stamp when crossing pages
In reply to Steven RostedtFrom: "Steven Rostedt (VMware)" <[email protected]>
The current ring buffer logic checks to see if the updating of the event buffer was interrupted, and if it is, it will try to fix up the before stamp with the write stamp to make them equal again. This logic is flawed, because if it is not interrupted, the two are guaranteed to be different, as the current event just updated the before stamp before allocation. This guarantees that the next event (this one or another interrupting one) will think it interrupted the time updates of a previous event and inject an absolute time stamp to compensate.
The correct logic is to always update the timestamps when traversing to a new sub buffer.
--- kernel/trace/ring_buffer.c | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-)
kernel/trace/ring_buffer.c +6 -8
@@ -3234,14 +3234,12 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,/* See if we shot pass the end of this buffer page */ if (unlikely (write >BUF_PAGE_SIZE )) { -if (tail != w) { -/* before and after may now different, fix it up*/ - b_ok =rb_time_read (&cpu_buffer->before_stamp, &info->before); - a_ok =rb_time_read (&cpu_buffer->write_stamp, &info->after); -if (a_ok && b_ok && info->before != info->after) - (void )rb_time_cmpxchg (&cpu_buffer->before_stamp, - info->before, info->after); - } +/* before and after may now different, fix it up*/ + b_ok =rb_time_read (&cpu_buffer->before_stamp, &info->before); + a_ok =rb_time_read (&cpu_buffer->write_stamp, &info->after); +if (a_ok && b_ok && info->before != info->after) + (void )rb_time_cmpxchg (&cpu_buffer->before_stamp, + info->before, info->after);return rb_move_tail (cpu_buffer, tail, info); }
Signature · 1 line
2.28.0