diff options
| author | Kees Cook <keescook@chromium.org> | 2017-02-24 15:00:38 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2017-02-24 17:46:56 -0800 |
| commit | 85caa95b9f19bb3a26d7e025d1134760b69e0c40 (patch) | |
| tree | 9db3bbeccc4329287960f42189ba4b1d4ee7a561 /lib/memweight.c | |
| parent | 849de0cd2c873c878fc2605156f10a8ade9bde28 (diff) | |
| download | linux-85caa95b9f19bb3a26d7e025d1134760b69e0c40.tar.bz2 | |
bug: switch data corruption check to __must_check
The CHECK_DATA_CORRUPTION() macro was designed to have callers do
something meaningful/protective on failure. However, using "return
false" in the macro too strictly limits the design patterns of callers.
Instead, let callers handle the logic test directly, but make sure that
the result IS checked by forcing __must_check (which appears to not be
able to be used directly on macro expressions).
Link: http://lkml.kernel.org/r/20170206204547.GA125312@beast
Signed-off-by: Kees Cook <keescook@chromium.org>
Suggested-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'lib/memweight.c')
0 files changed, 0 insertions, 0 deletions