From: "Gustavo A. R. Silva" <gustavo@embeddedor.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Arnd Bergmann <arnd@kernel.org>, Robert Richter <rric@kernel.org>,
Tony Luck <tony.luck@intel.com>,
Sergey Temerkhanov <s.temerkhanov@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Kees Cook <keescook@chromium.org>,
James Morse <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Yeqi Fu <asuk4.q@gmail.com>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] EDAC, thunderx: fix possible out-of-bounds string access.
Date: Thu, 23 Nov 2023 08:41:33 -0600 [thread overview]
Message-ID: <ece872de-46fa-4138-959d-28e76e6b5edb@embeddedor.com> (raw)
In-Reply-To: <20231123143019.GDZV9h+zIVj5pBQySh@fat_crate.local>
On 11/23/23 08:30, Borislav Petkov wrote:
> On Thu, Nov 23, 2023 at 08:03:58AM -0600, Gustavo A. R. Silva wrote:
>> That's correct, yes.
>
> Commit ID is stable enough so that it doesn't change?
Well, it has changed a couple of times in a week.
>
> I don't want to commit it now and it would happen to change later and
> I'll have a stale reference in the commit message...
>
To avoid that, I would just say (in the changelog text) that this patch
is fixing some -Wstringop-overflow warnings, without specifying any
commit ID.
--
Gustavo
next prev parent reply other threads:[~2023-11-23 14:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 22:19 Arnd Bergmann
2023-11-22 23:07 ` Gustavo A. R. Silva
2023-11-23 11:58 ` Borislav Petkov
2023-11-23 14:03 ` Gustavo A. R. Silva
2023-11-23 14:30 ` Borislav Petkov
2023-11-23 14:41 ` Gustavo A. R. Silva [this message]
2023-11-23 16:39 ` Borislav Petkov
2023-11-23 17:05 ` Borislav Petkov
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=ece872de-46fa-4138-959d-28e76e6b5edb@embeddedor.com \
--to=gustavo@embeddedor.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=asuk4.q@gmail.com \
--cc=bp@alien8.de \
--cc=gustavoars@kernel.org \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@kernel.org \
--cc=s.temerkhanov@gmail.com \
--cc=tony.luck@intel.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
all inboxes | Powered by JetHome®