From: Marcelo Tosatti <mtosatti@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Andy Lutomirski <luto@amacapital.net>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Gleb Natapov <gleb@kernel.org>, kvm list <kvm@vger.kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
Andrew Lutomirski <luto@kernel.org>
Subject: Re: [GIT PULL] First batch of KVM changes for 4.1
Date: Thu, 23 Apr 2015 14:06:17 -0300 [thread overview]
Message-ID: <20150423170617.GC7482@amt.cnet> (raw)
In-Reply-To: <5538DF55.30709@redhat.com>
On Thu, Apr 23, 2015 at 02:02:29PM +0200, Paolo Bonzini wrote:
>
>
> On 23/04/2015 13:51, Marcelo Tosatti wrote:
> >>> > > https://bugzilla.redhat.com/show_bug.cgi?id=1174664
> >> >
> >> > That was the missing volatile in an asm. Older compilers didn't catch
> >> > it. :(
> > How do you know that? It looks like memory corruption (look at the
> > pattern at the end).
>
> I suspect some kind of operator error there, it makes no sense.
if (unlikely(s->flags & SLAB_POISON))
memset(start, POISON_INUSE, PAGE_SIZE << order);
* Padding is done using 0x5a (POISON_INUSE)
> On the other hand, bug 1178975 is much clearer and the symptoms are the
> same. In that bug, you can see that the same kernel source works on f20
> (package version 3.17.7-200.fc20.x86_64) and fails on f21 (package
> version 3.17.7-300.fc21.x86_64). Of course the compiler is different.
> The newer one hoists the lsl out of the loop; if you get a CPU migration
> at the wrong time, the cpu != cpu1 condition will always be true the
> loop will never exit.
>
> Paolo
next prev parent reply other threads:[~2015-04-23 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 15:01 [GIT PULL] First batch of KVM changes for 4.1 Paolo Bonzini
2015-04-17 8:52 ` Peter Zijlstra
2015-04-17 9:17 ` Peter Zijlstra
2015-04-17 10:09 ` Paolo Bonzini
2015-04-17 10:36 ` Peter Zijlstra
2015-04-17 10:38 ` Paolo Bonzini
2015-04-17 10:55 ` Peter Zijlstra
2015-04-17 12:46 ` Paolo Bonzini
2015-04-17 13:10 ` Peter Zijlstra
2015-04-17 13:38 ` Paolo Bonzini
2015-04-17 13:43 ` Peter Zijlstra
2015-04-17 14:57 ` Paolo Bonzini
2015-04-17 19:01 ` Marcelo Tosatti
2015-04-17 19:16 ` Andy Lutomirski
2015-04-17 19:57 ` Paolo Bonzini
2015-04-17 20:18 ` Marcelo Tosatti
2015-04-17 20:39 ` Andy Lutomirski
2015-04-17 21:28 ` Linus Torvalds
2015-04-17 21:42 ` Andy Lutomirski
2015-04-17 22:04 ` Linus Torvalds
2015-04-17 22:25 ` Andy Lutomirski
2015-04-17 23:39 ` Marcelo Tosatti
2015-04-18 16:20 ` Paolo Bonzini
2015-04-20 16:59 ` Paolo Bonzini
2015-04-20 20:27 ` Andy Lutomirski
2015-04-22 21:21 ` Marcelo Tosatti
2015-04-23 9:13 ` Paolo Bonzini
2015-04-23 11:51 ` Marcelo Tosatti
2015-04-23 12:02 ` Paolo Bonzini
2015-04-23 17:06 ` Marcelo Tosatti [this message]
2015-04-22 20:56 ` Marcelo Tosatti
2015-04-22 21:01 ` Paolo Bonzini
2015-04-22 22:55 ` Marcelo Tosatti
2015-04-23 11:29 ` Paolo Bonzini
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=20150423170617.GC7482@amt.cnet \
--to=mtosatti@redhat.com \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=ralf@linux-mips.org \
--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