ChangeSet@1.1371, 2003-10-27 13:37:04-08:00, akpm@osdl.org [PATCH] Fix binfmt_misc locking This fixes a sleep-in-spinlock bug for binfmt_misc registration. That lock is purely for the list, not for the dentry. ChangeSet@1.1370, 2003-10-27 11:52:49-08:00, torvalds@home.osdl.org Don't force PS/2 mouse rate or resolution by default. Only set the rate/resolution if the user actually asked for it. Some mice and KVM switches don't like to have their rate forced. ChangeSet@1.1369, 2003-10-27 11:50:03-08:00, torvalds@home.osdl.org Fix ZOMBIE race with self-reaping threads. exit_notify() used to leave a window open when a thread died that made the thread visible as a ZOMBIE even though the thread reaped itself. This closes that window by marking the thread DEAD within the tasklist_lock. ChangeSet@1.1350.2.2, 2003-10-27 08:37:48-08:00, kevcorry@us.ibm.com [PATCH] Fix DM on top of raid Force Device-Mapper to use PAGE_SIZE or smaller I/O when the underlying device has a bvec_merge_fn routine registered. This will fix the situation of Device-Mapper submitting I/Os to RAID-0 that span the RAID-0 chunk boundaries. Joe is working on a better solution that actually honors the MD merge_bvec_fn routine. But this minimal change will fix the problem for the time being. ChangeSet@1.1350.2.1, 2003-10-27 08:35:23-08:00, torvalds@home.osdl.org Put the compiler barrier() on the right side of the preemption enable on UP-PREEMPT. Without this, the enable could "migrate" up into the critical region (on SMP, the actual spinlock would act as an additional barrier and PREEMPT was ok). ChangeSet@1.1366, 2003-10-27 03:29:16-08:00, herbert@gondor.apana.org.au [IPSEC]: Fix accidental too many ref drops on policies. ChangeSet@1.1365, 2003-10-27 00:56:29-08:00, davem@nuts.ninka.net [IPV6]: Do not virt_to_page() on stack addresses, fixes OOPS. ChangeSet@1.1364, 2003-10-27 00:29:03-08:00, davem@nuts.ninka.net Revert "Zero initial timestamps are valid" changeset. I am still not sure that this change all by itself is enough to make us accept zero initial timestamps properly. Cset exclude: davem@nuts.ninka.net|ChangeSet|20031025060257|60993 ChangeSet@1.1363, 2003-10-27 00:28:16-08:00, davem@nuts.ninka.net Revert signal handling changes in tcp.c - they break SIGURG. Cset exclude: kuznet@ms2.inr.ac.ru|ChangeSet|20031021052951|52463 ChangeSet@1.1362, 2003-10-27 00:11:51-08:00, bdschuym@pandora.be [NETFILTER]: Fix potential OOPS in ipt_REDIRECT. ChangeSet@1.1361, 2003-10-27 00:05:29-08:00, yoshfuji@linux-ipv6.org [IPV6]: Fix bogus semicolon typo in mcast.c ChangeSet@1.1360, 2003-10-27 00:01:25-08:00, rusty@rustcorp.com.au [NETFILTER]: Fix ipchains oops in NAT We updated ip_nat_setup_info to set the initialized flag and call place_in_hashes, but *didn't* change the call in ip_fw_compat_masq.c which also calls place_in_hashes() itself (again!). Result: corrupt list, and next thing which lands in the same hash bucket goes boom. Thanks to Andy Polyakov for chasing this down. ChangeSet@1.1359, 2003-10-27 00:00:07-08:00, yoshfuji@linux-ipv6.org [IPV6]: Process ipv4-mapped addresses properly on UDPv6 sockets. ChangeSet@1.1358, 2003-10-26 23:58:17-08:00, yoshfuji@linux-ipv6.org [IPV4,6]: Use common storage for cork'd flow, needed to handle mapped-ipv4 ipv6 addresses properly. ChangeSet@1.1357, 2003-10-26 23:55:54-08:00, yoshfuji@linux-ipv6.org [IPV6]: Use real storage for cork'd packets, else MSG_MORE corrupts UDP packets. ChangeSet@1.1356, 2003-10-26 23:52:56-08:00, yoshfuji@linux-ipv6.org [IPV6]: Typo in address comparison. ChangeSet@1.1355, 2003-10-26 23:52:27-08:00, ak@muc.de [NET]: Fix oops in ethertap_rx(). ChangeSet@1.1354, 2003-10-26 23:51:48-08:00, levon@movementarian.org [NETFILTER]: Fix modular iptables build. ChangeSet@1.1350.1.10, 2003-10-26 19:16:23-08:00, torvalds@home.osdl.org Add a sticky "PF_DEAD" task flag to keep track of dead processes. Use this to simplify 'finish_task_switch', but perhaps more importantly we can use this to track down why some processes seem to sometimes not die properly even after having been marked as ZOMBIE. The "task->state" flags are too fluid to allow that well. ChangeSet@1.1350.1.9, 2003-10-26 14:27:04-08:00, tausq@debian.org [PATCH] fix __div64_32 to do division properly This fixes the generic __div64_32() to correctly handle divisions by large 32-bit values (as used by nanosleep() and friends, for example). It's a simple bit-at-a-time implementation with a reduction of the high 32-bits handled manually. Architectures that can do 64/32-bit divisions in hardware should implement their own more efficient versions. ChangeSet@1.1350.1.8, 2003-10-26 09:23:40-08:00, ysato@users.sourceforge.jp [PATCH] fix h8/300 support - add 'sched_clock' - delete smplock.h ChangeSet@1.1350.1.7, 2003-10-26 09:17:34-08:00, ak@muc.de [PATCH] Essential x86-64 updates The most important part is that it makes x86-64 compile again. Without that 2.6 users won't be very happy. It also works around a bug that allowed every user program to reboot the system on B stepping K8. Also update to match some recent i386 fixes. Full ChangeLog: - Add acpi_pic_set_level_irq to make ACPI compile again - Work around compat mode K8 bug in IRET exception handling - Increase exception stack. The old 1k stack was too easy to overflow (from Jim Paradis, changed by me) - Replace safe_smp_processor_id with cpuid (needed for above) - When there is only one node always enable fake_node mode - Merge with i386 (NTP gettimeofday monoticity fix, irq nr_vectors change) - Fix compile problem for UP kernels in time/cpufreq - Set all nodes online at bootup - Define node_to_cpumask correctly ChangeSet@1.1350.1.6, 2003-10-26 09:11:40-08:00, stelian@popies.net [PATCH] meye: documentation This documents the existence of a forth 'motioneye' camera plugged into the USB bus, of course unsupported by the meye driver. ChangeSet@1.1350.1.5, 2003-10-26 09:11:20-08:00, stelian@popies.net [PATCH] sonypi: fix Zoom/Thumbphrase button events This corrects the Zoom and Thumbphrase button events. ChangeSet@1.1350.1.4, 2003-10-26 09:11:03-08:00, Andries.Brouwer@cwi.nl [PATCH] Relax FATFS validity tests The first FAT entry should have the media byte (0xf0,0xf8,...,0xff) extended with all 1 bits in the first FAT entry. Checking this is a good idea, it prevents us from mounting garbage as FAT - there is no good magic for FAT. Unfortunately, Windows does not enforce this, and 2.4 doesn't either. It turns out that there are filesystems around (two reports so far) that have a zero first FAT entry, and work under Windows and 2.4 but fail to mount under 2.6. So, this weakens the test. ChangeSet@1.1350.1.3, 2003-10-26 09:10:52-08:00, Andries.Brouwer@cwi.nl [PATCH] atkbd: 0xfa is ACK The 0xfa code can be a key scancode or it can be a protocol scancode. Only few keyboards use it as a key scancode, and if we always interpret it as a protocol scancode then these rare keyboards will have a dead key. If we interpret it as a key scancode then we have a dead keyboard in case it was protocol. Clearly it is safer to prefer to interpret it as a protocol scancode. This moves the test for ACK and NAK up, so that they are always seen as protocol. This is just a minimal patch. What I did in 1.1.54 was to keep track of commands sent with a flag reply_expected, so that 0xfa could be taken as ACK when a reply is expected and as key scancode otherwise. That is the better solution, but requires larger surgery. ChangeSet@1.1350.1.2, 2003-10-25 11:38:01-07:00, torvalds@home.osdl.org Linux 2.6.0-test9 TAG: v2.6.0-test9