From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Kees Cook <keescook@chromium.org>
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 11:57:46 +0100 [thread overview]
Message-ID: <f1ca3cea-01ae-998a-2aa8-c3e40cf46975@leemhuis.info> (raw)
In-Reply-To: <202301052218.042D2BFE@keescook>
On 06.01.23 07:22, Kees Cook wrote:
> On Thu, Dec 15, 2022 at 08:11:06AM +0100, Thorsten Leemhuis wrote:
>> [Note: this mail contains only information for Linux kernel regression
>> tracking. Mails like these contain '#forregzbot' in the subject to make
>> then easy to spot and filter out. The author also tried to remove most
>> or all individuals from the list of recipients to spare them the hassle.]
>>
>> On 08.12.22 15:53, Thorsten Leemhuis wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=216785 :
>>>
>>>> Alexandre Pereira 2022-12-07 18:51:55 UTC
>>>>
>>>> Testing linux kernel 6.1-rc8, I have several kernel erros regarding bcache.
>>>>
>>>> For context, I have a bcache configuration that is working without issues on 6.0.x and previous versions.
>>>>
>>>> The errors:
>>>>
>>>> dez 07 18:33:45 stormtrooper kernel: ------------[ cut here ]------------
>>>> dez 07 18:33:45 stormtrooper kernel: memcpy: detected field-spanning write (size 264) of single field "&i->j" at drivers/md/bcache/journal.c:152 (size 240)
>>
>> #regzbot inconclusive: stop tracking field-spanning write warnings, they
>> come from a new security feature
>>
>> https://lore.kernel.org/all/20210727205855.411487-1-keescook@chromium.org/
>>
>> Tracking them would cost time I better spend on more important things
>> for now
>
> FWIW, I'd find it handy to see these. I've been trying to track and fix
> them.
In that case I'd suggest: I forward any I see to you, but don't add them
to the regressions tracked with regzbot.
Does that sound fine for you? Or is there a strong reason why I should
track them? Then they would be in the weekly reports to Linus, but I
wonder if he cares. At least for now now I guess he does not -- at some
later point where of the problems that are still hiding surfaced and
were fixed it might be something different. But then I could start
tracking them.
> To that end, I've just sent out the following patches:
Great!
Ciao, Thorsten
next prev parent reply other threads:[~2023-01-06 10:57 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 [this message]
2023-01-06 20:16 ` Kees Cook
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=f1ca3cea-01ae-998a-2aa8-c3e40cf46975@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=keescook@chromium.org \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 NNTP newsgroup(s).