From: bugzilla-daemon--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [Bug 219586] Unable to find file after unicode change
Date: Thu, 12 Dec 2024 15:25:27 +0000 [thread overview]
Message-ID: <bug-219586-202145-3ER8J0qwQV@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219586-202145@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219586
--- Comment #5 from Chao Yu (chao@kernel.org) ---
(In reply to HanQi from comment #0)
> Hi everybody,
> The f2fs filesystem is unable to read some files with special characters,
> such as ❤️, after the kernel was updated with the following patch:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/
> ?id=18b5f47e7da46d3a0d7331e48befcaf151ed2ddf
Hi HanQi, I guess you can report this bug to Gabriel Krisman Bertazi
<krisman@kernel.org>?
Thanks,
--
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:[~2024-12-12 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 6:58 [f2fs-dev] [Bug 219586] New: Unable to find file after unicode change bugzilla-daemon--- via Linux-f2fs-devel
2024-12-10 15:47 ` [f2fs-dev] [Bug 219586] " bugzilla-daemon--- via Linux-f2fs-devel
2024-12-11 0:08 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-11 2:11 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-11 4:13 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-12 8:35 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-12 8:39 ` bugzilla-daemon--- via Linux-f2fs-devel
2024-12-12 15:25 ` bugzilla-daemon--- via Linux-f2fs-devel [this message]
2024-12-13 1:32 ` bugzilla-daemon--- via Linux-f2fs-devel
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-219586-202145-3ER8J0qwQV@https.bugzilla.kernel.org/ \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=bugzilla-daemon@kernel.org \
/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.