From: bugzilla-daemon@kernel.org
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 215235] page fault in f2fs_setxattr() when mount and operate on corrupted image
Date: Fri, 21 Oct 2022 14:24:29 +0000 [thread overview]
Message-ID: <bug-215235-202145-TDufUDFPf1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215235-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215235
alexwriter (alexwriter2003@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alexwriter2003@gmail.com
--- Comment #6 from alexwriter (alexwriter2003@gmail.com) ---
Re:
- Overview
page fault in f2fs_setxattr(https://stemhave.com/programming-help.html) when
mount and operate on corrupted image
- Reproduce
tested on kernel 5.16-rc3, 5.15.X under root
# unzip tmp7.zip
#./single.sh f2fs 7
Sometimes need to run the script several times
---------------------------------
Thaks for fix this...
--
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
prev parent reply other threads:[~2022-10-21 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 5:34 [f2fs-dev] [Bug 215235] New: page fault in f2fs_setxattr() when mount and operate on corrupted image bugzilla-daemon
2021-12-11 15:43 ` [f2fs-dev] [Bug 215235] " bugzilla-daemon
2021-12-11 16:53 ` bugzilla-daemon
2021-12-12 4:06 ` bugzilla-daemon
2022-01-10 14:26 ` bugzilla-daemon
2022-01-11 3:41 ` bugzilla-daemon
2022-10-21 14:24 ` bugzilla-daemon [this message]
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-215235-202145-TDufUDFPf1@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).