1
0
Files
linux/kernel
Lai Jiangshan ac91d85456 tracing: Fix warning in s_next of trace file ops
This warning in s_next() can be triggered by lseek():
 [<c018b3f7>] ? s_next+0x77/0x80
 [<c013e3c1>] warn_slowpath_common+0x81/0xa0
 [<c018b3f7>] ? s_next+0x77/0x80
 [<c013e3fa>] warn_slowpath_null+0x1a/0x20
 [<c018b3f7>] s_next+0x77/0x80
 [<c01efa77>] traverse+0x117/0x200
 [<c01eff13>] seq_lseek+0xa3/0x120
 [<c01efe70>] ? seq_lseek+0x0/0x120
 [<c01d7081>] vfs_llseek+0x41/0x50
 [<c01d8116>] sys_llseek+0x66/0xa0
 [<c0102bd0>] sysenter_do_call+0x12/0x26

The iterator "leftover" variable is zeroed in the opening of the trace
file. But lseek can call s_start() which will call s_next() without
reseting the "leftover" variable back to zero, which might trigger
the WARN_ON_ONCE(iter->leftover) that is in s_next().

Cc: stable@kernel.org
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
LKML-Reference: <4B8CE06A.9090207@cn.fujitsu.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
2010-03-02 21:11:47 -05:00
..
2009-09-21 14:29:21 +02:00
2009-12-15 08:53:10 -08:00
2009-12-22 12:27:34 -05:00
2010-02-25 12:02:13 +01:00
2009-12-06 21:10:56 +01:00
2010-02-03 10:21:57 +11:00
2009-09-18 09:48:52 -07:00
2009-12-14 23:55:34 +01:00
2010-01-21 13:40:18 +01:00
2009-07-24 10:53:29 +02:00
2009-12-31 19:45:04 +00:00
2010-02-26 08:20:46 +01:00
2010-02-02 06:58:27 +01:00
2009-12-09 10:03:07 +01:00
2010-02-18 14:30:18 -08:00
2009-12-22 14:10:37 -08:00
2009-09-23 18:13:10 -07:00
2010-01-21 13:40:18 +01:00