- 09 Jan, 2003 22 commits
-
-
David S. Miller authored
-
Stephen Rothwell authored
-
David S. Miller authored
-
David S. Miller authored
-
Rob Radez authored
-
http://linux-acpi.bkbits.net/linux-acpiLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Andy Grover authored
-
Linus Torvalds authored
-
bk://bk.arm.linux.org.ukLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Russell King authored
-
Luca Barbieri authored
This patch, which depends on the previous %ebx -> %ebp patch, removes all pop instruction in the sysenter return path. This leaks the thread_info address to user mode but this shouldn't be a security problem. This is what happens to the various registers: %eax: return value from system call: already in place %ebx, %esi, %edi: saved by the C compiler %ecx, %edx, %ebp: restored by user mode, fixed values by kernels %esp, eip: copied to %ecx/%edx and restored by sysexit %ds, %es: initialized to __USER_DS on kernel entry %cs, %ss: restored by sysexit based on msr %fs, %gs: not modified by the kernel (saved around context switch) eflags: not preserved, iopl saved around context switch FP, XMM: any code that modifies them must save/restore them Note that while it is possible to change %ebx, %esi, %edi, %ecx, %edx or %ebp via struct pt_regs, anything that does should set TIF_IRET or another work flag (and it hopefully already does).
-
Luca Barbieri authored
This patch changes assembly code that accesses thread_info to use %ebp rather than %ebx. This allows me to take advantage of the fact that %ebp is restored by user mode in the sysenter register pop removal patch. vm86() direct return code updated to match [ Linus ]
-
bk://bk.arm.linux.org.ukLinus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
bk://linuxusb.bkbits.net/linus-2.5Linus Torvalds authored
into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux
-
Andy Grover authored
into groveronline.com:/root/bk/linux-acpi
-
Greg Kroah-Hartman authored
-
bk://ppc.bkbits.net/for-linus-ppcLinus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
Paul Mackerras authored
This also cleans up the machine check code generally.
-
Paul Mackerras authored
-
bk://68.0.152.218/linux-2.5-miscPaul Mackerras authored
into samba.org:/home/paulus/kernel/for-linus-ppc
-
bk://kernel.bkbits.net/davem/sparc-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
bk://kernel.bkbits.net/davem/net-2.5Linus Torvalds authored
into home.transmeta.com:/home/torvalds/v2.5/linux
-
- 08 Jan, 2003 18 commits
-
-
Russell King authored
Supply the old termios, along with the max and min acceptable baud rate to uart_get_baud_rate(). uart_get_baud_rate() will now try to find a baud rate that satisfies the max and min constraint out of (requested rate, old rate, 9600 baud). We remove the code which performed a similar act in uart_get_divisor() and pass an appropriate min and max baud rate to uart_get_baud_rate() based on the UART clock rate.
-
Russell King authored
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/sparc-2.5
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.5
-
David S. Miller authored
-
David S. Miller authored
-
Oskar Andreasson authored
-
James Morris authored
-
David S. Miller authored
-
James Morris authored
- Merged AES code from Adam J. Richter <adam@yggdrasil.com> - Add kconfig help and test vector code from Martin Clausen <martin@ostenfeld.dk> - Minor cleanups: removed EXPORT_NO_SYMBOLS (not needed for 2.5), removed debugging code etc. - Documentation updates.
-
James Morris authored
-
Greg Kroah-Hartman authored
into kroah.com:/home/linux/linux/BK/gregkh-2.5
-
Linus Torvalds authored
-
Dave Jones authored
-
Dave Jones authored
Since we killed off the broken 486 strings copies, the config item isn't needed any longer.
-
Dave Jones authored
Next in line for the -W cleanups is this patch from Willy which I've been carrying since 2.5.29 or so. Should be no functional differences, just no more warnings when we compile with -W
-
Dave Jones authored
s/boundry/boundary/
-
Dave Jones authored
-