From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, zealci@zte.com.cn,
xu.panda@zte.com.cn, baihaowen@meizu.com, xu.xin16@zte.com.cn,
akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] ia64-mca-use-strscpy-is-more-robust-and-safer.patch removed from -mm tree
Date: Tue, 11 Oct 2022 18:51:43 -0700 [thread overview]
Message-ID: <20221012015143.B31F7C433D7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: ia64: mca: use strscpy() is more robust and safer
has been removed from the -mm tree. Its filename was
ia64-mca-use-strscpy-is-more-robust-and-safer.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: xu xin <xu.xin16@zte.com.cn>
Subject: ia64: mca: use strscpy() is more robust and safer
Date: Fri, 30 Sep 2022 06:19:50 +0000
The implementation of strscpy() is more robust and safer. That's now the
recommended way to copy NUL terminated strings.
Link: https://lkml.kernel.org/r/20220930061950.288290-1-xu.xin16@zte.com.cn
Reported-by: Zeal Robot <zealci@zte.com.cn>
Signed-off-by: Xu Panda <xu.panda@zte.com.cn>
Signed-off-by: xu xin <xu.xin16@zte.com.cn>
Cc: Haowen Bai <baihaowen@meizu.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
arch/ia64/kernel/mca.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/arch/ia64/kernel/mca.c~ia64-mca-use-strscpy-is-more-robust-and-safer
+++ a/arch/ia64/kernel/mca.c
@@ -1793,7 +1793,7 @@ format_mca_init_stack(void *mca_data, un
p->parent = p->real_parent = p->group_leader = p;
INIT_LIST_HEAD(&p->children);
INIT_LIST_HEAD(&p->sibling);
- strncpy(p->comm, type, sizeof(p->comm)-1);
+ strscpy(p->comm, type, sizeof(p->comm)-1);
}
/* Caller prevents this from being called after init */
_
Patches currently in -mm which might be from xu.xin16@zte.com.cn are
reply other threads:[~2022-10-12 1:51 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=20221012015143.B31F7C433D7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=baihaowen@meizu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=xu.panda@zte.com.cn \
--cc=xu.xin16@zte.com.cn \
--cc=zealci@zte.com.cn \
/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.