general protection fault in fanotify_should_merge

5 views
Skip to first unread message

syzbot

unread,
Aug 5, 2021, 7:31:27 PM8/5/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: d4affd6b6e81 Merge tag 'perf-tools-fixes-for-v5.14-2021-08..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14ab949a300000
kernel config: https://syzkaller.appspot.com/x/.config?x=6cc86e19161c9d37
dashboard link: https://syzkaller.appspot.com/bug?extid=8215eb88c60d2e597d46
compiler: Debian clang version 11.0.1-2, GNU ld (GNU Binutils for Debian) 2.35.1
CC: [amir...@gmail.com ja...@suse.cz linux-...@vger.kernel.org linux-...@vger.kernel.org rep...@google.com]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8215eb...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xee0e0a000e0ee003: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0x7070700070770018-0x707070007077001f]
CPU: 1 PID: 18613 Comm: syz-executor.5 Not tainted 5.14.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:fanotify_should_merge+0x33/0xe20 fs/notify/fanotify/fanotify.c:119
Code: 53 48 83 ec 28 49 89 f6 49 89 fd e8 57 bd 97 ff 0f 1f 44 00 00 49 bc 00 00 00 00 00 fc ff df 49 8d 5d 24 48 89 d8 48 c1 e8 03 <42> 8a 04 20 84 c0 0f 85 fa 08 00 00 44 8b 3b 49 8d 5e 24 48 89 d8
RSP: 0018:ffffc900147f7878 EFLAGS: 00010206
RAX: 0e0e0e000e0ee003 RBX: 707070007077001b RCX: ffff8880ae7a3880
RDX: 0000000000000000 RSI: ffff888036cbfd68 RDI: 707070007076fff7
RBP: 0000000000000001 R08: ffffffff81e84e7c R09: 0000000000000003
R10: fffff520028fef15 R11: 0000000000000004 R12: dffffc0000000000
R13: 707070007076fff7 R14: ffff888036cbfd68 R15: ffff888036cbfd68
FS: 0000000002e57400(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff93df8bfe8 CR3: 00000000a275e000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
fanotify_merge+0x11f/0x260 fs/notify/fanotify/fanotify.c:177
fsnotify_add_event+0x151/0x410 fs/notify/notification.c:113
fanotify_handle_event+0x13c9/0x19c0 fs/notify/fanotify/fanotify.c:781
send_to_group+0x755/0x1180 fs/notify/fsnotify.c:360
fsnotify+0x9e5/0x12e0 fs/notify/fsnotify.c:541
__fsnotify_parent+0x433/0x670 fs/notify/fsnotify.c:232
fsnotify_parent include/linux/fsnotify.h:68 [inline]
fsnotify_file include/linux/fsnotify.h:90 [inline]
fsnotify_close include/linux/fsnotify.h:279 [inline]
__fput+0x252/0x7b0 fs/file_table.c:266
task_work_run+0x146/0x1c0 kernel/task_work.c:164
tracehook_notify_resume include/linux/tracehook.h:189 [inline]
exit_to_user_mode_loop kernel/entry/common.c:175 [inline]
exit_to_user_mode_prepare+0x201/0x220 kernel/entry/common.c:209
__syscall_exit_to_user_mode_work kernel/entry/common.c:291 [inline]
syscall_exit_to_user_mode+0x26/0x60 kernel/entry/common.c:302
do_syscall_64+0x4c/0xb0 arch/x86/entry/common.c:86
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x4193fb
Code: 0f 05 48 3d 00 f0 ff ff 77 45 c3 0f 1f 40 00 48 83 ec 18 89 7c 24 0c e8 63 fc ff ff 8b 7c 24 0c 41 89 c0 b8 03 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 89 44 24 0c e8 a1 fc ff ff 8b 44
RSP: 002b:00007ffc4b6df460 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00000000004193fb
RDX: 0000000000000000 RSI: 00007ff95bba02a8 RDI: 0000000000000004
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000001b33922780
R10: 0000000000001ead R11: 0000000000000293 R12: 000000000056cb00
R13: 000000000056cb00 R14: 000000000056bf80 R15: 00000000002a682b
Modules linked in:
---[ end trace d2928274730ba070 ]---
RIP: 0010:fanotify_should_merge+0x33/0xe20 fs/notify/fanotify/fanotify.c:119
Code: 53 48 83 ec 28 49 89 f6 49 89 fd e8 57 bd 97 ff 0f 1f 44 00 00 49 bc 00 00 00 00 00 fc ff df 49 8d 5d 24 48 89 d8 48 c1 e8 03 <42> 8a 04 20 84 c0 0f 85 fa 08 00 00 44 8b 3b 49 8d 5e 24 48 89 d8
RSP: 0018:ffffc900147f7878 EFLAGS: 00010206
RAX: 0e0e0e000e0ee003 RBX: 707070007077001b RCX: ffff8880ae7a3880
RDX: 0000000000000000 RSI: ffff888036cbfd68 RDI: 707070007076fff7
RBP: 0000000000000001 R08: ffffffff81e84e7c R09: 0000000000000003
R10: fffff520028fef15 R11: 0000000000000004 R12: dffffc0000000000
R13: 707070007076fff7 R14: ffff888036cbfd68 R15: ffff888036cbfd68
FS: 0000000002e57400(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff93df8bfe8 CR3: 00000000a275e000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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 syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Oct 30, 2021, 7:29:18 PM10/30/21
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages