aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorAndrey Ryabinin <[email protected]>2018-08-10 17:23:03 -0700
committerLinus Torvalds <[email protected]>2018-08-10 20:19:58 -0700
commit3ca17b1f3628f916f79e0ab62f1bf0e45ec9ba92 (patch)
tree079b00ad1bc4e3dd0770f091a7a8b62d851a73b8 /tools/perf/scripts/python/export-to-postgresql.py
parent5832fcf9990c0e72c468e0dc6022836bb1b8d1e8 (diff)
lib/ubsan: remove null-pointer checks
With gcc-8 fsanitize=null become very noisy. GCC started to complain about things like &a->b, where 'a' is NULL pointer. There is no NULL dereference, we just calculate address to struct member. It's technically undefined behavior so UBSAN is correct to report it. But as long as there is no real NULL-dereference, I think, we should be fine. -fno-delete-null-pointer-checks compiler flag should protect us from any consequences. So let's just no use -fsanitize=null as it's not useful for us. If there is a real NULL-deref we will see crash. Even if userspace mapped something at NULL (root can do this), with things like SMAP should catch the issue. Link: http://lkml.kernel.org/r/[email protected] Signed-off-by: Andrey Ryabinin <[email protected]> Signed-off-by: Andrew Morton <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions