Revert "fanotify: remove unneeded sub-zero check for unsigned value"
This reverts commit e659522446
.
These kinds of patches are only making the code worse.
Compilers don't care about the unnecessary check, but removing it makes
the code less obvious to a human. The declaration of 'len' is more than
80 lines earlier, so a human won't easily see that 'len' is of an
unsigned type, so to a human the range check that checks against zero is
much more explicit and obvious.
Any tool that complains about a range check like this just because the
variable is unsigned is actively detrimental, and should be ignored.
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
This commit is contained in:
parent
5af9d1cf39
commit
d0e71e23ec
@ -502,7 +502,7 @@ static int copy_fid_info_to_user(__kernel_fsid_t *fsid, struct fanotify_fh *fh,
|
||||
}
|
||||
|
||||
/* Pad with 0's */
|
||||
WARN_ON_ONCE(len >= FANOTIFY_EVENT_ALIGN);
|
||||
WARN_ON_ONCE(len < 0 || len >= FANOTIFY_EVENT_ALIGN);
|
||||
if (len > 0 && clear_user(buf, len))
|
||||
return -EFAULT;
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user