Searched hist:d8434c31378d5f2009741fa171bd1143c77a6e4a (Results 1 – 2 of 2) sorted by relevance
| /linux/include/trace/events/ |
| H A D | smbus.h | d8434c31378d5f2009741fa171bd1143c77a6e4a Wed Feb 13 03:40:57 UTC 2019 John Sperbeck <jsperbeck@google.com> i2c: core-smbus: don't trace smbus_reply data on errors
If an smbus transfer fails, there's no guarantee that the output
buffer was written. So, avoid trying to show the output buffer when
tracing after an error. This was 'mostly harmless', but would trip
up kasan checking if left-over cruft in byte 0 is a large length,
causing us to read from unwritten memory.
Signed-off-by: John Sperbeck <jsperbeck@google.com>
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
|
| /linux/drivers/i2c/ |
| H A D | i2c-core-smbus.c | d8434c31378d5f2009741fa171bd1143c77a6e4a Wed Feb 13 03:40:57 UTC 2019 John Sperbeck <jsperbeck@google.com> i2c: core-smbus: don't trace smbus_reply data on errors
If an smbus transfer fails, there's no guarantee that the output
buffer was written. So, avoid trying to show the output buffer when
tracing after an error. This was 'mostly harmless', but would trip
up kasan checking if left-over cruft in byte 0 is a large length,
causing us to read from unwritten memory.
Signed-off-by: John Sperbeck <jsperbeck@google.com>
Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
|