mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>, <lkp@intel.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	<linux-kernel@vger.kernel.org>,
	"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL] objtool fixes and updates
Date: Mon, 31 Mar 2025 20:44:25 +0800	[thread overview]
Message-ID: <Z+qOKZ2xNK+hUP6x@rli9-mobl> (raw)
In-Reply-To: <20250331123649.GCZ-qMYfyI9gZWwFRm@fat_crate.local>

On Mon, Mar 31, 2025 at 02:36:49PM +0200, Borislav Petkov wrote:
> On Mon, Mar 31, 2025 at 08:31:08PM +0800, Philip Li wrote:
> > For 0a7fb6f07e3a, the bot only reported 2 times on x86 [1][2]. For this
> > loongarch report, the bisection is wrong and is a false positive, I will
> > further check. Meanwhile, the bot will ignore the bisection of this new
> > objtool message as it is not really a new kernel issue.
> 
> Can you guys get a human being to double-check and vet those reports?! Please!

Really sorry, we will add more strict check of objtool warnings. We have
logic to detect the low confidence one and send to https://lore.kernel.org/oe-kbuild/
for manual check before sending out. But there's still case that we fail to
detect.

> 
> Because we kinda trust them but
> 
> 1. they're not really helpful and hard to understand what you're reporting
> 
> 2. that summary thing is especially useless:
> 
> "Error/Warning ids grouped by kconfigs:
> 
> recent_errors
> `-- loongarch-randconfig-001-20250328
>     `-- arch-loongarch-kernel-traps.o:warning:objtool:show_stack:skipping-duplicate-warning(s)"
> 
> When I see this, I need to go look for the original reports and somehow
> scratch them together. And you have all that info, why don't you simply dump
> a URL with the bug materials so that one can inspect them?

I will also check this as it is designed to have link together with reported
error in the summary. It is another bug that the bot should be fixed.

> 
> 3. Last but not least, if this doesn't change I will start ignoring them.
>    Because they're not really helping - on the contrary - they're actively
>    interfering.

Apologize again, we will continue improving the bot to make it really useful.

> 
> Thx.
> 
> -- 
> Regards/Gruss,
>     Boris.
> 
> https://people.kernel.org/tglx/notes-about-netiquette

  reply	other threads:[~2025-03-31 12:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28 21:18 Ingo Molnar
2025-03-29 15:32 ` Borislav Petkov
2025-03-30 22:19   ` Linus Torvalds
2025-03-30 23:13     ` Borislav Petkov
2025-03-31  1:39       ` Josh Poimboeuf
2025-03-31  9:39         ` Ingo Molnar
2025-03-31 15:29           ` Josh Poimboeuf
2025-03-31 16:07             ` Ingo Molnar
2025-03-31 22:19         ` Josh Poimboeuf
2025-04-01  7:58           ` Ingo Molnar
2025-03-31 11:55   ` Ingo Molnar
2025-03-31 12:31     ` Philip Li
2025-03-31 12:36       ` Borislav Petkov
2025-03-31 12:44         ` Philip Li [this message]
2025-03-31 12:49           ` Borislav Petkov
2025-03-31 13:27             ` Philip Li
2025-03-31 16:10       ` Ingo Molnar
2025-03-31 22:17         ` Josh Poimboeuf
2025-04-01  0:38           ` Philip Li
2025-04-01  2:05             ` Tiezhu Yang
2025-04-01  4:15               ` Josh Poimboeuf
2025-04-01  6:12                 ` Tiezhu Yang
2025-04-02 17:48 ` pr-tracker-bot

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=Z+qOKZ2xNK+hUP6x@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=jpoimboe@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --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®