From: Chao Yu <yuchao0@huawei.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] kernel BUG at fs/f2fs/segment.c:2391 during xfstest generic/204
Date: Fri, 16 Aug 2019 16:37:35 +0800 [thread overview]
Message-ID: <13d9a0eb-2c5f-25c8-9ebb-16815a178d8f@huawei.com> (raw)
In-Reply-To: <20190729174140.GA169027@gmail.com>
Hi Eric,
Sorry for late reply...
I only hit ENOSPC error:
QA output created by 204
line 82: echo: write error: No space left on device
What is your mkfs/mount option?
On 2019/7/30 1:41, Eric Biggers wrote:
> On xfstest generic/204 on f2fs, I'm getting a kernel BUG.
>
> It bisects to:
>
> commit 1cb50f87e10696e8cc61fb62d0d948e11b0e6dc1
> Author: Jaegeuk Kim <jaegeuk@kernel.org>
> Date: Fri Jul 6 16:47:34 2018 -0700
>
> f2fs: do checkpoint in kill_sb
>
> Here is the BUG, on v5.3-rc2:
>
> generic/204 1s ... [10:34:22][ 6.005271] run fstests generic/204 at 2019-07-29 10:34:22
> ------------[ cut here ]------------
> kernel BUG at fs/f2fs/segment.c:2391!
> invalid opcode: 0000 [#1] SMP
> CPU: 1 PID: 111 Comm: kworker/u4:2 Not tainted 5.3.0-rc2 #4
> Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014
> Workqueue: writeback wb_workfn (flush-254:32)
> RIP: 0010:get_new_segment fs/f2fs/segment.c:2382 [inline]
> RIP: 0010:new_curseg+0x350/0x360 fs/f2fs/segment.c:2512
> Code: 8b 7b 48 44 89 ea 41 0f af f6 e8 5b cb 06 00 41 8b 97 18 0b 00 00 41 89 c2 41 0f af d6 39 d0 0f 82 97 fe ff ff e9 a7 fd ff ff <0f> 0b 45 31 e4 45 31 ed e9 47 f2
> RSP: 0018:ffffc9000045f5c8 EFLAGS: 00010246
> RAX: 0000000000000031 RBX: ffff88807b533800 RCX: 0000000000000040
> RDX: 0000000000000031 RSI: 0000000000000000 RDI: ffff88807af35b60
> RBP: ffffc9000045f618 R08: 000000000000000a R09: 0000000000000001
> R10: ffff88807b533828 R11: 0000000000000001 R12: 0000000000000000
> R13: 0000000000000001 R14: 0000000000000000 R15: ffff888078d3c000
> FS: 0000000000000000(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000055db93c6b2d8 CR3: 0000000078c43005 CR4: 0000000000760ee0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> PKRU: 55555554
> Call Trace:
> allocate_segment_by_default+0x9c/0x100 fs/f2fs/segment.c:2651
> f2fs_allocate_data_block+0x1f3/0x600 fs/f2fs/segment.c:3101
> do_write_page+0x9d/0x110 fs/f2fs/segment.c:3165
> f2fs_do_write_node_page+0x35/0xb0 fs/f2fs/segment.c:3216
> __write_node_page+0x290/0x660 fs/f2fs/node.c:1574
> f2fs_sync_node_pages+0x6e1/0x790 fs/f2fs/node.c:1843
> block_operations fs/f2fs/checkpoint.c:1225 [inline]
> f2fs_write_checkpoint+0x282/0x920 fs/f2fs/checkpoint.c:1576
> f2fs_sync_fs+0xc6/0x1b0 fs/f2fs/super.c:1116
> f2fs_balance_fs_bg+0x107/0x300 fs/f2fs/segment.c:557
> f2fs_write_node_pages+0x55/0x310 fs/f2fs/node.c:1931
> do_writepages+0x43/0xf0 mm/page-writeback.c:2342
> __writeback_single_inode+0x56/0x5b0 fs/fs-writeback.c:1364
> writeback_sb_inodes+0x253/0x580 fs/fs-writeback.c:1628
> wb_writeback+0x10f/0x480 fs/fs-writeback.c:1804
> wb_do_writeback fs/fs-writeback.c:1949 [inline]
> wb_workfn+0xa9/0x570 fs/fs-writeback.c:1990
> process_one_work+0x21c/0x5c0 kernel/workqueue.c:2269
> worker_thread+0x3a/0x3b0 kernel/workqueue.c:2415
> kthread+0x124/0x140 kernel/kthread.c:255
> ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:352
> ---[ end trace 63bbe1af16f6dd61 ]---
> RIP: 0010:get_new_segment fs/f2fs/segment.c:2382 [inline]
> RIP: 0010:new_curseg+0x350/0x360 fs/f2fs/segment.c:2512
> Code: 8b 7b 48 44 89 ea 41 0f af f6 e8 5b cb 06 00 41 8b 97 18 0b 00 00 41 89 c2 41 0f af d6 39 d0 0f 82 97 fe ff ff e9 a7 fd ff ff <0f> 0b 45 31 e4 45 31 ed e9 47 f2
> RSP: 0018:ffffc9000045f5c8 EFLAGS: 00010246
> RAX: 0000000000000031 RBX: ffff88807b533800 RCX: 0000000000000040
> RDX: 0000000000000031 RSI: 0000000000000000 RDI: ffff88807af35b60
> RBP: ffffc9000045f618 R08: 000000000000000a R09: 0000000000000001
> R10: ffff88807b533828 R11: 0000000000000001 R12: 0000000000000000
> R13: 0000000000000001 R14: 0000000000000000 R15: ffff888078d3c000
> FS: 0000000000000000(0000) GS:ffff88807fd00000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 000055db93c6b2d8 CR3: 0000000078c43005 CR4: 0000000000760ee0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> PKRU: 55555554
>
>
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
> .
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next parent reply other threads:[~2019-08-16 8:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190729174140.GA169027@gmail.com>
2019-08-16 8:37 ` Chao Yu [this message]
2019-08-18 16:03 ` [f2fs-dev] kernel BUG at fs/f2fs/segment.c:2391 during xfstest generic/204 Eric Biggers
2019-08-22 8:29 ` Chao Yu
2019-08-22 9:21 ` Chao Yu
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=13d9a0eb-2c5f-25c8-9ebb-16815a178d8f@huawei.com \
--to=yuchao0@huawei.com \
--cc=ebiggers@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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).