diff options
author | Akinobu Mita <[email protected]> | 2023-02-26 21:42:54 +0900 |
---|---|---|
committer | Christoph Hellwig <[email protected]> | 2023-02-28 06:14:44 -0700 |
commit | 76d54bf20cdcc1ed7569a89885e09636e9a8d71d (patch) | |
tree | 8e3f71e12f26ceb97febce3a84fd038ff398de86 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
parent | 51d24f701f453c18cb5f4596d8bbe8034e5d3fb4 (diff) |
nvme-tcp: don't access released socket during error recovery
While the error recovery work is temporarily failing reconnect attempts,
running the 'nvme list' command causes a kernel NULL pointer dereference
by calling getsockname() with a released socket.
During error recovery work, the nvme tcp socket is released and a new one
created, so it is not safe to access the socket without proper check.
Signed-off-by: Akinobu Mita <[email protected]>
Fixes: 02c57a82c008 ("nvme-tcp: print actual source IP address through sysfs "address" attr")
Reviewed-by: Martin Belanger <[email protected]>
Reviewed-by: Hannes Reinecke <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions