From: bugzilla-daemon@bugzilla.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: Mon, 10 Jan 2022 14:26:32 +0000 [thread overview]
Message-ID: <bug-215235-202145-cGe2bPPTxT@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215235-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215235
David Disseldorp (ddiss.dev@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ddiss.dev@gmail.com
--- Comment #4 from David Disseldorp (ddiss.dev@gmail.com) ---
(In reply to Chao Yu from comment #1)
> Thanks for the report!
>
> I've submitted a fixing patch, could you please have a try?
>
> https://lore.kernel.org/linux-f2fs-devel/20211211154059.7173-1-chao@kernel.
> org/T/#u
This fix appears to be missing from mainline. Do you still plan on submitting
it?
--
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:[~2022-01-10 14:26 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 [this message]
2022-01-11 3:41 ` bugzilla-daemon
2022-10-21 14:24 ` 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-215235-202145-cGe2bPPTxT@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.