From: Rong Chen <rong.a.chen@intel.com>
To: Borislav Petkov <bp@alien8.de>, kernel test robot <lkp@intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [kbuild-all] Re: [tip:x86/cpu 2/3] arch/x86/kernel/alternative.c:96:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+10' is out of bounds.
Date: Tue, 16 Mar 2021 18:01:37 +0800 [thread overview]
Message-ID: <a7522586-6496-1b09-6d98-0682f0a60dce@intel.com> (raw)
In-Reply-To: <20210316082703.GA18003@zn.tnic>
On 3/16/21 4:27 PM, Borislav Petkov wrote:
> Yet another useless report!
>
> On Tue, Mar 16, 2021 at 07:50:10AM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/cpu
>> head: 301cddc21a157a3072d789a3097857202e550a24
>> commit: a89dfde3dc3c2dbf56910af75e2d8b11ec5308f6 [2/3] x86: Remove dynamic NOP selection
>> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>>
>> cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
> What's cppcheck?
>
> That?
>
> Description-en: tool for static C/C++ code analysis (CLI)
> Cppcheck is a command-line tool that tries to detect bugs that your
>
>
>>>> arch/x86/kernel/alternative.c:96:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+10' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4,
>> ^
>> arch/x86/kernel/alternative.c:97:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+15' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4 + 5,
>> ^
>> arch/x86/kernel/alternative.c:98:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+21' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4 + 5 + 6,
>> ^
>> arch/x86/kernel/alternative.c:99:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+28' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4 + 5 + 6 + 7,
>> ^
>>>> arch/x86/kernel/ftrace.c:304:7: warning: union member 'ftrace_op_code_union::code' is never used. [unusedStructMember]
>> char code[OP_REF_SIZE];
>> ^
> How do you trigger this?
>
> /me ignores it until there's some info on how those things can be
> reproduced.
>
Hi Borislav,
Sorry for the inconvenience, there's a bug in our system which sent
internal reports to outside.
please ignore the warnings.
Best Regards,
Rong Chen
WARNING: multiple messages have this Message-ID (diff)
From: Rong Chen <rong.a.chen@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [tip:x86/cpu 2/3] arch/x86/kernel/alternative.c:96:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+10' is out of bounds.
Date: Tue, 16 Mar 2021 18:01:37 +0800 [thread overview]
Message-ID: <a7522586-6496-1b09-6d98-0682f0a60dce@intel.com> (raw)
In-Reply-To: <20210316082703.GA18003@zn.tnic>
[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]
On 3/16/21 4:27 PM, Borislav Petkov wrote:
> Yet another useless report!
>
> On Tue, Mar 16, 2021 at 07:50:10AM +0800, kernel test robot wrote:
>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/cpu
>> head: 301cddc21a157a3072d789a3097857202e550a24
>> commit: a89dfde3dc3c2dbf56910af75e2d8b11ec5308f6 [2/3] x86: Remove dynamic NOP selection
>> compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
>>
>> If you fix the issue, kindly add following tag as appropriate
>> Reported-by: kernel test robot <lkp@intel.com>
>>
>>
>> cppcheck possible warnings: (new ones prefixed by >>, may not real problems)
> What's cppcheck?
>
> That?
>
> Description-en: tool for static C/C++ code analysis (CLI)
> Cppcheck is a command-line tool that tries to detect bugs that your
>
>
>>>> arch/x86/kernel/alternative.c:96:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+10' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4,
>> ^
>> arch/x86/kernel/alternative.c:97:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+15' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4 + 5,
>> ^
>> arch/x86/kernel/alternative.c:98:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+21' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4 + 5 + 6,
>> ^
>> arch/x86/kernel/alternative.c:99:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+28' is out of bounds. [pointerOutOfBounds]
>> x86nops + 1 + 2 + 3 + 4 + 5 + 6 + 7,
>> ^
>>>> arch/x86/kernel/ftrace.c:304:7: warning: union member 'ftrace_op_code_union::code' is never used. [unusedStructMember]
>> char code[OP_REF_SIZE];
>> ^
> How do you trigger this?
>
> /me ignores it until there's some info on how those things can be
> reproduced.
>
Hi Borislav,
Sorry for the inconvenience, there's a bug in our system which sent
internal reports to outside.
please ignore the warnings.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2021-03-16 10:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 23:50 [tip:x86/cpu 2/3] arch/x86/kernel/alternative.c:96:10: warning: Undefined behaviour, pointer arithmetic 'x86nops+10' is out of bounds kernel test robot
2021-03-15 23:50 ` kernel test robot
2021-03-16 8:27 ` Borislav Petkov
2021-03-16 8:27 ` Borislav Petkov
2021-03-16 9:01 ` Peter Zijlstra
2021-03-16 9:01 ` Peter Zijlstra
2021-03-16 10:01 ` Rong Chen [this message]
2021-03-16 10:01 ` Rong Chen
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=a7522586-6496-1b09-6d98-0682f0a60dce@intel.com \
--to=rong.a.chen@intel.com \
--cc=bp@alien8.de \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=peterz@infradead.org \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.