Skip to content

Commit fe1c021

Browse files
Tetsuo Handagregkh
Tetsuo Handa
authored andcommitted
tomoyo: don't emit warning in tomoyo_write_control()
[ Upstream commit 3df7546 ] 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]> Signed-off-by: Sasha Levin <[email protected]>
1 parent 093286c commit fe1c021

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

security/tomoyo/common.c

+1-1
Original file line numberDiff line numberDiff line change
@@ -2665,7 +2665,7 @@ ssize_t tomoyo_write_control(struct tomoyo_io_buffer *head,
26652665

26662666
if (head->w.avail >= head->writebuf_size - 1) {
26672667
const int len = head->writebuf_size * 2;
2668-
char *cp = kzalloc(len, GFP_NOFS);
2668+
char *cp = kzalloc(len, GFP_NOFS | __GFP_NOWARN);
26692669

26702670
if (!cp) {
26712671
error = -ENOMEM;

0 commit comments

Comments
 (0)