kernel BUG at drivers/dma-buf/dma-buf.c:LINE!

32 views
Skip to first unread message

syzbot

unread,
Mar 30, 2020, 8:56:14 PM3/30/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 54b4fa6d Linux 4.19.113
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1765cedbe00000
kernel config: https://syzkaller.appspot.com/x/.config?x=7b1a0bc5526ebc49
dashboard link: https://syzkaller.appspot.com/bug?extid=ff5fdc7631dd7c04c65b
compiler: gcc (GCC) 9.0.0 20181231 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1142cb4de00000

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

IPv6: ADDRCONF(NETDEV_CHANGE): veth1_to_batadv: link becomes ready
audit: type=1400 audit(1585616012.898:41): avc: denied { associate } for pid=8016 comm="syz-executor.0" name="syz0" scontext=unconfined_u:object_r:unlabeled_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=filesystem permissive=1
------------[ cut here ]------------
kernel BUG at drivers/dma-buf/dma-buf.c:68!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 8051 Comm: syz-executor.0 Not tainted 4.19.113-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:dma_buf_release+0x345/0x630 drivers/dma-buf/dma-buf.c:68
Code: e4 e8 af 63 49 fd 48 89 ef e8 f7 7b 88 fd e8 72 da 52 fd 44 89 e0 48 83 c4 10 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 5b da 52 fd <0f> 0b e8 54 da 52 fd e8 ff 91 40 fd 48 8d bd 38 02 00 00 48 b8 00
RSP: 0018:ffff88807e84fdf8 EFLAGS: 00010293
RAX: ffff8880988de6c0 RBX: 0000000000000004 RCX: ffffffff8414c5ec
RDX: 0000000000000000 RSI: ffffffff8414c845 RDI: 0000000000000005
RBP: ffff8880980e8d80 R08: ffff8880988de6c0 R09: 0000000000000000
R10: ffff88807e84fe40 R11: 0000000000000000 R12: ffff888092eb13bc
R13: ffff888092eb1368 R14: ffffffff8414c500 R15: ffff88821b6b6820
FS: 0000000001555940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff0b6590db8 CR3: 00000000a0188000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__fput+0x2cd/0x890 fs/file_table.c:278
task_work_run+0x13f/0x1b0 kernel/task_work.c:113
tracehook_notify_resume include/linux/tracehook.h:193 [inline]
exit_to_usermode_loop+0x25a/0x2b0 arch/x86/entry/common.c:167
prepare_exit_to_usermode arch/x86/entry/common.c:198 [inline]
syscall_return_slowpath arch/x86/entry/common.c:271 [inline]
do_syscall_64+0x538/0x620 arch/x86/entry/common.c:296
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x4163e1
Code: 75 14 b8 03 00 00 00 0f 05 48 3d 01 f0 ff ff 0f 83 04 1b 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:00007ffd79643c40 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 00000000004163e1
RDX: 0000000000000000 RSI: 0000000000000081 RDI: 0000000000000007
RBP: 0000000000000000 R08: 0000000000000000 R09: 01ffffffffffffff
R10: 00000000007708c0 R11: 0000000000000293 R12: 000000000076bf00
R13: 00000000007708d0 R14: 0000000000000000 R15: 000000000076bf0c
Modules linked in:
---[ end trace 5b687ef3a3f54b29 ]---
RIP: 0010:dma_buf_release+0x345/0x630 drivers/dma-buf/dma-buf.c:68
Code: e4 e8 af 63 49 fd 48 89 ef e8 f7 7b 88 fd e8 72 da 52 fd 44 89 e0 48 83 c4 10 5b 5d 41 5c 41 5d 41 5e 41 5f c3 e8 5b da 52 fd <0f> 0b e8 54 da 52 fd e8 ff 91 40 fd 48 8d bd 38 02 00 00 48 b8 00
RSP: 0018:ffff88807e84fdf8 EFLAGS: 00010293
RAX: ffff8880988de6c0 RBX: 0000000000000004 RCX: ffffffff8414c5ec
RDX: 0000000000000000 RSI: ffffffff8414c845 RDI: 0000000000000005
RBP: ffff8880980e8d80 R08: ffff8880988de6c0 R09: 0000000000000000
R10: ffff88807e84fe40 R11: 0000000000000000 R12: ffff888092eb13bc
R13: ffff888092eb1368 R14: ffffffff8414c500 R15: ffff88821b6b6820
FS: 0000000001555940(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ff0b6590db8 CR3: 00000000a0188000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This bug 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 bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
syzbot can test patches for this bug, for details see:
https://goo.gl/tpsmEJ#testing-patches

syzbot

unread,
Aug 25, 2021, 7:26:12 PM8/25/21
to syzkaller...@googlegroups.com
syzbot suspects this issue was fixed by commit:

commit 020a44cc54d65e673a13195e96fc0addbfd3a601
Author: Charles Baylis <cb-k...@fishzet.co.uk>
Date: Fri Jul 16 16:43:12 2021 +0000

drm: Return -ENOTTY for non-drm ioctls

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=15466a59300000
start commit: 54b4fa6d3955 Linux 4.19.113
git tree: linux-4.19.y
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1142cb4de00000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: drm: Return -ENOTTY for non-drm ioctls

For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Reply all
Reply to author
Forward
0 new messages