From: Andrei Vagin <avagin@openvz.org>
To: David Howells <dhowells@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, Andrei Vagin <avagin@gmail.com>
Subject: [PATCH dhowells/mount-api] fs: typo fix in legacy_parse_param
Date: Thu, 2 Aug 2018 00:28:10 -0700 [thread overview]
Message-ID: <20180802072810.3126-1-avagin@openvz.org> (raw)
From: Andrei Vagin <avagin@gmail.com>
Signed-off-by: Andrei Vagin <avagin@gmail.com>
---
fs/fs_context.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/fs_context.c b/fs/fs_context.c
index 90338ef7bb92..a6597a2fbf2b 100644
--- a/fs/fs_context.c
+++ b/fs/fs_context.c
@@ -625,7 +625,7 @@ static int legacy_parse_param(struct fs_context *fc, struct fs_parameter *param)
if (param->type == fs_value_is_string) {
ctx->legacy_data[size++] = '=';
memcpy(ctx->legacy_data + size, param->string, param->size);
- size += len;
+ size += param->size;
}
ctx->legacy_data[size] = '\0';
ctx->data_size = size;
--
2.17.1
next reply other threads:[~2018-08-02 9:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-02 7:28 Andrei Vagin [this message]
2018-08-02 7:50 ` [PATCH dhowells/mount-api] fs: typo fix in legacy_parse_param David Howells
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=20180802072810.3126-1-avagin@openvz.org \
--to=avagin@openvz.org \
--cc=avagin@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@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).