From: Zdenek Kabelac <zkabelac@sourceware.org>
To: lvm-devel@redhat.com
Subject: main - cov: fix copy from tmp_name buffer
Date: Mon, 13 Sep 2021 10:36:09 +0000 (GMT) [thread overview]
Message-ID: <20210913103609.3BECE3858006@sourceware.org> (raw)
Gitweb: https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=aa522d586227ecafb18d671cab284ae27ca65eed
Commit: aa522d586227ecafb18d671cab284ae27ca65eed
Parent: 7af0a1b9d87827f0d15e6b062b753ee3043f75dc
Author: Zdenek Kabelac <zkabelac@redhat.com>
AuthorDate: Thu Sep 9 22:32:09 2021 +0200
Committer: Zdenek Kabelac <zkabelac@redhat.com>
CommitterDate: Mon Sep 13 12:34:41 2021 +0200
cov: fix copy from tmp_name buffer
Mask for strncpy() Coverity report warning would
actually need to copy buffer from 'tmp_name' instead of 'str'.
But replace it directly with single 'strncpy()' again for better readbility,
just mask out the warning reported for this strncpy instance
(so we do not need to put comment fro every call of strcpy_name_len).
---
daemons/lvmlockd/lvmlockd-sanlock.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/daemons/lvmlockd/lvmlockd-sanlock.c b/daemons/lvmlockd/lvmlockd-sanlock.c
index b351b1d44..13567cf95 100644
--- a/daemons/lvmlockd/lvmlockd-sanlock.c
+++ b/daemons/lvmlockd/lvmlockd-sanlock.c
@@ -234,11 +234,8 @@ static uint64_t daemon_test_lv_count;
*/
static void strcpy_name_len(char *buf, char *str, int len)
{
- char tmp_name[SANLK_NAME_LEN + 1] = { 0 };
-
- strncpy(tmp_name, str, SANLK_NAME_LEN);
-
- memcpy(buf, str, SANLK_NAME_LEN);
+ /* coverity[buffer_size_warning] */
+ strncpy(buf, str, SANLK_NAME_LEN);
}
static int lock_lv_name_from_args(char *vg_args, char *lock_lv_name)
reply other threads:[~2021-09-13 10:36 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=20210913103609.3BECE3858006@sourceware.org \
--to=zkabelac@sourceware.org \
--cc=lvm-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.