BUG: unable to handle kernel paging request in __dev_queue_xmit

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: b7452388 Add linux-next specific files for 20210421
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=173c9f61d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=986cb71606538211
dashboard link: https://syzkaller.appspot.com/bug?extid=ee8764967f3e55556a54
CC: [ax...@kernel.dk jus...@coraid.com linux...@vger.kernel.org linux-...@vger.kernel.org]

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+ee8764...@syzkaller.appspotmail.com

ieee802154 phy0 wpan0: encryption failed: -22
ieee802154 phy1 wpan1: encryption failed: -22
BUG: unable to handle page fault for address: ffffffff0000704e
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD bc8f067 P4D bc8f067 PUD 0
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 3258 Comm: aoe_tx0 Not tainted 5.12.0-rc8-next-20210421-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__dev_queue_xmit+0x7ce/0x2e50 net/core/dev.c:4212
Code: fa 45 84 ed 0f 85 af 0e 00 00 e8 fd df 6a fa 48 89 da 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 d0 21 00 00 <48> 83 3b 00 0f 85 3d 09 00 00 e8 d3 df 6a fa 48 8b 04 24 48 8d b8
RSP: 0018:ffffc90002bffc78 EFLAGS: 00010246

RAX: dffffc0000000000 RBX: ffffffff0000704e RCX: 0000000000000000
RDX: 1fffffffe0000e09 RSI: ffffffff87099a73 RDI: 0000000000000003
RBP: ffff88801ec7d8c0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff8709a983 R11: 0000000000000000 R12: ffff888025258000
R13: 0000000000000000 R14: 0000000000000020 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff0000704e CR3: 0000000024ecf000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
tx+0x68/0xb0 drivers/block/aoe/aoenet.c:63
kthread+0x1e7/0x3a0 drivers/block/aoe/aoecmd.c:1230
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
Modules linked in:

CR2: ffffffff0000704e
---[ end trace b8e6a0e636e0bf11 ]---
RIP: 0010:__dev_queue_xmit+0x7ce/0x2e50 net/core/dev.c:4212
Code: fa 45 84 ed 0f 85 af 0e 00 00 e8 fd df 6a fa 48 89 da 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 d0 21 00 00 <48> 83 3b 00 0f 85 3d 09 00 00 e8 d3 df 6a fa 48 8b 04 24 48 8d b8
RSP: 0018:ffffc90002bffc78 EFLAGS: 00010246

RAX: dffffc0000000000 RBX: ffffffff0000704e RCX: 0000000000000000
RDX: 1fffffffe0000e09 RSI: ffffffff87099a73 RDI: 0000000000000003
RBP: ffff88801ec7d8c0 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff8709a983 R11: 0000000000000000 R12: ffff888025258000
R13: 0000000000000000 R14: 0000000000000020 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffffff0000704e CR3: 0000000024ecf000 CR4: 00000000001506f0
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]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.