public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+0338e3cdaaea6cc59e92@syzkaller.appspotmail.com>
To: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	linux-kernel@vger.kernel.org, luto@kernel.org, mingo@redhat.com,
	peterz@infradead.org, syzkaller-bugs@googlegroups.com,
	tglx@linutronix.de, x86@kernel.org
Subject: upstream test error: WARNING in flush_tlb_mm_range
Date: Wed, 05 Aug 2020 00:19:16 -0700	[thread overview]
Message-ID: <00000000000084a83605ac1c302e@google.com> (raw)

Hello,

syzbot found the following issue on:

HEAD commit:    442489c2 Merge tag 'timers-core-2020-08-04' of git://git.k..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1563e7ca900000
kernel config:  https://syzkaller.appspot.com/x/.config?x=25e437ac2202c1c3
dashboard link: https://syzkaller.appspot.com/bug?extid=0338e3cdaaea6cc59e92
compiler:       clang version 11.0.0 (https://github.com/llvm/llvm-project.git ca2dcbd030eadbf0aa9b660efe864ff08af6e18b)

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

------------[ cut here ]------------
WARNING: CPU: 1 PID: 5077 at arch/x86/mm/tlb.c:936 flush_tlb_mm_range+0x182/0x1a0 arch/x86/mm/tlb.c:946
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 5077 Comm: systemd-udevd Not tainted 5.8.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
 __dump_stack lib/dump_stack.c:77 [inline]
 dump_stack+0x16e/0x25d lib/dump_stack.c:118
 panic+0x20c/0x69a kernel/panic.c:231
 __warn+0x211/0x240 kernel/panic.c:600
 report_bug+0x153/0x1d0 lib/bug.c:198
 handle_bug+0x4d/0x90 arch/x86/kernel/traps.c:235
 exc_invalid_op+0x16/0x70 arch/x86/kernel/traps.c:255
 asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:547
RIP: 0010:flush_tlb_mm_range+0x182/0x1a0 arch/x86/mm/tlb.c:946
Code: 01 00 00 00 e8 5f 00 16 00 65 8b 05 b4 0f e0 7e 85 c0 74 0f 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 07 f0 de ff eb ea <0f> 0b 48 83 3d 84 3a ea 06 00 0f 85 5b ff ff ff 0f 0b 0f 0b 0f 0b
RSP: 0000:ffffc90000e23c08 EFLAGS: 00010246
RAX: 0000000000000000 RBX: ffff888124284cc0 RCX: ffff88812c12ce40
RDX: 00007f85bc6c4000 RSI: 0000000000000002 RDI: 0000000000000000
RBP: 00007f85bc6c4000 R08: 0000000000000000 R09: 00008881240d0a6f
R10: 0000ffffffffffff R11: 0000000000000000 R12: 0000000000000000
R13: 000000000000000c R14: 00007f85bc6c3000 R15: 0000000000000373
 flush_tlb_page arch/x86/include/asm/tlbflush.h:235 [inline]
 ptep_clear_flush+0xb3/0xd0 mm/pgtable-generic.c:97
 wp_page_copy+0x7b0/0x1360 mm/memory.c:2713
 do_wp_page+0x9de/0xd40 arch/x86/include/asm/atomic.h:95
 handle_pte_fault mm/memory.c:4243 [inline]
 __handle_mm_fault mm/memory.c:4357 [inline]
 handle_mm_fault+0x173d/0x1980 mm/memory.c:4394
 do_user_addr_fault+0x3a0/0x820 arch/x86/mm/fault.c:1295
 handle_page_fault arch/x86/mm/fault.c:1365 [inline]
 exc_page_fault+0xbf/0x210 arch/x86/mm/fault.c:1418
 asm_exc_page_fault+0x1e/0x30 arch/x86/include/asm/idtentry.h:549
RIP: 0033:0x7f85bc39c1f7
Code: 25 10 00 00 00 48 3b 15 6f 75 32 00 74 46 be 01 00 00 00 31 c0 83 3d 17 a5 32 00 00 74 0c f0 0f b1 35 4d 75 32 00 75 0b eb 23 <0f> b1 35 42 75 32 00 74 1a 48 8d 3d 39 75 32 00 48 81 ec 80 00 00
RSP: 002b:00007ffc677521c0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 00005622f70bf120 RCX: 00005622f70bf210
RDX: 00007f85bd5908c0 RSI: 0000000000000001 RDI: 00007ffc677521c0
RBP: 0000000000000001 R08: 00007f85bc6bdf00 R09: 0000000000000230
R10: b8a2bbf99842869b R11: 00007f85bc485184 R12: 00005622f58cc68a
R13: 0000000000000001 R14: 00005622f70d1260 R15: 00007ffc677523c0
Kernel Offset: disabled
Rebooting in 86400 seconds..


---
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-08-05  7:19 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=00000000000084a83605ac1c302e@google.com \
    --to=syzbot+0338e3cdaaea6cc59e92@syzkaller.appspotmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox