ChangeSet@1.1762, 2004-05-28 21:25:09-07:00, benh@kernel.crashing.org [PATCH] radeonfb iBook & IGP fixes This patch to radeonfb fixes support for the latest iBook models along with an initialisation problem on some IGP chipsets. Please apply. Signed-off-by: Benjamin Herrenschmidt Signed-off-by: Linus Torvalds ChangeSet@1.1756.1.5, 2004-05-28 14:35:14-07:00, torvalds@ppc970.osdl.org Revert 3c905C initialization changes that cause problems Cset exclude: akpm@osdl.org[torvalds]|ChangeSet|20040510205830|02933 ChangeSet@1.1756.3.1, 2004-05-28 14:08:27-07:00, greg@kroah.com Merge kroah.com:/home/greg/linux/BK/bleed-2.6 into kroah.com:/home/greg/linux/BK/usb-2.6 ChangeSet@1.1717.18.8, 2004-05-28 13:48:49-07:00, fishor@gmx.net [PATCH] I2C: add max1619 driver This is a driver for "Remote/Local Temperature Sensor with Dual-Alarm Outputs and SMBus Serial Interface" MAX1619. I found this chip an my Laptop SAMSUNG NV5000. Daryng I use Linux cooling didn't worked at all, naw with this driwer it's working. I hope this will be usefool for ather too. I didn't hade any expiriens with programming, but i didn't wont to wait wann some body make it vor me. Jean halped me correrct any mysteiks wich i made. Thanks Jaen :) Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1717.18.7, 2004-05-28 13:47:51-07:00, khali@linux-fr.org [PATCH] I2C: i2c-parport: support the ADM1031 evaluation board The following patch adds support for the ADM1030 and ADM1031 evaluation boards to the i2c-parport and i2c-parport-light drivers. They are almost compatible with the already supported ADM1025 and ADM1032 boards, except that the ADM1032 board needs some pins to be set high to draw its power, while the same pins power up heating resistors on the ADM1031 board. I considered it was a bit dangerous to do that by default, so I ended up with two different device definitions, one with powering pins set, and one with these pins cleared. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1759, 2004-05-28 13:37:08-07:00, lcapitulino@prefeitura.sp.gov.br [PATCH] PCI: fix pci/probe.c possible NULL pointer. In drivers/pci/probe.c::pci_scan_bridge() the call for pci_alloc_child_bus() can return NULL, but it is not handled by the function (detected by Coverity's checker). The patch bellow fix that returning `max' if we got the NULL, but I do not know if it is right. I guess it is, because in that case the function will act in the same way as with `pass != 0'. Signed-off by: Luiz Capitulino Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1758, 2004-05-28 13:36:07-07:00, trimmer@infiniconsys.com [PATCH] PCI: Add InfiniCon PCI ID to pci_ids.h We would like to have the InfiniCon PCI Vendor ID added to pci_ids.h Below is a context diff, which would would greatly appreciate if you applied and included in future kernel releases. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1743.3.20, 2004-05-28 13:28:41-07:00, abbotti@mev.co.uk [PATCH] USB: ftdi_sio throttling fix This patch fixes throttling problems in the ftdi_sio driver for the 2.6 kernel. The old throttling mechanism (unlinking the read urb) often failed to work, and even it did work, would lose any data held in the transfer buffer. The new mechanism presented here is based on what the whitehead driver does (defer processing and resubmitting of the read urb until unthrottled). Signed-off-by: Ian Abbott Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1743.3.19, 2004-05-28 13:28:14-07:00, stern@rowland.harvard.edu [PATCH] USB: Use normal return codes for several routines in hub.c This patch changes the return codes used by hub_port_wait_reset(), hub_port_reset(), and hub_port_debounce() in hub.c. I couldn't stand the {-1=error, 0=okay, 1=disconnect} scheme; the meanings seemed arbitrary and I constantly forgot which number stood for what status. The revised code uses normal negative error codes, including -ENOTCONN to indicate device disconnected, or 0 for success. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1756.1.4, 2004-05-28 22:18:49+02:00, wim@iguana.be [WATCHDOG] v2.6.6 linux/fs.h-patch From: Christoph Hellwig All watchdog drivers need linux/fs.h ChangeSet@1.1756.2.2, 2004-05-28 13:13:30-07:00, tpoynor@mvista.com [PATCH] Fix for leave-runtime-suspended-devices-off-at-system-resume.patch A patch to fix my previous leave-runtime-suspended-devices-off-at-system-resume patch; the new changes save a copy of power.power_state in order to know whether to resume a device, independently of mods to that field by a driver suspend routine. This fixes 2.6.7-rc1-mm1 in the same fashion as the updated 2.6.6 patch sent previously. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1756.1.3, 2004-05-28 21:59:46+02:00, sean@mess.org [WATCHDOG] v2.6.6 sc520_wdt.c-patch2 This patch also removes the cbar usage which is unnecessary. The MMCR is always available at 0xfffef000; there is no need to use the cbar register (if mmcr aliasing is enabled, then the MMCR is _also_ available at another address set by CBAR). ChangeSet@1.1756.1.2, 2004-05-28 21:46:05+02:00, wim@iguana.be [WATCHDOG] v2.6.6 sc520_wdt.c-patch1 Clean-up (general stuff: comments, keep module parameters together, ...) Added clear definitions for the Watchdog Timer Control Register bits Made start, stop and keepalive return 0 if successful Fixed nowayout behaviour so that it is consistent with other watchdog drivers Fixed release behaviour so that it is consistent with other watchdog drivers Added wdt_set_heartbeat function to set the timeout/heartbeat of the watchdog Made sure that memory remapping (wdtmrctl) is done before misc_register is started MMCR_BASE_DEFAULT was wrong (Bug 2497 reported by Sean Young) Tested by Sean Young ChangeSet@1.1756.1.1, 2004-05-28 21:38:43+02:00, wim@iguana.be [WATCHDOG] v2.6.6 w83627hf_wdt.c When drivers starts show the correct watchdog driver info. ChangeSet@1.1717.7.7, 2004-05-28 10:31:37-07:00, greg@kroah.com Minor coding style fixups in resume code and added a bit of debugging help. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1757, 2004-05-28 10:20:42-07:00, greg@kroah.com Merge kroah.com:/home/greg/linux/BK/bleed-2.6 into kroah.com:/home/greg/linux/BK/pci-2.6 ChangeSet@1.1717.7.6, 2004-05-28 10:05:31-07:00, greg@kroah.com [PATCH] Report which device failed to suspend Based on a patch from Nickolai Zeldovich but put into the proper place by me. Signed-off-by: Andrew Morton Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1717.7.5, 2004-05-28 10:04:44-07:00, tpoynor@mvista.com [PATCH] Leave runtime suspended devices off at system resume Currently all devices are resumed at system resume time, including any that were individually powered off ("at runtime") prior to the system suspend. In certain cases it can be nice to force back on individually suspended devices, such as the display, but hopefully this policy can be left up to userspace power managers; the kernel should probably honor the settings previously made by userspace/drivers. This seems preferable to requiring a power-conscious system to re-suspend devices after a system resume; furthermore, for certain platforms (such as XScale PXA27X) there can be disastrous consequences of powering up devices when the system is in a state incompatible with operation of the device. Suggested patch does this: (1) At system resume, checks power_state to see if the device was suspended prior to system suspend, and skips powering on the device if so. (2) Does not re-suspend an already-suspended device at system suspend (using a different method than is currently employed, which reorders the list, see #3). (3) Preserves the active/off device list order despite the above changes to suspend/resume behavior, to avoid dependency problems that tend to occur when the list is reordered. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1717.7.4, 2004-05-28 10:04:18-07:00, tpoynor@mvista.com [PATCH] Device runtime suspend/resume fixes (1) Set device power state at runtime resume (as is done for runtime suspend) so that a later suspend does not think the device is still suspended (refusing to suspend it again). (2) Move devices from the active list to the off list only when suspending all devices as part of a system suspend, not for runtime suspend. This matches the resume code, which only moves devices from off to active during system resume, such that runtime resume currently doesn't move the suspended device back to the active list. (This also avoids reordering the device list for runtime suspends; the list is in order of registration and suspend/resume works best that way -- granted, more sweeping improvements in how device dependencies are accounted for in the suspend/resume order are also needed someday.) Runtime device suspend/resume is in some cases used frequently on battery-powered embedded devices, to save additional power and to handle device power state interactions with overall system power state on certain platforms. Signed-off-by: Greg Kroah-Hartman ChangeSet@1.1743.15.1, 2004-05-28 15:42:38+01:00, rmk@flint.arm.linux.org.uk [ARM] Fix sparse complaint Sparse found an instance where we were directly dereferencing a userspace pointer in the signal handling code. This change fixes that. ChangeSet@1.1755, 2004-05-28 00:38:21-07:00, davidm@napali.hpl.hp.com [PATCH] ia64: use new ptep_set_access_flags ia64: Implement race-free ptep_set_access_flags() Signed-off-by: davidm@hpl.hp.com Signed-off-by: Linus Torvalds ChangeSet@1.1754, 2004-05-28 00:38:10-07:00, benh@kernel.crashing.org [PATCH] ppc32: Fix typo in USB sleep code on intrepid based laptops This fixes a typo in the low level platform code that puts to sleep and wakes up the USB cell. This fixes a problem when pmdisk is used on those machines (pmdisk patch not merged yet, soon maybe...) From: Guido Guenther Signed-off-by: Benjamin Herrenschmidt Signed-off-by: Linus Torvalds ChangeSet@1.1743.14.1, 2004-05-28 12:02:07+10:00, nathans@sgi.com Merge sgi.com:/source2/linux-2.6 into sgi.com:/source2/xfs-linux-2.6 ChangeSet@1.1737.1.100, 2004-05-28 11:45:30+10:00, hch@sgi.com [XFS] Don't leak locked pages on readahead failure SGI Modid: xfs-linux:xfs-kern:172618a ChangeSet@1.1737.1.99, 2004-05-28 11:41:54+10:00, sandeen@sgi.com [XFS] Fix overflow in mapping test at offsets of 2^63-1 bytes SGI Modid: xfs-linux:xfs-kern:172649a ChangeSet@1.1717.7.3, 2004-05-27 15:48:10-07:00, greg@kroah.com Remove the smbios driver as it is not needed. You can do the same from userspace, and the author requests that the driver be deleted from the kernel tree before people start using it. ChangeSet@1.1743.1.43, 2004-05-27 16:42:46-04:00, jgarzik@redhat.com [netdrvr] Add 'gigabit ethernet' config option ChangeSet@1.1743.1.42, 2004-05-27 16:22:20-04:00, jgarzik@redhat.com [netdrvr ixgb] massive update Since Intel agreed to submit further updates via broken-up patches like they do currently (and admirably) for e1000 and e100, I agreed to merge this update to bring the driver up to speed. Contributed by: Ayyappan.Veeraiyan@intel.com Changes: Features implemented * Support for new 850nm adapters. * Copyright notice updated to include year 2004. * Fix for "ixgb does not maintain non-default MTU setting across a link loss" issue - When link loss happens in non-default MTU environment, driver will incorrectly operate with default 1500 MTU setting. * Netpoll support added * Ethtool support - status functionality, FlowControl interface, Checksum interface, TSO and Scatter Gather interfaces * Race condition fix - Race condition (TX path) exists between ixgb_xmit_frame and clean_tx_irq routines in handling the queue. * Removed dead code segments (#if 0) Performance improvement features * Mod operator usage is removed - used to cause performance problems in non-IA architecture based machines * Multiple ICR register read in ISR is avoided * RS bit set on only 'end of packet' TX descriptors - to avoid multiple writebacks by controller for packets with multiple descriptors. * RX descriptors prefetch is done - improved 1500 MTU TX performance All relevant e1000 driver cleanups ported to ixgb * Valid error propagation in functions ixgb_up, ixgb_probe, ixgb_open. * NAPI code cleanups * u8, u16 and u32 data types are changed to uint8_t, uint16_t and uint32_t respectively. We use these types on our shared code for multiple OSes and also to make it uniform with e1000 driver. * Some functions in ixgb_main.c are moved to different location - This enables easy porting of e1000 bug fixes to ixgb ChangeSet@1.1743.1.37, 2004-05-27 15:33:27-04:00, akpm@osdl.org [PATCH] net/sk98lin: correct buggy VPD in ASUS MB From: Jeff Lightfoot The following patch to net/sk98lin/skvpd.c was put together by Marc Bouget, mbouget at club-internet.fr. This patch works around a corrupt EEPROM (VPD?) in the ASUS K8V Deluxe SE motherboard ethernet chipset and allows the network driver to work correctly. We have written to ASUS and the sk98lin maintainers but have not heard anything back. ChangeSet@1.1743.1.36, 2004-05-27 15:15:11-04:00, hch@lst.de sb1000 and wan/sealevel net drivers need to include linux/init.h. ChangeSet@1.1743.13.1, 2004-05-27 15:12:36-04:00, mporter@kernel.crashing.org Add new IBM PPC4xx EMAC net driver. ChangeSet@1.1743.12.5, 2004-05-27 15:08:08-04:00, rl@hellgate.ch [PATCH] via-rhine: netdev_priv() Found another patch that should go with this batch: Switch to netdev_priv(). Fix outdated comment and bump version number while we're at it. ChangeSet@1.1743.12.4, 2004-05-27 15:07:59-04:00, rl@hellgate.ch [PATCH] via-rhine: USE_MEM, USE_IO -> USE_MMIO Replace USE_MEM and USE_IO with USE_MMIO define. ChangeSet@1.1743.12.3, 2004-05-27 15:07:51-04:00, rl@hellgate.ch [PATCH] via-rhine: Whitespace clean-up - Switch to 8 char tabs. - Remove kernel log pointer to the scyld web site -- it's a) fairly irrelevant by now and b) gone. - Remove Emacs Voodoo. - More white space clean up, mostly coding style. ChangeSet@1.1743.12.2, 2004-05-27 15:07:42-04:00, rl@hellgate.ch [PATCH] via-rhine: Rename some symbols This patch renames symbols: via_rhine_* -> rhine_* struct netdev_private *np -> struct rhine_private *rp ChangeSet@1.1743.12.1, 2004-05-27 15:07:33-04:00, rl@hellgate.ch [PATCH] via-rhine: Fix force media Lucas Nussbaum and Dirk Koeppen each found independently that the code for forcing media options in via-rhine is borked and suggested the fix below. I've been sitting on this way too long because there is more badness in the immediate vicinity which needs a bigger surgery. The second hunk fixes a braino I managed to introduce myself. ChangeSet@1.1743.9.10, 2004-05-27 14:07:05-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: fix for patch 8 le16_to_cpu Joe Perches pointed out an error in patch 8. As I looked at the results closer 3 out of 4 looked correct. This fixes the output for the last case. Output is now the same on IA32 and PPC64 hardware. ChangeSet@1.1743.1.35, 2004-05-27 14:05:00-04:00, pelle@dsv.su.se [netdrvr tulip] new pci id ChangeSet@1.1743.1.34, 2004-05-27 13:51:22-04:00, srompf@isg.de [netdrvr b44] always restore PCI config on resume the Broadcom BCM4401 driver restores pci configuration on resume only when the device is up. On my notebook, this leads to a failure when the device is down during the S3 cycle. Short solution for now: Always restore pci config. ChangeSet@1.1743.11.6, 2004-05-27 13:44:06-04:00, ganesh.venkatesan@intel.com [PATCH] e1000 7/7: Support for ethtool msglevel based error Also included are driver version update and change logs ChangeSet@1.1743.11.5, 2004-05-27 13:43:57-04:00, ganesh.venkatesan@intel.com [PATCH] e1000 6/7: ethtool_ops support ChangeSet@1.1743.11.4, 2004-05-27 13:43:49-04:00, ganesh.venkatesan@intel.com [PATCH] e1000 4/7: Estimate number of tx descriptors required Reduce scope of tx_lock ChangeSet@1.1743.11.3, 2004-05-27 13:43:40-04:00, ganesh.venkatesan@intel.com [PATCH] e1000 3/7: Determine link status correctly while using ChangeSet@1.1743.11.2, 2004-05-27 13:43:32-04:00, ganesh.venkatesan@intel.com [PATCH] e1000 2/7: Workaround for link LED staying ON even when ChangeSet@1.1743.11.1, 2004-05-27 13:43:24-04:00, ganesh.venkatesan@intel.com [PATCH] e1000 1/7: Clear Auto-MDIX when the link is forced to ChangeSet@1.1743.1.33, 2004-05-27 13:33:57-04:00, achirica@telefonica.net [wireless airo] Add RFMON support for MPI and latest Cisco ChangeSet@1.1743.10.1, 2004-05-27 13:24:17-04:00, kevin.curtis@farsite.co.uk [netdrvr wan] farsync driver update 1) Provides support for new FarSync cards T1U, T2U, T4U and TE1 2) Provides support for an E1 interface 3) Provides support for a variant of X.21 that allows transmit and receive clocks 4) Provide a raw socket interface directly to the data from the line. 5) Improves performance with less time in interrupts and more in BH's ChangeSet@1.1743.9.9, 2004-05-27 13:12:31-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: avoid timeout with tcpdump This patch avoids a timeout when entering/exiting promiscuous mode with tcpdump. All pending xmit operations are flushed and if the queue is full the timeout will occur. The wake_queue avoids that timeout. Tested ppc64 and ia32. ChangeSet@1.1743.9.8, 2004-05-27 13:12:23-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: correct printk for big-endian arch This patch corrects a printk when executed on a big-endian system. Tested ppc64. ChangeSet@1.1743.9.7, 2004-05-27 13:12:15-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: fix bogus carrier errors with 79c973 The 79C973 version of the pcnet32 chipset would report all transmit operations as being sent with a carrier error. The root cause was writing reserved bits in bcr33. It caused the 973 to report xmit as errors, and caused 975 and 976 to hard hang when reading bcr34. My thanks to Bruce Penrod for his help in finding the cause of this bug. ChangeSet@1.1743.9.6, 2004-05-27 13:12:06-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: limit frames received during interrupt. The current code will allow an infinite number of frames to be received during one interrupt. Tested ia32 and ppc64. ChangeSet@1.1743.9.5, 2004-05-27 13:04:02-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: remove timer and complexity. This removes the timer I recently added, and the 'ltint' interrupt mitigation from the 79C971 and 79C972. It did not improve performance, added complexity, and was a bad idea in hind sight. ChangeSet@1.1743.9.4, 2004-05-27 13:03:48-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: fix boundary comparison bug. This patch fixes a boundary condition. It is possible to get an interrupt and have the transmit queue completely full. Without this the driver will leak skb's and pci maps (if the arch supports them). ChangeSet@1.1743.9.3, 2004-05-27 13:03:35-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: correct 79C976 variant string. This patch correctly identifies the 79C976 as a PCnet/PRO not a FAST III. ChangeSet@1.1743.9.2, 2004-05-27 13:03:22-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: avoid hard hang with some chip variants. This patch fixes a hard hang with 79C975 and 79C976 chip variants when dumping BCR register #34. ChangeSet@1.1743.9.1, 2004-05-27 13:03:08-04:00, brazilnut@us.ibm.com [PATCH] pcnet32: add static to two routines. This patch adds 'static' to two routines. The prototype has static but the instantiation did not. ChangeSet@1.1743.1.32, 2004-05-27 12:54:22-04:00, rusty@rustcorp.com.au [PATCH] Fix incorrect but unused define in net_sk_mca.h From: Jean Delvare ChangeSet@1.1743.1.31, 2004-05-27 12:54:08-04:00, rusty@rustcorp.com.au [PATCH] Update Alfred Arnold contact info From: Jean Delvare ChangeSet@1.1743.8.1, 2004-05-27 12:53:44-04:00, lethal@linux-sh.org [PATCH] Fix 8139too ring size for dreamcast/embedded Presently 2.6.6 backs out the CONFIG_8139_RXBUF_IDX in favor of using a hardcoded 8139_RXBUF_IDX (again). This seems to have been done due to some issues occuring with 8139_RXBUF_IDX =3D=3D 3, however (as the Kconfig pointed out), we still need 8139_RXBUF_IDX =3D=3D 1 in the CONFIG_SH_DREAMC= AST case. The patch which made this change can be seen at: {MIME-mangled URL} Before that, CONFIG_8139_RXBUF_IDX was set to 1 both in the CONFIG_SH_DREAMCAST and CONFIG_EMBEDDED cases. This patch adds that back into the current 8139too. ChangeSet@1.1743.1.30, 2004-05-27 12:52:07-04:00, lcapitulino@prefeitura.sp.gov.br [PATCH] fix net/tulip/winbond-840.c warning. ChangeSet@1.1751, 2004-05-27 09:49:52-07:00, davem@nuts.davemloft.net [SPARC64]: Export _do_write_trylock to modules. ChangeSet@1.1743.1.29, 2004-05-27 07:36:46-07:00, akpm@osdl.org [PATCH] nfsd: deleting symlinks over nfs causes oops on unmount From: "J. Bruce Fields" From: Neil Brown This fixes an oops on unmount (failure of the assertation at fs/ext3/super.c:421). Probably reproduceable just by creating and deleting a single symlink over nfs and then unmounting the exported filesystem. Recent change to fh_compose means dentry reference is *not* consumed, and so usually has to be explicitly dput afterwards. One usage was missed in that patch, so this dput is needed. Signed-off-by: Andrew Morton ChangeSet@1.1743.1.28, 2004-05-27 07:36:36-07:00, akpm@osdl.org [PATCH] Print backtrace for bad vfree() From: Andi Kleen Only the printk alone is not too useful, print the backtrace too. Signed-off-by: Andrew Morton ChangeSet@1.1743.1.27, 2004-05-27 07:36:25-07:00, akpm@osdl.org [PATCH] swsusp documentation updates From: Pavel Machek Signed-off-by: Andrew Morton ChangeSet@1.1743.1.26, 2004-05-27 07:36:14-07:00, akpm@osdl.org [PATCH] CPU Hotplug: restore Idle task's priority during CPU_DEAD notification From: Srivatsa Vaddagiri Fix a CPU Hotplug problem wherein idle task's "->prio" value is not restored to MAX_PRIO during CPU_DEAD handling. Without this patch, once a CPU is offlined and then later onlined, it becomes "more or less" useless (does not run any task other than its idle task!) Ingo said: The __setscheduler() call is (technically) incorrect because in the SCHED_NORMAL case the prio should be zero. So it's a bit cleaner to set up the static priority to MAX_PRIO and then revert the policy to SCHED_NORMAL via __setscheduler(). Signed-off-by: Ingo Molnar Signed-off-by: Andrew Morton ChangeSet@1.1743.1.25, 2004-05-27 07:36:04-07:00, akpm@osdl.org [PATCH] remove message: POSIX conformance testing by UNIFIX From: "Randy.Dunlap" Remove the outdated "POSIX conformance testing by UNIFIX" message. There is a general desire to reduce the quantity of noisy and/or outdated kernel boot-time messages... Suggested by Andi Kleen. Ulrich's (old) comments: http://www.nsa.gov/selinux/list-archive/0107/0525.cfm Certifying Linux (Linux Journal): http://www.linuxjournal.com/article.php?sid=0131 Agreed by Tim Bird, no dissenters that I heard of: http://marc.theaimsgroup.com/?l=linux-kernel&m=108362954024749&w=2 Signed-off-by: Andrew Morton ChangeSet@1.1743.1.24, 2004-05-27 07:35:53-07:00, akpm@osdl.org [PATCH] wdt.c warning fix drivers/char/watchdog/wdt.c: In function `wdt_init': drivers/char/watchdog/wdt.c:638: warning: label `outrbt' defined but not used Signed-off-by: Andrew Morton ChangeSet@1.1743.1.23, 2004-05-27 07:35:42-07:00, akpm@osdl.org [PATCH] Fix the setting of file->f_ra on block-special files We need to set file->f_ra _after_ calling blkdev_open(), when inode->i_mapping points at the right thing. And we need to get it from inode->i_mapping->host->i_mapping too, which represents the underlying device. Also, don't test for null file->f_mapping in the O_DIRECT checks. Signed-off-by: Andrew Morton ChangeSet@1.1743.1.22, 2004-05-27 07:35:31-07:00, akpm@osdl.org [PATCH] Set d_bucket correctly for anonymous dentries From: Neil Brown In researching the oopses reported in bug #2761, Neil came up with: I have found one problem, but it isn't particularly new and I cannot see how it would be related. When d_alloc_anon creates an anonymous dentry, it is put on a special hash chain for anonymous dentries (sb->s_anon), but d_bucket is set to d_hash(parent, name_hash) If, when it is eventually moved to a proper name, that hash value is the same as the final hash value, it will not be moved to the right bucket, and so it not be accessible by name. This patch should fix it. anonymous dentries have their own private hash "bucket" (sb->s_anon) and so d_bucket should be set to a unique (impossible) address, else d_move will get confused. Signed-off-by: Neil Brown Signed-off-by: Andrew Morton ChangeSet@1.1743.1.21, 2004-05-27 07:35:21-07:00, akpm@osdl.org [PATCH] posix locks oops fix From: Andreas Gruenbacher There is a race between unshare_files() and the following steal_locks(). As a consequence, steal_locks() may steal some additional FL_POSIX locks that don't belong to the current thread. This triggers a BUG in locks_remove_flock(). In detail, the current thread shares its files struct with other threads. This causes unshare_files() to associate the current thread with a copy of its files_struct. The copy shares all file objects with the original files struct. In the time between unshare_files() and steal_locks(), another thread creates a new file and a FL_POSIX lock on it. The current thread gets into steal_locks() and takes over all FL_POSIX locks that refer to the previous files_struct, including the new lock. We do put_files_struct(original files_struct). This causes the file handle to the new file to be closed. We get into locks_remove_posix() and miss the lock, because its fl_owner field now refers to the new files_struct. Finally we get into locks_remove_flock(), and stumble upon the lock. While looking into this bug report I gathered the following data with a SUSE kernel (oops and LKCD dump from Chris): kernel BUG at fs/locks.c:1736! invalid operand: 0000 [#1] SMP CPU: 0 EIP: 0060:[] Tainted: G U EFLAGS: 00010246 (2.6.5-0-testing) EIP is at locks_remove_flock+0x8b/0x130 eax: f7b89998 ebx: f61df3fc ecx: f61df354 edx: 00000000 esi: f61df354 edi: f6702b80 ebp: f6179c24 esp: f6179c08 ds: 007b es: 007b ss: 0068 Process owcimomd (pid: 1713, threadinfo=f6178000 task=f66d0d60) Stack: c1e1fdac c1e1fdac f7fe83c0 00000296 f6702b80 f7fe87c0 f61df354 f6179c3c c016ce00 f61ddadc f6702b80 00000000 f6703b00 f6179c54 c0168b1f c0000000 0000026f 00000012 f6703b00 f6179c6c c0124ba7 00000001 f6179e5c f6179d88 Call Trace: [] __fput+0x30/0x120 [] filp_close+0x4f/0x90 [] put_files_struct+0x67/0xc0 [] load_elf_binary+0x3f5/0x1596 [] update_atime+0x9f/0xc0 [] __generic_file_aio_read+0x1cd/0x200 [] file_read_actor+0x0/0xd0 [] search_binary_handler+0x97/0x270 [] do_execve+0x172/0x200 [] sys_execve+0x32/0x70 [] sysenter_past_esp+0x52/0x71 Code: 0f 0b c8 06 eb 74 35 c0 eb db b8 00 e0 ff ff 21 e0 8b 10 8b put_files_struct+0x67 is equivalent to fs/binfmt_elf.c:681 in 2.6.6 current->files == fl->fl_owner fl->fl_file = 0xf6702b80 (a valid struct file) current->files = max_fds=32 max_fdset=1024 next_fd=3 fd=[0xf6927080 0xf6951b80 0xf6951b80 0 ...] Here's a proposed fix. As a side effect, steal_locks no longer walks the global list of locks, but only the locks of all open inodes. What are the reasons (other than historic ones) for not getting rid of fl_owner and using fl_pid instead, by the way? I think that would clean up the whole mess with file locks a bit. Signed-off-by: Andrew Morton ChangeSet@1.1743.1.20, 2004-05-27 07:35:10-07:00, akpm@osdl.org [PATCH] ppc32: fix 'make O=...' From: Tom Rini Fix arch/ppc/boot/ so that everything now works with 'make O='. Partially by: Geoffrey LEVAND . Signed-off-by: Tom Rini Signed-off-by: Andrew Morton ChangeSet@1.1743.1.19, 2004-05-27 07:34:58-07:00, akpm@osdl.org [PATCH] ppc64 kernel hackers can't spell From: Anton Blanchard From: Dave Hansen This patch is obviously of the utmost importance. It probably doesn't matter as much for kernel error messages, but one of these mistakes is in a user-readable /proc file. Signed-off-by: Anton Blanchard Signed-off-by: Dave Hansen Signed-off-by: Andrew Morton ChangeSet@1.1717.6.26, 2004-05-26 15:37:25-07:00, arjanv@redhat.com [PATCH] PCI: restore pci config space on resume The patch below enhances the PCI layer with 2 things 1) enable and busmaster state are stored in the pci device struct 2) pci config space is stored to the pci device struct with that, it is possible to make a generic pci resume method that restores config space and reenables the device, including busmaster when appropriate. One can rightfully argue that the driver resume method should do this, and yes that is right. So the patch only does it for devices that don't have a resume method. Like the main PCI bridge on my testbox of which the bios so nicely forgets to restore the bus master bit during resume.. With this patch my testbox resumes just fine while it, well, wasn't all too happy as you can imagine without a busmaster pci bridge. ChangeSet@1.1750, 2004-05-26 11:15:27-07:00, davem@nuts.davemloft.net [SPARC64]: Kill unused var warnings/errors. ChangeSet@1.1743.7.5, 2004-05-26 09:03:18-07:00, paulus@samba.org [PATCH] ppc64: fix nonexistent irq affinity This fixes a bug where, if we try to set the affinity on an unused virtual IRQ number on a logically-partitioned pSeries system, we call the firmware with physical IRQ number = -1, which it doesn't like. With this patch we just ignore the attempt. Signed-off-by: Paul Mackerras Signed-off-by: Linus Torvalds ChangeSet@1.1743.7.4, 2004-05-26 08:30:08-07:00, B.Zolnierkiewicz@elka.pw.edu.pl [PATCH] ide: use msleep() instead of ide_delay_50ms() msleep() does msecs to jiffies conversion correctly regardless of HZ value and sets the current task's state in a safe way. Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Linus Torvalds ChangeSet@1.1743.7.3, 2004-05-26 08:29:57-07:00, B.Zolnierkiewicz@elka.pw.edu.pl [PATCH] ide: fix ide_delay_50ms() in ide.c to always sleep Noticed by Christoph Hellwig . Probably somebody got the logic wrong while adding #ifndef CONFIG_BLK_DEV_IDECS back in 2.4.0-test2. Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Linus Torvalds ChangeSet@1.1743.7.2, 2004-05-26 08:29:48-07:00, B.Zolnierkiewicz@elka.pw.edu.pl [PATCH] ide: missing rq checks in ide-disk ide-disk only checks for drive->blocked and blk_fs_request() if TASKFILE_IO is defined. Move these checks (and TCQ check too) to upper function. Signed-off-by: Jens Axboe Signed-off-by: Bartlomiej Zolnierkiewicz Signed-off-by: Linus Torvalds ChangeSet@1.1743.7.1, 2004-05-26 07:56:23-07:00, torvalds@ppc970.osdl.org Split ptep_establish into "establish" and "update_access_flags" ptep_establish() is used to establish a new mapping at COW time, and it always replaces a non-writable page mapping with a totally new page mapping that is dirty (and likely writable, although ptrace may cause a non-writable new mapping). Because it was nonwritable, we don't have to worry about losing concurrent dirty page bit updates. ptep_update_access_flags() leaves the same page mapping, but updates the accessed/dirty/writable bits (it only ever sets them, and never removes any permissions). Often easier, but it may race with a dirty bit update on another CPU. Booted on x86 and ppc64. Signed-off-by: Benjamin Herrenschmidt Signed-off-by: Linus Torvalds ChangeSet@1.1743.6.1, 2004-05-25 23:13:48-07:00, dtor_core@ameritech.net [NET_SCHED] Do not oops when user tries to attach a filter to a TBF qdisc. (TBF does not allow attaching filters as it has only one class, filter should be attached either to TBF's parent or to its child) ChangeSet@1.1749, 2004-05-25 22:52:09-07:00, davem@nuts.davemloft.net [SPARC64]: Move over to HZ==1000. ChangeSet@1.1743.1.15, 2004-05-25 22:24:29-07:00, torvalds@ppc970.osdl.org Remove bogus test preprocessor test. PAGE_SIZE isn't even always defined at this point, which makes us test undefined preprocessor symbols. It so happens that the test works in that case, but since the test is a bit pointless in the first place... ChangeSet@1.1743.1.14, 2004-05-25 22:22:33-07:00, torvalds@ppc970.osdl.org Make constant types explicit, rather than depend on some rather subtle C type expansion rules. This makes sparse happier. ChangeSet@1.1743.1.13, 2004-05-25 22:21:34-07:00, torvalds@ppc970.osdl.org Don't return void types from void functions. This helps reduce sparse noise. ChangeSet@1.1748, 2004-05-25 22:04:26-07:00, davem@nuts.davemloft.net [SPARC64]: Update defconfig. ChangeSet@1.1747, 2004-05-25 22:01:48-07:00, davem@nuts.davemloft.net [SPARC64]: Implement _raw_spin_lock_flags(). ChangeSet@1.1745, 2004-05-25 14:01:13-07:00, davem@nuts.davemloft.net [SPARC64]: Implement debugging version of write_trylock(). ChangeSet@1.1743.1.9, 2004-05-25 13:09:27-07:00, sxking@qwest.net [IPSEC]: Fix buglet in AF_KEY spddelete When trying to spddelete individual entries using setkey, spddelete always fails. The culprit is in net/af_key.c; spdadd sets the family field of the selector when creating an entry, but spddelete doesn't when building a selector to match for xfrm_policy_bysel. Trivial fix is to have spddelete set the family field in the selector in same way spdadd does. ChangeSet@1.1717.23.6, 2004-05-25 13:06:21-07:00, davem@nuts.davemloft.net [TG3]: Update driver version and reldate. ChangeSet@1.1743.2.67, 2004-05-25 13:04:59-07:00, torvalds@ppc970.osdl.org Introduce architecture-specific "ptep_update_dirty_accessed()" helper function to write-back the dirty and accessed bits from ptep_establish(). Right now this defaults to the same old "set_pte()" that we've always done, except for x86 where we now fix the (unlikely) race in updating accessed bits and dropping a concurrent dirty bit. ChangeSet@1.1717.23.5, 2004-05-25 13:04:23-07:00, akepner@sgi.com [TG3]: Make sure RX/TX flow control settings actually get set. ChangeSet@1.1743.2.66, 2004-05-25 12:37:15-07:00, torvalds@ppc970.osdl.org Pass in a "dirty" argument to ptep_establish in preparation for pte update race fix. This does not actually use the information yet, but the next few patches will start to put it to some good use. ChangeSet@1.1743.3.18, 2004-05-25 12:33:50-07:00, stern@rowland.harvard.edu [PATCH] USB: Gonzo variable renaming in hub.c As part of the cleanup effort, I wanted to name all the variables in hub.c uniformly. Currently there are different names for the same thing in different routines, and the same names are used for different things -- it's impossible to keep things straight. I also wanted to step away from the deplorable practice of naming everything "dev". It is not an exaggeration that up until relatively recently one of the drivers (not the hub driver, fortunately!) contained a line which looked basically like this: dev->dev.dev = &intf->dev; If you can make sense out of that, you're a better code reader than I am! Ranting aside, this patch institutes the following name scheme for local variables in hub.c: hub: struct usb_hub hdev: hub's corresponding struct usb_device hub_dev: hub interface's embedded struct device udev: general struct usb_device There are a couple of genuine code changes hidden in there too. Just trivial things, like creating a local hub_dev variable for use in place of &hub->intf->dev. ChangeSet@1.1743.3.17, 2004-05-25 12:33:17-07:00, stern@rowland.harvard.edu [PATCH] USB: Make usb_choose_configuration() a separate subroutine This patch creates a separate subroutine to encapsulate the work required in choosing an initial configuration for a device. In my opinion that reflects a policy decision that should be kept apart from all the other work involved in creating a new device structure. The existing code in usb_new_device() is simply moved into usb_choose_configuration(). ChangeSet@1.1743.3.16, 2004-05-25 12:27:47-07:00, stern@rowland.harvard.edu [PATCH] USB: Add usb_release_address() and move usb_set_address() This patch adds usb_release_address() as a complement to usb_choose_address(), to centralize the work required when freeing an allocated device address. It also moves the usb_set_address() routine from usb.c to hub.c -- which is the only place it is ever used -- and renames it to hub_set_address(). ChangeSet@1.1743.3.15, 2004-05-25 11:50:29-07:00, stern@rowland.harvard.edu [PATCH] USB: Change "driverfs" to "sysfs" in usbcore Before fixing up the device locking and device reset code, I want to do some cleanups of the hub driver and related areas. This is the first of a series of patches for that purpose. This patch changes all the occurrences of "driverfs" in usbcore to "sysfs" -- I just couldn't stand seeing the out-of-date name any more (and I kept confusing it with usbfs, don't know why). Although I did a "bk mv driverfs.c sysfs.c" when creating the patch, the exported patch file itself doesn't reflect that very well. It looks like driverfs.c was deleted and sysfs.c created from scratch. If you prefer, I can resubmit this in a slightly different form, with the file name unchanged so that you can issue the "bk mv" command in your repository after applying the patch. ChangeSet@1.1743.3.14, 2004-05-25 11:38:39-07:00, stern@rowland.harvard.edu [PATCH] USB UHCI: allow URBs to be unlinked when IRQs don't work A lot of people with USB controllers made by VIA have been suffering from the fact that these controllers stop working when they receive a babble packet. In particular, they stop generating interrupt requests. Since the UHCI driver relies on IRQs from the controller for proper timing and interlocking of unlink requests, this means that those broken controllers will hang the UHCI driver and drivers for any device connected through it. This patch, written by Herbert Xu, gives the UCHI driver the ability to manage the unlink procedure using timer interrupts as well as controller interrupts. (It also fixes a race in the UHCI irq handler.) Although it won't prevent the VIA controllers from flaking out when they encounter babble, at least now users will be able to rmmod the uhci-hcd driver and then reload it, restoring their systems back to normal operation (until the next babble!). P.S.: Herbert, there's one loose end I still want to tie up. When the controller isn't running (i.e., is suspended) the frame number won't change, but unlinks still need to work. It's a small point, not too likely to come up in normal usage. I'll fix it later on when I update the state-changing part of the driver. ChangeSet@1.1743.3.13, 2004-05-25 11:37:59-07:00, stern@rowland.harvard.edu [PATCH] USB: Initially read 9 bytes of config descriptor This patch reads the full 9 bytes of a configuration descriptor during enumeration rather than just the first 8 bytes. That's how Windows does it, and today I ran across a device that doesn't work properly when asked to send only 8 bytes worth. I doubt very much this will cause any problems with currently-working devices; since the descriptor itself is 9 bytes long and since the devices are most likely to expect a 9-byte request, anything that can handle an 8-byte request should have no difficulty. (Also, some debugging messages have been slightly improved.) Incidentally, USB traces taken from Windows 2000 and Windows XP show that when those operating systems retrieve a string descriptor during enumeration, they do so by requesting a 255-byte transfer. They do not first ask just for the initial 2 bytes (which contain the actual length) and then ask for the actual length, which is what we do. Interestingly, back in 2.4 we _did_ do things the same as Windows. ChangeSet@1.1743.3.12, 2004-05-25 11:31:08-07:00, jnardelli@infosciences.com [PATCH] USB: visor: Fix Oops on disconnect This fixes http://bugme.osdl.org/show_bug.cgi?id=2289 This patch has been tweaked by greg@kroah.com ChangeSet@1.1743.2.65, 2004-05-25 11:11:46-07:00, ak@muc.de [PATCH] Fix nodemask clearing bug in NUMA API Fix over long nodemask clearing in get_mem_policy() by using the right size for the node mask. ChangeSet@1.1743.1.8, 2004-05-25 11:04:01-07:00, linux-kernel@vortech.net [VLAN]: Use KERN_INFO for VLAN_INF. ChangeSet@1.1743.1.7, 2004-05-25 11:02:48-07:00, herbert@gondor.apana.org.au [IPSEC]: Use add_timer() in xfrm_state_find. ChangeSet@1.1743.1.6, 2004-05-25 11:02:07-07:00, herbert@gondor.apana.org.au [IPSEC]: Fix outdated comment in __xfrm_state_delete. ChangeSet@1.1743.1.5, 2004-05-25 11:01:22-07:00, herbert@gondor.apana.org.au [IPSEC]: Do not leak entries in xfrm_state_find. In xfrm_state_find, the larval state never actually matures with Openswan so it only ever gets deleted by the timer which means that the time crash can't happen :) It becomes a (possible) memory leak instead. ChangeSet@1.1743.3.11, 2004-05-25 11:00:57-07:00, olh@suse.de [PATCH] USB: out of bounds access in hiddev_cleanup hiddev_table[] is an array of pointers. the minor number is used as an offset. hiddev minors start either with zero, or with 96. If they start with 96, the offset must be reduced by HIDDEV_MINOR_BASE because only 16 minors are available. unplugging a hiddevice will zero data outside the hiddev_table array. this was spotted by Takashi Iwai. ChangeSet@1.1743.3.10, 2004-05-25 11:00:18-07:00, jamesl@appliedminds.com [PATCH] USB: Fix down() in hard IRQ in powermate driver Fixes this warning: May 18 06:56:01 Knoppix kernel: Debug: sleeping function called from invalid context at include/asm/semaphore.h:119 May 18 06:56:01 Knoppix kernel: in_atomic():1, irqs_disabled():0 May 18 06:56:01 Knoppix kernel: Call Trace: May 18 06:56:01 Knoppix kernel: [] __might_sleep+0xb2/0xd3 May 18 06:56:01 Knoppix kernel: [] powermate_config_complete+0x33/0x77 [powermate] May 18 06:56:01 Knoppix kernel: [] usb_hcd_giveback_urb+0x25/0x39 May 18 06:56:01 Knoppix kernel: [] uhci_finish_urb+0x54/0xa1 May 18 06:56:01 Knoppix kernel: [] uhci_finish_completion+0x43/0x55 May 18 06:56:01 Knoppix kernel: [] uhci_irq+0xf8/0x179 May 18 06:56:01 Knoppix kernel: [] usb_hcd_irq+0x36/0x67 May 18 06:56:01 Knoppix kernel: [] handle_IRQ_event+0x3a/0x64 May 18 06:56:01 Knoppix kernel: [] do_IRQ+0xb8/0x192 May 18 06:56:01 Knoppix kernel: [] common_interrupt+0x18/0x20 Attached patch uses spinlocks instead of a semaphore so that we can't sleep when in_atomic(). ChangeSet@1.1743.1.4, 2004-05-25 10:58:43-07:00, shemminger@osdl.org [BRIDGE]: Update bridge.txt Trent Jarvi noticed this. The file was out of date with current web site and maintainer. Please apply to 2.4 and 2.6. Signed-off-by: Stephen Hemminger ChangeSet@1.1743.2.64, 2004-05-25 10:27:46-07:00, paulus@samba.org [PATCH] IRQ stacks for PPC64 Even with a 16kB stack, we have been seeing stack overflows on PPC64 under stress. This patch implements separate per-cpu stacks for processing interrupts and softirqs, along the lines of the CONFIG_4KSTACKS stuff on x86. At the moment the stacks are still 16kB but I hope we can reduce that to 8kB in future. (Gcc is capable of adding instructions to the function prolog to check the stack pointer whenever it moves it downwards, and I want to use that when I try using 8kB stacks so I can be confident that we aren't overflowing the stack.) Signed-off-by: Paul Mackerras ChangeSet@1.1743.2.63, 2004-05-25 10:06:18-07:00, mingo@elte.hu [PATCH] x86-bigsmp: use fixed interrupt delivery This patch, from Venkatesh Pallipadi, changes x86 IO-APICs to use fixed interrupt delivery instead of lowest priority to support larger number of CPUs. Only bigsmp is affected by this cleanup. From: Venkatesh Pallipadi Signed-off-by: Ingo Molnar ChangeSet@1.1743.2.62, 2004-05-25 08:45:46-07:00, akpm@osdl.org [PATCH] missing compat ioctl mapping for DM_REMOVE_ALL Signed-off-by: Marcus Meissner Added missing DM_REMOVE_ALL call. ChangeSet@1.1743.2.61, 2004-05-25 08:45:35-07:00, akpm@osdl.org [PATCH] sched_yield() microoptimisation Signed-off-by: Ingo Molnar We can avoid the local_irq_enable() in sched_yield() because schedule() unconditionally enables interrupts anyway. ChangeSet@1.1743.2.60, 2004-05-25 08:45:24-07:00, akpm@osdl.org [PATCH] sched.h comment typo fix Signed-off-by: Christian Meder Signed-off-by: Ingo Molnar sched.h typo fix from Christian Meder. ChangeSet@1.1743.2.59, 2004-05-25 08:45:13-07:00, akpm@osdl.org [PATCH] Subject: Re: Help understanding slow down Signed-off-by: Ingo Molnar Add a warning that "idle=poll" is a performance hit on hyperthreaded CPUs. ChangeSet@1.1743.2.58, 2004-05-25 08:45:03-07:00, akpm@osdl.org [PATCH] No interpretation of HD spindown timeout in laptop mode ACPI binding script. From: Bart Samwel Currently the ACPI binding script in the Laptop Mode doc always says "20 seconds" and "2 hours" for the timeouts it uses. This is incorrect if the user changed the config values, so we print something more general. ChangeSet@1.1743.2.57, 2004-05-25 08:44:52-07:00, akpm@osdl.org [PATCH] rmap build fix From: William Lee Irwin III PMD_SIZE is not a compile-time constant on sparc. Use min() in there so that the cluster size will be evaluated at runtime if the architecture insists on doing that. ChangeSet@1.1743.2.56, 2004-05-25 08:44:41-07:00, akpm@osdl.org [PATCH] ir-kbd-gpio.c build fix It's initialising slot 24 in two places. Gerd Knorr says "This one should be 23.". ChangeSet@1.1743.2.55, 2004-05-25 08:44:29-07:00, akpm@osdl.org [PATCH] Revert bogus x86-64 change From: Andi Kleen The 32bit generic nops added with a previous patch to x86-64 alternative() are not completely 64bit clean. This caused crashes in some cases. This patch reverts this broken change. ChangeSet@1.1743.2.54, 2004-05-25 08:44:14-07:00, akpm@osdl.org [PATCH] isapnp sb16 virtual pc From: David Sanders Patch adds support for the emulated Soundblaster 16 in Virtual PC 2004. ChangeSet@1.1743.4.4, 2004-05-25 08:44:10-07:00, ink@jurassic.park.msu.ru [PATCH] fix PCI bridge swizzle on takara and eiger This fixes NULL pointer dereference (bus->self) for PCI devices on the root bus. Ivan. ChangeSet@1.1743.2.53, 2004-05-25 08:44:01-07:00, akpm@osdl.org [PATCH] ext2: fix build with DEBUG=y From: FabF ChangeSet@1.1743.2.52, 2004-05-25 08:43:49-07:00, akpm@osdl.org [PATCH] minor sched.c cleanup Signed-off-by: Christian Meder Signed-off-by: Ingo Molnar The following obviously correct patch from Christian Meder simplifies the DELTA() define. ChangeSet@1.1743.2.51, 2004-05-25 08:43:39-07:00, akpm@osdl.org [PATCH] Really enable NUMA API on x86-64 From: Andi Kleen Really enable the NUMA API system calls on x86-64. ChangeSet@1.1743.2.50, 2004-05-25 08:43:28-07:00, akpm@osdl.org [PATCH] remap_file_pages: fix syscall declaration Signed-off-by: Hugh Dickins sys_remap_file_pages is declared as asmlinkage in mm/fremap.c, but is the one syscall declared without asmlinkage in include/linux/syscalls.h. ChangeSet@1.1743.2.49, 2004-05-25 08:43:17-07:00, akpm@osdl.org [PATCH] remap_file_pages: implement MAP_POPULATE for all protections Signed-off-by: Hugh Dickins It seems eccentric to implement MAP_POPULATE only on PROT_NONE mappings: do_mmap_pgoff is passing down prot, then sys_remap_file_pages verifies it's not set. I guess that's an oversight from when we realized that the prot arg to sys_remap_file_pages was misdesigned. There's another oddity whose heritage is harder for me to understand, so please let me leave it to you: sys_remap_file_pages is declared as asmlinkage in mm/fremap.c, but is the one syscall declared without asmlinkage in include/linux/syscalls.h. ChangeSet@1.1743.2.48, 2004-05-25 08:43:06-07:00, akpm@osdl.org [PATCH] Fix for lockup in reiserfs acl/xattrs From: Jeff Mahoney The following is a patch to fix a locking problem in ACL/xattr code. It manifests when a user attempts to set an xattr on a file which they do not own, and on which an ACL is applied. What happens is this: reiserfs_setxattr [write lock inode xattr sem] ->xattr_set -> lookup -> __reiserfs_permission [if conditions above are met, and need_lock= is unset, read lock inode xattr sem] *lockup* Since we already keep track of when to lock during permission calls, the fix is simple: just make the locking conditional as it was before. Credits to Andreas Gruenbacher ChangeSet@1.1743.2.47, 2004-05-25 08:42:56-07:00, akpm@osdl.org [PATCH] UDF: directory reading fix From: Ben Fennema The problem occured when files were stored on the disc in 16-bit per character mode when all the upper bits were 0. The fs module converted the file name given by the user to a 8-bit per character string to compare, so the comparison always failed. The patch maps the file from disc into the current locale and then compares it directly to the file name given by the user. ChangeSet@1.1743.4.3, 2004-05-25 08:42:55-07:00, ink@jurassic.park.msu.ru [PATCH] compile fix for mm/init.c Fix another page->count reference (in addition to numa.c one that I've sent earlier). Ivan. ChangeSet@1.1743.2.46, 2004-05-25 08:42:45-07:00, akpm@osdl.org [PATCH] bk-kernel-howto reversion From: Rusty Russell This one snuck through - Jeff prefers the bk:// addresses. ChangeSet@1.1743.2.45, 2004-05-25 08:42:34-07:00, akpm@osdl.org [PATCH] CREDITS is unmaintained From: Adrian Bunk This information seems to be quite outdated. ChangeSet@1.1743.2.44, 2004-05-25 08:42:23-07:00, akpm@osdl.org [PATCH] H8/300 ne driver module fix From: Yoshinori Sato - module support fix ChangeSet@1.1743.2.43, 2004-05-25 08:42:12-07:00, akpm@osdl.org [PATCH] H8/300 module fix From: Yoshinori Sato - fix relocation - define SYMBOL_PREFIX ChangeSet@1.1743.2.42, 2004-05-25 08:42:00-07:00, akpm@osdl.org [PATCH] Fix various memory leaks From: Yury Umanets Thanks to smatch I have found few memory leaks and other related issues. ChangeSet@1.1743.2.41, 2004-05-25 08:41:49-07:00, akpm@osdl.org [PATCH] v4l: use saa7111 i2c module in V4L MXB driver From: Michael Hunold The attached patch changes my "Multimedia eXtension Board" (MXB) Video4Linux-driver to use the standard saa7111 video decoder infrastructure (to which I recently submitted changes through Ronald Bultje) instead of some home-brewn direct-access stuff. Nothing serious, but it removes code duplication and makes the code use the video decoder api. ChangeSet@1.1743.4.2, 2004-05-25 08:41:45-07:00, ink@jurassic.park.msu.ru [PATCH] fix NUMA build Replace reference to page->count with page_count(). Ivan. ChangeSet@1.1743.2.40, 2004-05-25 08:41:40-07:00, akpm@osdl.org [PATCH] initramfs uncpio fix From: init/initramfs.c::do_skip() has an off-by-one that leads to unpacking failures for some gzipped cpio images. We have static int __init do_skip(void) { if (this_header + count <= next_header) { eat(count); return 1; } else { eat(next_header - this_header); state = next_state; return 0; } } and that <= should actually be <. It almost never matters, since if we hit the boundary case (header ending exactly on the gunzip window end) the current variant will simply end up doing extra call of do_skip() when we get to the next window and that will finish the work (assign state). The only exception is when we hit that in the last window. That is, if there's nothing after the final header (trailer). Then we miss the final state transition (Skip -> Reset) and get "junk in archive" panic. Normally cpio(1) pads the image to multiple of 512, so we actually have a bunch of zeroes after the trailer. And that almost always saves our butts - trailer is followed by zeroes, so we get to Reset state just fine. So we never see that on small in-kernel image (it's less than 512 bytes, so it gets a lot of padding) and we almost never see that on external ones (1:127 odds of hitting the bug). ChangeSet@1.1743.2.39, 2004-05-25 08:41:29-07:00, akpm@osdl.org [PATCH] FAT: small fixes From: OGAWA Hirofumi - use fat_fs_panic() instead of BUG() if it read a corrupted inode. - add missing "\n". ChangeSet@1.1743.2.38, 2004-05-25 08:41:18-07:00, akpm@osdl.org [PATCH] swsusp: fix swsusp with intel-agp From: Pavel Machek swsusp contained rather nasty bug where it killed machine when intel-agp or anything else split kernel 4MB mapping. Herbert Xu diagnosed this. Fixed by switching to "known good" mapping for during suspend/resume. ChangeSet@1.1743.2.37, 2004-05-25 08:41:07-07:00, akpm@osdl.org [PATCH] Don't use "cut" in laptop mode control script -- it is in /usr. From: Bart Samwel We don't want to use "cut" in the laptop mode control script, because that is in /usr. This patch is from Jasper Spaans. ChangeSet@1.1743.2.36, 2004-05-25 08:40:54-07:00, akpm@osdl.org [PATCH] matroxfb: Add support for mapping CRTC<->outputs at boot time Signed-off-by: Petr Vandrovec Some people expressed interest in having possibility to set CRTC <-> outputs mapping at boot time, without having to use 'matroxset' later after kernel boots. This patch adds option 'video=matroxfb:outputs:XYZ', where X sets which CRTC will connect to primary output, Y sets secondary output and Z sets DVI output. In addition to that I also added missing memset() into maven, which was broken since i2c was kobjectified. ChangeSet@1.1743.2.35, 2004-05-25 08:40:43-07:00, akpm@osdl.org [PATCH] ext3: remove duplicated ext3_std_error() call From: Andi Kleen When start_transaction() detects an error it already calls ext3_std_error. No need to do it again in the caller. ChangeSet@1.1743.2.34, 2004-05-25 08:40:34-07:00, akpm@osdl.org [PATCH] make i386 dma-mapping.h includeable standalone From: Christoph Hellwig From: Debian kernel package, author probably Herbert Xu Include asm/io.h and asm/scatterlist.h in include/asm-i386/dma-mapping.h to make it useable standalone, which is already true for most architectures. ChangeSet@1.1743.2.33, 2004-05-25 08:40:22-07:00, akpm@osdl.org [PATCH] befs: typo fix From: "Sergey S. Kostyliov" Fix a typo in an error message. ChangeSet@1.1743.2.32, 2004-05-25 08:40:12-07:00, akpm@osdl.org [PATCH] include linux/selection.h for color_table in drivers/video/tgafb.c From: Christoph Hellwig From: Debian kernel package, author probably Herbert Xu ChangeSet@1.1743.2.31, 2004-05-25 08:40:01-07:00, akpm@osdl.org [PATCH] include linux/root_dev.h for ROOT_DEV in drivers/mtd/maps/uclinux.c From: Christoph Hellwig * Include linux/root_dev.h for ROOT_DEV in drivers/mtd/maps/uclinux.c ChangeSet@1.1743.2.30, 2004-05-25 08:39:49-07:00, akpm@osdl.org [PATCH] missing init.h in drivers/mtd/chips/sharp.c From: Christoph Hellwig again needed by most non-x86 arches. * Include linux/init.h for __init ChangeSet@1.1743.2.29, 2004-05-25 08:39:38-07:00, akpm@osdl.org [PATCH] add one more neomagic audio device id From: Christoph Hellwig From: Mattia Monga via Debian kernel package Add support for nm256xl+ in sound/oss/nm256_audio.c ChangeSet@1.1743.2.28, 2004-05-25 08:39:28-07:00, akpm@osdl.org [PATCH] remove a dead variable from isofs From: Christoph Hellwig From: Debian kernel package, author is probably Herbert Xu * Do not get seqno since we will not use it in fs/isofs/inode.c ChangeSet@1.1743.2.27, 2004-05-25 08:39:18-07:00, akpm@osdl.org [PATCH] fix a bash-ism in toplevel Makefile From: Christoph Hellwig From: Debian kernel package, author probably Herbert Xu. * Fixed bashism in Makefile ChangeSet@1.1743.2.26, 2004-05-25 08:39:07-07:00, akpm@osdl.org [PATCH] befs: nls fix From: "Sergey S. Kostyliov" Fix nls support for character sets with character width large than 1. ChangeSet@1.1743.2.25, 2004-05-25 08:38:57-07:00, akpm@osdl.org [PATCH] hfsplus: update dir time after change From: Roman Zippel Update dir ctime/mtime when adding/removing an entry. ChangeSet@1.1743.2.24, 2004-05-25 08:38:46-07:00, akpm@osdl.org [PATCH] hfsplus: don't release not existing nodes From: Roman Zippel When releasing a page don't try to release not existing nodes. ChangeSet@1.1743.4.1, 2004-05-25 08:38:44-07:00, ink@jurassic.park.msu.ru [PATCH] fix system clock on ruffian Unlike most other alphas, ruffian uses i8253 timer instead of RTC as the system clock source. However, the PIT clock divisor (LATCH) is bogus since CLOCK_TICK_RATE has been changed to 32 KHz. Fixed using recently introduced PIT_TICK_RATE macro. Ivan. ChangeSet@1.1743.2.23, 2004-05-25 08:38:35-07:00, akpm@osdl.org [PATCH] hfsplus: completely remove half inserted catalog entry From: Roman Zippel If the inserting of the file or dir record failed, remove the previously inserted thread record. ChangeSet@1.1743.2.22, 2004-05-25 08:38:25-07:00, akpm@osdl.org [PATCH] hfsplus: delete inode properly From: Roman Zippel Call hfsplus_delete_inode() to delete an inode when adding it to the filesystem failed, so superblock info is correctly updated. ChangeSet@1.1743.2.21, 2004-05-25 08:38:14-07:00, akpm@osdl.org [PATCH] hfsplus: correct dentry initialization for dir dentries. From: Roman Zippel Initialize d_fsdata field also for dir dentries, use hfsplus_instantiate helper function for this. ChangeSet@1.1743.2.20, 2004-05-25 08:38:04-07:00, akpm@osdl.org [PATCH] hfsplus: fix key length for index nodes From: Roman Zippel Use the correct key length for index nodes. ChangeSet@1.1743.2.19, 2004-05-25 08:37:53-07:00, akpm@osdl.org [PATCH] Decrease srtuct file size by 8 From: Kurt Garloff Attached patch decreases the size of struct file by 8 bytes on 64 bit arches by avoiding unecessary padding. ChangeSet@1.1743.2.18, 2004-05-25 08:37:44-07:00, akpm@osdl.org [PATCH] remove stale comments above struct page From: Christoph Hellwig struct page easily fits into a single cacheline with any recent CPU, and the ordering isn't as described anymore anyway. ChangeSet@1.1743.2.17, 2004-05-25 08:37:33-07:00, akpm@osdl.org [PATCH] don't export vma_prio_tree_next From: Christoph Hellwig there's no user is modules, the function isn't in mainline and I don't see why modules should use it. ChangeSet@1.1743.2.16, 2004-05-25 08:37:14-07:00, akpm@osdl.org [PATCH] Fix race condition with current->group_info From: Olaf Kirch I have been chasing a corruption of current->group_info on PPC during NFS stress tests. The problem seems to be that nfsd is messing with its group_info quite a bit, while some monitoring processes look at /proc//status and do a get_group_info/put_group_info without any locking. This problem can be reproduced on ppc platforms within a few seconds if you generate some NFS load and do a "cat /proc/XXX/status" of an nfsd thread in a tight loop. I therefore think changes to current->group_info, and querying it from a different process, needs to be protected using the task_lock. (akpm: task->group_info here is safe against exit() because the task holds a ref on group_info which is released in __put_task_struct, and the /proc file has a ref on the task_struct). ChangeSet@1.1743.2.15, 2004-05-25 08:36:57-07:00, akpm@osdl.org [PATCH] ep_send_events() stack reduction ep_send_events() uses ~350 bytes of stack for a local buffer of events to send to userspace. The patch fixes that by removing the double-buffering altogether. A pipe-based microbenchmark from Davide Libenzi was sped up by 1-2%. ChangeSet@1.1743.2.14, 2004-05-25 08:36:46-07:00, akpm@osdl.org [PATCH] Fix the mangled-oops-output-on-SMP problem From: Ingo Molnar printk currently does if (oops_in_progres) bust_printk_locks(); which means that once we oops, the printk locking is 100% ineffective and multiple CPUs make an unreadable mess on a serial console. It's a significant development hassle. Fix that up by only popping locks once per ten seconds. akpm@osdl.org did: - Bump the timeout to 30 seconds - 9600 baud is slow. - Handle jiffy wraps: change the logic so that we only skip the lockbust if the current time is within 30 seconds of the previous lockbusting attempt. ChangeSet@1.1743.2.13, 2004-05-25 08:36:31-07:00, akpm@osdl.org [PATCH] Prevent scary warnings from knfsd From: "J. Bruce Fields" The kernel currently prints: nfsd: nobody listening for auth.unix.ip upcall; has some daemon not been started? on every bootup, during initscripts. Neil Brown says: It was part of the recent set of idmapper patches. Bruce wanted the admin to get a warning when the idmapper daemon wasn't running. I thought the same warning should apply to any daemon that responded to upcalls. In the case of auth.unix.ip it isn't strictly necessary for a daemon to be running (for comparability with 2.4). You can get rid of the warning by doing: mount -t nfsd nfsd /proc/fs/nfs before mountd is started (init scripts should start doing this I hope, but distributions don't tend to use the init script from nfs-utils, so it is hard to push it). This will trigger mountd to listen on auth.unix.ip and others. That's a hassle, so Bruce's patch limits the warning purely to the new idmapper cache. It provides a callback in the cache_detail that individual caches can use to log messages when upcalls fail because a userspace daemon not running. Implement this method for the idmapping caches. ChangeSet@1.1743.2.12, 2004-05-25 08:36:18-07:00, akpm@osdl.org [PATCH] Fix userspace include of linux/fs.h From: Mans Rullgard There are a few include which should have been under __KERNEL__. ChangeSet@1.1743.2.11, 2004-05-25 08:36:02-07:00, akpm@osdl.org [PATCH] use SLAB_PANIC in ll_rw_blk.c ChangeSet@1.1743.2.10, 2004-05-25 08:35:48-07:00, akpm@osdl.org [PATCH] ppc64: avoid bogus real IRQ numbers Signed-off-by: Paul Mackerras Early in the boot process on pSeries machines, we look in the Open Firmware device tree for information about the interrupt assignments, and assign virtual IRQ numbers for each physical IRQ. There is currently a couple of bugs in this code which result in us assigning virtual IRQs for nonexistent physical IRQs. This causes problems when we call the firmware to enable or disable those nonexistent physical IRQs. Some versions at least of the firmware will hit an assertion failure and crash the machine when this happens. This patch fixes the bugs and ensures that we don't try and use nonexistent physical IRQ numbers. One bug was that we were mapping ISA interrupts, which is unnecessary since virtual IRQ numbers 0 - 15 are reserved for them. The other was that when we had a PCI interrupt (which is always in the range 1 to 4, corresponding to INTA to INTD) which didn't have a mapping in the PCI host bridge above it, we were just using the original number (usually 1) rather than ignoring it. ChangeSet@1.1743.2.9, 2004-05-25 08:35:31-07:00, akpm@osdl.org [PATCH] ppc64: bump IOMMU_MAX_ORDER Signed-off-by: Anton Blanchard We have cards that want over 2MB of PCI consistent memory. The IOMAP_MAX_ORDER limit is just to catch bad drivers early, so we can bump this a bit. We want some room to grow but our maximum get_free_pages allocation on ppc64 is currently 16MB, so it doesnt make sense to go above that. ChangeSet@1.1743.2.8, 2004-05-25 08:35:13-07:00, akpm@osdl.org [PATCH] ppc64: small enter_rtas fix From: Anton Blanchard enter_rtas now takes an unsigned long. ChangeSet@1.1743.2.7, 2004-05-25 08:34:57-07:00, akpm@osdl.org [PATCH] dynamic addition of virtual disks on PPC64 iSeries From: Stephen Rothwell This patch allows us to dynamically add virtual disks to an iSeries partition. It works like this: after you have created the virtual disk file on OS/400 and attached it to the Linux partition, you need to write to /sys/bus/vio/drivers/viodasd/probe (it doesn't matter what you write). This will do the probe. It calls add_disk() for each new disk, so we get hotplug events as a side effect. This was the nicest way I could think of doing this as the interface to the hypervisor is polled ... ChangeSet@1.1743.2.6, 2004-05-25 08:34:44-07:00, akpm@osdl.org [PATCH] ppc64: fix to viopath.c From: Anton Blanchard From: Olaf Hering and Nathan Lynch: Fix a couple of nasty lurking bugs in viopath.c and add information required to know if the iseries_veth module should be loaded on legacy iSeries systems. ChangeSet@1.1743.2.5, 2004-05-25 08:34:35-07:00, akpm@osdl.org [PATCH] ppc64: NUMA fixes From: Anton Blanchard From: Anton Blanchard, Dave Hansen and Olof Johansson: Fix multiple bugs in the ppc64 NUMA topology probe code. - We were using HW cpu numbers instead of logical ones. 615, 630, 650, some 670 and some 690 SMP will all fail to boot without this patch. - The old code would BUG() when it got confused (more NUMA zones than the kernel is configured for etc). - The common depth calculation was incorrect. Dave found an OF property that gives us exactly what we want. - Things were broken on SMT machines. The new code should work on those broken systems and should no longer BUG() but fall back to a flat topology when it gets confused. ChangeSet@1.1743.2.4, 2004-05-25 08:34:24-07:00, akpm@osdl.org [PATCH] ppc64: fix inline spinlocks From: Anton Blanchard In _raw_spin_lock_flags we were branching to the wrong spot and would restore random stuff to the MSR. ChangeSet@1.1743.2.3, 2004-05-25 08:05:12-07:00, davej@redhat.com [PATCH] Make early_cpu_detect() set x86_cache_alignment on pre-cpuid CPU's too From: Zdenek Pavlas On any x86 without cpuid, early_cpu_detect() left x86_cache_alignment as zero, so kmem_cache_init() calls cache_estimate() with align == 0, and it loops forever. I've tried this trivial fix, and it works for me. Andi Kleen looked over this, and ok'd it. ChangeSet@1.1743.2.2, 2004-05-24 17:19:59-07:00, paulus@samba.org [PATCH] ppc64: better stack traces This improves the stack traces we get on PPC64 by putting a marker in those stack frames that are created as a result of an interrupt or exception. The marker is "regshere" (0x7265677368657265). With this, stack traces show where exceptions have occurred, which can be very useful. This also improves the accuracy of the trace because the relevant return address can be in the link register at the time of the exception rather than on the stack. We now print the PC and exception type for each exception frame, and then the link register if appropriate as the next item in the trace. ChangeSet@1.1743.3.9, 2004-05-24 17:06:48-07:00, Thomas.Wahrenbruch@kobil.com [PATCH] USB: Fix kobil_sct with uhci the kobil_sct didn't work with uhci hcds. It used usb_fill_bulk_urb instead of usb_fill_int_urb. The attached patch fixes this. It starts reading in open now - this gives apps (CT-API) the chance to detect the p'n'p string correctly. ChangeSet@1.1743.3.8, 2004-05-24 17:06:06-07:00, movits@bloomberg.com [PATCH] USB: add support for MS adapter to usb pegasus net driver I took the relevant parts from the patch (not some PHY stuff that was irrelevant). Attached is the patch against stock 2.6.6. ChangeSet@1.1743.3.7, 2004-05-24 17:05:26-07:00, david-b@pacbell.net [PATCH] USB: PXA 2xx UDC and RNDIS g_ether I noticed some problems with the PXA 2xx UDC and the RNDIS version of the ethernet-over-usb link: - Static linking needs more than just two endpoints now - The endpoint autoconfig misbehaves (sounds like what Stefan reported a couple weeks ago) This patch fixes those two problems, though there are a couple others lurking too. ChangeSet@1.1743.3.6, 2004-05-24 17:04:38-07:00, lcapitulino@prefeitura.sp.gov.br [PATCH] USB: /usb/gadget/serial.c warning fix. that code is generating the fallowing warning: drivers/usb/gadget/serial.c:162: warning: `debug' defined but not used When G_SERIAL_DEBUG is not defined, `debug' is not used, because the gs_debug() function is compiled only when G_SERIAL_DEBUG is defined. Thus, a solution is to define `debug' only when G_SERIAL_DEBUG is defined. That includes the use of `debug' as a module parameter (this last part I'm not sure). The patch bellow does that (compiles ok, not tested because I don't have that hardware): ChangeSet@1.1743.3.5, 2004-05-24 17:03:52-07:00, oliver@neukum.org [PATCH] USB: fix fix to kaweth.c the previous patch was buggy. The state must be set _before_ the condition is checked, or there's a window missing a wakeup. This incremental change set fixes that. - fix race condition with current->state ChangeSet@1.1743.3.4, 2004-05-24 17:03:19-07:00, oliver@neukum.org [PATCH] USB: waitqueue related problem in kaweth this was buggy for the same reason that the old msleep was buggy. - safe waiting in case we are left on other wait queues ChangeSet@1.1743.3.3, 2004-05-24 17:02:47-07:00, oliver@neukum.org [PATCH] USB: yet another place for msleep this is in kobil_sct. It uses msleep() and replaces needless GFP_ATOMICs with GFP_NOIO as this function can sleep. - no need for GFP_ATOMIC - use msleep() ChangeSet@1.1743.3.2, 2004-05-24 17:02:10-07:00, oliver@neukum.org [PATCH] USB: clean delays for ehci Here's one you overlooked. - safe sleep helper ChangeSet@1.1743.3.1, 2004-05-24 17:01:41-07:00, errandir_news@mph.eclipse.co.uk [PATCH] USB: usblp printer GET_DEVICE_ID fix There is a problem in the usblp GET_DEVICE_ID ioctl() implementation. The patch below (against 2.6 current) fixes the code to be according to the official usb printer spec. Most printers are not affected by this fix, as they use interface 0 and alternate 0. For those, nothing changes. But my printer/scanner uses interface 1 for the printer. ChangeSet@1.1737.3.15, 2004-05-24 23:14:52+01:00, rmk@flint.arm.linux.org.uk [ARM] pxa2xx_udc needs asm/mach-types.h ChangeSet@1.1737.3.14, 2004-05-24 22:42:29+01:00, rmk@flint.arm.linux.org.uk [ARM] Fix lubbock PCMCIA driver. - access SA1111 GPIO using sa1111_set_io functions. - access Lubbock misc register using lubbock_set_misc_wr - fix CF voltage selection. - don't fiddle with PCMCIA voltage selection when selecting CF voltage. - wait for the voltage switches to stabilise before reading the new card state. ChangeSet@1.1743.1.2, 2004-05-24 10:15:43-07:00, herbert@gondor.apana.org.au [IPSEC]: Use add_timer in find_acq. ChangeSet@1.1743.1.1, 2004-05-24 10:13:27-07:00, herbert@gondor.apana.org.au [IPSEC]: Fix OOPS when deleting an ip address. Looks like I was too hasty in blaming myself :) Although my patch does fix a real bug, it cannot have been responsible for the crash that the OP reported. The reason is that the state timer always keeps a reference to the state so even if it is incorrectly re-added the reference will prevent the crash. Hence the problem is still a bug in the ref counting. I think I've found the real culprit now. __xfrm?_find_acq() is missing an xfrm_state_hold on the create path. This also explains why I never see it myself since Openswan never creates states through that code-path. ChangeSet@1.1744, 2004-05-24 10:09:27-07:00, mroos@linux.ee [SPARC64]: Make 32 CPUs the default. ChangeSet@1.1737.3.13, 2004-05-24 17:29:49+01:00, rmk@flint.arm.linux.org.uk [ARM] Don't reference __machine_arch_type directly. ChangeSet@1.1737.3.12, 2004-05-24 17:18:24+01:00, icampbell@com.rmk.(none) [ARM PATCH] 1893/1: define __ARCH_WANT_SYS_PAUSE for ARM Patch from Ian Campbell The recent changeset "Sanitise handling of unneeded syscall stubs" missed __ARCH_WANT_SYS_PAUSE from include/asm-arm/unistd.h. ChangeSet@1.1737.3.11, 2004-05-24 17:14:00+01:00, rmk@flint.arm.linux.org.uk [ARM] Remove needless include of asm/mach-types.h ChangeSet@1.1737.5.2, 2004-05-24 08:20:03-07:00, James.Bottomley@SteelEye.com [PATCH] pa-risc: kernel/fork.c broken by the new rmap Any architecture (like pa-risc) that makes use of the helper function flush_dcache_mmap_lock() won't compile with the new rmap due to use of the wrong "mapping". Trivial fix. ChangeSet@1.1737.5.1, 2004-05-24 08:16:24-07:00, torvalds@ppc970.osdl.org Merge bk://linux-scsi.bkbits.net/scsi-for-linus-2.6 into ppc970.osdl.org:/home/torvalds/v2.6/linux ChangeSet@1.1737.3.10, 2004-05-24 13:16:26+01:00, rmk@flint.arm.linux.org.uk [ARM] Enable IRQs over context switches Disabling IRQs over context switches causes unreasonable IRQ latency on VIVT cached machines, so provide our own prepare_arch_switch(), finish_arch_switch() and task_running() implementations. We provide an optimised UP version so we don't end up needlessly incrementing and decrementing the preempt count. ChangeSet@1.1737.3.9, 2004-05-24 12:17:09+01:00, rmk@flint.arm.linux.org.uk [ARM] Fix sorting of machine class symbols. These are supposed to be ordered by option name. ChangeSet@1.1737.4.2, 2004-05-24 16:42:26+10:00, nathans@sgi.com [XFS] Rename a subdirectory to make life easier for people (esp. distributors) picking up changes directly from the XFS CVS tree. ChangeSet@1.1737.4.1, 2004-05-24 11:39:19+10:00, nathans@sgi.com Merge sgi.com:/source2/linux-2.6 into sgi.com:/source2/xfs-linux-2.6 ChangeSet@1.1737.3.8, 2004-05-24 00:34:23+01:00, rmk@flint.arm.linux.org.uk [ARM] Remove old static GPIO port definitions for SA1111. Using these old definitions on PXA will result in randomly scribbling over memory. Remove them. ChangeSet@1.1737.1.96, 2004-05-23 16:19:28-07:00, vadim@cs.washington.edu [NET]: Save some space with sysfs strings. ChangeSet@1.1737.1.95, 2004-05-23 16:13:00-07:00, davem@nuts.davemloft.net Merge http://linux-mh.bkbits.net/bluetooth-2.6 into nuts.davemloft.net:/disk1/BK/net-2.6 ChangeSet@1.1737.3.7, 2004-05-24 00:09:54+01:00, rmk@flint.arm.linux.org.uk [ARM] PXAFB bug fixes - There are only 16 entries in the pseudo palette - For dual-panel displays, we need to halve the display height - When disabling the LCD controller, use LCCR0_DIS (aka slow disable) rather than quick disable. - Clean up compiler warnings. ChangeSet@1.1737.3.6, 2004-05-23 23:52:39+01:00, rmk@flint.arm.linux.org.uk [ARM] Remove SA1111 PS/2 IRQ_HANDLED handling. Some SA1111 devices are unable to clear the PS/2 receive IRQ before it has been serviced, so we always re-enter the handler one more time than is strictly necessary. We can't clear the IRQ after servicing because that causes race conditions with other SA1111 devices, so we take the easy option and always return IRQ_HANDLED. ChangeSet@1.1737.3.5, 2004-05-23 23:41:39+01:00, rmk@flint.arm.linux.org.uk [ARM] Update PXA serial driver. - Move CKEN manipulation into power management handling (so we don't shut down the clock to the console port.) - .iotype should be using UPIO_xxx not SERIAL_IO_xxx - Remove each port when module is unloaded. - Remove needless #include. - Remove ASYNC_SKIP_TEST - we don't have any tests to skip. ChangeSet@1.1737.3.4, 2004-05-23 23:29:13+01:00, rmk@flint.arm.linux.org.uk [ARM] Add LCD display parameters for Lubbock board. ChangeSet@1.1737.3.3, 2004-05-23 23:23:59+01:00, rmk@flint.arm.linux.org.uk [ARM] Add lubbock_set_misc_wr() This provides an atomic method to update the Lubbock board specific register from various drivers. ChangeSet@1.1737.3.2, 2004-05-23 22:06:28+01:00, rmk@flint.arm.linux.org.uk [ARM] Provide coherent_dma_mask for PXA MCI device. ChangeSet@1.1737.3.1, 2004-05-23 21:56:17+01:00, rmk@flint.arm.linux.org.uk [ARM] Fix oops in dma_unmap_single() Fix an oops caused by a missing failure return value for devices which do not require DMA bouncing. ChangeSet@1.1737.1.94, 2004-05-23 12:22:09-07:00, viro@parcelfarce.linux.theplanet.co.uk [PATCH] ncpfs compat ioctls This takes ncpfs ioctl handling into fs/compat_ioctl.c, removing it from ppc64 and sparc64 code. Code sanitized, switched to compat_alloc_user_space(), bunch of {k,v}malloc() killed. ChangeSet@1.1612.5.27, 2004-05-23 11:44:28-05:00, brking@us.ibm.com [PATCH] ipr driver version 2.0.7 Bump driver version ChangeSet@1.1612.5.26, 2004-05-23 11:37:37-05:00, brking@us.ibm.com [PATCH] ipr remove anonymous unions for gcc 2.95 This patch removes all usage of anonymous unions from the ipr driver since gcc 2.95 does not support anonymous unions. ChangeSet@1.1612.5.25, 2004-05-23 11:25:01-05:00, brking@us.ibm.com [PATCH] ipr fix for ioa reset timeout oops This patch fixes an oops discovered in test which can occur on bad hardware if the ipr adapter times out coming operational. ChangeSet@1.1612.5.24, 2004-05-23 11:22:07-05:00, brking@us.ibm.com [PATCH] ipr add error logs to abort and reset paths This patch adds additional error logging to abort, device reset, and bus reset paths to help in diagnosing scsi problems on ipr. ChangeSet@1.1612.5.23, 2004-05-23 11:19:21-05:00, brking@us.ibm.com [PATCH] ipr gcc attributes fixes This patch fixes an issue where ipr was including a kernel data structure, list_head, in a packed structure, which causes compile issues on some architectures, and is just a bad thing to do. ChangeSet@1.1612.5.22, 2004-05-23 11:17:44-05:00, jejb@mulgrave.(none) initial 2.6 fixup for ATP870U scsi From: Alan Cox Pretty minimal. queue_command is now called locked, this requires propogating some small locking changes for send_s870 ChangeSet@1.1608.4.6, 2004-05-23 13:43:34+02:00, marcel@holtmann.org [Bluetooth] Define .kobj.k_name for the fake device The PCMCIA devices are not devices for the kernel and the bt3c_cs driver uses a fake device for calling request_firmware(). The fake device initialization must also set .kobj.k_name to prevent an oops until PCMCIA devices are fully integrated into the driver model. ChangeSet@1.1608.4.5, 2004-05-23 13:31:00+02:00, marcel@holtmann.org [Bluetooth] Use try_module_get() for RFCOMM sessions It is not possible to use __module_get() when adding a new RFCOMM session, because there is a case where no reference count is hold. This happens when the module is not in use right now and an incoming connection occurs. ChangeSet@1.1742, 2004-05-23 10:22:27+02:00, perex@suse.cz ALSA CVS update - Jaroslav Kysela PCM Midlevel,ALSA Core Added SNDRV_PCM_SYNC_PTR_APPL and SNDRV_PCM_SYNC_PTR_AVAIL_MIN extensions to SYNC_PTR ioctl for PCM API. ChangeSet@1.1741, 2004-05-23 10:22:01+02:00, perex@suse.cz ALSA CVS update - Takashi Iwai VIA82xx driver - added the DXS entry for ECS K7VTA3 v8.0 - fixed the DXS entry for ASUS A7V8X to NO_VRA. ChangeSet@1.1740, 2004-05-23 10:21:22+02:00, perex@suse.cz ALSA CVS update - Takashi Iwai ALSA Core added reverse selections of components to CONFIG_SND_BIT32_EMUL. ChangeSet@1.1739, 2004-05-23 10:14:09+02:00, perex@suse.cz ALSA CVS update - Takashi Iwai PCI drivers,ICE1712 driver,ICE1724 driver - improved the description of ice1724 driver on Kconfig. - better support of VT1720 with snd-ice1724 driver. - check PCI subsystem IDs when no EEPROM is available (ice1724 only) - change the driver name string if given in the board list. - merged prodigy 7.1 support into aureon.c. they are almost identical. - allow to use PDMA4 and RMDA1 for non-SPDIF purpose if specified (ice1724 only). ChangeSet@1.1737.1.93, 2004-05-22 22:46:07-07:00, torvalds@ppc970.osdl.org Linux 2.6.7-rc1 TAG: v2.6.7-rc1