[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-d1e7e02f30be672c6f6ee40908be83877a0d49d1@git.kernel.org>
Date: Fri, 10 Apr 2009 11:06:49 GMT
From: Lai Jiangshan <laijs@...fujitsu.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
fweisbec@...il.com, srostedt@...hat.com, tglx@...utronix.de,
laijs@...fujitsu.com, mingo@...e.hu
Subject: [tip:tracing/core] tracing: disable seeking for trace_pipe_raw
Commit-ID: d1e7e02f30be672c6f6ee40908be83877a0d49d1
Gitweb: http://git.kernel.org/tip/d1e7e02f30be672c6f6ee40908be83877a0d49d1
Author: Lai Jiangshan <laijs@...fujitsu.com>
AuthorDate: Thu, 2 Apr 2009 15:16:56 +0800
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Fri, 10 Apr 2009 12:44:42 +0200
tracing: disable seeking for trace_pipe_raw
Impact: disable pread()
We set tracing_buffers_fops.llseek to no_llseek,
but we can still perform pread() to read this file.
That is not expected.
This fix uses nonseekable_open() to disable it.
tracing_buffers_fops.llseek is still set to no_llseek,
it mark this file is a "non-seekable device" and is used by
sys_splice(). See also do_splice() or manual of splice(2):
ERRORS
EINVAL Target file system doesn't support splicing;
neither of the descriptors refers to a pipe;
or offset given for non-seekable device.
Signed-off-by: Lai Jiangshan <laijs@...fujitsu.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>
Cc: Steven Rostedt <srostedt@...hat.com>
LKML-Reference: <49D46668.8030806@...fujitsu.com>
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
kernel/trace/trace.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 9d28476..24b0168 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -3285,7 +3285,7 @@ static int tracing_buffers_open(struct inode *inode, struct file *filp)
filp->private_data = info;
- return 0;
+ return nonseekable_open(inode, filp);
out:
kfree(info);
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists