From: Eric Biggers <ebiggers3@gmail.com>
To: syzbot
<bot+137b5b6092cc658adb927eb6f016a5721e040e17@syzkaller.appspotmail.com>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com, viro@zeniv.linux.org.uk
Subject: Re: WARNING in mark_buffer_dirty
Date: Tue, 12 Dec 2017 12:56:29 -0800 [thread overview]
Message-ID: <20171212205629.GB185376@gmail.com> (raw)
In-Reply-To: <001a114740a0b5fa37055e14cf3b@google.com>
On Wed, Nov 15, 2017 at 11:46:00PM -0800, syzbot wrote:
> WARNING: CPU: 3 PID: 13366 at fs/buffer.c:1108
> mark_buffer_dirty+0x48b/0x5d0 fs/buffer.c:1108
> Kernel panic - not syncing: panic_on_warn set ...
>
> hub 1-0:1.0: activate --> -22
> CPU: 3 PID: 13366 Comm: syzkaller183798 Not tainted
> 4.14.0-rc8-next-20171109+ #11
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011
> Call Trace:
> __dump_stack lib/dump_stack.c:17 [inline]
> dump_stack+0x194/0x257 lib/dump_stack.c:53
> panic+0x1e4/0x41c kernel/panic.c:183
> __warn+0x1c4/0x1e0 kernel/panic.c:546
> report_bug+0x211/0x2d0 lib/bug.c:184
> fixup_bug+0x40/0x90 arch/x86/kernel/traps.c:176
> do_trap_no_signal arch/x86/kernel/traps.c:210 [inline]
> do_trap+0x260/0x390 arch/x86/kernel/traps.c:259
> do_error_trap+0x120/0x390 arch/x86/kernel/traps.c:296
> hub 1-0:1.0: activate --> -22
> do_invalid_op+0x1b/0x20 arch/x86/kernel/traps.c:309
> invalid_op+0x18/0x20 arch/x86/entry/entry_64.S:926
> RIP: 0010:mark_buffer_dirty+0x48b/0x5d0 fs/buffer.c:1108
> RSP: 0018:ffff88007ab27188 EFLAGS: 00010293
> RAX: ffff880079fa6500 RBX: ffff88007a727d20 RCX: ffffffff81bbfe5b
> RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88007a727d20
> RBP: ffff88007ab27298 R08: 0000000000000200 R09: ffffea0001e53580
> R10: 0000000000000040 R11: ffffed000f29ac3f R12: 1ffff1000f564e32
> R13: dffffc0000000000 R14: ffff88007ab27270 R15: 0000000000000000
> hub 1-0:1.0: activate --> -22
> __block_commit_write.isra.32+0x13b/0x2f0 fs/buffer.c:2060
> block_write_end+0x99/0x1c0 fs/buffer.c:2138
> blkdev_write_end+0xc3/0x280 fs/block_dev.c:593
> generic_perform_write+0x3a4/0x600 mm/filemap.c:3149
> hub 1-0:1.0: activate --> -22
> __generic_file_write_iter+0x366/0x5b0 mm/filemap.c:3263
> blkdev_write_iter+0x207/0x3e0 fs/block_dev.c:1893
> call_write_iter include/linux/fs.h:1772 [inline]
> do_iter_readv_writev+0x531/0x7f0 fs/read_write.c:653
> do_iter_write+0x15a/0x540 fs/read_write.c:932
> vfs_iter_write+0x77/0xb0 fs/read_write.c:945
> iter_file_splice_write+0x7db/0xf30 fs/splice.c:749
> do_splice_from fs/splice.c:851 [inline]
> direct_splice_actor+0x125/0x180 fs/splice.c:1018
> splice_direct_to_actor+0x2c1/0x820 fs/splice.c:973
> hub 1-0:1.0: activate --> -22
> do_splice_direct+0x2a7/0x3d0 fs/splice.c:1061
> do_sendfile+0x5d5/0xe90 fs/read_write.c:1413
> SYSC_sendfile64 fs/read_write.c:1468 [inline]
> SyS_sendfile64+0xbd/0x160 fs/read_write.c:1460
> entry_SYSCALL_64_fastpath+0x1f/0x96
Still happens on latest Linus tree as of today, though it takes a little while
(~30 seconds) for the C reproducer to trigger the WARN.
next parent reply other threads:[~2017-12-12 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001a114740a0b5fa37055e14cf3b@google.com>
2017-12-12 20:56 ` Eric Biggers [this message]
2024-03-16 4:29 WARNING in mark_buffer_dirty cheung wall
2024-03-16 4:54 ` Matthew Wilcox
2024-03-18 10:12 ` Jan Kara
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=20171212205629.GB185376@gmail.com \
--to=ebiggers3@gmail.com \
--cc=bot+137b5b6092cc658adb927eb6f016a5721e040e17@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;
as well as URLs for NNTP newsgroup(s).