[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2e4e65a8-87b4-fac6-ef89-76b118b0cec4@leemhuis.info>
Date: Thu, 15 Dec 2022 08:11:06 +0100
From: Thorsten Leemhuis <regressions@...mhuis.info>
To: "regressions@...ts.linux.dev" <regressions@...ts.linux.dev>
Cc: linux-bcache@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [regression] BugĀ 216785 - "memcpy: detected field-spanning write..." warnings with bcache #forregzbot
[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
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
Powered by blists - more mailing lists