From: bugzilla-daemon@bugzilla.kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 215293] F2FS: kernel bug at fs/f2fs/segment.c:2543
Date: Sat, 11 Dec 2021 04:55:32 +0000 [thread overview]
Message-ID: <bug-215293-202145-lo0fGDY2wE@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215293-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215293
--- Comment #4 from bughunter (yanming@tju.edu.cn) ---
I have written a script to facilitate reproduction, which have been compiled
into a binary file called "a". And you can simply reproduce the bug by running
the folloing scripts:
dd if=/dev/zero of=f2fs.img bs=1M count=1051
mkfs.f2fs -a 0 -o 14 -t 1 -z 4 -q f2fs.img
losetup /dev/loop10 f2fs.img
./a f2fs /dev/loop10 /root/mnt
The file operations and mount operations are shown in file "a.c", which can not
be compiled directly :( . but you can see the corresponding operations. As to
the kernel config, I only added the following configs:
CONFIG_KASAN=y
CONFIG_KASAN_INLINE=y
Hope this can be helpful to you.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-12-11 4:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 14:03 [f2fs-dev] [Bug 215293] New: F2FS: kernel bug at fs/f2fs/segment.c:2543 bugzilla-daemon
2021-12-10 14:41 ` [f2fs-dev] [Bug 215293] " bugzilla-daemon
2021-12-11 4:54 ` bugzilla-daemon
2021-12-11 4:55 ` bugzilla-daemon
2021-12-11 4:55 ` bugzilla-daemon [this message]
2021-12-11 13:38 ` bugzilla-daemon
2021-12-12 3:41 ` bugzilla-daemon
2021-12-12 4:02 ` bugzilla-daemon
2021-12-12 4:04 ` bugzilla-daemon
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=bug-215293-202145-lo0fGDY2wE@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 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.