All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+5671b8bcd5178fe56c23@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [dri?] [reiserfs?] WARNING: bad unlock balance in vkms_vblank_simulate
Date: Mon, 14 Aug 2023 06:12:33 -0700	[thread overview]
Message-ID: <000000000000c6570d0602e1d030@google.com> (raw)
In-Reply-To: <20230814125546.1492-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
BUG: unable to handle kernel paging request in corrupted

BUG: unable to handle page fault for address: 000000000000ff01
#PF: supervisor instruction fetch in kernel mode
#PF: error_code(0x0010) - not-present page
PGD 68064067 P4D 68064067 PUD 6806d067 PMD 0 
Oops: 0010 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 5037 Comm: kworker/1:3 Not tainted 6.5.0-rc5-next-20230808-syzkaller-dirty #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
Workqueue:  0x0 (events)
RIP: 0010:0xff01
Code: Unable to access opcode bytes at 0xfed7.
RSP: 0018:ffffc90003b2fc60 EFLAGS: 00010086
RAX: ffff888024685940 RBX: 000000000000ff01 RCX: 0000000000000000
RDX: ffff888021963b80 RSI: ffffffff812d721d RDI: 0000000000000007
RBP: 0000000100040020 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000100040020
R13: 000000000000ff01 R14: 0000000100040020 R15: 000000000000ff01
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000ff01 CR3: 000000001ef98000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 </TASK>
Modules linked in:
CR2: 000000000000ff01
---[ end trace 0000000000000000 ]---
RIP: 0010:0xff01
Code: Unable to access opcode bytes at 0xfed7.
RSP: 0018:ffffc90003b2fc60 EFLAGS: 00010086

RAX: ffff888024685940 RBX: 000000000000ff01 RCX: 0000000000000000
RDX: ffff888021963b80 RSI: ffffffff812d721d RDI: 0000000000000007
RBP: 0000000100040020 R08: 0000000000000007 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000100040020
R13: 000000000000ff01 R14: 0000000100040020 R15: 000000000000ff01
FS:  0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000000000000ff01 CR3: 000000001ef98000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


Tested on:

commit:         71cd4fc4 Add linux-next specific files for 20230808
git tree:       https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
console output: https://syzkaller.appspot.com/x/log.txt?x=166b9763a80000
kernel config:  https://syzkaller.appspot.com/x/.config?x=e36b5ba725f7349d
dashboard link: https://syzkaller.appspot.com/bug?extid=5671b8bcd5178fe56c23
compiler:       gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch:          https://syzkaller.appspot.com/x/patch.diff?x=10060e27a80000


       reply	other threads:[~2023-08-14 13:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230814125546.1492-1-hdanton@sina.com>
2023-08-14 13:12 ` syzbot [this message]
     [not found] <20230814111358.1427-1-hdanton@sina.com>
2023-08-14 12:02 ` [syzbot] [dri?] [reiserfs?] WARNING: bad unlock balance in vkms_vblank_simulate syzbot
2023-08-13  7:24 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=000000000000c6570d0602e1d030@google.com \
    --to=syzbot+5671b8bcd5178fe56c23@syzkaller.appspotmail.com \
    --cc=hdanton@sina.com \
    --cc=linux-kernel@vger.kernel.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.