From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>,
Marco Elver <elver@google.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Kees Cook <kees@kernel.org>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 6.2-rc3
Date: Mon, 9 Jan 2023 23:43:29 +0100 [thread overview]
Message-ID: <f39c266c-9802-71a5-8f1c-2d0a1340f59f@suse.cz> (raw)
In-Reply-To: <CAHk-=whC+YpdympyegB0Wr_0_6=LYggdabkMExRus2DtAdsv-Q@mail.gmail.com>
On 1/9/23 23:18, Linus Torvalds wrote:
> On Mon, Jan 9, 2023 at 11:47 AM Guenter Roeck <linux@roeck-us.net> wrote:
>>
>> fs/f2fs/inline.c: In function 'f2fs_move_inline_dirents':
>> include/linux/fortify-string.h:59:33: error: '__builtin_memset' pointer overflow between offset [28, 898293814] and size [-898293787, -1] [-Werror=array-bounds]
>
> Ok, I guess we'll have to disable this gcc warning for this version
> again. I don't think anybody figured out why it happens. We had
> several people look at it (Kees, Vlastimil, Jaegeuk) and I think
> everybody ended up going "tis looks like a compiler thing".
>
> Does anybody remember - what was the compiler version again and what
> do we need to disable?
Guenter reported that "The problem is seen with gcc 11.3.0, but not with gcc
12.2.0 nor with gcc 10.3.0."
https://lore.kernel.org/all/20221227002941.GA2691687@roeck-us.net/
Kees said it's -Warray-bounds, already disabled on gcc 12 for other reasons:
https://lore.kernel.org/all/D8BDBF66-E44C-45D4-9758-BAAA4F0C1998@kernel.org/
next prev parent reply other threads:[~2023-01-09 22:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 18:06 Linus Torvalds
2023-01-09 9:01 ` Build regressions/improvements in v6.2-rc3-8-g1fe4fd6f5cad346e Geert Uytterhoeven
2023-01-09 17:47 ` Linux 6.2-rc3 Guenter Roeck
2023-01-09 22:18 ` Linus Torvalds
2023-01-09 22:29 ` Marco Elver
2023-01-09 22:34 ` Linus Torvalds
2023-01-09 22:43 ` Vlastimil Babka [this message]
2023-01-09 23:14 ` Linus Torvalds
2023-01-09 23:32 ` Guenter Roeck
2023-01-09 23:14 ` Guenter Roeck
2023-01-10 10:44 ` Peter Zijlstra
2023-01-10 11:32 ` Linus Torvalds
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=f39c266c-9802-71a5-8f1c-2d0a1340f59f@suse.cz \
--to=vbabka@suse.cz \
--cc=elver@google.com \
--cc=jaegeuk@kernel.org \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®