From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: rostedt@goodmis.org
Cc: linux-kernel@vger.kernel.org, Tom Zanussi <tom.zanussi@linux.intel.com>
Subject: [PATCH 1/2] tracing: Add __rcu to enter/exit_syscall_files
Date: Sun, 10 Nov 2013 23:03:45 -0600 [thread overview]
Message-ID: <5e250e4e8a87071fe6e0b2042fea27f42d63794a.1384145701.git.tom.zanussi@linux.intel.com> (raw)
In-Reply-To: <cover.1384145701.git.tom.zanussi@linux.intel.com>
In-Reply-To: <cover.1384145701.git.tom.zanussi@linux.intel.com>
Add __rcu annotation to the contents of enter/exit_syscall_files to
signify that they're protected by rcu and to silence the following
sparse warnings when CONFIG_SPARSE_RCU_POINTER=y:
kernel/trace/trace_syscalls.c:320:23: error: incompatible types in
comparison expression (different address spaces)
kernel/trace/trace_syscalls.c:368:23: error: incompatible types in
comparison expression (different address spaces)
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Reported-by: Fengguang Wu <fengguang.wu@intel.com>
---
kernel/trace/trace.h | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace.h b/kernel/trace/trace.h
index 11a04d6..7ca1993 100644
--- a/kernel/trace/trace.h
+++ b/kernel/trace/trace.h
@@ -192,8 +192,8 @@ struct trace_array {
#ifdef CONFIG_FTRACE_SYSCALLS
int sys_refcount_enter;
int sys_refcount_exit;
- struct ftrace_event_file *enter_syscall_files[NR_syscalls];
- struct ftrace_event_file *exit_syscall_files[NR_syscalls];
+ struct ftrace_event_file __rcu *enter_syscall_files[NR_syscalls];
+ struct ftrace_event_file __rcu *exit_syscall_files[NR_syscalls];
#endif
int stop_count;
int clock_id;
--
1.8.3.1
next prev parent reply other threads:[~2013-11-11 5:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-11 5:03 [PATCH 0/2] tracing: a couple minor for-next fixes Tom Zanussi
2013-11-11 5:03 ` Tom Zanussi [this message]
2013-11-11 5:03 ` [PATCH 2/2] tracing: Remove redundant destroy_call_preds() call Tom Zanussi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5e250e4e8a87071fe6e0b2042fea27f42d63794a.1384145701.git.tom.zanussi@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®