Summary of changes from v2.6.3-rc3 to v2.6.3-rc4 ============================================ [Bluetooth] Revert reference counting fixes The RFCOMM TTY code don't leak reference counting, because the TTY layer will call the ->close() method even if open fails and the reference count is decreased there. Patch from David Woodhouse [PATCH] Sparc no longer F*cked Up From: Keith M Wesolowski As of 2.6.3, restore_flags will no longer modify cwp on sparc. Therefore you can apply this patch to the locking guide. [ Indeed. I'll also remove the atomic comments from Hacking Guide as part of my revision there when I get back to it. --RR ] [PATCH] Remove debug cruft from via-pmu.c driver [PATCH] Fix Oops & warning on PPC in rivafb Independently from the other fbdev updates I'm cooking (some of them will be in your mailbox rsn), this fixes an error in parameter passing to a function in rivafb (only used on ppc) that could cause an oops and definitely causes a warning at compile time. [PATCH] shield fbdev operations with console semaphore This fixes the fbdev ioctl's and fbcon cursor management with the console semaphore, which is the best we can do at this point in 2.6, thus fixing a bunch of races where we could have, for example, tried to blit while changing mode, etc.. [PATCH] Fix fbdev pixmap locking This removes the broken locking code in the pixmaps, and rewrite the buffer access function to properly call fb_sync when needed. The old broken loocking is useless as we are covered by the console semaphore in all cases hopefully (except if I missed one :) [PATCH] Update aty128fb video driver This updates the aty128fb driver. It adds more PCI IDs, uses the new framebuffer alloc/release functions, make BIOS PLL data access more reliable (using ROM whenever possible, with a fallback to RAM BIOS image), cleanup the Power Management stuff (get rid of PowerMac specific stuffs, use real PCI ones instead), along with some style cleanups [PATCH] fbdev state management This adds some "state" information for power management to fbdev's, along with a notifier mecanism to inform clients of state changes. It also "uses" this mecanism in the function fb_set_suspend() which was an empty placeholder previously, and "shields" various places that access the HW when state isn't running. (It's best to not call them in the first place, but the current state of fbcon makes that _very_ difficult) [PATCH] fbcon notified of suspend/resume This makes fbcon ask for notification of events from fbdev to deal with suspend/resume (stop cursor on suspend, refresh screen on resume). Could probably do more (like dealing better with the cursor timer), but this simple implementation works fine enough for now. [PATCH] Missing initialization code for old radeon driver You can still build the old driver, but it doesn't work unless you also enable it like this.. Fix new radeon clock calculation. From Peter Osterlund This code only ends up being used when all else fails, so probably very few people actually ever saw this. Fix user-visible typo in printk. Somebody has been watching lord of the rings a bit too much.. "My precioussssss.." [PATCH] fix radeonfb "noaccel" command line Fix proper detection of the "noaccel" command line argument for new radeonfb so we can boot without acceleration. Useful when diagnosing an accel-related problem. Fix radeonfb to use the proper BIOS reference divider for flat-panel displays. From: Benjamin Herrenschmidt [PATCH] Update mac network drivers This should merge up the final piece of the ppc32/64 saga: the mac PowerMac MACE and Airport network drivers. Both of them are ported to the mac-io infrastructure, all probe code rewritting & cleaned up, better error handling & resource management. [PATCH] radeonfb: limit ioremap size & debug output This adds a limit on how much of the framebuffer is ioremap'ed by radeonfb, thus enabling it to work with 128Mb VRAM or more on an x86 with 900Mb of lowmem in the linear mapping. It also adds a significant amount of debug messages and adds a CONFIG option to enable the debugging output, that should help with diagnosing new problems. Among others, it dumps the connector info as I understand them (so far, they give "strange" informations on laptops, I need more data on more various laptops to see if there's a pattern I can really use to figure out on which connector the LVDS is) Regarding the "lid closed at boot", ultimately, we may want to default to the VGA output in those cases, though I'm not sure what logic to use here. Maybe we could standardize some way for the platform to provide this "environment" information to the driver, but i wouldn't rely on it. More reliably, if we can find out that there is an LVDS output, and LVDS is disabled, just ignore the flat panel... We could assume any mobility chip has LVDS, which is true, but that would still cause a problem for laptops with an additional DVI output (only Macs so far afaik). [PATCH] Update platinumfb driver This updates the PowerMac-only platinumfb driver to use the new mac-io device infrastructure. It also switch allocation to the new framebuffer_alloc/release and fix a couple of bugs. [PATCH] fix ppc64 LPAR This fixes pSeries LPAR (logical partitioned) machines. We weren't initialising the pci_dma_ops stuff. [PATCH] SELinux: context mount support - LSM/FS From: James Morris This series of patches adds support for SELinux 'context mounts', which allows filesystems to be assigned security context information at mount time. For example, some filesystems do not support extended attributes (e.g. NFS, vfat), and this feature allows security contexts to be assigned to them on a per-mountpoint basis. It is also useful when the existing labeling on a filesystem is untrusted or unwanted for some reason (e.g. removable media), and needs to be overridden with a safe default. The first patch below consists of infrastructure changes to the kernel: - A new LSM hook has been added, sb_copy_data, which allows the security module to copy security-specific mount data once the superblock has been setup by the filesystem. - The sb_kern_mount hook has been modified to take this security data as a parameter, and would typically be used at that point to configure the security parameters of the filesystem being mounted. - Allocation and freeing of the security data has been implemented in the core fs code as it is cleaner than trying to do it purely via LSM hooks, and should make maintenance easier. This code will be compiled away if LSM is not enabled. [PATCH] SELinux: context mount support - NFS From: James Morris This patch modifies the kernel's NFS mount data structure to include SELinux context mount data. It allows NFS fileystems to be labeled on a per-mountpoint basis, and should not affect existing versions of userspace mount. (A patch to the userspace mount code is available at http://people.redhat.com/jmorris/selinux/context_mounts/) [PATCH] SELinux: context mount support - SELinux changes. From: James Morris This patch implements context mount support within SELinux. Three new mount options are provided: context=%s Label the entire filesystem with the specified security context during mount and change the labeling behavior to 'mountpoint labeling'. The /proc/self/attr/fscreate attribute will be ignored for file creation on the filesystem, although policy-specified transitions will still work normally. This also sets the aggregate filesystem security context. fscontext=%s Set the label of the aggregate filesystem to the specified security context, so that SELinux policy controls over the filesystem itself may be reinstated. Only works for filesystems without EA labeling support, and is not valid if 'context' has been specified. defcontext=%s Set the default security context for files created in this filesystem to the specified security context (as opposed to the current global default). Only works for filesystems without EA labeling support, and is not valid if 'context' has been specified. To set the context or fscontext options, the security policy must specify appropriate permissions for the filesystem relabelfrom and filesystem relabelto controls. For the defcontext option, the filesystem relablefrom and filesystem assoicate controls are invoked. The security mount options are parsed out and stripped from the normal mount option data so that no normal filesystems need to be aware of them. Filesystems with binary mount option data (e.g. NFS, SMBFS, AFS, Coda) need to be handled as special cases: only NFS is supprted at this stage per the previous patch. [PATCH] devfs do_mount fix From: James Morris devfs is passing an empty string to do_mount when it expects a page. [PATCH] selinux: Allow non-root processes to read selinuxfs enforce node From: Stephen Smalley This patch changes the mode bits on the selinuxfs enforce node so that non-root processes can read it. This is necessary to allow non-root userspace policy enforcers to check the enforcing flag upon a permission failure as well. A process must still have the appropriate SELinux permission in order to read the node. [PATCH] selinux: mark avc_init with __init From: James Morris The avc_init function is only called during kernel init, so it can be marked with __init. [PATCH] SELinux: Fix error handling bug. From: James Morris The patch below fixes an error handling flaw, where we need to return a Netfilter verdict from the function rather than a standard error code. [PATCH] Small typo in aty128fb This fixes a small merge error in aty128fb resulting in a compile failure. Fix link error with RADEON_DEBUG and !RADEON_I2C. [PATCH] fix OOPS on non-DMA IDE hosts with CONFIG_BLK_DEV_IDEDMA=y From: Glenn Wurster [PATCH] ide-tape: fix "sleeping function called from invalid context" From: Willem Riede [PATCH] ide-tape: warn about soon to be removed OnStream support I see only pros of removing OnStream support: - SCSI osst.c driver is actively maintained by Willem Riede - there is no functionality loss (OnStream IDE drives don't support DSC) - ide-tape.c driver is too ugly & complicated even without OnStream support - long term benefits (2.7.x plans on unifying storage drivers) [PATCH] remove ide_dma_{good,bad}_drive from ide_hwif_t Use __ide_dma_{good,bad}_drive() directly and remove these wrappers. [PATCH] remove __ide_dma_count() and ide_hwif_t->ide_dma_count ->ide_dma_count() was introduced in kernel 2.5.35 and was meant to add support for host FIFO counters (for VDMA), but is only a wrapper for ->ide_dma_begin() (even for siimage.c b/c SIIMAGE_VIRTUAL_DMAPIO is undefined). Moreover it should be possible to add VDMA code directly to ->ide_dma_begin(). [PATCH] make __ide_dma_off() generic and remove ide_hwif_t->ide_dma_off Move ide-dma.c:__ide_dma_off() outside of #ifdef CONFIG_BLK_DEV_IDEDMA_PCI, so it can be used for all DMA capable hosts. Remove ide_hwif_t->ide_dma_off. [PATCH] Fix rtasd zombie on PowerMac G5 The rtasd kernel thread would exit before daemoniz'ing itself if RTAS wasn't present (or if allocation of the buffer failed), thus leaving a zombie. This patch fixes it (and remove #if 0'ed code) Revert the dodgy ia64 serial console changeset by Bjorn Helgaas. It results in serial console getting initialised really late and the suggested workaround is broken according to Keith. Cset exclude: akpm@osdl.org|ChangeSet|20040213234712|28554 [PATCH] Fix building both old & new radeonfb's This fixes the build of "allyesconfig", old and new radeonfb's would collide on some symbols. [PATCH] ppc32: Fix MPC82xx thinko From: Tom Rini Replace MSR_, which is gone now, with the value it used to be. Required to get the MPC82xx platforms compiling again. [PATCH] ppc32: Fix MPC82xx UARTs From: Tom Rini Hello. The following patch is all that is required to get current 2.6 to compile and work on MPC82xx platforms. [PATCH] Fix ppc compile problem with gcc 3.4 There's an incorrect redefinition extern/static in prep_pci. Just remove it. Linux 2.6.3-rc4