[Empty message]

I'm not sure that it is too hard. OK it is far from trivial... This is not a new idea though, it has been floated around for a long time (since before Linux I'm sure, although have no references). There are lots of reasons why such an approach has fundamental performance problems too, however. Your kernel can't use huge tlbs for a lot of memory, you can't find the physical address of a page without walking page tables, defragmenting still has a significant cost in terms of moving pages and flus...

Hi all. Commit 831441862956fffa17b9801db37e6ea1650b0f69 (Freezer: make kernel threads nonfreezable by default) breaks freezing when attempting to resume from an initrd, because the init (which is freezeable) spins while waiting for another thread to run /linuxrc, but doesn't check whether it has been told to enter the refrigerator. The original patch replaced a call to try_to_freeze() with a call to yield(). I believe a simple reversion is wrong because if !CONFIG_PM_SLEEP, try_to_freeze() is a noo...

So last week was a bust, with a lot of core people away for the kernel summit, and with -rc5 having two rather nasty (and silly) one-liner problems that bit a number of people - a missing NULL pointer check in TCP, and a missing list terminator in ata_piix. So the fixes for those things were both pretty trivial, and they've been in the -git trees for the last few days, but I just pushed out an -rc6 that also merges up some other updates that did come in during the week. Most of the diff i...

The last BAR on the nForce4 ADMA controllers on this board are at 0xdfefe000 and 0xdfefd000. But it looks like PnP ACPI is also reserving those memory ranges: Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range 0xdfefd000-0xdfefd3ff has been reserved Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range 0xdfefe000-0xdfefe3ff has been reserved Which I very much doubt it should be doing, the BIOS doesn't need to reserve PCI BAR ranges in the ACPI tables. This sounds like a BIOS bug. You...

It depends where the data got corrupted. Normally transfers over the PCI or PCI Express bus are protected by parity (or CRC or something, I assume on PCI-E) so errors there would get detected. This is quite rare unless the motherboard or expansion card is faulty or badly designed with timing problems. However, it's conceivable that data could get corrupted inside the controller, or inside the chipset. This seems quite rare however, except in the presence of design flaws (like some VIA south...

This adds support for the Maple Bus - Sega's proprietary serial if with peripherals - for the Dreamcast. Signed-off by: Adrian McMenamin <adrian@mcmen.demon.co.uk> diff --git a/arch/sh/Kconfig b/arch/sh/Kconfig index 54878f0..c1771b7 100644 --- a/arch/sh/Kconfig +++ b/arch/sh/Kconfig @@ -702,6 +702,17 @@ config CF_BASE_ADDR default "0xb8000000" if CF_AREA6 default "0xb4000000" if CF_AREA5 +config MAPLE + tristate "Maple Bus Support" + depends on SH_DREAMCAST + help + The Mapl...

Support for the Maple bus keyboard on the SEGA Dreamcast. Signed-off by: Adrian McMenamin <adrian@mcmen.demon.co.uk> diff --git a/drivers/input/keyboard/Kconfig b/drivers/input/keyboard/Kconfig index c97d5eb..056cc52 100644 --- a/drivers/input/keyboard/Kconfig +++ b/drivers/input/keyboard/Kconfig @@ -253,4 +253,14 @@ config KEYBOARD_GPIO To compile this driver as a module, choose M here: the module will be called gpio-keys. + +config KEYBOARD_MAPLE + tristate "Maple bus keyboa...

Add a BUG_ON() to check for passing an unreferenced dentry to dput(). This is analogous to the similar check in dget(), and will make reference-counting bugs in filesystems more immediately obvious. (I just spent a while debugging an oops that turned out to be due to broken fs reference counting.) Signed-off-by: Paul Menage <menage@google.com> --- fs/dcache.c | 1 + 1 file changed, 1 insertion(+) Index: container-2.6.23-rc3-mm1/fs/dcache.c ========================================...

Hi, We've got an unusual elf binary and we seem to be running into a bug in the elf loader. I'm not an elf expert, so my apologies if I get the terminology wrong. The elf spec says that PT_LOAD segments must be ordered by vaddr. We want to have a segment at a relatively low fixed vaddr. The exact address is not important, except that it's lower than the standard elf headers and so it must be the first segment in the elf file. However, this segment also has no size in the file...it's ...

Intel framebuffer now supports interlaced video modes. Signed-off-by: Krzysztof Halasa <khc@pm.waw.pl> --- a/drivers/video/intelfb/intelfbhw.c +++ b/drivers/video/intelfb/intelfbhw.c @@ -323,11 +323,7 @@ intelfbhw_validate_mode(struct intelfb_info *dinfo, return 1; } - /* Check for interlaced/doublescan modes. */ - if (var->vmode & FB_VMODE_INTERLACED) { - WRN_MSG("Mode is interlaced.\n"); - return 1; - } + /* Check for doublescan modes. */ if (var->vmode & F...

A few changes have gone into the futex code but not into the futex_compat code, the most significant one being a fix for FUTEX_WAKE_OP in commit f54f098612d7f86463b5fb4763d03533d634de73. This brings both versions in sync again. Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Andrew Morton <akpm@linux-foundation.org> Cc: David Miller <davem@davemloft.net> Signed-off-by: Arnd Bergmann <arnd@arndb.de> Index: linux-2.6/kernel/futex_compat....

The futex_compat code currently mixes pointers to robust_list and compat_robust_list for no apparent reason other than requiring extra typecasts. It also uses an extra argument to fetch_robust_entry() that is not useful but has caused bugs to be introduced before. Clean up the code to get rid of all this and make the compat version look more like the native one. Cc: Ingo Molnar <mingo@elte.hu> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Andrew Morton <akpm@linux-foundation.org&g...

The futex list traversal on the compat side appears to have a bug. It's loop termination condition compares: while (compat_ptr(uentry) != &head->list) But that can't be right because "uentry" has the special "pi" indicator bit still potentially set at bit 0. This is cleared by fetch_robust_entry() into the "entry" return value. What this seems to mean is that the list won't terminate when list iteration gets back to the the head. And we'll also process the list head like a...

After looking at the futex_compat code some more, this is what I ended up with. Please look closely at the changes, as I have not actually tested them, being on a 32 bit machine at the moment. I'd suggest merging the first patch in 2.6.23 instead of the original one from David Miller, and the other two for 2.6.24. Arnd <>< -- -

Looks good in principle. My only suggestion would be to name it something differently than vdir. I know that's what GNU make calls it, but it's still pretty cryptic. How about just fallback-dir ? Also what would be nice (I don't know if it's doable in make) would be a separate variable (e.g. other-obj-... := ) that contains the fallback names and that is double checked against the fallback directory. That would document it clearly what's going on. Failing that stuffing them into a comment would...

Sam, while in general this is definitely a nice change, it does not really solve the real problem of code scattered across two architectures. The Makefile polishing is the least thing we care about. Thanks, tglx -

Partly so. Took a look at the x86 tree. The main Makefile are at least not merged. Neither are pci/Makefile not boot/compressed/Makefile. And some of the rest of the Makefiles are not pretty with the huge arch specific sections ifdeffed out. I have long thought about some extensions to the kbuild 'language' along the following lines: Additional shorthands for obj-m: obj-m-if-m obj-m-if-y obj-m-ifn- Additional shorthands for obj-y: obj-y-if-m obj-y-if-y obj-y-ifn- The ifn- versio...

As it stands this comment is confusing, and not quite grammatical. Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu> --- fs/dcache.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/dcache.c b/fs/dcache.c index 678d39d..2bacdf6 100644 --- a/fs/dcache.c +++ b/fs/dcache.c @@ -1514,8 +1514,8 @@ static void switch_names(struct dentry *dentry, struct dentry *target) * This forceful removal will result in ugly /proc output if * somebody holds a file ope...

Work in progress, still not for inclusion. But code now complete! This is a respin of the following prior posting: http://lkml.org/lkml/2007/9/5/268 This release adds an additional patch that adds fixes to comments and RCU documentation, along with one macro being renamed. The rcutorture patch has a modification to make it a bit more vicious to priority boosting (though the current design relies on -rt latencies for much of the priority-boost torturing effectiveness in this case -- run the te...

Work in progress, not for inclusion. This patch updates the RCU documentation to reflect preemptible RCU as well as recent publications. Fix an incorrect comment in the code. Change the name ORDERED_WRT_IRQ() to ACCESS_ONCE() to better describe its function. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> --- Documentation/RCU/RTFP.txt | 234 ++++++++++++++++++++++++++++++++++++++++-- Documentation/RCU/rcu.txt | 20 +++ Documentation/RCU/torture.txt | 44 ++++...

Work in progress, not for inclusion. Still uses xtime because this patch is still against 2.6.22. This patch modifies rcutorture to also torture RCU priority boosting. The torturing involves forcing RCU read-side critical sections (already performed as part of the torturing of RCU) to run for extremely long time periods, increasing the probability of their being preempted and thus needing priority boosting. The fact that rcutorture's "nreaders" module parameter defaults to twice the number of CPU...

Work in progress, not for inclusion. This patch allows preemptible RCU to tolerate CPU-hotplug operations. It accomplishes this by maintaining a local copy of a map of online CPUs, which it accesses under its own lock. Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> --- include/linux/rcuclassic.h | 2 include/linux/rcupreempt.h | 2 kernel/rcuclassic.c | 8 +++ kernel/rcupreempt.c | 93 +++++++++++++++++++++++++++++++++++++++++++-- 4 files chan...

Work in progress, not for inclusion. This patch implements a new version of RCU which allows its read-side critical sections to be preempted. It uses a set of counter pairs to keep track of the read-side critical sections and flips them when all tasks exit read-side critical section. The details of this implementation can be found in this paper - http://www.rdrop.com/users/paulmck/RCU/OLSrtRCU.2006.08.11a.pdf This patch was developed as a part of the -rt kernel development and meant to provide...

Work in progress, not for inclusion. Fix rcu_barrier() to work properly in preemptive kernel environment. Also, the ordering of callback must be preserved while moving callbacks to another CPU during CPU hotplug. Signed-off-by: Dipankar Sarma <dipankar@in.ibm.com> Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com> --- rcuclassic.c | 2 +- rcupdate.c | 10 ++++++++++ 2 files changed, 11 insertions(+), 1 deletion(-) diff -urpNa -X dontdiff linux-2.6.22-a-splitcl...