From: Miklos Szeredi <miklos@szeredi.hu>
To: Christian Brauner <brauner@kernel.org>
Cc: Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org,
Karel Zak <kzak@redhat.com>,
Christian Brauner <christian@brauner.io>,
Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH] statmount: add flag to retrieve unescaped options
Date: Thu, 14 Nov 2024 15:53:44 +0100 [thread overview]
Message-ID: <CAJfpegtLiOjbtP4np-WjJ_oyC-u3FwZ4BWQxGkSSmWxurBOQdA@mail.gmail.com> (raw)
In-Reply-To: <20241113-wandmalerei-haben-9b19b61e5118@brauner>
On Wed, 13 Nov 2024 at 17:31, Christian Brauner <brauner@kernel.org> wrote:
> Please take a look at the top of #vfs.misc and tell me whether this is
> ok with you.
One more thing I'd do is:
- if (seq->count == start)
+ if (seq->count <= start + 1)
This would handle the (broken) case of just a single comma in the
options. So it's not a bug fix per-se, but would make it clear that
the loop will run at least once, and so the seq->count calculation at
the end won't be skewed.
The buf_start calculation could also be moved further down before the
loop, where it's actually used.
I don't find the variable naming much better, how about taking the
naming from string_unescape:
opt_start -> src - pointer to escaped string
buf_start -> dst - pointer to de-escaped string
The others make sense.
Thanks,
Miklos
next prev parent reply other threads:[~2024-11-14 14:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 10:10 [PATCH] statmount: add flag to retrieve unescaped options Miklos Szeredi
2024-11-12 12:20 ` Jeff Layton
2024-11-12 12:24 ` Miklos Szeredi
2024-11-12 12:29 ` Jeff Layton
2024-11-13 12:27 ` Christian Brauner
2024-11-13 16:30 ` Christian Brauner
2024-11-14 14:53 ` Miklos Szeredi [this message]
2024-11-15 8:10 ` Christian Brauner
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=CAJfpegtLiOjbtP4np-WjJ_oyC-u3FwZ4BWQxGkSSmWxurBOQdA@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=brauner@kernel.org \
--cc=christian@brauner.io \
--cc=josef@toxicpanda.com \
--cc=kzak@redhat.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mszeredi@redhat.com \
/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).