All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Hahn <hahn@univention.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: KVM: x86: handle idiv overflow at kvm_write_tsc for stable-3.10
Date: Tue, 09 Sep 2014 15:34:26 +0200	[thread overview]
Message-ID: <540F01E2.1040806@univention.de> (raw)
In-Reply-To: <20140903184213.GC5240@amt.cnet>

Hello Marcelo,

On 03.09.2014 20:42, Marcelo Tosatti wrote:
> On Wed, Sep 03, 2014 at 10:16:40AM +0200, Philipp Hahn wrote:
>> can we please 8915aa27d5efbb9185357175b0acf884325565f9 get applied to
>> 3.10 too?
>>
>>> commit 8915aa27d5efbb9185357175b0acf884325565f9
>>> Author: Marcelo Tosatti <mtosatti@redhat.com>
>>> Date:   Tue Jun 11 23:31:12 2013 -0300
>>>
>>>     KVM: x86: handle idiv overflow at kvm_write_tsc
>>>
>>>     Its possible that idivl overflows (due to large delta stored in
>> usdiff,
>>>     valid scenario).
>>>
>>>     Create an exception handler to catch the overflow exception
>> (division by zero
>>>     is protected by vcpu->arch.virtual_tsc_khz check), and interpret
>> it accordingly
>>>     (delta is larger than USEC_PER_SEC).
>>>
>>>     Fixes https://bugzilla.redhat.com/show_bug.cgi?id=969644
>>>
>>>     Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
>>>     Signed-off-by: Gleb Natapov <gleb@redhat.com>
...
>> Tested-by: Philipp Hahn <hahn@univention.de>
...
> Yes, can you send the patch accordingly to the stable guidelines please?

Maybe I'm to stupid right now, but I find
linux/Documentation/stable_kernel_rules.txt unclear on what I'm supposed
to do:

1. cherry-pick the patch myself?
2. amend the commit message by adding the original commit it
3. where should the name of the stable branch go?
4. amend the commit message by adding myself as a tester? Or do I need
to sign it off?
5. send that patch to <mailto:stable@vger.kernel.org>.

It did seem to have worked, as I never received an acknowledgement nor
is it listed in
<http://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git>.
Maybe you can do it and cc: me so I can do it right next time myself.

Thanks.

Philipp

           reply	other threads:[~2014-09-09 13:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20140903184213.GC5240@amt.cnet>]

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=540F01E2.1040806@univention.de \
    --to=hahn@univention.de \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.