From: syzbot <syzbot+05d57384ff3551e412be@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: memory leak in anon_inode_getfile
Date: Mon, 09 Nov 2020 05:24:22 -0800 [thread overview]
Message-ID: <000000000000f4db7805b3ac7a65@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 9dbc1c03 Merge tag 'xfs-5.10-fixes-3' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14554746500000
kernel config: https://syzkaller.appspot.com/x/.config?x=da948f64bffc0baf
dashboard link: https://syzkaller.appspot.com/bug?extid=05d57384ff3551e412be
compiler: gcc (GCC) 10.1.0-syz 20200507
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10db2f92500000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1698d134500000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+05d57384ff3551e412be@syzkaller.appspotmail.com
BUG: memory leak
unreferenced object 0xffff8881019e6d00 (size 256):
comm "syz-executor550", pid 8486, jiffies 4294950527 (age 34.300s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0 e0 fd 40 81 88 ff ff c0 96 fc 0f 81 88 ff ff ...@............
backtrace:
[<00000000e44e21fc>] kmem_cache_zalloc include/linux/slab.h:654 [inline]
[<00000000e44e21fc>] __alloc_file+0x1f/0x130 fs/file_table.c:101
[<00000000d4a5a020>] alloc_empty_file+0x69/0x120 fs/file_table.c:151
[<00000000eb40cf42>] alloc_file+0x33/0x1b0 fs/file_table.c:193
[<000000001c6c0501>] alloc_file_pseudo+0xb2/0x140 fs/file_table.c:233
[<00000000acbecb3c>] anon_inode_getfile fs/anon_inodes.c:91 [inline]
[<00000000acbecb3c>] anon_inode_getfile+0xaa/0x120 fs/anon_inodes.c:74
[<0000000047c0be97>] io_uring_get_fd fs/io_uring.c:9172 [inline]
[<0000000047c0be97>] io_uring_create fs/io_uring.c:9351 [inline]
[<0000000047c0be97>] io_uring_setup+0x1139/0x1640 fs/io_uring.c:9385
[<0000000079584e06>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<000000009e5ef977>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff888110e3ce58 (size 24):
comm "syz-executor550", pid 8486, jiffies 4294950527 (age 34.300s)
hex dump (first 24 bytes):
00 00 00 00 00 00 00 00 b0 4e 93 00 81 88 ff ff .........N......
00 00 00 00 00 00 00 00 ........
backtrace:
[<00000000c78e23d5>] kmem_cache_zalloc include/linux/slab.h:654 [inline]
[<00000000c78e23d5>] lsm_file_alloc security/security.c:568 [inline]
[<00000000c78e23d5>] security_file_alloc+0x2a/0xb0 security/security.c:1456
[<000000000d394d00>] __alloc_file+0x5d/0x130 fs/file_table.c:106
[<00000000d4a5a020>] alloc_empty_file+0x69/0x120 fs/file_table.c:151
[<00000000eb40cf42>] alloc_file+0x33/0x1b0 fs/file_table.c:193
[<000000001c6c0501>] alloc_file_pseudo+0xb2/0x140 fs/file_table.c:233
[<00000000acbecb3c>] anon_inode_getfile fs/anon_inodes.c:91 [inline]
[<00000000acbecb3c>] anon_inode_getfile+0xaa/0x120 fs/anon_inodes.c:74
[<0000000047c0be97>] io_uring_get_fd fs/io_uring.c:9172 [inline]
[<0000000047c0be97>] io_uring_create fs/io_uring.c:9351 [inline]
[<0000000047c0be97>] io_uring_setup+0x1139/0x1640 fs/io_uring.c:9385
[<0000000079584e06>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<000000009e5ef977>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff888101abb840 (size 168):
comm "syz-executor550", pid 8473, jiffies 4294952674 (age 12.830s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<0000000046ab9583>] prepare_creds+0x25/0x390 kernel/cred.c:258
[<00000000064d32d3>] copy_creds+0x3a/0x230 kernel/cred.c:358
[<00000000d2f3a3f7>] copy_process+0x66f/0x2510 kernel/fork.c:1971
[<00000000e82686f8>] kernel_clone+0xf3/0x670 kernel/fork.c:2456
[<00000000bbc67aa6>] __do_sys_clone+0x76/0xa0 kernel/fork.c:2573
[<0000000079584e06>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<000000009e5ef977>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
BUG: memory leak
unreferenced object 0xffff888101716600 (size 256):
comm "syz-executor550", pid 8502, jiffies 4294952674 (age 12.830s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
a0 e0 fd 40 81 88 ff ff 80 fd fd 0f 81 88 ff ff ...@............
backtrace:
[<00000000e44e21fc>] kmem_cache_zalloc include/linux/slab.h:654 [inline]
[<00000000e44e21fc>] __alloc_file+0x1f/0x130 fs/file_table.c:101
[<00000000d4a5a020>] alloc_empty_file+0x69/0x120 fs/file_table.c:151
[<00000000eb40cf42>] alloc_file+0x33/0x1b0 fs/file_table.c:193
[<000000001c6c0501>] alloc_file_pseudo+0xb2/0x140 fs/file_table.c:233
[<00000000acbecb3c>] anon_inode_getfile fs/anon_inodes.c:91 [inline]
[<00000000acbecb3c>] anon_inode_getfile+0xaa/0x120 fs/anon_inodes.c:74
[<0000000047c0be97>] io_uring_get_fd fs/io_uring.c:9172 [inline]
[<0000000047c0be97>] io_uring_create fs/io_uring.c:9351 [inline]
[<0000000047c0be97>] io_uring_setup+0x1139/0x1640 fs/io_uring.c:9385
[<0000000079584e06>] do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
[<000000009e5ef977>] entry_SYSCALL_64_after_hwframe+0x44/0xa9
---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this issue, for details see:
https://goo.gl/tpsmEJ#testing-patches
reply other threads:[~2020-11-09 13:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=000000000000f4db7805b3ac7a65@google.com \
--to=syzbot+05d57384ff3551e412be@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).