From: syzbot <syzbot+7d5c3e0439dc861b68fc@syzkaller.appspotmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: WARNING in mark_buffer_dirty (3)
Date: Sun, 14 Feb 2021 08:48:16 -0800 [thread overview]
Message-ID: <000000000000c2d2c005bb4ea200@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: e0756cfc Merge tag 'trace-v5.11-rc7' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14d0f814d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a53fd47f16f22f8c
dashboard link: https://syzkaller.appspot.com/bug?extid=7d5c3e0439dc861b68fc
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+7d5c3e0439dc861b68fc@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 3 PID: 5031 at fs/buffer.c:1113 mark_buffer_dirty+0x488/0x5d0 fs/buffer.c:1113
Modules linked in:
CPU: 3 PID: 5031 Comm: jbd2/sda1-8 Not tainted 5.11.0-rc7-syzkaller #0
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.14.0-2 04/01/2014
RIP: 0010:mark_buffer_dirty+0x488/0x5d0 fs/buffer.c:1113
Code: c1 ea 03 80 3c 02 00 0f 85 52 01 00 00 48 8b 3b be 04 00 00 00 e8 b8 ac fc ff 5b 5d 41 5c 41 5d e9 2d 9d a2 ff e8 28 9d a2 ff <0f> 0b e9 bf fb ff ff e8 1c 9d a2 ff 0f 0b e9 e3 fb ff ff e8 10 9d
RSP: 0018:ffffc9000df3fa20 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff888017d0b698 RCX: 0000000000000000
RDX: ffff888014b420c0 RSI: ffffffff81d039a8 RDI: 0000000000000003
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff81d03565 R11: 0000000000000000 R12: ffff888017d0b698
R13: ffff88801ad9e980 R14: ffff888022e8ea50 R15: ffff888022e8ea50
FS: 0000000000000000(0000) GS:ffff88802cd00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000557ba7d6b967 CR3: 000000000ba8e000 CR4: 0000000000150ee0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
__jbd2_journal_temp_unlink_buffer+0x3ba/0x500 fs/jbd2/transaction.c:2021
__jbd2_journal_unfile_buffer+0x60/0xb0 fs/jbd2/transaction.c:2035
__jbd2_journal_refile_buffer+0x3d2/0x4a0 fs/jbd2/transaction.c:2581
jbd2_journal_commit_transaction+0x43ef/0x6b90 fs/jbd2/commit.c:1084
kjournald2+0x1d0/0x930 fs/jbd2/journal.c:213
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296
---
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:[~2021-02-14 16:49 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=000000000000c2d2c005bb4ea200@google.com \
--to=syzbot+7d5c3e0439dc861b68fc@syzkaller.appspotmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=viro@zeniv.linux.org.uk \
/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