Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

From: Michael Matz

Subject: Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI wrt direction flag

Date: Wednesday, March 5, 2008 - 2:59 pm

Hi,

On Wed, 5 Mar 2008, Chris Lattner wrote:

quoted text> 
> On Mar 5, 2008, at 1:34 PM, H. Peter Anvin wrote:
> 
> >Richard Guenther wrote:
> > >We didn't yet run into this issue and build openSUSE with 4.3 since more
> > >than
> > >three month.
> >
> >Well, how often do you take a trap inside an overlapping memmove()?
> 
> How hard is it to change the kernel signal entry path from "pushf" to
> "pushf;cld"?  Problem solved, no?

The problem is with old kernels, which by definition stay unfixed.


Ciao,
Michael.
--
unsubscribe noticeTo unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., Michael Matz, (Wed Mar 5, 2:59 pm)

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., Adrian Bunk, (Wed Mar 5, 3:13 pm)

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., David Miller, (Wed Mar 5, 3:21 pm)

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., Olivier Galibert, (Wed Mar 5, 4:13 pm)

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., Chris Lattner, (Wed Mar 5, 5:36 pm)

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., H. Peter Anvin, (Wed Mar 5, 5:47 pm)

Re: RELEASE BLOCKER: Linux doesn't follow x86/x86-64 ABI w ..., Aurelien Jarno, (Wed Mar 5, 5:49 pm)


linux-kernel:
Rafael J. Wysocki	[Bug #16136] Linux 2.6.34 causes system lockup on Compaq Presario 2200 Laptop
Joerg Roedel	Re: [patch] dma-debug: off by one issue
Tetsuo Handa	Re: [AppArmor #7 0/13] AppArmor security module
Pekka Enberg	Re: BUG in free_block (tainted)
Jakub Narebski	Re: [PATCH] gitweb: Fix shortlog only showing HEAD revision.
git:
Christian Stimming	git-gui: Fix broken revert confirmation.
Johannes Schindelin	Re: [PATCH 2/2] git-svn: support fetch with autocrlf on
Mark Burton	Re: [PATCH] builtin-branch: highlight current remote branches with an asterisk
Junio C Hamano	Re: git-svnimport
Junio C Hamano	Re: [PATCH 6/6] Teach core object handling functions about gitlinks
linux-netdev:
Nick Piggin	Re: Kernel WARNING: at net/core/dev.c:1330 __netif_schedule+0x2c/0x98()
Daniel Lezcano	getsockopt(TCP_DEFER_ACCEPT) value change
David Miller	Re: 2.6.27.18: bnx2/tg3: BUG: "scheduling while atomic" trying to ifenslave a seco...
Amit Kumar Salecha	[PATCH NEXT 10/10] qlcnic: add cksum flag
Patrick McHardy	Re: [PATCH RESEND 1/3] netfilter: xtables: inclusion of xt_condition
git-commits-head:
Linux Kernel Mailing List	ath9k_htc: Allocate URBs properly
Linux Kernel Mailing List	ath9k: Added get_survey callback in order to get channel noise
Linux Kernel Mailing List	ALSA: snd-usb-caiaq: Do not expose hardware input mode 0 of A4DJ
Linux Kernel Mailing List	cpumask: make irq_set_affinity() take a const struct cpumask
Linux Kernel Mailing List	V4L/DVB (9041): Add support YUAN High-Tech STK7700D (1164:1f08)
openbsd-misc:
Conor	Re: RFID Reader
Josh Grosse	ssh/sshd challenge-response seems to have stopped working in -current
Stuart Henderson	Re: SquidGuard problem
Henning Brauer	Re: 3ware hardware raid support?
Ryan McBride	Re: Packets Per Second Limit?