kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Andrew Theurer <habanero@linux.vnet.ibm.com>
Cc: kvm@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: kernel bug in kvm_intel
Date: Sat, 31 Oct 2009 18:38:57 +0200	[thread overview]
Message-ID: <4AEC6821.7010801@redhat.com> (raw)
In-Reply-To: <4AEC6699.6000202@redhat.com>

On 10/31/2009 06:32 PM, Avi Kivity wrote:
> On 10/31/2009 06:25 PM, Andrew Theurer wrote:
>>> 5579 is not the preceding commit, it is the merged branch:
>>>
>>> commit ada3fa15057205b7d3f727bba5cd26b5912e350f
>>> Merge: 2f82af0 5579fd7
>>> Author: Linus Torvalds <torvalds@linux-foundation.org>
>>> Date:   Tue Sep 15 09:39:44 2009 -0700
>>>
>>>     Merge branch 'for-linus' of 
>>> git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu
>>>
>>>
>>> What happens with 2f82af0?
>>>
>>
>> 2f82af0 is:
>>
>>> Nicolas Pitre has a new email address
>>>
>>> Due to problems at cam.org, my nico@cam.org email address is no longer
>>> valid.  FRom now on, nico@fluxnic.net should be used instead.
>>
>> I have not tested that, but it doesn't seem likely that it would have 
>> anything to do with the problem.  Or maybe I am misunderstanding the 
>> impact of this commit?
>
> ada3fa15 is known broken.  It is the merge of two branches: 2f82 
> (mainline) and 5597.  Testing both branches would indicate the problem 
> is in the merge if both test ok.
>
>> Oh, wait, that commit was tested, in the middle of the log above.
>
> So the problem is the merge.  Will look.
>

Only, that merge doesn't change virt/kvm or arch/x86/kvm.

Tejun, anything known bad about that merge?  ada3fa15 kills kvm.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2009-10-31 16:39 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09 20:04 kernel bug in kvm_intel Andrew Theurer
2009-10-11  5:19 ` Avi Kivity
2009-10-12 18:42   ` Andrew Theurer
2009-10-13  6:50     ` Avi Kivity
2009-10-13 14:04       ` Andrew Theurer
2009-10-14 17:10         ` Avi Kivity
2009-10-15 20:18           ` Andrew Theurer
2009-10-30 18:07             ` Andrew Theurer
2009-10-31 15:47               ` Avi Kivity
2009-10-31 16:25                 ` Andrew Theurer
2009-10-31 16:32                   ` Avi Kivity
2009-10-31 16:38                     ` Avi Kivity [this message]
2009-11-01 10:00                       ` Tejun Heo
2009-11-01 10:20                         ` Avi Kivity
2009-11-01 10:45                           ` Tejun Heo
2009-11-01 11:31                             ` Avi Kivity
2009-11-18  9:26                               ` Tejun Heo
2009-11-26  1:35                                 ` Andrew Theurer
2009-11-26  1:41                                   ` Tejun Heo
2009-11-26 10:31                                   ` Avi Kivity
2009-11-26 13:47                                     ` Andrew Theurer
2009-11-29 14:46                                   ` Avi Kivity
2009-11-30 16:27                                     ` Andrew Theurer
2009-10-13 14:31       ` Marcelo Tosatti

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=4AEC6821.7010801@redhat.com \
    --to=avi@redhat.com \
    --cc=habanero@linux.vnet.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=tj@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;
as well as URLs for NNTP newsgroup(s).