This patch will add support for the Dreamcast keyboard when used alongside the maple bus patch (http://lkml.org/lkml/2007/9/4/165) and the pvr2 patch. Signed off by: Adrian McMenamin <adrian@mcmen.demon.co.uk> diff --git a/drivers/input/keyboard/Kconfig b/drivers/input/keyboard/Kconfig index c97d5eb..1689f73 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 ...

The maple bus driver (http://lkml.org/lkml/2007/9/4/165) uses hardware synchronisation between the maple bus and the VBLANK to poll the maple bus. This patch makes the interrupt shareable. By definition the interrupt is for both devices. Signed-off by: Adrian McMenamin <adrian@mcmen.demon.co.uk> diff --git a/drivers/video/pvr2fb.c b/drivers/video/pvr2fb.c index 7d6c298..13de07f 100644 --- a/drivers/video/pvr2fb.c +++ b/drivers/video/pvr2fb.c @@ -890,7 +890,7 @@ static int __init pvr2fb_...

Declare mtdsuper to be gpl-licensed so it can access get_mtd_device and put_mtd_device when loaded as a module. Signed-off-by: Jason Lunz <lunz@falooley.org> --- drivers/mtd/mtdsuper.c | 1 + 1 file changed, 1 insertion(+) Index: linux-2.6.22.6-uml/drivers/mtd/mtdsuper.c =================================================================== --- linux-2.6.22.6-uml.orig/drivers/mtd/mtdsuper.c +++ linux-2.6.22.6-uml/drivers/mtd/mtdsuper.c @@ -14,6 +14,8 @@ #include <linux/namei.h&...

Boaz raised my attention to this patchset today... We suspect we'll still need the extern entry points for handling the bidi request in the scsi_io_completion() path as we only want to call end_that_request_chunk on req->next_rq and never end_that_request_last. (see http://www.bhalevy.com/open-osd/download/linux-2.6.23-rc2_and_iscsi-iscsi-2007_08_09/0...) If this is ok with you I'd leave these entry points in place rather than taking them out and putting them back ...

There's no point in leaving them in when nothing current needs it, I'd much rather add it back in should the need arise. That's the proper way to handle things like this. -- Jens Axboe -

A look at the 'cpuidle' branch of git-acpi shows a commit e40cede7d63a029e92712a3fe02faee60cc38fb4, "cpuidle: first round of documentation updates" that doesn't show up in that branch online. The entire Documentation/cpuidle directory is missing from the tree when looking at the web pages, and it's missing from git-acpi.patch in 2.6.23-rc4-mm1 (but the patch shows up in the summary information in the patch header.) Where did it go? And how can -mm be used to test things if its patches don't even mat...

It never occurred to me that a patch would just remove documentation. Thanks for looking into that... -

[Sorry, I did not see this message until Christoph forwarded it to me. I'm I'm thinking that the best approach would be to define a cpu_sibling_map() macro to handle the cases where cpu_sibling_map is not a per_cpu variable? Perhaps something like: #ifdef CONFIG_SCHED_SMT #ifndef cpu_sibling_map #define cpu_sibling_map(cpu) cpu_sibling_map[cpu] #endif #endif My question though, would include/linux/smp.h be the appropriate place for the above define? (That is, if the above approach is t...

I can easily do the changes for ia64 and test them. I don't have the capability of testing on the powerpc. And are you asking for just the changes to fix the build problem, or the whole set of the changes that were made for x86_64 and i386 in regards to converting NR_CPU arrays to per cpu data? Thanks, Mike -

Hey all- So I've had a deadlock reported to me. I've found that the sequence of events goes like this: 1) process A (modprobe) runs to remove ip_tables.ko 2) process B (iptables-restore) runs and calls setsockopt on a netfilter socket, increasing the ip_tables socket_ops use count 3) process A acquires a file lock on the file ip_tables.ko, calls remove_module in the kernel, which in turn executes the ip_tables module cleanup routine, which calls nf_unregister_sockopt 4) nf_unregister_sock...

I don't think any of the mentioned tools is to blame. Please use the distro's bugtracker. Thanks, Kay -

It might make sense to add your above commit message to the code as a comment. -

