- 12 Jun, 2004 16 commits
-
-
Andrew Morton authored
struct page_state is large (148 bytes) and we put them on the stack in awkward code paths (page reclaim...) So implement a simple read_page_state() which can be used to pluck out a single member from the all-cpus page_state accumulators. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Nick Piggin <nickpiggin@yahoo.com.au> Replace lots of parameters to functions in mm/vmscan.c with a structure struct scan_control. Signed-off-by: Nick Piggin <nickpiggin@yahoo.com.au> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Nick Piggin <nickpiggin@yahoo.com.au> Move the invocation of ->writepage for to-be-reclaimed pages into its own function "pageout". From: Nikita Danilov <nikita@namesys.com> with small changes from Nick Piggin Signed-off-by: Nick Piggin <nickpiggin@cyberone.com.au> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
Page reclaim bales out very early if reclaim isn't working out for !__GFP_FS allocation attempts. It was a fairly arbitrary thing in the first place and chances are the caller will simply retry the allocation or will do something which is disruptive to userspace. So remove that code and do much more scanning. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
Teach page reclaim to understand synchronous ->writepage implementations. If ->writepage completed I/O prior to returning we can proceed to reclaim the page without giving it another trip around the LRU. This is beneficial for ramdisk-backed S_ISREG files: we can reclaim the file's pages as fast as the ramdisk driver needs to allocate them and this prevents I/O errors due to OOM in rd_blkdev_pagecache_IO(). Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
NUMA-Q requires CONFIG_NUMA and CONFIG_DISCONTIGMEM to build. Cc: Martin J. Bligh <mbligh@aracnet.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> Voyager doesn't support HT, so smp_num_siblings doesn't exist. Cc: James Bottomley <James.Bottomley@SteelEye.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> Voyager doesn't compile any of the APIC or IO-APIC -related code in arch/i386/kernel/ at all -- so it's a logical impossibility that this could ever work. Cc: James Bottomley <James.Bottomley@SteelEye.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> mm/mempolicy.c: In function `verify_pages': mm/mempolicy.c:246: warning: implicit declaration of function `kmap_atomic' mm/mempolicy.c:249: warning: implicit declaration of function `kunmap_atomic' pte_offset_map() invokes kmap_atomic() via macro, without including the required header. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Andi Kleen <ak@suse.de> Originally by Juergen Kreileder, changed by me. The test for unhandled signals was wrong. Correct it. This helps Java users, who would see bogus printks in their kernel logs previously. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Arnd Bergmann <arnd@arndb.de> On s390, kmem_bufctl_t was added inside of an #ifdef, breaking 64 bit builds. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Andi Kleen <ak@suse.de> Fix more bad issues in the x86-64 machine check handler. - Actually test status after reading it from the register, not before. - Check the UC bit instead of the PCC bit to detect the bank which caused the exception. - Add tolerant==3 level for easier testing. This will avoid any panics. - Don't threat bank overflows as fatal - they must have come from a non fatal exception, which should not cause a panic. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Bruno Ducrot <poup@poupinou.org> I'm trying to replace for_each_cpu() with for_each_cpu_mask() in arch/i386/kernel/cpu/cpufreq/p4-clockmod.c Unfortunately, though, davej pointed me that for_each_cpu_mask() is not defined in -bk if CONFIG_SMP is not defined. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andi Kleen authored
Discard FPU exceptions in exit and execve on x86-64 too. Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Linus Torvalds authored
sparse tokenizes everything. Including #include directives. Which means that it doesn't want to see "//" in a include filename, since that's a comment outside of a string. And inside of a string it's too dark to read.
-
Linus Torvalds authored
We need to clear all exceptions before synchronizing with the FPU, since we aren't ready to handle a FP exception here and we're getting rid of all FP state. Special thanks to Alexander Nyberg for reports and testing. Alternate patches by Sergey Vlasov and Andi Kleen, who both worked on this. Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
- 10 Jun, 2004 4 commits
-
-
bk://linux-ntfs.bkbits.net/ntfs-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Anton Altaparmakov authored
- Modify fs/ntfs/ntfs_readdir() to copy the index root attribute value to a buffer so that we can put the search context and unmap the mft record before calling the filldir() callback. We need to do this because of NFSd which calls ->lookup() from its filldir callback() and this causes NTFS to deadlock as ntfs_lookup() maps the mft record of the directory and since ntfs_readdir() has got it mapped already ntfs_lookup() deadlocks. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
-
Anton Altaparmakov authored
into cantab.net:/home/src/ntfs-2.6
-
-
- 12 Jun, 2004 2 commits
-
-
-
Dave Airlie authored
and/or d->send_sizes. When these functions are called from gamma_dma, these pointers are user pointers and are thus not safe to deref. This patch copies over the pointers inside gamma_dma_priority and gamma_dma_send_buffers. Submitted-by: Robert T. Johnson <rtjohnso@eecs.berkeley.edu> Signed-off-by: Dave Airlie <airlied@linux.ie>
-
- 10 Jun, 2004 2 commits
-
-
Jens Axboe authored
This bug took forever to debug (just ask Ben :-). When we move the completion event from the failed request to the sense request, we risk either the initial complete and then later complete on a long gone ->waiting. I think this business of moving the completion structure to the request sense is a bit bogus and always has been, and the bug is fixed nicely by just rewriting this logic a bit. So instead we simply unconditionally dequeue the failed request (regardless of whether it was REQ_PC or REQ_BLOCK_PC), and pass a reference to it in the sense request. When the sense completes, we call end io on the originally failed request (which does the complete() etc). Signed-off-by: Jens Axboe <axboe@suse.de> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Geert Uytterhoeven authored
-
- 09 Jun, 2004 16 commits
-
-
Anton Altaparmakov authored
into cantab.net:/home/src/ntfs-2.6
-
Dave Airlie authored
With the old DRM interface, the devname was set in DRM(setunique), but with the current DRM interface >=1.1 the devname is not being set in DRM(set_busid). From: Alan Swanson Approved-by: Dave Airlie <airlied@linux.ie>
-
bk://kernel.bkbits.net/davem/sparc-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
David S. Miller authored
-
Andrew Morton authored
Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: David S. Miller <davem@redhat.com>
-
David S. Miller authored
into nuts.davemloft.net:/disk1/BK/sparc-2.6
-
Oleg Nesterov authored
dup_mmap() unnecessarily tries to account for memory of the vma's it has created if it fails in the middle. However, that's pointless (and wrong), since the exit_mmap() path called through mmput() will do so anyway in the failure path. Just remove the bogus un-accounting code.
-
bk://cifs.bkbits.net/linux-2.5cifsLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Randy Dunlap authored
Add __user annotations to kernel/sysctl.c to satisfy sparse for !CONFIG_SYSCTL, !CONFIG_PROC_FS. Signed-off-by: Randy Dunlap <rddunlap@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Linus Torvalds authored
It puts two 2kB temp areas on the stack, which is guaranteed to overflow a 4kB stack if that path is ever taken. Both marked in the source, and both should be easy to fix but need testing. Found by Jörn Engel.
-
Andrew Morton authored
From: Herbert Xu <herbert@gondor.apana.org.au> The recent change to vga16fb's memory mapping that you partially reverted is still broken. In particular, it's setting fix.mem_start to a virtual address on i386. The value of fix.mem_start is meant to be physical. We could simply apply virt_to_phys to it, but somehow I doubt that is what it's meant to do on arm. So until we hear from someone who knows how it works on arm, let's just revert this change. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
Randy Dunlap <rddunlap@osdl.org> points out that sparse warns about the test of an undefined preprocessor identifier. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Andy Whitcroft <apw@shadowen.org> The sysctl interfaces for updating the uts entries such as hostname and domainname are using the wrong length for these buffers; they are hard coded to 64. Although safe, this artifically limits the size of these fields to one less than the true maximum. This generates an inconsistency between the various methods of update for these fields. # hostname 12345678901234567890123456789012345678901234567890123456789012345 hostname: name too long # hostname 1234567890123456789012345678901234567890123456789012345678901234 # hostname 1234567890123456789012345678901234567890123456789012345678901234 # sysctl -w kernel.hostname=1234567890123456789012345678901234567890123456789012345678901234567890 kernel.hostname = 1234567890123456789012345678901234567890123456789012345678901234567890 # hostname 123456789012345678901234567890123456789012345678901234567890123 # The error originates from the fact the handler for strings (proc_dostring) already allows for the string terminator. This patch corrects the limit, taking the oppotunity to convert to use of sizeof(). Signed-off-by: Andy Whitcroft <apw@shadowen.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: john stultz <johnstul@us.ibm.com> In testing for SLES9, we ran across a bug caused by userspace apps poking the PIT which caused bad values to be read by the kernel. This would then trigger the lost tick detection code with insane values and would then break the SCSI subsystem. This patch includes the PIT sanity check from the TSC timesource into the cyclone timesource code, which catches the bad case described above and resolves the issue. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: "Anil" <anil.s.keshavamurthy@intel.com> We don't need lock_cpu_hotplug()/unlock_cpu_hotplug for singlethreaded workqueues. Signed-off-by: Anil Keshavamurthy <anil.s.keshavamurthy@intel.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Martin Schwidefsky <schwidefsky@de.ibm.com> This patch adds support for 6 system call arguments on s390. The first exploiter of this will be the sys_futex system call for the FUTEX_CMP_REQUEUE operation. The idea is simple: use register %r7 for the 6th argument. This can be extended to 7/8/9/... arguments if there ever will be the need for it. To call the system call function in the kernel the additional arguments needs to get stored on the stack. 8 bytes are added to the head of struct pt_regs. %r7 is stored to the additional field for all system calls. The store is hidden in a address-generation-interlock slot, it doesn't slow down the system call path. Signed-off-by: Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-