From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 215914] New: kernel hangs after mounting the image
Date: Thu, 28 Apr 2022 16:20:12 +0000 [thread overview]
Message-ID: <bug-215914-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215914
Bug ID: 215914
Summary: kernel hangs after mounting the image
Product: File System
Version: 2.5
Kernel Version: 5.17
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
I have mounted a F2FS image with several mount options. When I try to perform
any file operations on the mount point, the kernel hangs. The process even
cannot be killed. I am wondering whether there is a bug in the file system?
The image is provided at
(https://drive.google.com/file/d/1EwbxTExo7lsNgGKRpK-CP3ccIkFJe4kg/view?usp=sharing).
This issue can be reproduced by running the following commands:
losetup /dev/loop0 case.img
mount -o
"disable_ext_identify,inline_data,nobarrier,extent_cache,grpquota,fsync_mode=nobarrier,test_dummy_encryption"
/dev/loop0 /mnt/test/
cd /mnt/test/
touch test
--
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-04-28 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 16:20 bugzilla-daemon [this message]
2022-04-30 4:53 ` [f2fs-dev] [Bug 215914] kernel hangs after mounting the image bugzilla-daemon
2022-04-30 7:33 ` 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-215914-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 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.