diff options
| author | Philipp Stanner <[email protected]> | 2023-11-03 12:12:08 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <[email protected]> | 2023-11-25 07:23:16 +0000 |
| commit | e651faa2fba4d387aa00b3c02e9c10232852d2ef (patch) | |
| tree | 30a81de33ad819a75f1beae0061839edb0edbb8b /tools/perf/scripts/python | |
| parent | 727e08b1a56a60ee9b68ae5c7539cbcfe2cfe552 (diff) | |
drivers/tty/vt: use standard array-copy-functions
tty/vt currently uses memdup_user() and vmemdup_array_user() to copy
userspace arrays.
Whereas there is no danger of overflowing, the call to vmemdup_user()
currently utilizes array_size() to calculate the array size
nevertheless. This is not useful because array_size() would return
SIZE_MAX and pass it to vmemdup_user() in case of (the impossible)
overflow.
string.h from the core-API now provides the wrappers memdup_array_user()
and vmemdup_array_user() to copy userspace arrays in a standardized
manner. Additionally, they also perform generic overflow-checks.
Use these wrappers to make it more obvious and readable that arrays are
being copied.
As we are at it, remove two unnecessary empty lines.
Suggested-by: Dave Airlie <[email protected]>
Signed-off-by: Philipp Stanner <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions