- 28 Oct, 2004 40 commits
-
-
Olaf Hering authored
__handle_sysrq already prints a newline, so the action_msg string doesnt need yet another newline. Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Gerd Knorr authored
- Make bttv check the device_register return value. - Yet another unchecked return value fixed. Signed-off-by:
Gerd Knorr <kraxel@bytesex.org> Signed-off-by:
-
Jens Axboe authored
There are two issues with online io scheduler switching that this patch addresses. The first is pretty simple - it concerns racing with scheduler removal on switch. elevator_find() does not grab a reference to the io scheduler, so before elevator_attach() is run it could go away. Add elevator_get() to solve that. Second issue is the flushing out of requests that is needed before switching can be problematic with requests that aren't allocated in the block layer (such as requests on the stack of a process). The problem is that we don't know when they will have finished, and most io schedulers need to access the elevator structures on io completion. This can be fixed by adding an intermedia step that switches to noop, since it doesn't need to touch anything but the request_queue. The queue drain can then safely be split into two operations - one that waits for file system requests, and one that waits for the queue to completely empty. Requests arriving after the first drain will get stuck in a seperate queue list. Signed-off-by:
Jens Axboe <axboe@suse.de> Signed-off-by:
-
Manfred Spraul authored
register_sysctl_table() fails if sysctl support is not compiled into the kernel. The POSIX message queue subsystem aborted it's initialization if register_sysctl_table() fails, and that causes an oops in sys_mq_open(). The patch fixes that by ignoring failures from register_sysctl_table(). Signed-off-by; Manfred Spraul <manfred@colorfullife.com> Signed-off-by:
Adrian Bunk <bunk@stusta.de> Signed-off-by:
-
Jens Axboe authored
Fix online switching issue with cfq v2. It does deferred clearing of e->elevator_data, which screws up the current io scheduler. It does not have to, so just remove it. Signed-off-by:
-
William Lee Irwin III authored
These two variables are long, long dead. This patch removes them. Signed-off-by:
William Irwin <wli@holomorphy.com> Signed-off-by:
-
Colin Leroy authored
This patch fixes via-pmu.c compilation when CONFIG_PMAC_PBOOK is not set. Looks like the #endif was one line too late. Signed-off-by:
Colin Leroy <colin@colino.net> Acked-by:
Benjamin Herrenschmidt <benh@kernel.crashing.org> Signed-off-by:
-
Christoph Hellwig authored
It's been totally obsoleted by the input layer Acked-by:
Alan Cox <alan@redhat.com> Signed-off-by:
-
Christoph Hellwig authored
This was used by the early irqstacks implementation on s390 and has been replaced by __ARCH_HAS_DO_SOFTIRQ now. Signed-off-by:
-
Christoph Hellwig authored
module_attribute.show is defined to return ssize_t Signed-off-by:
-
Thomas Gleixner authored
To make spinlock/rwlock initialization consistent all over the kernel, this patch converts explicit lock-initializers into spin_lock_init() and rwlock_init() calls. Currently, spinlocks and rwlocks are initialized in two different ways: lock = SPIN_LOCK_UNLOCKED spin_lock_init(&lock) rwlock = RW_LOCK_UNLOCKED rwlock_init(&rwlock) this patch converts all explicit lock initializations to spin_lock_init() or rwlock_init(). (Besides consistency this also helps automatic lock validators and debugging code.) The conversion was done with a script, it was verified manually and it was reviewed, compiled and tested as far as possible on x86, ARM, PPC. There is no runtime overhead or actual code change resulting out of this patch, because spin_lock_init() and rwlock_init() are macros and are thus equivalent to the explicit initialization method. Signed-off-by:
Thomas Gleixner <tglx@linutronix.de> Acked-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Thomas Gleixner authored
To make spinlock/rwlock initialization consistent all over the kernel, this patch converts explicit lock-initializers into spin_lock_init() and rwlock_init() calls. Currently, spinlocks and rwlocks are initialized in two different ways: lock = SPIN_LOCK_UNLOCKED spin_lock_init(&lock) rwlock = RW_LOCK_UNLOCKED rwlock_init(&rwlock) this patch converts all explicit lock initializations to spin_lock_init() or rwlock_init(). (Besides consistency this also helps automatic lock validators and debugging code.) The conversion was done with a script, it was verified manually and it was reviewed, compiled and tested as far as possible on x86, ARM, PPC. There is no runtime overhead or actual code change resulting out of this patch, because spin_lock_init() and rwlock_init() are macros and are thus equivalent to the explicit initialization method. Signed-off-by:
-
Pawel Sikora authored
Signed-off-by:
-
James Nelson authored
Description: Cleanup and update to Documentation/ftape.txt Signed-off by: James Nelson <james4765@gmail.com> Signed-off-by:
-
James Nelson authored
After tracking down the original author of the ftape sources, I found out that he no longer had interest in maintaining it. Signed-off-by:
James Nelson <james4765@gmail.com> Signed-off-by:
-
Werner Almesberger authored
Allow the buffer_foo() predicates to take a (const struct buffer_head *). I've checked that the argument of test_bit is indeed "const" on all architectures. Signed-off-by:
Werner Almesberger <werner@almesberger.net> Signed-off-by:
-
Jesper Juhl authored
Add a bunch of entries to Documentation/00-INDEX that are currently missing (and removes the entry for one file that no longer exist). Patch has already been OK'ed by Paul G. Signed-off-by:
Jesper Juhl <juhl-lkml@dif.dk> Signed-off-by:
-
Peter Osterlund authored
cdrom_is_mrw() can incorrectly think that a drive is Mt Rainier capable, because if forgets to check if the "GET CONFIGURATION" command returns the MRW feature number. According to the MMC spec, the drive shall return all feature numbers >= the starting feature number, so even if the drive doesn't support Mt Rainier, it can return some data that makes cdrom_is_mrw() incorrectly think the drive is MRW capable. This problem stops me from mounting DVD+RW discs in R/W mode on my laptop, because it makes cdrom_open_write() call cdrom_mrw_open_write() which fails because the drive isn't really MRW capable. The fix is to make sure the returned feature number is the correct one for Mt Rainier. Signed-off-by:
Peter Osterlund <petero2@telia.com> Acked-by:
-
Arjan van de Ven authored
add_timer_on() isn't used by modules (in fact it's only used ONCE, in workqueue.c) and it's not even a good api for drivers, in fact, the comment for it says * This is not very scalable on SMP. Double adds are not possible. Signed-off-by:
Arjan van de Ven <arjan@infradead.org> Acked-by:
-
Jens Axboe authored
Don't know where this came from, but dumping this on every open gets boring really quickly. Signed-off-by:
-
David Howells authored
Remove some of the exports on RxRPC symbols that aren't currently used (and most probably won't be) by external modules. Signed-off-by:
David Howells <dhowells@redhat.com> Signed-off-by:
-
James Nelson authored
General cleanup and updating of ramdisk.txt. Signed-off by: Jim Nelson <james4765@gmail.com> Signed-off-by:
-
Christoph Hellwig authored
it's marked static already, and there's no point in exporting it Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Christoph Hellwig authored
There's lots of exports in parport that aren't used by any drivers. Behind many of them there's actually dead code. Signed-off-by:
-
Christoph Hellwig authored
I think Andreas exported them to allow modular xattr handlers, but with James rework these aren't possible anymore, and we never had them anyway. Signed-off-by:
-
Christoph Hellwig authored
Fortunately dvb stopped using it in their firmware loader Signed-off-by:
-
Christoph Hellwig authored
All filesystems have been switched to page_follow_link_light Signed-off-by:
-
Christoph Hellwig authored
This isn't exactly the kind of interface modules should use. Signed-off-by:
-
Christoph Hellwig authored
This recently added function is only used by the posix timers code, no need to be exported. Signed-off-by:
-
Christoph Hellwig authored
Signed-off-by:
-
Paul E. McKenney authored
This patch uses the rcu_assign_pointer() API to eliminate a number of explicit memory barriers from the SysV IPC code that uses RCU. It also restructures the ipc_ids structure so that the array size is stored in the same memory block as the array itself (see the new struct ipc_id_ary). This prevents the race that the earlier code was subject to, where a reader could see a mismatch between the size and the actual array. With the size stored with the array, the possibility of mismatch is eliminated -- with out the need for careful ordering and explicit memory barriers. This has been tested successfully on i386 and ppc64. Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Paul E. McKenney authored
This patch uses the rcu_assign_pointer() API to eliminate a number of explicit memory barriers from code using RCU. This has been tested successfully on i386 and ppc64. Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Paul E. McKenney authored
This patch adds the rcu_assign_pointer() API that helps reduce the need for explicit memory barriers in code that uses RCU. This API buries the required memory barriers in a macro that also does the assignment. This has been tested successfully on i386 and ppc64. Signed-off-by: <paulmck@us.ibm.com> Signed-off-by:
-
Gerd Knorr authored
Cleanup the video4linux driver configuration by using "select" instead of "default if ...". Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
The patch just removes all trailing whitespaces, there are no actual code changes. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
Gerd Knorr authored
This is an update for the v4l tuner modules (tuner.o + tda9887.o). Changes: * fix two tuner config entries. * switch insmod options to new 2.6-ish style. * add suspend/resume functions. The patch also removes all trailing whitespaces. I've a script to remove them from my sources now, that should kill those no-op whitespace changes in my patches after merging this initial cleanup. Signed-off-by:
-
