From: Daniel Vacek <neelx@suse.com>
To: dsterba@suse.cz
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, Josef Bacik <josef@toxicpanda.com>,
Sweet Tea Dorminy <sweettea-kernel@dorminy.me>
Subject: Re: [PATCH 8/8] btrfs-progs: string-utils: do not escape space while printing
Date: Sat, 18 Oct 2025 19:50:40 +0200 [thread overview]
Message-ID: <CAPjX3Ffk5Wdbw5jUncQQKahDTA9_+OXpcUg3Hc4ifFCqdOxRHA@mail.gmail.com> (raw)
In-Reply-To: <20251017164314.GL13776@twin.jikos.cz>
On Fri, 17 Oct 2025 at 18:43, David Sterba <dsterba@suse.cz> wrote:
>
> On Wed, Oct 15, 2025 at 02:11:56PM +0200, Daniel Vacek wrote:
> > Space is a valid printable character in C. On the other hand
> > string "\ " in fact results in an unknown escape sequence.
>
> The space is escaped because the helper is used to print stream dump
> or tree dump where space is the separator, so this patch would break it.
> Unless there's another reason than esaped space is not valid in C then
> we can't do that.
The reason is fstests are parsing the output of dump-tree and failing
on any space in the encrypted filename. That's how I found the bug.
Namely it's the generic/582 checking the encrypted filenames, well the
btrfs part of the test as I implemented it. It's the
get_ciphertext_filename() function in common/encrypt. I went through
several iterations but I could not come up with any better solution.
Hints are welcome here.
Thinking about it again, this is also missing correctly escaping %
into %% which I mangled in fstests. I should have really done it here.
next prev parent reply other threads:[~2025-10-18 17:50 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 12:11 [PATCH 0/8] btrfs-progs: fscrypt updates Daniel Vacek
2025-10-15 12:11 ` [PATCH 1/8] btrfs-progs: check: fix max inline extent size Daniel Vacek
2025-10-15 12:11 ` [PATCH 2/8] btrfs-progs: add new FEATURE_INCOMPAT_ENCRYPT flag Daniel Vacek
2025-10-24 21:16 ` David Sterba
2025-10-15 12:11 ` [PATCH 3/8] btrfs-progs: start tracking extent encryption context info Daniel Vacek
2025-10-24 21:29 ` David Sterba
2025-10-24 22:43 ` Qu Wenruo
2025-11-05 8:28 ` Daniel Vacek
2025-11-05 8:22 ` Daniel Vacek
2025-11-05 8:27 ` Daniel Vacek
2025-11-05 9:12 ` Qu Wenruo
2025-11-05 10:55 ` Daniel Vacek
2025-11-26 14:11 ` David Sterba
2025-11-27 8:40 ` Daniel Vacek
2025-10-15 12:11 ` [PATCH 4/8] btrfs-progs: add inode encryption contexts Daniel Vacek
2025-10-15 12:11 ` [PATCH 5/8] btrfs-progs: interpret encrypted file extents Daniel Vacek
2025-11-02 22:26 ` Qu Wenruo
2025-11-03 9:57 ` Daniel Vacek
2025-11-05 7:46 ` Daniel Vacek
2025-10-15 12:11 ` [PATCH 6/8] btrfs-progs: handle fscrypt context items Daniel Vacek
2025-10-15 12:11 ` [PATCH 7/8] btrfs-progs: check: update inline extent length checking Daniel Vacek
2025-10-15 12:11 ` [PATCH 8/8] btrfs-progs: string-utils: do not escape space while printing Daniel Vacek
2025-10-17 16:43 ` David Sterba
2025-10-18 17:50 ` Daniel Vacek [this message]
2025-10-15 21:10 ` [PATCH 0/8] btrfs-progs: fscrypt updates Qu Wenruo
2025-10-15 21:19 ` Daniel Vacek
2025-10-15 21:20 ` Qu Wenruo
2025-10-16 15:16 ` Johannes Thumshirn
2025-10-17 20:54 ` Mark Harmstone
2025-10-24 21:10 ` David Sterba
2025-10-17 16:45 ` David Sterba
2025-10-18 18:01 ` Daniel Vacek
2025-11-04 14:56 ` David Sterba
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=CAPjX3Ffk5Wdbw5jUncQQKahDTA9_+OXpcUg3Hc4ifFCqdOxRHA@mail.gmail.com \
--to=neelx@suse.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sweettea-kernel@dorminy.me \
/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).