The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Joerg Roedel <jroedel@suse.de>
To: Ye Xiaolong <xiaolong.ye@intel.com>
Cc: kernel test robot <lkp@intel.com>,
	Thomas Gleixner <tglx@linutronix.de>, LKP <lkp@01.org>,
	linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [LKP] [lkp-robot] [confidence: ] 7757d607c6 [ 56.996267] BUG: Bad page map in process trinity-c2 pte:0d755065 pmd:0d55b067
Date: Tue, 31 Jul 2018 09:27:25 +0200	[thread overview]
Message-ID: <20180731072725.ecbhfm6642xxao5z@suse.de> (raw)
In-Reply-To: <20180731020036.GB22500@yexl-desktop>

On Tue, Jul 31, 2018 at 10:00:36AM +0800, Ye Xiaolong wrote:
> On 07/27, Joerg Roedel wrote:
> >May I ask how this was bisected? I found it very hard to reproduce, it
> >triggered less then two times a day with the attached reproducer. Given
> >that the report came pretty fast after the patches landed in
> >tip/x86/pti, I guess it triggered a lot faster in your testing.
> >
> 
> There is higher reproduce rate (2/310) in 0day environment, and we got dozens
> of qemu running simultaneously for bisection thus can get bisect result promptly.

Ah okay, that makes sense. Thanks for your answer and thanks for the
report again.


Regards,

	Joerg


      reply	other threads:[~2018-07-31  7:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-21  2:23 [lkp-robot] [confidence: ] 7757d607c6 [ 56.996267] BUG: Bad page map in process trinity-c2 pte:0d755065 pmd:0d55b067 kernel test robot
2018-07-27 13:25 ` Joerg Roedel
2018-07-31  2:00   ` [LKP] " Ye Xiaolong
2018-07-31  7:27     ` Joerg Roedel [this message]

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=20180731072725.ecbhfm6642xxao5z@suse.de \
    --to=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=lkp@intel.com \
    --cc=tglx@linutronix.de \
    --cc=xiaolong.ye@intel.com \
    /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