summaryrefslogtreecommitdiff
path: root/lib/bucket_locks.c
diff options
context:
space:
mode:
authorAleksa Sarai <cyphar@cyphar.com>2019-10-06 10:30:28 +1100
committerChristian Brauner <christian.brauner@ubuntu.com>2019-10-07 02:03:07 +0200
commitc90012ac85c24547e5c3468ef00aabf44aa7332d (patch)
treebd1f9f766105c864a30c4278ad1cbc59887a74aa /lib/bucket_locks.c
parentda0c9ea146cbe92b832f1b0f694840ea8eb33cce (diff)
lib: test_user_copy: style cleanup
While writing the tests for copy_struct_from_user(), I used a construct that Linus doesn't appear to be too fond of: On 2019-10-04, Linus Torvalds <torvalds@linux-foundation.org> wrote: > Hmm. That code is ugly, both before and after the fix. > > This just doesn't make sense for so many reasons: > > if ((ret |= test(umem_src == NULL, "kmalloc failed"))) > > where the insanity comes from > > - why "|=" when you know that "ret" was zero before (and it had to > be, for the test to make sense) > > - why do this as a single line anyway? > > - don't do the stupid "double parenthesis" to hide a warning. Make it > use an actual comparison if you add a layer of parentheses. So instead, use a bog-standard check that isn't nearly as ugly. Fixes: 341115822f88 ("usercopy: Add parentheses around assignment in test_copy_struct_from_user") Fixes: f5a1a536fa14 ("lib: introduce copy_struct_from_user() helper") Signed-off-by: Aleksa Sarai <cyphar@cyphar.com> Reviewed-by: Nathan Chancellor <natechancellor@gmail.com> Reviewed-by: Christian Brauner <christian.brauner@ubuntu.com> Link: https://lore.kernel.org/r/20191005233028.18566-1-cyphar@cyphar.com Signed-off-by: Christian Brauner <christian.brauner@ubuntu.com>
Diffstat (limited to 'lib/bucket_locks.c')
0 files changed, 0 insertions, 0 deletions