mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Dmitry Vyukov <dvyukov@google.com>,
	Gleb Natapov <gleb@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	"x86@kernel.org" <x86@kernel.org>,
	kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Cc: syzkaller <syzkaller@googlegroups.com>,
	Kostya Serebryany <kcc@google.com>,
	Alexander Potapenko <glider@google.com>,
	Eric Dumazet <edumazet@google.com>,
	Sasha Levin <sasha.levin@oracle.com>
Subject: Re: kvm: GPF in kvm_lapic_latched_init
Date: Tue, 31 May 2016 12:35:59 +0200	[thread overview]
Message-ID: <f2586939-506c-3579-34a9-b664afd5d372@redhat.com> (raw)
In-Reply-To: <CACT4Y+ZfD8PXmbONprT=yj_8bMKQE2ioa_iCYfg5+57Qj8pvNQ@mail.gmail.com>



On 08/01/2016 19:42, Dmitry Vyukov wrote:
> Hello,
> 
> The following program triggers GPF in kvm_lapic_latched_init if run in
> a parallel loop:
> https://gist.githubusercontent.com/dvyukov/524b398f379440b21115/raw/9627095f57a72501fb51bf7565471d31732beeee/gistfile1.txt

I've noticed that the program here tends to segfault a lot, even before
reaching the kernel.  Is this intended?

Thanks,

Paolo

  parent reply	other threads:[~2016-05-31 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 18:42 Dmitry Vyukov
2016-01-15 17:12 ` Dmitry Vyukov
2016-01-18  9:57   ` Xiao Guangrong
2016-01-18 10:11     ` Dmitry Vyukov
2016-06-22  8:20   ` Dmitry Vyukov
2016-06-22  8:36     ` Paolo Bonzini
2016-06-22  8:38       ` Dmitry Vyukov
2016-06-22  8:46         ` Paolo Bonzini
2016-06-22  9:56           ` Dmitry Vyukov
2016-01-15 19:59 ` Jeff Merkey
2016-01-15 20:09   ` Dmitry Vyukov
2016-01-15 20:54     ` Jeff Merkey
2016-05-31 10:35 ` Paolo Bonzini [this message]
2016-06-01  7:59   ` Dmitry Vyukov

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=f2586939-506c-3579-34a9-b664afd5d372@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=dvyukov@google.com \
    --cc=edumazet@google.com \
    --cc=gleb@kernel.org \
    --cc=glider@google.com \
    --cc=hpa@zytor.com \
    --cc=kcc@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=sasha.levin@oracle.com \
    --cc=syzkaller@googlegroups.com \
    --cc=tglx@linutronix.de \
    --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
all inboxes | Powered by JetHome®