Re: BUG: unable to handle kernel NULL pointer dereference in loop_rw_iter

2020-08-10 Thread Jens Axboe
On 8/10/20 9:46 AM, syzbot wrote:
> Hello,
> 
> syzbot found the following issue on:
> 
> HEAD commit:9420f1ce Merge tag 'pinctrl-v5.9-1' of git://git.kernel.or..
> git tree:   upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=13662f6290
> kernel config:  https://syzkaller.appspot.com/x/.config?x=72cf85e4237850c8
> dashboard link: https://syzkaller.appspot.com/bug?extid=1abbd16e49910f6bbe45
> compiler:   gcc (GCC) 10.1.0-syz 20200507
> syz repro:  https://syzkaller.appspot.com/x/repro.syz?x=1592900690
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15e196aa90
> 
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+1abbd16e49910f6bb...@syzkaller.appspotmail.com

Already fixed, just not upstream yet:

https://git.kernel.dk/cgit/linux-block/commit/?h=io_uring-5.9=2dd2111d0d383df104b144e0d1f6b5a00cb7cd88

-- 
Jens Axboe



BUG: unable to handle kernel NULL pointer dereference in loop_rw_iter

2020-08-10 Thread syzbot
Hello,

syzbot found the following issue on:

HEAD commit:9420f1ce Merge tag 'pinctrl-v5.9-1' of git://git.kernel.or..
git tree:   upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13662f6290
kernel config:  https://syzkaller.appspot.com/x/.config?x=72cf85e4237850c8
dashboard link: https://syzkaller.appspot.com/bug?extid=1abbd16e49910f6bbe45
compiler:   gcc (GCC) 10.1.0-syz 20200507
syz repro:  https://syzkaller.appspot.com/x/repro.syz?x=1592900690
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15e196aa90

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

BUG: kernel NULL pointer dereference, address: 
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD a652e067 P4D a652e067 PUD a652f067 PMD 0 
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 7461 Comm: io_wqe_worker-0 Not tainted 5.8.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 
01/01/2011
RIP: 0010:0x0
Code: Bad RIP value.
RSP: 0018:c9000804f910 EFLAGS: 00010246
RAX: 110b0b9b RBX: dc00 RCX: 88808962e1c8
RDX: 003c RSI: 2740 RDI: 88809fb2dcc0
RBP: 2740 R08: c9000804fa28 R09: 8880a7639c0f
R10:  R11:  R12: c9000804fa28
R13: 88585cc0 R14: 003c R15: 0001
FS:  () GS:8880ae70() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: ffd6 CR3: 8e2a7000 CR4: 001506e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400
Call Trace:
 loop_rw_iter.part.0+0x26e/0x450 fs/io_uring.c:2850
 loop_rw_iter fs/io_uring.c:2829 [inline]
 io_write+0x6a2/0x7a0 fs/io_uring.c:3190
 io_issue_sqe+0x1b0/0x60d0 fs/io_uring.c:5530
 io_wq_submit_work+0x183/0x3d0 fs/io_uring.c:5775
 io_worker_handle_work+0xa45/0x13f0 fs/io-wq.c:527
 io_wqe_worker+0xbf0/0x10e0 fs/io-wq.c:569
 kthread+0x3b5/0x4a0 kernel/kthread.c:292
 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
Modules linked in:
CR2: 
---[ end trace 97e511c5a98da2fe ]---
RIP: 0010:0x0
Code: Bad RIP value.
RSP: 0018:c9000804f910 EFLAGS: 00010246
RAX: 110b0b9b RBX: dc00 RCX: 88808962e1c8
RDX: 003c RSI: 2740 RDI: 88809fb2dcc0
RBP: 2740 R08: c9000804fa28 R09: 8880a7639c0f
R10:  R11:  R12: c9000804fa28
R13: 88585cc0 R14: 003c R15: 0001
FS:  () GS:8880ae70() knlGS:
CS:  0010 DS:  ES:  CR0: 80050033
CR2: 7f84c3b15028 CR3: 8e2a7000 CR4: 001506e0
DR0:  DR1:  DR2: 
DR3:  DR6: fffe0ff0 DR7: 0400


---
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 syzkal...@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