From: Kees Cook <keescook@chromium.org>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
linux-bcache@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [regression] Bug 216785 - "memcpy: detected field-spanning write..." warnings with bcache #forregzbot
Date: Fri, 6 Jan 2023 12:16:47 -0800 [thread overview]
Message-ID: <202301061216.CF08E5E2@keescook> (raw)
In-Reply-To: <f1ca3cea-01ae-998a-2aa8-c3e40cf46975@leemhuis.info>
On Fri, Jan 06, 2023 at 11:57:46AM +0100, Thorsten Leemhuis wrote:
> In that case I'd suggest: I forward any I see to you, but don't add them
> to the regressions tracked with regzbot.
That would be much appreicated; thank you! :)
--
Kees Cook
prev parent reply other threads:[~2023-01-06 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 14:53 [regression] Bug 216785 - "memcpy: detected field-spanning write..." warnings with bcache Thorsten Leemhuis
2022-12-08 15:01 ` Coly Li
2022-12-15 7:11 ` [regression] Bug 216785 - "memcpy: detected field-spanning write..." warnings with bcache #forregzbot Thorsten Leemhuis
2023-01-06 6:22 ` Kees Cook
2023-01-06 10:57 ` Thorsten Leemhuis
2023-01-06 20:16 ` Kees Cook [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=202301061216.CF08E5E2@keescook \
--to=keescook@chromium.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).