public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>
Subject: Re: [PATCH][STABLE] KVM: x86: Fix TSS size check for 16-bit tasks
Date: Wed, 21 Apr 2010 12:25:49 +0200	[thread overview]
Message-ID: <4BCED2AD.5030904@siemens.com> (raw)
In-Reply-To: <4BCEC28A.9060309@redhat.com>

Avi Kivity wrote:
> On 04/14/2010 05:57 PM, Jan Kiszka wrote:
>> A 16-bit TSS is only 44 bytes long. So make sure to test for the correct
>> size on task switch.
>>
>> Signed-off-by: Jan Kiszka<jan.kiszka@siemens.com>
>> ---
>>
>> This is a backport of 8f2d524 from master. It applies at least down to
>> 2.6.32 and should be considered for the stable queues.
>>
>>    
> 
> This (and the exception thing) does not qualify under the usual stable 
> rules (regression or host security: in, otherwise out).  I prefer to 
> delay brining up a new guest for one release rather than risk a 
> regression.  If you have a special requirement for it this can be relaxed.
> 

In the end, we have to convince the customer's distro provider to
include this. It would have been easier with an upstream merge, but it
also is not impossible without it.

But I'm not 100% convinced that the criteria you mentioned match all the
merged stable patches. There have been feature fixes before - though
they had more impact on common guests. I can understand your concerns
regarding the exception fix (which diverges from master after recent
refactorings), but I can't see what makes this obvious fix problematic.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2010-04-21 10:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-14 14:57 [PATCH][STABLE] KVM: x86: Fix TSS size check for 16-bit tasks Jan Kiszka
2010-04-21  9:16 ` Avi Kivity
2010-04-21 10:25   ` Jan Kiszka [this message]
2010-04-21 10:47     ` Avi Kivity

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=4BCED2AD.5030904@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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