From: Benjamin Coddington <bcodding@redhat.com>
To: Steve Dickson <steved@redhat.com>
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2] libnsm: fix the safer atomic filenames fix
Date: Wed, 27 Nov 2024 06:44:09 -0500 [thread overview]
Message-ID: <7fa1fc7f2a8d72e11e5a468c0ed4bbdefb035830.1732707758.git.bcodding@redhat.com> (raw)
Commit 9f7a91b51ffc ("libnsm: safer atomic filenames") messed up the length
arguement to snprintf() in nsm_make_temp_pathname such that the length is
longer than the computed string. When compiled with "-O
-D_FORTIFY_SOURCE=3", __snprintf_chk will fail and abort statd.
The fix is to correct the original size calculation, then pull one from the
snprintf length for the final "/".
Fixes: 9f7a91b51ffc ("libnsm: safer atomic filenames")
Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
---
v2: ensure we handle paths without '/', simplify.
---
support/nsm/file.c | 12 ++++++++----
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/support/nsm/file.c b/support/nsm/file.c
index e0804136ccbe..de122b0fc5a1 100644
--- a/support/nsm/file.c
+++ b/support/nsm/file.c
@@ -187,7 +187,7 @@ nsm_make_temp_pathname(const char *pathname)
char *path, *base;
int len;
- size = strlen(pathname) + sizeof(".new") + 3;
+ size = strlen(pathname) + sizeof(".new") + 1;
if (size > PATH_MAX)
return NULL;
@@ -196,15 +196,19 @@ nsm_make_temp_pathname(const char *pathname)
return NULL;
base = strrchr(pathname, '/');
- strcpy(path, pathname);
+ if (base == NULL)
+ base = pathname;
+ else
+ base++;
+ strcpy(path, pathname);
len = base - pathname;
- len += snprintf(path + len + 1, size-len, ".%s.new", base+1);
+ len += snprintf(path + len, size - len, ".%s.new", base);
+
if (error_check(len, size)) {
free(path);
return NULL;
}
-
return path;
}
base-commit: eb5abb5c60ab60f3c2f22518d513ed187f39bd9b
--
2.47.0
next reply other threads:[~2024-11-27 11:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-27 11:44 Benjamin Coddington [this message]
2024-11-30 13:11 ` [PATCH v2] libnsm: fix the safer atomic filenames fix Steve Dickson
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=7fa1fc7f2a8d72e11e5a468c0ed4bbdefb035830.1732707758.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@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