All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+b41193cb6e40673119c1@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, syzkaller-bugs@googlegroups.com
Subject: BUG: unable to handle kernel paging request in free_swap_cache
Date: Thu, 10 Sep 2020 05:55:21 -0700	[thread overview]
Message-ID: <000000000000b7c4dd05aef51494@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    dd9fb9bb Merge tags 'auxdisplay-for-linus-v5.9-rc4', 'clan..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=164e35cd900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=bd46548257448703
dashboard link: https://syzkaller.appspot.com/bug?extid=b41193cb6e40673119c1
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+b41193cb6e40673119c1@syzkaller.appspotmail.com

BUG: unable to handle page fault for address: ffffea007777777f
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 12fff8067 P4D 12fff8067 PUD 0 
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 10690 Comm: syz-executor.2 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:compound_head include/linux/page-flags.h:182 [inline]
RIP: 0010:PageSwapCache include/linux/page-flags.h:391 [inline]
RIP: 0010:free_swap_cache+0x32/0x300 mm/swap_state.c:325
Code: 49 89 fc 55 4d 8d 6c 24 08 53 e8 49 10 c7 ff 4c 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 85 02 00 00 <4d> 8b 74 24 08 31 ff 4c 89 e5 4c 89 f3 83 e3 01 48 89 de e8 b6 0c
RSP: 0018:ffffc900088a76d0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff888000143848 RCX: ffffffff81ad73c2
RDX: 1ffffd400eeeeeef RSI: ffffffff81ad3ab7 RDI: ffffea0077777777
RBP: 0000000000000107 R08: 0000000000000000 R09: ffffea00018ec9c7
R10: 00000000000001fe R11: 0000000000000000 R12: ffffea0077777777
R13: ffffea007777777f R14: dffffc0000000000 R15: ffffc900088a7a80
FS:  0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffea007777777f CR3: 0000000214b08000 CR4: 00000000001526e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 free_pages_and_swap_cache+0x58/0x90 mm/swap_state.c:353
 tlb_batch_pages_flush mm/mmu_gather.c:49 [inline]
 tlb_flush_mmu_free mm/mmu_gather.c:242 [inline]
 tlb_flush_mmu+0xe9/0x6b0 mm/mmu_gather.c:249
 zap_pte_range mm/memory.c:1159 [inline]
 zap_pmd_range mm/memory.c:1197 [inline]
 zap_pud_range mm/memory.c:1226 [inline]
 zap_p4d_range mm/memory.c:1247 [inline]
 unmap_page_range+0x1e22/0x2b20 mm/memory.c:1268
 unmap_single_vma+0x198/0x300 mm/memory.c:1313
 unmap_vmas+0x168/0x2e0 mm/memory.c:1345
 exit_mmap+0x2b1/0x530 mm/mmap.c:3183
 __mmput+0x122/0x470 kernel/fork.c:1076
 mmput+0x53/0x60 kernel/fork.c:1097
 exit_mm kernel/exit.c:483 [inline]
 do_exit+0xa8b/0x29f0 kernel/exit.c:793
 do_group_exit+0x125/0x310 kernel/exit.c:903
 get_signal+0x428/0x1f00 kernel/signal.c:2757
 arch_do_signal+0x82/0x2520 arch/x86/kernel/signal.c:811
 exit_to_user_mode_loop kernel/entry/common.c:136 [inline]
 exit_to_user_mode_prepare+0x1ae/0x200 kernel/entry/common.c:167
 syscall_exit_to_user_mode+0x7e/0x2e0 kernel/entry/common.c:242
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5b9
Code: Bad RIP value.
RSP: 002b:00007f77c0d90cf8 EFLAGS: 00000246 ORIG_RAX: 00000000000000ca
RAX: 0000000000000001 RBX: 000000000118cf48 RCX: 000000000045d5b9
RDX: 00000000000f4240 RSI: 0000000000000081 RDI: 000000000118cf4c
RBP: 000000000118cf40 R08: 000000000000000e R09: 0000000000000000
R10: 0000000000000003 R11: 0000000000000246 R12: 000000000118cf4c
R13: 000000000169fb6f R14: 00007f77c0d919c0 R15: 000000000118cf4c
Modules linked in:
CR2: ffffea007777777f
---[ end trace 07566fd2f7a76eaf ]---
RIP: 0010:compound_head include/linux/page-flags.h:182 [inline]
RIP: 0010:PageSwapCache include/linux/page-flags.h:391 [inline]
RIP: 0010:free_swap_cache+0x32/0x300 mm/swap_state.c:325
Code: 49 89 fc 55 4d 8d 6c 24 08 53 e8 49 10 c7 ff 4c 89 ea 48 b8 00 00 00 00 00 fc ff df 48 c1 ea 03 80 3c 02 00 0f 85 85 02 00 00 <4d> 8b 74 24 08 31 ff 4c 89 e5 4c 89 f3 83 e3 01 48 89 de e8 b6 0c
RSP: 0018:ffffc900088a76d0 EFLAGS: 00010246
RAX: dffffc0000000000 RBX: ffff888000143848 RCX: ffffffff81ad73c2
RDX: 1ffffd400eeeeeef RSI: ffffffff81ad3ab7 RDI: ffffea0077777777
RBP: 0000000000000107 R08: 0000000000000000 R09: ffffea00018ec9c7
R10: 00000000000001fe R11: 0000000000000000 R12: ffffea0077777777
R13: ffffea007777777f R14: dffffc0000000000 R15: ffffc900088a7a80
FS:  0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffea007777777f CR3: 0000000214b08000 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 syzkaller@googlegroups.com.

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

             reply	other threads:[~2020-09-10 21:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 12:55 syzbot [this message]
2020-09-10 12:55 ` BUG: unable to handle kernel paging request in free_swap_cache syzbot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=000000000000b7c4dd05aef51494@google.com \
    --to=syzbot+b41193cb6e40673119c1@syzkaller.appspotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=syzkaller-bugs@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.