The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: kernel test robot <lkp@intel.com>
Cc: x86-ml <x86@kernel.org>, linux-kernel@vger.kernel.org
Subject: Re: [tip:ras/core] BUILD SUCCESS de768416b203ac84e02a757b782a32efb388476f
Date: Wed, 29 Dec 2021 10:34:25 +0100	[thread overview]
Message-ID: <YcwrofZrHadGAMlD@zn.tnic> (raw)
In-Reply-To: <61cba815.Her0ebRPVzS617KT%lkp@intel.com>

On Wed, Dec 29, 2021 at 08:13:09AM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras/core
> branch HEAD: de768416b203ac84e02a757b782a32efb388476f  x86/mce/inject: Avoid out-of-bounds write when setting flags
> 
> possible Warning in current branch (please contact us if interested):
> 
> vmlinux.o: warning: objtool: do_machine_check()+0x59a: call to test_bit() leaves .noinstr.text section
> 
> Warning ids grouped by kconfigs:
> 
> gcc_recent_errors
> `-- x86_64-buildonly-randconfig-r006-20211228
>     `-- vmlinux.o:warning:objtool:do_machine_check():call-to-test_bit()-leaves-.noinstr.text-section

Yes, I'm interested. Please send me reproduction instructions.

Thx.

-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2021-12-29  9:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-29  0:13 [tip:ras/core] BUILD SUCCESS de768416b203ac84e02a757b782a32efb388476f kernel test robot
2021-12-29  9:34 ` Borislav Petkov [this message]
2021-12-31  0:46   ` Chen, Rong A
2021-12-31 11:48     ` Borislav Petkov
2022-01-17 17:51       ` [PATCH] x86/mce: Fix two more noinstr issues Borislav Petkov

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=YcwrofZrHadGAMlD@zn.tnic \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox