From: Peter Zijlstra <peterz@infradead.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: Thomas Gleixner <tglx@linutronix.de>,
kernel test robot <rong.a.chen@intel.com>,
Alexandre Chartre <alexandre.chartre@oracle.com>,
Andy Lutomirski <luto@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, ltp@lists.linux.it
Subject: Re: [x86/entry] 2bbc68f837: ltp.ptrace08.fail
Date: Tue, 16 Jun 2020 15:27:05 +0200 [thread overview]
Message-ID: <20200616132705.GW2531@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <8E41B15F-D567-4C52-94E9-367015480345@amacapital.net>
On Tue, Jun 16, 2020 at 06:22:10AM -0700, Andy Lutomirski wrote:
>
> > On Jun 16, 2020, at 1:44 AM, Thomas Gleixner <tglx@linutronix.de> wrote:
> >
> > kernel test robot <rong.a.chen@intel.com> writes:
> >> FYI, we noticed the following commit (built with gcc-9):
> >>
> >> commit: 2bbc68f8373c0631ebf137f376fbea00e8086be7 ("x86/entry: Convert Debug exception to IDTENTRY_DB")
> >> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> >
> > Is the head of linux.git exposing the same problem or is this an
> > intermittent failure, which only affects bisectability?
>
> It sure looks deterministic:
>
> ptrace08.c:62: BROK: Cannot find address of kernel symbol "do_debug"
ROFL
next prev parent reply other threads:[~2020-06-16 13:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200616075533.GL5653@shao2-debian>
2020-06-16 8:44 ` Thomas Gleixner
2020-06-16 12:24 ` [LKP] " Rong Chen
[not found] ` <8E41B15F-D567-4C52-94E9-367015480345@amacapital.net>
2020-06-16 13:27 ` Peter Zijlstra [this message]
2020-06-17 13:17 ` [LTP] " Cyril Hrubis
2020-06-18 18:20 ` Andy Lutomirski
2020-08-12 9:31 ` Cyril Hrubis
2020-08-14 14:58 ` Cyril Hrubis
2020-08-14 16:42 ` Andy Lutomirski
2020-06-18 20:02 ` Thomas Gleixner
2020-06-22 10:16 ` [LKP] " Naresh Kamboju
2020-06-16 14:57 ` Thomas Gleixner
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=20200616132705.GW2531@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=alexandre.chartre@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=ltp@lists.linux.it \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=rong.a.chen@intel.com \
--cc=tglx@linutronix.de \
/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®