- 17 Sep, 2004 40 commits
-
-
Andrey V. Savochkin authored
Currently metadata writing errors are ignored and not returned from sys_fsync on ext2 and ext3 filesystems. That is, at least ext2 and ext3. Both ext2 and ext3 resort to sync_inode() in their ->sync_inode method, which in turn calls ->write_inode. ->write_inode method has void type, and any IO errors happening inside are lost. Make ->write_inode return the error code? Signed-off-by:
Andrey Savochkin <saw@saw.sw.com.sg> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Andi Kleen authored
Copy ioperm bitmaps more efficiently at context switch time. Only copy upto the highest used port. Originally from Ingo Molnar Signed-off-by:
Andi Kleen <ak@muc.de> Signed-off-by:
-
Andi Kleen authored
Turn per cpu TSS into per cpu data. Signed-off-by:
-
Andi Kleen authored
Don't pass CR2 address on alignment faults. They report the address of the last page fault, which is a information leak. Fix this for i386 and x86-64 by passing 0 instead. Pointed out by Zachary Amsden <zach@vmware.com> Signed-off-by:
Andi Kleen <ak@suse.de> Signed-off-by:
-
Andi Kleen authored
Add read implies exec personality. Signed-off-by:
-
Andi Kleen authored
Sync x86-64 video.S with i386 changes Signed-off-by:
-
Andi Kleen authored
From: James Cleverdon The value that cpuinfo returns for command 1 in ebx is the physical APIC ID latched when the system comes out of reset. Ordinarily, this is identical to the value in the local APIC's ID register, because nearly all BIOSes accept the HW assigned value. Our systems, made up of individual building blocks, can't do that. Each node boots as a separate system and is joined together by the BIOS. Thus, the BIOS rewrites the local APIC ID register with a new value. Potomac and Nocona chips have a mechanism by which the BIOS writer can change bits 7:5 to match the assigned cluster ID. Bits 2:0 come from the thread ID. However, bits 4:3 are still those latched at reset. Oops! Summary: Large clustered systems can't use cpuid to derive the sibling information. Fix: Use the local APIC ID. That's the value we use to online the CPUs, so it had better be OK. For non-clustered systems, cpuid == local APIC, so nothing but large boxes should be affected. Signed-off-by:
-
Andi Kleen authored
Fix bug that caused oops with mem= on certain NUMA configurations Signed-off-by:
-
Andi Kleen authored
Add might_sleep to more *_user functions. Signed-off-by:
-
Andi Kleen authored
Print mce bank enable mask in sysfs in hex Signed-off-by:
-
Andi Kleen authored
Remove WARN_ON in smp_call_function. it breaks the machine check handling and there is no good way to enable interrupts here. Call Trace:<ffffffff8011cb33>{smp_call_function+115} <ffffffff8011cbf9>{smp_send_stop+25} <ffffffff80138012>{panic+274} <ffffffff801187e0>{do_machine_check+0} <ffffffff80118c3a>{do_machine_check+1114} <ffffffff80111663>{machine_check+127} <ffffffff803434d7>{net_rx_action+215} <EOE> <IRQ> <ffffffff8013c8e3>{__do_softirq+83} <ffffffff8013c975>{do_softirq+53} <ffffffff80113cdd>{do_IRQ+317} <<ffffffff8010f3b0>{default_idle+0} <ffffffff80110b81>{ret_from_intr+0} <EOI> <ffffffff8010f3d0>{default_idle+32} <ffffffff8010f86a>{cpu_idle+26} <ffffffff8058f886>{start_kernel+502} <ffffffff8058f1e0>{_sinittext+48 Signed-off-by: -
Andi Kleen authored
Make the x86-64 machine check handler configurable when EMBEDDED Signed-off-by:
-
Andi Kleen authored
Do IO-APIC suspend/resume. Untested so far. Signed-off-by:
-
Andi Kleen authored
Don't panic when io apic id cannot be set. Signed-off-by:
-
Andi Kleen authored
Avoid deadlock when kernel fault happens inside mmap sem. Signed-off-by:
-
Andi Kleen authored
Update x86-64 defconfig Signed-off-by:
-
Andi Kleen authored
Ported from i386 Allow to quieten apic boot output on the command line using apic={verbose,debug,quiet} Make it quiet by default Add extra #define for making apic print functions __init or not __init (for easier debugging) Signed-off-by: -
Andi Kleen authored
Make APIC errors KERN_DEBUG Signed-off-by:
-
Andi Kleen authored
Add an atomic64_t type to x86-64. Not used right now, but may be useful in the future, e.g. for rss together with C.Lameter's page fault scalability patches. Signed-off-by:
-
David Gibson authored
For historical reasons, ppc64 has ended up with two #defines for the size of a large (16M) page: LARGE_PAGE_SHIFT and HPAGE_SHIFT. This patch removes LARGE_PAGE_SHIFT in favour of the more widely used HPAGE_SHIFT. Signed-off-by:
David Gibson <dwg@au1.ibm.com> Signed-off-by:
-
Anton Blanchard authored
When I cleaned up our cmdline parsing, I missed a RELOC of CONFIG_CMDLINE itself. Without it we copy something random into cmd_line, but only when CONFIG_CMDLINE is enabled. Signed-off-by:
Anton Blanchard <anton@samba.org> Signed-off-by:
-
Anton Blanchard authored
The mace, bmac and dmasound drivers use virt_to_bus and so will not work on ppc64. Reflect this in the relevant Kconfig files. Signed-off-by:
-
Anton Blanchard authored
When a pseries+pmac kernel is built, the rtas stop-self token wasnt being initialised. Since doing this will safely fail on pmac, remove the !CONFIG_PPC_PMAC restriction Signed-off-by:
-
Anton Blanchard authored
From: Nathan Lynch <nathanl@austin.ibm.com> Fedora has a patch which introduces a new system state during boot. Change system_state == SYSTEM_BOOTING to system_state < SYSTEM_RUNNING to match it. Signed-off-by:
-
Anton Blanchard authored
yenta_socket wants probe_irq_mask, so export it. Signed-off-by:
-
Anton Blanchard authored
Remove the A() and AA() macros. Now we have compat_ptr we should be using that. Signed-off-by:
-
Benjamin Herrenschmidt authored
This patch fixes some warnings that popped up with the removal of -Wno-uninitialized around the code doing tlbie's. Signed-off-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Anton Blanchard authored
Remove some old definitions that arent relevant to us. Signed-off-by:
-
Anton Blanchard authored
Fix one compile warning and one build warning on iseries. Signed-off-by:
-
Anton Blanchard authored
Replace the mmu_context_queue structure with the idr allocator. The mmu_context_queue allocation was quite large (~200kB) so on most machines we will have a reduction in usage. We might put a single entry cache on the front of this so we are more likely to reuse ppc64 MMU hashtable entries that are in the caches. Signed-off-by:
-
Anton Blanchard authored
Implement powersave_nap sysctl, like ppc32. This allows us to disable the nap function which is useful when profiling with oprofile (to get an accurate count of idle time). Signed-off-by:
-
Anton Blanchard authored
Replace do_exit() in 64bit signal code with force_sig/force_sigsegv where appropriate. Signed-off-by:
-
Olaf Hering authored
arch/ppc/syslib/open_pic2.c: In function `init_openpic2_sysfs': arch/ppc/syslib/open_pic2.c:694: error: `ENODEV' undeclared (first use in this function) arch/ppc/syslib/open_pic2.c:694: error: (Each undeclared identifier is reported only once arch/ppc/syslib/open_pic2.c:694: error: for each function it appears in.) possible fix below. Signed-off-by:
Olaf Hering <olh@suse.de> Signed-off-by:
-
Tom Rini authored
When <linux/timex.h> started including <asm/io.h> this exposed one of the fragilities of the code in arch/ppc/boot/, namely that it is tied to the kernel headers for some information, yet not really the kernel. The following starts us in the direction of being less tied to the kernel by providing our own serial_state definition (all we care about is the ability to grab information from SERIAL_PORT_DFNS). Signed-off-by:
Tom Rini <trini@kernel.crashing.org> Signed-off-by:
-
Roland McGrath authored
Exec fails to clean up posix-timers. This manifests itself in two ways, one worse than the other. In the single-threaded case, it just fails to clear out the timers on exec. POSIX says that exec clears out the timers from timer_create (though not the setitimer ones), so it's wrong that a lingering timer could fire after exec and kill the process with a signal it's not expecting. In the multi-threaded case, it not only leaves lingering timers, but it leaks them entirely when it replaces signal_struct, so they will never be freed by the process exiting after that exec. The new per-user RLIMIT_SIGPENDING actually limits the damage here, because a UID will fill up its quota with leaked timers and then never be able to use timer_create again (that's what my test program does). But if you have many many untrusted UIDs, this leak could be considered a DoS risk. Signed-off-by:
-
Ingo Molnar authored
This uses Davide's do_general_protection() fault based io-bitmap lazy update code and combines it with the ioport-owner cache. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Ingo Molnar authored
There's one additional step we can do ontop of the ports-max code to get rid of copying in X.org's case: cache the last task that set up the IO bitmap. This means we can set the offset to invalid and keep the IO bitmap of that task, and switch back to a valid offset (without any copying) when switching back to that task. (or do a copy if there is another ioperm task we switch to.) I've attached ioport-cache-2.6.8.1.patch that implements this. When there's a single active ioperm() using task in the system then the context-switch overhead is very low and constant: # ./ioperm-latency default no ioperm: scheduling latency: 2478 cycles turning on port 80 ioperm: scheduling latency: 2499 cycles turning on port 65535 ioperm: scheduling latency: 2481 cycles This single-ioperm-user situation matches 99% of the actual ioperm() usage scenarios and gets rid of any copying whatsoever - without relying on any fault mechanism. I can see no advantage of the GPF approach over this patch. Signed-off-by:
-
Ryan S. Arnold authored
Due to the tty ldisc code not stopping write operations against a driver even after a tty has been closed I added a mechanism to hvc_console in my previous patch to prevent this by nulling out the tty->driver_data in hvc_close() but I forgot to check tty->driver_data in hvc_write(). Anton Blanchard got several oops'es from hvc_write() accessing NULL as if it were a pointer to an hvc_struct usually stored in tty->driver_data. So this patch checks tty->driver_data in hvc_write() before it is used. Hopefully once Alan Cox's patch is checked in ldisc writes won't continue to happen after tty closes. Anton Blanchard has tested this patch and is unable to reproduce the oops with it applied. Changelog: drivers/char/hvc_console.c - Added comment to hvc_close() to explain the reason for NULLing tty->driver_data. - Added check to hvc_write() to verify that tty->driver_data is valid (NOT NULL) which would be the case if the write operation was invoked after a tty close was initiated on the tty. Signed-off-by:
Ryan S. Arnold <rsa@us.ibm.com> Signed-off-by:
-
Markus Lidel authored
The I2O subsystem currently map all memory from the I2O controller for the controller's in queue, even if it is not necessary. This is a problem, because on some systems the size returned from pci_resource_len() could be 128MB and only 1-4MB is needed. Changes: - only ioremap as much memory as the controller is actually using. Signed-off-by:
-
bk://ppc.bkbits.net/for-linus-ppcLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
