linux-toradex.git/arch, branch v2.6.22.8

[PATCH] x86_64: Zero extend all registers after ptrace in 32bit entry path.

2007-09-21T22:38:11+00:00

Strictly it's only needed for eax.

It actually does a little more than strictly needed -- the other registers
are already zero extended.

Also remove the now unnecessary and non functional compat task check
in ptrace.

This is CVE-2007-4573

Found by Wojciech Purczynski

Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds 
Signed-off-by: Chris Wright

SPARC64: Fix sparc64 PCI config accesses on sun4u

2007-08-31T06:01:51+00:00

[SPARC64]: Fix sun4u PCI config space accesses on sun4u.

Don't provide fake PCI config space for sun4u.

Also, put back the funny host controller space handling that
at least Sabre needs.  You have to read PCI host controller
registers at their nature size otherwise you get zeros instead
of correct values.

Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

SPARC64: Fix sparc64 task stack traces.

2007-08-31T06:01:51+00:00

It didn't handle that case at all, and now dump_stack()
can be implemented directly as show_stack(current, NULL)

Signed-off-by: David S. Miller 
Signed-off-by: Greg Kroah-Hartman

i386: fix lazy mode vmalloc synchronization for paravirt

2007-08-31T06:01:01+00:00

Found this looping Ubuntu installs with VMI.

If unlucky enough to hit a vmalloc sync fault during a lazy mode
operation (from an IRQ handler for a module which was not yet populated
in current page directory, or from inside copy_one_pte, which touches
swap_map, and hit in an unused 4M region), the required PDE update would
never get flushed, causing an infinite page fault loop.

This bug affects any paravirt-ops backend which uses lazy updates, I
believe that makes it a bug in Xen, VMI and lguest.  It only happens on
LOWMEM kernels.


Touching vmalloc memory in the middle of a lazy mode update can generate a
kernel PDE update, which must be flushed immediately.  The fix is to leave
lazy mode when doing a vmalloc sync.

Signed-off-by: Zachary Amsden 
Cc: Andi Kleen 
Cc: Jeremy Fitzhardinge 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

uml: fix previous request size limit fix

2007-08-31T06:01:01+00:00

The previous patch which limited the number of sectors in a single request
to a COWed device was correct in concept, but the limit was implemented in
the wrong place.

By putting it in ubd_add, it covered the cases where the COWing was
specified on the command line.  However, when the command line only has the
COW file specified, the fact that it's a COW file isn't known until it's
opened, so the limit is missed in these cases.

This patch moves the sector limit from ubd_add to ubd_open_dev.

Signed-off-by: Jeff Dike 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

i386: Fix double fault handler

2007-08-22T23:23:27+00:00

The new percpu code has apparently broken the doublefault handler
when CONFIG_DEBUG_SPINLOCK is set. Doublefault is handled by
a hardware task, making the check

        SPIN_BUG_ON(lock->owner == current, lock, "recursion");

fault because it uses the FS register to access the percpu data
for current, and that register is zero in the new TSS. (The trace
I saw was on 2.6.20 where it was GS, but it looks like this will
still happen with FS on 2.6.22.)

Initializing FS in the doublefault_tss should fix it.

AK: Also fix broken ptr_ok() and turn printks into KERN_EMERG
AK: And add a PANIC prefix to make clear the system will hang
AK: (e.g. x86-64 will recover)

Signed-off-by: Chuck Ebbert 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

i386: Handle P6s without performance counters in nmi watchdog

2007-08-22T23:23:27+00:00

I got an oops while booting a 32bit kernel on KVM because it doesn't
implement performance counters used by the NMI watchdog. Handle this
case.


Cc: Avi Kivity 
Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

x86_64: Change PMDS invocation to single macro

2007-08-22T23:23:26+00:00

Very old binutils (2.12.90...) seem to have trouble with newlines
in assembler macro invocation. They put them into the resulting
argument expansion. In this case this lead to a parse error because
a .rept expression ended up spread over multiple lines. Change the PMDS()
invocation to a single line.

Signed-off-by: Andi Kleen 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

x86_64: Check for .cfi_rel_offset in CFI probe

2007-08-22T23:23:26+00:00

Very old binutils have .cfi_startproc/endproc, but
no .cfi_rel_offset. Check for .cfi_rel_offset too.

Cc: Jan Beulich 
Cc: Sam Ravnborg 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

i386: allow debuggers to access the vsyscall page with compat vDSO

2007-08-22T23:23:26+00:00

From: Jan Beulich 
Signed-off-by: Jan Beulich 
Signed-off-by: Andi Kleen 
Signed-off-by: Greg Kroah-Hartman