From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 202771] New: Malformed file name generates some issues.
Date: Tue, 05 Mar 2019 13:14:06 +0000 [thread overview]
Message-ID: <bug-202771-13602@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=202771
Bug ID: 202771
Summary: Malformed file name generates some issues.
Product: File System
Version: 2.5
Kernel Version: 4.18.6-1~bpo9+1 (Debian stretch)
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: ext4
Assignee: fs_ext4@kernel-bugs.osdl.org
Reporter: addammo@tiscali.it
Regression: No
Created attachment 281511
--> https://bugzilla.kernel.org/attachment.cgi?id=281511&action=edit
The file that causes the issue due to its name.
With the attached file I get some issues.
1) some program cannot properly recognize it, and cannot write any character
into it, such as vim.tiny and Geany.
2) Other programs such as JuffED can write into it, then I get two files. They
will always show the same content.
--
You are receiving this mail because:
You are watching the assignee of the bug.
reply other threads:[~2019-03-05 13:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-202771-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.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 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).