diff options
author | Andrey Ryabinin <aryabinin@virtuozzo.com> | 2018-08-10 17:23:03 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-08-10 20:19:58 -0700 |
commit | 3ca17b1f3628f916f79e0ab62f1bf0e45ec9ba92 (patch) | |
tree | 079b00ad1bc4e3dd0770f091a7a8b62d851a73b8 /tools | |
parent | 5832fcf9990c0e72c468e0dc6022836bb1b8d1e8 (diff) | |
download | linux-3ca17b1f3628f916f79e0ab62f1bf0e45ec9ba92.tar.bz2 |
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/20180802153209.813-1-aryabinin@virtuozzo.com
Signed-off-by: Andrey Ryabinin <aryabinin@virtuozzo.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions