virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Zachary Amsden <zach@vmware.com>
Cc: caglar@pardus.org.tr, Andi Kleen <ak@suse.de>,
	lkml <linux-kernel@vger.kernel.org>,
	Virtualization Mailing List <virtualization@lists.osdl.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Fix potential interrupts during alternative patching [was Re: [RFC] Avoid PIT SMP lockups]
Date: Thu, 19 Oct 2006 22:25:47 -0700	[thread overview]
Message-ID: <20061020052546.GC8881@kroah.com> (raw)
In-Reply-To: <453730B7.3040906@vmware.com>

On Thu, Oct 19, 2006 at 01:00:55AM -0700, Zachary Amsden wrote:
> S.??a??lar Onur wrote:
> >17 Eki 2006 Sal 01:21 tarihinde, S.??a??lar Onur ??unlar?? yazm????t??: 
> >  
> >>17 Eki 2006 Sal 01:17 tarihinde, Zachary Amsden ??unlar?? yazm????t??:
> >>    
> >>>My nasty quick patch might not apply - the only tree I've got is a very
> >>>hacked 2.6.18-rc6-mm1+local-patches thing, but the fix should be obvious
> >>>enough.
> >>>      
> >>Ok, I'll test and report back...
> >>    
> >
> >Both 2.6.18 and 2.6.18.1 boots without any problem (and of course without 
> >noreplacement workarund) with that patch.
> >
> >Cheers
> >  
> 
> So this patch is an obvious bugfix - please apply, and to stable as 
> well. I'm not sure when this broke, but taking interrupts in the middle 
> of self modifying code is not a pretty sight.

Please send -stable patches to stable@kernel.org, not to me directly (we
are a team and hand off ownership to each other, by sending it to the
alias it makes sure that nothing gets lots in our individual mail
boxes.)

Also, please let stable know when this is upstream, we don't want to
apply it before then.

thanks,

greg k-h

      parent reply	other threads:[~2006-10-20  5:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1160170736.6140.31.camel@localhost.localdomain>
     [not found] ` <453404F6.5040202@vmware.com>
     [not found]   ` <200610170121.51492.caglar@pardus.org.tr>
     [not found]     ` <200610171505.53576.caglar@pardus.org.tr>
2006-10-19  8:00       ` [PATCH] Fix potential interrupts during alternative patching [was Re: [RFC] Avoid PIT SMP lockups] Zachary Amsden
2006-10-19  8:49         ` Jeremy Fitzhardinge
2006-10-19  9:00           ` Zachary Amsden
2006-10-20 10:36             ` S.Çağlar Onur
2006-10-20  5:25         ` Greg KH [this message]

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=20061020052546.GC8881@kroah.com \
    --to=greg@kroah.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=caglar@pardus.org.tr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.org \
    --cc=zach@vmware.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;
as well as URLs for NNTP newsgroup(s).