From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 215709] New: kernel deadlocks while mounting the image
Date: Mon, 21 Mar 2022 10:54:32 +0000 [thread overview]
Message-ID: <bug-215709-202145@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215709
Bug ID: 215709
Summary: kernel deadlocks while mounting the image
Product: File System
Version: 2.5
Kernel Version: 5.15.4
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 created an image with mkfs.f2fs, and modified some of the metadata of
the image. Unfortunately, when I tried to mount the image with a loop device,
the kernel deadlocked. I have attempted many ways to stop the mount process,
even executed a 'kill' command, but they are failed, only what I can do is to
reboot the system. Can anyone tell me why the kernel deadlocked, and how can I
fix this problem?
I have upload the image to the Google Drive
(https://drive.google.com/file/d/1DBwKP0-MpkD3eHPTluz3KPcxbdZAw06t/view?usp=sharing).
Looking forward to getting a reply :)
--
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-03-21 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 10:54 bugzilla-daemon [this message]
2022-03-21 15:26 ` [f2fs-dev] [Bug 215709] kernel deadlocks while mounting the image bugzilla-daemon
2022-03-22 4:01 ` bugzilla-daemon
2022-03-25 22:18 ` 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-215709-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.