From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 215935] New: kernel hangs when invoking system calls
Date: Tue, 03 May 2022 05:08:12 +0000 [thread overview]
Message-ID: <bug-215935-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215935
Bug ID: 215935
Summary: kernel hangs when invoking system calls
Product: File System
Version: 2.5
Kernel Version: 5.18.0-rc2
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: f2fs
Assignee: filesystem_f2fs@kernel-bugs.kernel.org
Reporter: yanming@tju.edu.cn
Regression: No
Created attachment 300870
--> https://bugzilla.kernel.org/attachment.cgi?id=300870&action=edit
case.c
I'd mounted a F2FS image with several mount options. When I was invoking file
operations on the mount point, the kernel hangs, and the process cannot be
killed.
The file operations are in case.c, and the image is provided at
(https://drive.google.com/file/d/1YchwhB5R5ToURLSFy20rQc0wDOvRCltP/view?usp=sharing).
This issue can be reproduced by running the following commands:
losetup /dev/loop0 case.img
mount -o
"disable_roll_forward,nouser_xattr,noacl,active_logs=6,disable_ext_identify,inline_dentry,flush_merge,nobarrier,fastboot,data_flush,alloc_mode=reuse,fsync_mode=posix,test_dummy_encryption"
/dev/loop0 /mnt/test/
gcc -o case case.c
./case
--
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 reply other threads:[~2022-05-03 5:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 5:08 bugzilla-daemon [this message]
2022-05-03 16:41 ` [f2fs-dev] [Bug 215935] kernel hangs when invoking system calls bugzilla-daemon
2022-05-05 3:45 ` 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-215935-202145@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).