diff options
author | Daniel Latypov <dlatypov@google.com> | 2022-07-22 20:15:34 +0300 |
---|---|---|
committer | Shuah Khan <skhan@linuxfoundation.org> | 2022-10-07 19:15:56 +0300 |
commit | 185d57797c5ea82e941befc2489dba0cf162b9c4 (patch) | |
tree | a410492b1fb6ccdfef80f39c916cb02fe697ac2c /tools/testing/kunit/qemu_configs/riscv.py | |
parent | e562e309d1d4ac05457c1454b6007071f13b5684 (diff) | |
download | linux-185d57797c5ea82e941befc2489dba0cf162b9c4.tar.xz |
kunit: make kunit_kfree(NULL) a no-op to match kfree()
The real kfree() function will silently return when given a NULL.
So a user might reasonably think they can write the following code:
char *buffer = NULL;
if (param->use_buffer) buffer = kunit_kzalloc(test, 10, GFP_KERNEL);
...
kunit_kfree(test, buffer);
As-is, kunit_kfree() will mark the test as FAILED when buffer is NULL.
(And in earlier times, it would segfault).
Let's match the semantics of kfree().
Suggested-by: David Gow <davidgow@google.com>
Signed-off-by: Daniel Latypov <dlatypov@google.com>
Reviewed-by: David Gow <davidgow@google.com>
Reviewed-by: Brendan Higgins <brendanhiggins@google.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/testing/kunit/qemu_configs/riscv.py')
0 files changed, 0 insertions, 0 deletions