lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:   Wed, 16 Dec 2020 14:34:10 -0800
From:   syzbot <syzbot+e3f15f0b58a330ddfc30@...kaller.appspotmail.com>
To:     dmitry.torokhov@...il.com, gustavoars@...nel.org,
        linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzkaller-bugs@...glegroups.com
Subject: WARNING in atp_close

Hello,

syzbot found the following issue on:

HEAD commit:    7b1b868e Merge tag 'for-linus' of git://git.kernel.org/pub..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17b34b37500000
kernel config:  https://syzkaller.appspot.com/x/.config?x=5ed9af1b47477866
dashboard link: https://syzkaller.appspot.com/bug?extid=e3f15f0b58a330ddfc30
compiler:       gcc (GCC) 10.1.0-syz 20200507

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+e3f15f0b58a330ddfc30@...kaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 1 PID: 11091 at kernel/workqueue.c:3040 __flush_work+0x91a/0xac0 kernel/workqueue.c:3040
Modules linked in:
CPU: 1 PID: 11091 Comm: syz-executor.1 Not tainted 5.10.0-rc7-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__flush_work+0x91a/0xac0 kernel/workqueue.c:3040
Code: e3 08 48 0f ba 28 03 48 8b 95 70 fe ff ff 81 cb e0 01 00 00 e9 50 fa ff ff e8 f2 03 28 00 0f 0b e9 19 fc ff ff e8 e6 03 28 00 <0f> 0b 45 31 f6 e9 0a fc ff ff e8 d7 03 28 00 e8 62 8d 14 00 31 ff
RSP: 0018:ffffc900063efb58 EFLAGS: 00010293
RAX: 0000000000000000 RBX: dffffc0000000000 RCX: ffffffff8147f9a6
RDX: ffff888075a2a380 RSI: ffffffff8148021a RDI: 0000000000000001
RBP: ffffc900063efce8 R08: 0000000000000001 R09: ffffffff8ebb96a7
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 1ffff92000c7dfa0 R14: 0000000000000001 R15: ffff888075a2a380
FS:  0000000003523940(0000) GS:ffff8880b9f00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f5537bf2934 CR3: 0000000015468000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 __cancel_work_timer+0x3b3/0x520 kernel/workqueue.c:3136
 atp_close+0x5e/0xa0 drivers/input/mouse/appletouch.c:812
 input_close_device+0x110/0x1a0 drivers/input/input.c:683
 evdev_close_device drivers/input/evdev.c:414 [inline]
 evdev_release+0x34c/0x410 drivers/input/evdev.c:456
 __fput+0x285/0x920 fs/file_table.c:281
 task_work_run+0xdd/0x190 kernel/task_work.c:151
 tracehook_notify_resume include/linux/tracehook.h:188 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:164 [inline]
 exit_to_user_mode_prepare+0x17e/0x1a0 kernel/entry/common.c:191
 syscall_exit_to_user_mode+0x38/0x260 kernel/entry/common.c:266
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x417ab1
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 a4 1a 00 00 c3 48 83 ec 08 e8 0a fc ff ff 48 89 04 24 b8 03 00 00 00 0f 05 <48> 8b 3c 24 48 89 c2 e8 53 fc ff ff 48 89 d0 48 83 c4 08 48 3d 01
RSP: 002b:00007ffe30172430 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 0000000000417ab1
RDX: 0000000000000000 RSI: ffffffff88e8c21e RDI: 0000000000000004
RBP: 0000000000000001 R08: ffffffff8130c47a R09: 00000000648e67d9
R10: 00007ffe30172510 R11: 0000000000000293 R12: ffffffffffffffff
R13: 000000000004decc R14: 00000000000003e8 R15: 000000000119bf8c


---
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@...glegroups.com.

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

Powered by blists - more mailing lists