diff options
| author | Tetsuo Handa <[email protected]> | 2024-12-16 10:38:40 +0000 |
|---|---|---|
| committer | Tetsuo Handa <[email protected]> | 2024-12-16 10:41:29 +0000 |
| commit | 3df7546fc03b8f004eee0b9e3256369f7d096685 (patch) | |
| tree | 94564a32dcd3a40fec843e9d9017792f2592c1c3 /net/switchdev/switchdev.c | |
| parent | Linux 6.13-rc3 (diff) | |
| download | kernel-3df7546fc03b8f004eee0b9e3256369f7d096685.tar.gz kernel-3df7546fc03b8f004eee0b9e3256369f7d096685.zip | |
tomoyo: don't emit warning in tomoyo_write_control()
syzbot is reporting too large allocation warning at tomoyo_write_control(),
for one can write a very very long line without new line character. To fix
this warning, I use __GFP_NOWARN rather than checking for KMALLOC_MAX_SIZE,
for practically a valid line should be always shorter than 32KB where the
"too small to fail" memory-allocation rule applies.
One might try to write a valid line that is longer than 32KB, but such
request will likely fail with -ENOMEM. Therefore, I feel that separately
returning -EINVAL when a line is longer than KMALLOC_MAX_SIZE is redundant.
There is no need to distinguish over-32KB and over-KMALLOC_MAX_SIZE.
Reported-by: [email protected]
Closes: https://syzkaller.appspot.com/bug?extid=7536f77535e5210a5c76
Reported-by: Leo Stone <[email protected]>
Closes: https://lkml.kernel.org/r/[email protected]
Signed-off-by: Tetsuo Handa <[email protected]>
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions
