Messages in this thread | | | Date | Tue, 25 Jan 2022 09:53:13 -0800 | From | Kees Cook <> | Subject | Re: linux-next: build failure after merge of the kspp tree |
| |
On Tue, Jan 25, 2022 at 09:01:52AM -0500, Steven Rostedt wrote: > On Tue, 25 Jan 2022 22:27:32 +0900 > Masami Hiramatsu <mhiramat@kernel.org> wrote: > > > > But if this is true, I would imagine there would be plenty of other > > > warnings? I'm currently stumped. > > > > That is because __rel_loc is used only in the sample code in the kernel > > for testing. Other use-cases comes from user-space. > > Hmm, can we skip this boundary check for this example? > > Is this only checked when __CHECKER__ is defined? If so, would this work?
__CHECKER__ is only for sparse. This is from re-enabling -Warray-bounds for gcc.
-- Kees Cook
| |