Hi! There is a race condition if an instance is executing "__exit device_exit" and calls remove_proc_entry, while someone is still using the procfile, right?. static void __exit device_exit(void) { // what if the procfile is still in use? remove_proc_entry(PROC_FILE_NAME, &proc_root); } To remove this race condition, the code in "__exit device_exit" must a) be sure that no other instance is in procfile functions b) call remove_proc_entry before any other instance accesses the procfi...

Thanks! I see you've been working on it: fix-rmmod-read-write-races-in-proc-entries... http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.22-rc6/2.6.22-rc6-m... (( older relevant posts: http://groups.google.com/group/linux.kernel/browse_thread/thread/4c74bbea17727e6e/809c...? http://groups.google.com/group/fa.linux.kernel/browse_thread/thread/fb03e1a500fcb258/5...? )) Thanks, Albert -

From: Jeff Norden <jnorden@math.tntech.edu> Fix "lost" interrupt problem when using dma with CD/DVD drives in some configurations. This problem can make installing linux from media impossible for distro's that have switched to libata-only configurations. The simple fix is to eliminate the use of dma for reading drive status, etc, by checking the number of bytes to transferred. This change will only affect the behavior of atapi devices, not disks. There is more info at [ message continues ]

This patch adds version information to the ELF kernel file. Together with the bzImage version information, this allows distributions to identify the kernel version based on the file name. Signed-off-by: Dan Aloni <da-x@monatomic.org> Signed-off-by: Bernhard Walle <bwalle@suse.de> --- include/linux/elfnote.h | 9 +++++++++ init/version.c | 3 +++ 2 files changed, 12 insertions(+) --- a/include/linux/elfnote.h +++ b/include/linux/elfnote.h @@ -93,6 +93,15 @@ ...

reiserfs_setattr can call notify_change recursively using the same iattr struct. This could cause it to trip the BUG() in notify_change. Fix reiserfs to clear those bits near the beginning of the function. Signed-off-by: Jeff Layton <jlayton@redhat.com> --- fs/reiserfs/inode.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/fs/reiserfs/inode.c b/fs/reiserfs/inode.c index 9ea1200..0804289 100644 --- a/fs/reiserfs/inode.c +++ b/fs/reiserfs/inode.c @@ -3061,7 ...

Make sure ecryptfs doesn't trip the BUG() in notify_change. This also allows the lower filesystem to interpret these bits in their own way. Signed-off-by: Jeff Layton <jlayton@redhat.com> --- fs/ecryptfs/inode.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-) diff --git a/fs/ecryptfs/inode.c b/fs/ecryptfs/inode.c index 131954b..dac4199 100644 --- a/fs/ecryptfs/inode.c +++ b/fs/ecryptfs/inode.c @@ -959,6 +959,14 @@ static int ecryptfs_setattr(struct dentry *dentry, stru...

If the ATTR_KILL_S*ID bits are set then any mode change is only for clearing the setuid/setgid bits. For NFS skip the mode change and let the server handle it. Signed-off-by: Jeff Layton <jlayton@redhat.com> --- fs/nfs/inode.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/fs/nfs/inode.c b/fs/nfs/inode.c index 45633f9..441bd8b 100644 --- a/fs/nfs/inode.c +++ b/fs/nfs/inode.c @@ -327,6 +327,10 @@ nfs_setattr(struct dentry *dentry, struct iattr *attr) nf...

When an unprivileged process attempts to modify a file that has the setuid or setgid bits set, the VFS will attempt to clear these bits. The VFS will set the ATTR_KILL_SUID or ATTR_KILL_SGID bits in the ia_valid mask, and then call notify_change to clear these bits and set the mode accordingly. With a networked filesystem (NFS and CIFS in particular but likely others), the client machine or process may not have credentials that allow for setting the mode. In some situations, this can lead to file ...

This patch just makes the version number in ips.c and ips.h consistent. It seems that this has been forgotten in a60768e2d43eb30a1adb8a119aeac35dc0d03ef6. Signed-off-by: Bernhard Walle <bwalle@suse.de> --- drivers/scsi/ips.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) --- a/drivers/scsi/ips.h +++ b/drivers/scsi/ips.h @@ -1175,9 +1175,9 @@ typedef struct { #define IPS_VER_MAJOR_STRING "7" #define IPS_VER_MINOR 12 #define IPS_VER_MINOR_STRING "12" -#define IPS_...

Hi, all I just tried booting a brand new 2.6.23-rc5 and after a few minutes it just panicked: machine totally frozen, blinking keyboard leds. I tried setting up a netconsole to get a trace of the panic, but nothing panic related appears there (only the normal boot up messages). The problem is the last kernel I was using was a 2.6.21, so this is a really large changeset to debug, and I don't have much time to try different kernels to narrow this down. Anyway, attached are both kernel co...

I've been running with that patch applied for a few hours now and everything seems to be working fine. Without the patch the kernel would hang in a few minutes, so I guess this fixed it. Thanks for the help, -- Paulo Marques - www.grupopie.com "The Computer made me do it." -

Basically, yes, but that's an oversimplification. We actually use page tables everywhere, but the conversion is simply +/- 0xC0000000 for the NORMAL zone, so we can skip most of the fancy VM work and just use a trivial macro. vmalloc can allocate large chunks of virtually contiguous memory even when the physical memory is heavily fragmented, and since we've set aside address space for it, it's visible in all process contexts. vmalloc is handy sometimes because it can complete even if there'...

Hi Christoph, I have upgraded to 2.6.22.5 and I have selected the SLUB. I have also added append=slub_debug to lilo.conf After a week uptime I got this error. I hope it will be useful for you. Linux version 2.6.22.5 (root@Mimosa) (gcc version 3.3.5) #1 Mon Aug 27 16:57:18 CEST 2007 BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009f800 (usable) BIOS-e820: 000000000009f800 - 00000000000a0000 (reserved) BIOS-e820: 00000000000dc000 - 00000000000e0000 (reserved) BIO...