- 02 Feb, 2005 37 commits
-
-
Mark A. Greer authored
824x and 107 bridges from Freescale/Tundra have an erratum where speculative PCI reads may return stale data. One of the two documented workarounds is to turn of speculative PCI reads. This patch does that. Signed-off-by:
Mark A. Greer <mgreer@mvista.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Akinobu Mita authored
This is oprofile timer-mode fallback fix for ppc. Signed-off-by:
Akinobu Mita <amgta@yacht.ocn.ne.jp> Signed-off-by:
-
Benjamin Herrenschmidt authored
The Pegasos machines have the VIA IDE controller configured in a strange way by the firmware. It claims to be fully native, but is actually routed to legacy irqs 14 and 15. This patch works around that in the driver. In the future, I'll try to do an ifdef-less patch by detecting that setup from the chip, and using the new pci_get_legacy_ide_irq() in that case, but I don't have proper HW infos. This patch is good enough in the meantime, I'll come up with a better one later eventually. Signed-off-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Acked-by:
Bartlomiej Zolnierkiewicz <bzolnier@elka.pw.edu.pl> Signed-off-by:
-
Matt Porter authored
Adds support for the STx GP3 board with an MPC8560. Thanks to Dan Malek for the original 2.4 port. Signed-off-by:
Matt Porter <mporter@kernel.crashing.org> Signed-off-by:
-
Albert Herranz authored
Fix a compilation warning due to a duplicate definition of MMCR0_PMXE. The definition comes in perfctr-ppc.patch, but was recently introduced too in Linus tree. Signed-off-by:
-
Mark A. Greer authored
This patch updates the cpci690 platform file. The platform file now uses the platform_notify hook to update platform_data. Signed-off-by:
-
Mark A. Greer authored
This patch updates the support for the ev64260 eval platform from Marvell. It: - uses the platform_notify hook to update platform_data - fixes a bug where a window to a device is disabled instead of enabled - does some misc fixups Signed-off-by:
-
Mark A. Greer authored
This patch updates support for the katana 750i, 752i, and 3750. It: - supports more bus frequencies - uses platform_notify hook to update platform_data entries - does some misc cleanup Signed-off-by:
-
Benjamin Herrenschmidt authored
This patch updates the PowerMac sleep support. The ability to sleep is now broken into 2 different flags, one, "may sleep" is set for all motherboards that we know how to put to sleep and wakeup. It gets turned into "can sleep" upon a call from the video driver indicating the ability to wakeup the video card. This doesn't deal with head-less machines, but this can be improved later. It also adds better cache flush code, which improves stability with cpufreq as well as sleep. This patch actually breaks sleep support until the video drivers for the affected machines have been updated. This will come as separate patches. Signed-off-by:
-
Mark A. Greer authored
This patch briges the mv64x60 related code up to the latest that I have. It: - adds MPSC support to some ppc bootwrapper files - adds an erratum workaround for the mv64460 - changes some platform_data related structure names - cleans up a bunch of whitespace Signed-off-by:
-
Matthew Wilcox authored
__get_free_pages() calls alloc_pages, finds the page_address() and throws away the struct page *. Slab then calls virt_to_page to get it back again. Much more efficient for slab to call alloc_pages itself, as well as making the NUMA and non-NUMA cases more similarr to each other. Signed-off-by:
Matthew Wilcox <matthew@wil.cx> Signed-off-by:
Manfred Spraul <manfred@colorfullife.com> Signed-off-by:
-
Christoph Lameter authored
This patch adds a new function alloc_zeroed_user_highpage that is then used in the anonymous page fault handler and in the COW code to allocate zeroed pages. The function can be defined per arch to setup special processing for user pages by defining __HAVE_ARCH_ALLOC_ZEROED_USER_PAGE. For arches that do not need to do special things for user pages, alloc_zeroed_user_highpage is defined to simply do alloc_page_vma(GFP_HIGHUSER | __GFP_ZERO, vma, vaddr) This patch needs to update a number of archs. Wish there was a better way to do this. Signed-off-by:
Christoph Lameter <clameter@sgi.com> Signed-off-by:
-
Andrea Arcangeli authored
Convert the unsafe signed (16bit) used_math to a safe and optimal PF_USED_MATH I might have broken arm, see the very first change in the patch to asm-offsets.c, rest looks ok at first glance. If you want used_math to return 0 or 1 (instead of 0 or PF_USED_MATH), just s/!!// in the below patch and place !! in sched.h::*used_math() accordingly after applying the patch, it should work just fine. Using !! only when necessary as the below is optimal. From: Yoichi Yuasa <yuasa@hh.iij4u.or.jp> This patch had fixed restore_sigcontext/restore_sigcontext32 about MIPS. Signed-off-by:
Yoichi Yuasa <yuasa@hh.iij4u.or.jp> Signed-off-by:
Andrea Arcangeli <andrea@suse.de> Signed-off-by:
-
Andrea Arcangeli authored
This makes memdie a TIF_MEMDIE. memdie will not be modified by the current task, so it cannot be a PF_MEMDIE but it must be a TIF_MEMDIE. Signed-off-by:
-
Andrea Arcangeli authored
Fix several oom killer bugs, most important avoid spurious oom kills badness algorithm tweaked by Thomas Gleixner to deal with fork bombs This is the core of the oom-killer fixes I developed partly taking the idea from Thomas's patches of getting feedback from the exit path, plus I moved the oom killer into page_alloc.c as it should to be able to check the watermarks before killing more stuff. This also tweaks the badness to take thread bombs more into account (that change to badness is from Thomas, from my part I'd rather rewrite badness from scratch instead, but that's an orthgonal issue ;). With this applied the oom killer is very sane, no more 5 sec waits and suprious oom kills. Signed-off-by:
-
Andrea Arcangeli authored
- Rename various fields related to the lower-zone protection code to sync up with 2.4. - Remove the automatic determination of the values of the per-zone protection levels from a single tunable. Replace this with a simple per-zone sysctl. Signed-off-by:
-
Andrea Arcangeli authored
With <garloff@suse.de> This is protect-pids, a patch to allow the admin to tune the oom killer. The tweak is inherited between parent and child so it's easy to write a wrapper for complex apps. I made used_math a char at the light of later patches. Current patch breaks alpha, but future patches will fix it. Signed-off-by:
-
Michael Marineau authored
Signed-off-by:
Michael Marineau <marineam@gentoo.org> Cc: Vojtech Pavlik <vojtech@suse.cz> Signed-off-by:
-
Darrick Wong authored
With Suparna Bhattacharya <suparna@in.ibm.com> I was running a random system call generator against mainline the other day and got this bug report about AIO in dmesg: kernel BUG at fs/aio.c:1249! Each ioctx structure has a "users" field that acts as a reference counter for the ioctx, and a "dead" flag that seems to indicate that the ioctx isn't associated with any particular list of IO requests. The problem, then, lies in aio.c:1247. The io_destroy function checks the (old) value of the dead flag--if it's false (i.e. the ioctx is alive), then the function calls put_ioctx to decrease the reference count on the assumption that the ioctx is no longer associated with any requests. Later, it calls put_ioctx again, on the assumption that someone called lookup_ioctx to perform some operation at some point. This BUG is caused by the reference counts being off. The testcase that I provided looks for a chunk of user memory that's read-only and passes that to the sys_io_setup syscall. sys_io_setup checks that the pointer is readable, creates the ioctx and then tries to write the ioctx handle back to userland. This is where the problems start to surface. Since the pointer points to a non-writable region of memory, the write fails. The syscall handler then destroys the ioctx. The dead flag is zero, so io_destroy calls put_ioctx...but wait! Nobody ever put the ioctx into a request list. The ioctx is alive but not in a list, yet the io_destroy code assumes that being alive implies being in a request list somewhere. Hence, calling put_ioctx is bogus; the reference count becomes 0, and the ioctx is freed. Worse yet, put_ioctx is called again (on a freed pointer!) to clear up the lookup_ioctx that never happened. put_ioctx sees that the reference count has become negative and BUGs. Suparna's patch simply takes that additional ref so that io_destroy() will dtrt. Signed-off-by:
Darrick Wong <djwong@us.ibm.com> Signed-off-by:
-
John W. Linville authored
Signed-off-by:
-
Benjamin Herrenschmidt authored
Here's an updated version of the pegasos support patch for ppc32, fixing a typo in the previous one. Driver patches to come soon. Signed-off-by:
-
Kumar Gala authored
Back out previous patch to ppc idle that handled CPU's that did not have powersavings. Ingo's fixes to cpu_rest, cause this fix to no longer be needed. Signed-off-by:
Kumar Gala <kumar.gala@freescale.com> Signed-off-by:
-
Ingo Molnar authored
It's not necessary to keep IRQs disabled after the BKL has been dropped. In fact i think IRQ-disabling doesnt have to be done at all, the patch below ought to solve this scenario equally well, and should solve the PPC side-effects too. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Mike Waychison authored
Fix up signal_pending and timeout paths for wait_for_completion API extensions. Signed-off-by:
Mike Waychison <michael.waychison@sun.com> Acked-by:
-
Chris Wright authored
Some minor cleanups for audit_log_lost() messages. Signed-off-by:
Chris Wright <chrisw@osdl.org> Signed-off-by:
-
Chris Wright authored
When auditd is congested the kernel's audit system leaks skb's. First, it takes them off the audit_buffer sklist at which point they are lost, second, it allocates a new skb with 0 length payload. Then (likely still congested), it repeats this losing the new skb. Plug the leak by making sure to requeue the skb, and avoid audit_log_move() on 0 len audit_buffer. Signed-off-by:
-
Randy Dunlap authored
Need 'irq_affinity' array when CONFIG_PROC_FS=n. With CONFIG_PROC_FS=n, the irq_affinity[NR_IRQS] array is not available in arch/i386/kernel code: arch/i386/kernel/built-in.o(.text+0x10037): In function `do_irq_balance': : undefined reference to `irq_affinity' arch/i386/kernel/built-in.o(.text+0x101a9): In function `do_irq_balance': : undefined reference to `irq_affinity' Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Acked-by:
-
Jan Kara authored
Fix a subtle bug in error handling of ext2 xattrs. When ext2_sync_inode() fails because of ENOSPC (it could not write inode's dirty data) we want to keep xattrs in a consistent state and release the old block properly. Signed-off-by:
Jan Kara <jack@suse.cz> Signed-off-by:
-
Matt Mackall authored
Zwane reports an oops duie to add_entropy_words running off the top of the stack reading its input. The overrun is harmless until it causes a page fault. Looks like I introduced this bug in Aug 2003, but it was hard to trigger until the recent changes. Signed-off-by:
Matt Mackall <mpm@selenic.com> Signed-off-by:
-
Prasanna Meda authored
Looks like we fixed only part of the problem earlier. When the child moves away from ptrace notify and resets the last_siginfo, sighand lock helps. But if the child goes further in exit and releases the sighand, we need to test that case too. See ptrace_check_attach() and exit_sighand(). They also use the tasklist_lock. Followed Roland's suggestions on lock primitive and struct assignment. Signed-Off-by:
Prasanna Meda <pmeda@akamai.com> Signed-off-by:
-
James Morris authored
Looks like a cleanup broke the test vectors: http://linux.bkbits.net:8080/linux-2.5/gnupatch@41ad5cd9EXGuUhmmotTFBIZdIkTm0ASigned-off-by:
James Morris <jmorris@redhat.com> Signed-off-by:
-
Manish Lachwani authored
include/linux/kobject.h: In function `to_kset': include/linux/kobject.h:116: warning: implicit declaration of function `container_of' Signed-off-by:
Manish Lachwani <mlachwani@mvista.com> Cc: Greg KH <greg@kroah.com> Signed-off-by:
-
Serge Hallyn authored
2.6.11-rc2-bk5 introduces two syntax errors under drivers/char/ftape. The following patch replaces ");" at the end of two printks which were accidentally removed. Signed-off-by:
Serge Hallyn <serue@us.ibm.com> Signed-off-by:
-
Andrew Morton authored
drivers/serial/8250_pnp.c: In function `serial_pnp_probe': drivers/serial/8250_pnp.c:424: warning: cast to pointer from integer of different size drivers/serial/8250_pnp.c: In function `serial_pnp_remove': drivers/serial/8250_pnp.c:431: warning: cast from pointer to integer of different size Cc: Russell King <rmk@arm.linux.org.uk> Cc: Adam Belay <ambx1@neo.rr.com> Signed-off-by:
-
Andrew Morton authored
mm/memory.c: In function `clear_page_range': mm/memory.c:185: warning: suggest parentheses around + or - inside shift Signed-off-by:
-
Andrew Morton authored
nodemask.h wants find_next_zero_bit() to take a const address. Fix that up and modify find_next_bit() to suit. (These functions seem too big to be inlined...) Cc: Richard Henderson <rth@twiddle.net> Signed-off-by:
-
Ingo Molnar authored
With Joe Perches <joe@perches.com> Signed-off-by:
-
- 30 Jan, 2005 3 commits
-
-
bk://linux-acpi.bkbits.net/to-linusLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Len Brown authored
into intel.com:/home/lenb/src/26-latest-dev
-
