public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@kernel.org>
To: Greg KH <greg@kroah.com>
Cc: Marc Aurele La France <root@ualberta.ca>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	x86@kernel.org, stable@kernel.org, Research.Support@ualberta.ca,
	linux-kernel@vger.kernel.org
Subject: Re: [stable] [PATCH] x86, setup (2.6.30-stable) fix 80x34 and	80x60 console modes
Date: Mon, 29 Jun 2009 23:33:42 -0700	[thread overview]
Message-ID: <4A49B1C6.9040900@kernel.org> (raw)
In-Reply-To: <20090630034822.GC12373@kroah.com>

Greg KH wrote:
> On Mon, Jun 29, 2009 at 06:27:40PM -0700, H. Peter Anvin wrote:
>> Marc Aurele La France wrote:
>>> As coded, most INT10 calls in video-vga.c allow the compiler to assume EAX 
>>> remains unchanged across them, which is not always the case.  This 
>>> triggers an optimisation issue that causes vga_set_vertical_end() to be 
>>> called with an incorrect number of scanlines.  Fix this by beefing up the 
>>> asm constraints on these calls.
>>>
>>> Reported-by: Marc Aurele La France <tsi@xfree86.org>
>>> Signed-off-by: Marc Aurele La France <tsi@xfree86.org>
>>> Acked-by: H. Peter Anvin <hpa@zytor.com>
>> Note: this is not in upstream since upstream is not affected due to the
>> new "BIOS glovebox" subsystem.
> 
> So it is a ".30 only" type patch?  Any older kernel versions affected?
> 

Yes, all the way back to .23 or something like that.

	-hpa

  reply	other threads:[~2009-06-30  6:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  0:07 [PATCH] x86, setup (2.6.30-stable) fix 80x34 and 80x60 console modes Marc Aurele La France
2009-06-30  1:27 ` H. Peter Anvin
2009-06-30  3:48   ` [stable] " Greg KH
2009-06-30  6:33     ` H. Peter Anvin [this message]
2009-06-30 14:01       ` [rs] " Marc Aurele La France
2009-06-30 15:43         ` Greg KH

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=4A49B1C6.9040900@kernel.org \
    --to=hpa@kernel.org \
    --cc=Research.Support@ualberta.ca \
    --cc=greg@kroah.com \
    --cc=hpa@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@ualberta.ca \
    --cc=stable@kernel.org \
    --cc=x86@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