From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Andrew Chernyakov <acherniakov@astralinux.ru>,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@somainline.org>,
Mathieu Poirier <mathieu.poirier@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH 5.10 1/1] Backport of rpmsg: qcom: glink: replace strncpy() with strscpy_pad()
Date: Fri, 7 Oct 2022 14:26:16 +0200 [thread overview]
Message-ID: <10f629f9-733b-3b8e-4e80-af16920b3615@linaro.org> (raw)
In-Reply-To: <20221007104120.75208-2-acherniakov@astralinux.ru>
On 07/10/2022 12:41, Andrew Chernyakov wrote:
> The use of strncpy() is considered deprecated for NULL-terminated
> strings[1]. Replace strncpy() with strscpy_pad(), to keep existing
> pad-behavior of strncpy, strncpy was found on line 1424 of
> /drivers/rpmsg/qcom_glink_native.c.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Signed-off-by: Andrew Chernyakov <acherniakov@astralinux.ru>
This is not a correct backport. You lost entire information about
original patch and its history. You even dropped my authorship. The
certificate of origin chain is broken and not correct.
You must follow the process of backporting of patches:
https://elixir.bootlin.com/linux/v5.19.14/source/Documentation/process/submitting-patches.rst
Best regards,
Krzysztof
prev parent reply other threads:[~2022-10-07 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 10:41 [PATCH 5.10 0/1] Backport of rpmsg: qcom: glink: replace strncpy() with strscpy_pad() Andrew Chernyakov
2022-10-07 10:41 ` [PATCH 5.10 1/1] " Andrew Chernyakov
2022-10-07 11:39 ` [lvc-project] " Alexey Khoroshilov
2022-10-07 12:26 ` Krzysztof Kozlowski [this message]
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=10f629f9-733b-3b8e-4e80-af16920b3615@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=acherniakov@astralinux.ru \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=konrad.dybcio@somainline.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=mathieu.poirier@linaro.org \
--cc=stable@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).