3.1.5-stable review
Subsystems (59)
cover 3.1.5-stable review
This is the start of the stable review cycle for the 3.1.5 release. There are 104 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let us know. If anyone is a maintainer of the proper subsystem, and wants to add a Signed-off-by: line to the patch, please respond with it.
Responses should be made by Friday, December 9, 2011, 17:00:00 UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.1.5-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
Makefile | 4 +- arch/arm/Kconfig | 12 +++ arch/arm/configs/ezx_defconfig | 2 +- arch/arm/configs/imote2_defconfig | 2 +- arch/arm/configs/magician_defconfig | 2 +- arch/arm/configs/zeus_defconfig | 2 +- arch/arm/kernel/process.c | 3 + arch/arm/mach-mxs/clock-mx28.c | 2 +- arch/arm/mach-omap2/Kconfig | 1 + arch/arm/mach-omap2/omap_hwmod.c | 6 +- arch/arm/mach-omap2/pm.c | 6 +- arch/arm/mach-omap2/smartreflex.c | 2 +- arch/arm/mach-omap2/twl-common.c | 11 +++ arch/arm/mach-omap2/twl-common.h | 3 + arch/arm/mach-pxa/balloon3.c | 2 +- arch/arm/mach-pxa/colibri-pxa320.c | 2 +- arch/arm/mach-pxa/gumstix.c | 2 +- arch/arm/mach-pxa/include/mach/palm27x.h | 4 +- arch/arm/mach-pxa/palm27x.c | 4 +- arch/arm/mach-pxa/palmtc.c | 2 +- arch/arm/mach-pxa/vpac270.c | 2 +- arch/s390/kernel/ptrace.c | 18 +++++ arch/x86/include/asm/timer.h | 23 ++++++- arch/x86/kernel/cpu/perf_event_intel_ds.c | 6 +- arch/x86/kernel/mpparse.c | 2 +- arch/x86/kernel/reboot.c | 13 +++- arch/x86/mm/highmem_32.c | 2 + arch/x86/oprofile/init.c | 7 +- drivers/crypto/mv_cesa.c | 12 ++- drivers/firmware/sigma.c | 81 +++++++++++++++------ drivers/gpu/drm/drm_crtc.c | 4 + drivers/gpu/drm/i915/i915_irq.c | 1 + drivers/gpu/drm/i915/i915_reg.h | 4 + drivers/gpu/drm/i915/i915_suspend.c | 2 + drivers/gpu/drm/i915/intel_display.c | 14 ++++ drivers/gpu/drm/i915/intel_panel.c | 3 +- drivers/gpu/drm/radeon/evergreen.c | 7 ++- drivers/gpu/drm/radeon/r100.c | 7 ++- drivers/gpu/drm/radeon/radeon_atombios.c | 24 ++++++ drivers/gpu/drm/radeon/rs600.c | 7 ++- drivers/gpu/drm/radeon/rv770.c | 7 ++- drivers/hid/hid-core.c | 2 +- drivers/hid/hid-ids.h | 2 +- drivers/i2c/algos/i2c-algo-bit.c | 4 +- drivers/infiniband/core/addr.c | 9 ++- drivers/infiniband/hw/cxgb3/iwch_cm.c | 4 + drivers/infiniband/hw/cxgb4/cm.c | 4 + drivers/infiniband/hw/mlx4/qp.c | 2 +- drivers/infiniband/hw/nes/nes_cm.c | 6 +- drivers/infiniband/ulp/ipoib/ipoib_main.c | 18 +++-- drivers/infiniband/ulp/ipoib/ipoib_multicast.c | 6 +- drivers/net/wireless/iwlwifi/iwl-agn-rxon.c | 36 ++++++--- drivers/net/wireless/iwlwifi/iwl-agn-sta.c | 5 - drivers/net/wireless/iwlwifi/iwl-agn.c | 29 ++++---- drivers/net/wireless/iwlwifi/iwl-agn.h | 2 + drivers/net/wireless/iwlwifi/iwl-pci.c | 8 +- drivers/net/wireless/p54/p54spi.c | 5 +- drivers/net/wireless/rt2x00/rt2800lib.c | 2 +- drivers/net/wireless/rtlwifi/ps.c | 17 ++-- drivers/oprofile/oprof.c | 29 ++++++- drivers/oprofile/timer_int.c | 1 + drivers/pci/hotplug/shpchp_core.c | 4 +- drivers/pci/hotplug/shpchp_hpc.c | 4 +- drivers/regulator/aat2870-regulator.c | 2 +- drivers/regulator/twl-regulator.c | 46 +++++++++++- drivers/rtc/class.c | 10 +- drivers/rtc/interface.c | 44 +++++++++--- drivers/scsi/scsi_lib.c | 3 +- drivers/staging/comedi/comedi_fops.c | 94 ++++++++++++++++++------ drivers/staging/rts_pstor/rtsx.c | 1 + drivers/staging/usbip/vhci_rx.c | 10 ++- drivers/usb/host/ehci-sched.c | 22 ++++-- drivers/usb/host/whci/qset.c | 2 +- drivers/usb/host/xhci.c | 5 +- drivers/usb/musb/musb_core.c | 6 -- drivers/usb/serial/ftdi_sio.c | 1 + drivers/usb/serial/ftdi_sio_ids.h | 1 + drivers/usb/serial/option.c | 4 + drivers/usb/storage/unusual_devs.h | 7 ++ drivers/video/via/share.h | 4 +- fs/ecryptfs/crypto.c | 26 ++++--- fs/ecryptfs/ecryptfs_kernel.h | 5 +- fs/ecryptfs/file.c | 23 ++++++- fs/ecryptfs/inode.c | 52 ++++++++----- fs/ext4/inode.c | 2 +- fs/xfs/xfs_buf.h | 1 - fs/xfs/xfs_file.c | 34 +++++++-- fs/xfs/xfs_iops.c | 2 +- fs/xfs/xfs_mount.c | 29 +++----- fs/xfs/xfs_qm.c | 3 +- fs/xfs/xfs_vnodeops.c | 14 +++- include/drm/drm_mode.h | 2 + include/drm/drm_pciids.h | 8 ++ include/linux/clocksource.h | 3 +- include/linux/sigma.h | 13 +-- kernel/cgroup_freezer.c | 11 ++- kernel/hrtimer.c | 6 +- kernel/irq/manage.c | 5 +- kernel/irq/spurious.c | 4 +- kernel/jump_label.c | 3 +- kernel/time/clockevents.c | 1 + kernel/time/clocksource.c | 62 +++++++++++++--- kernel/time/tick-broadcast.c | 2 +- kernel/time/timekeeping.c | 11 +++ kernel/trace/ftrace.c | 1 - kernel/trace/trace_events.c | 1 - kernel/trace/trace_events_filter.c | 6 +- mm/hugetlb.c | 2 + mm/slab.c | 5 +- net/bridge/br_multicast.c | 2 + net/mac80211/agg-tx.c | 41 ++++++++++- net/mac80211/main.c | 6 ++ net/sunrpc/xprtsock.c | 3 +- net/wireless/nl80211.c | 4 +- net/wireless/reg.c | 49 ++++++++---- sound/pci/hda/patch_realtek.c | 14 +++- sound/pci/hda/patch_sigmatel.c | 18 ----- sound/pci/hda/patch_via.c | 76 +++++++++++-------- sound/pci/lx6464es/lx_core.c | 16 +++- sound/soc/codecs/ad1836.h | 2 +- sound/soc/codecs/sta32x.c | 63 ++++++++++++++++- sound/soc/codecs/sta32x.h | 1 + sound/soc/codecs/wm8731.c | 1 + sound/soc/codecs/wm8753.c | 3 + sound/soc/fsl/fsl_ssi.c | 1 + tools/perf/util/trace-event-parse.c | 2 + 126 files changed, 1030 insertions(+), 390 deletions(-)
PATCH 1/104 eCryptfs: Prevent file create race condition
3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tyler Hicks <[email protected]>
commit b59db43ad4434519feb338eacb01d77eb50825c5 upstream.
The file creation path prematurely called d_instantiate() and unlock_new_inode() before the eCryptfs inode info was fully allocated and initialized and before the eCryptfs metadata was written to the lower file.
This could result in race conditions in subsequent file and inode operations leading to unexpected error conditions or a null pointer dereference while attempting to use the unallocated memory.
https://launchpad.net/bugs/813146
--- fs/ecryptfs/crypto.c | 22 +++++++++-------- fs/ecryptfs/ecryptfs_kernel.h | 5 ++-- fs/ecryptfs/inode.c | 52 +++++++++++++++++++++++++----------------- 3 files changed, 46 insertions(+), 33 deletions(-)
fs/ecryptfs/crypto.c +12 -10
@@ -967,7 +967,7 @@ static void ecryptfs_set_default_crypt_s/** * ecryptfs_new_file_context -* @ecryptfs_dentry: The eCryptfs dentry +* @ecryptfs_inode: The eCryptfs inode * * If the crypto context for the file has not yet been established, * this is where we do that. Establishing a new crypto context
@@ -984,13 +984,13 @@ static void ecryptfs_set_default_crypt_s* * Returns zero on success; non-zero otherwise */ -int ecryptfs_new_file_context (struct dentry *ecryptfs_dentry) +int ecryptfs_new_file_context (struct inode *ecryptfs_inode) {struct ecryptfs_crypt_stat *crypt_stat = - &ecryptfs_inode_to_private (ecryptfs_dentry->d_inode)->crypt_stat; + &ecryptfs_inode_to_private (ecryptfs_inode)->crypt_stat;struct ecryptfs_mount_crypt_stat *mount_crypt_stat = &ecryptfs_superblock_to_private ( - ecryptfs_dentry->d_sb)->mount_crypt_stat; + ecryptfs_inode->i_sb)->mount_crypt_stat;int cipher_name_len;int rc =0 ;
@@ -1299,12 +1299,12 @@ static int ecryptfs_write_headers_virt(c }static int -ecryptfs_write_metadata_to_contents (struct dentry *ecryptfs_dentry, +ecryptfs_write_metadata_to_contents (struct inode *ecryptfs_inode,char *virt,size_t virt_len) {int rc; - rc =ecryptfs_write_lower (ecryptfs_dentry->d_inode, virt, + rc =ecryptfs_write_lower (ecryptfs_inode, virt,0 , virt_len);if (rc <0 ) printk(KERN_ERR "%s: Error attempting to write header "
@@ -1338,7 +1338,8 @@ static unsigned long ecryptfs_get_zeroed/** * ecryptfs_write_metadata -* @ecryptfs_dentry: The eCryptfs dentry +* @ecryptfs_dentry: The eCryptfs dentry, which should be negative +* @ecryptfs_inode: The newly created eCryptfs inode * * Write the file headers out. This will likely involve a userspace * callout, in which the session key is encrypted with one or more
@@ -1348,10 +1349,11 @@ static unsigned long ecryptfs_get_zeroed* * Returns zero on success; non-zero on error */ -int ecryptfs_write_metadata (struct dentry *ecryptfs_dentry) +int ecryptfs_write_metadata (struct dentry *ecryptfs_dentry, +struct inode *ecryptfs_inode) {struct ecryptfs_crypt_stat *crypt_stat = - &ecryptfs_inode_to_private (ecryptfs_dentry->d_inode)->crypt_stat; + &ecryptfs_inode_to_private (ecryptfs_inode)->crypt_stat;unsigned int order;char *virt;size_t virt_len;
@@ -1391,7 +1393,7 @@ int ecryptfs_write_metadata(struct dentr rc =ecryptfs_write_metadata_to_xattr (ecryptfs_dentry, virt, size); else - rc =ecryptfs_write_metadata_to_contents (ecryptfs_dentry, virt, + rc =ecryptfs_write_metadata_to_contents (ecryptfs_inode, virt, virt_len);if (rc) { printk(KERN_ERR "%s: Error writing metadata out to lower file; "
fs/ecryptfs/ecryptfs_kernel.h +3 -2
@@ -584,9 +584,10 @@ int ecryptfs_init_crypt_ctx(struct ecrypint ecryptfs_write_inode_size_to_metadata (struct inode *ecryptfs_inode);int ecryptfs_encrypt_page (struct page *page);int ecryptfs_decrypt_page (struct page *page); -int ecryptfs_write_metadata (struct dentry *ecryptfs_dentry); +int ecryptfs_write_metadata (struct dentry *ecryptfs_dentry, +struct inode *ecryptfs_inode);int ecryptfs_read_metadata (struct dentry *ecryptfs_dentry); -int ecryptfs_new_file_context (struct dentry *ecryptfs_dentry); +int ecryptfs_new_file_context (struct inode *ecryptfs_inode);void ecryptfs_write_crypt_stat_flags (char *page_virt,struct ecryptfs_crypt_stat *crypt_stat,size_t *written);
fs/ecryptfs/inode.c +31 -21
127 lines not on this page · raw message
PATCH 2/104 eCryptfs: Flush file in vma close
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tyler Hicks <[email protected]>
commit 32001d6fe9ac6b0423e674a3093aa56740849f3b upstream.
Dirty pages weren't being written back when an mmap'ed eCryptfs file was closed before the mapping was unmapped. Since f_ops->flush() is not called by the munmap() path, the lower file was simply being released. This patch flushes the eCryptfs file in the vm_ops->close() path.
https://launchpad.net/bugs/870326
--- fs/ecryptfs/file.c | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-)
fs/ecryptfs/file.c +22 -1
@@ -139,6 +139,27 @@ out:return rc; } +static void ecryptfs_vma_close (struct vm_area_struct *vma) +{ +filemap_write_and_wait (vma->vm_file->f_mapping); +} + +static const struct vm_operations_struct ecryptfs_file_vm_ops = { + .close = ecryptfs_vma_close, + .fault = filemap_fault, +}; + +static int ecryptfs_file_mmap (struct file *file,struct vm_area_struct *vma) +{ +int rc; + + rc =generic_file_mmap (file, vma); +if (!rc) + vma->vm_ops = &ecryptfs_file_vm_ops; + +return rc; +} +struct kmem_cache *ecryptfs_file_info_cache;/**
@@ -349,7 +370,7 @@ const struct file_operations ecryptfs_ma#ifdef CONFIG_COMPAT .compat_ioctl = ecryptfs_compat_ioctl, #endif - .mmap = generic_file_mmap, + .mmap = ecryptfs_file_mmap, .open = ecryptfs_open, .flush = ecryptfs_flush, .release = ecryptfs_release,
PATCH 3/104 i2c-algo-bit: Generate correct i2c address sequence for 10-bit target
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Jeffrey (Sheng-Hui) Chu" <[email protected]>
commit cc6bcf7d2ec2234e7b41770185e4dc826390185e upstream.
The wrong bits were put on the wire, fix that.
This fixes kernel bug #42562.
--- drivers/i2c/algos/i2c-algo-bit.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/i2c/algos/i2c-algo-bit.c +2 -2
@@ -486,7 +486,7 @@ static int bit_doAddress(struct i2c_adapif (flags &I2C_M_TEN ) {/* a ten bit address */ - addr =0xf0 | ((msg->addr >>7 ) &0x03 ); + addr =0xf0 | ((msg->addr >>7 ) &0x06 );bit_dbg (2 , &i2c_adap->dev,"addr0: %d\n" , addr);/* try extended address code...*/ ret =try_address (i2c_adap, addr, retries);
@@ -496,7 +496,7 @@ static int bit_doAddress(struct i2c_adapreturn -EREMOTEIO ; }/* the remaining 8 bit address */ - ret =i2c_outb (i2c_adap, msg->addr &0x7f ); + ret =i2c_outb (i2c_adap, msg->addr &0xff );if ((ret !=1 ) && !nak_ok) {/* the chip did not ack / xmission error occurred */ dev_err (&i2c_adap->dev,"died at 2nd address code\n" );
PATCH 4/104 eCryptfs: Extend array bounds for all filename chars
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tyler Hicks <[email protected]>
commit 0f751e641a71157aa584c2a2e22fda52b52b8a56 upstream.
Quoted 1 line
Quoted 1 line
From mhalcrow's original commit message:
Characters with ASCII values greater than the size of filename_rev_map[] are valid filename characters. ecryptfs_decode_from_filename() will access kernel memory beyond that array, and ecryptfs_parse_tag_70_packet() will then decrypt those characters. The attacker, using the FNEK of the crafted file, can then re-encrypt the characters to reveal the kernel memory past the end of the filename_rev_map[] array. I expect low security impact since this array is statically allocated in the text area, and the amount of memory past the array that is accessible is limited by the largest possible ASCII filename character.
This patch solves the issue reported by mhalcrow but with an implementation suggested by Linus to simply extend the length of filename_rev_map[] to 256. Characters greater than 0x7A are mapped to 0x00, which is how invalid characters less than 0x7A were previously being handled.
--- fs/ecryptfs/crypto.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
fs/ecryptfs/crypto.c +2 -2
@@ -1945,7 +1945,7 @@ static unsigned char *portable_filename_/* We could either offset on every reverse map or just pad some 0x00's * at the front here */ -static const unsigned char filename_rev_map[] = { +static const unsigned char filename_rev_map[256 ] = {0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,/* 7 */ 0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,/* 15 */ 0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,0x00 ,/* 23 */
@@ -1961,7 +1961,7 @@ static const unsigned char filename_rev_0x00 ,0x26 ,0x27 ,0x28 ,0x29 ,0x2A ,0x2B ,0x2C ,/* 103 */ 0x2D ,0x2E ,0x2F ,0x30 ,0x31 ,0x32 ,0x33 ,0x34 ,/* 111 */ 0x35 ,0x36 ,0x37 ,0x38 ,0x39 ,0x3A ,0x3B ,0x3C ,/* 119 */ -0x3D ,0x3E ,0x3F +0x3D ,0x3E ,0x3F /* 123 - 255 initialized to 0x00 */ };/**
PATCH 5/104 crypto: mv_cesa - fix hashing of chunks > 1920 bytes
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Phil Sutter <[email protected]>
commit 274252862f386b7868f35bf5ceaa5391a8ccfdf3 upstream.
This was broken by commit 7759995c75ae0cbd4c861582908449f6b6208e7a (yes, myself). The basic problem here is since the digest state is only saved after the last chunk, the state array is only valid when handling the first chunk of the next buffer. Broken since linux-3.0.
--- drivers/crypto/mv_cesa.c | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-)
drivers/crypto/mv_cesa.c +7 -5
@@ -342,11 +342,13 @@ static void mv_process_hash_current(intelse op.config |=CFG_MID_FRAG ; -writel (req_ctx->state[0 ], cpg->reg +DIGEST_INITIAL_VAL_A ); -writel (req_ctx->state[1 ], cpg->reg +DIGEST_INITIAL_VAL_B ); -writel (req_ctx->state[2 ], cpg->reg +DIGEST_INITIAL_VAL_C ); -writel (req_ctx->state[3 ], cpg->reg +DIGEST_INITIAL_VAL_D ); -writel (req_ctx->state[4 ], cpg->reg +DIGEST_INITIAL_VAL_E ); +if (first_block) { +writel (req_ctx->state[0 ], cpg->reg +DIGEST_INITIAL_VAL_A ); +writel (req_ctx->state[1 ], cpg->reg +DIGEST_INITIAL_VAL_B ); +writel (req_ctx->state[2 ], cpg->reg +DIGEST_INITIAL_VAL_C ); +writel (req_ctx->state[3 ], cpg->reg +DIGEST_INITIAL_VAL_D ); +writel (req_ctx->state[4 ], cpg->reg +DIGEST_INITIAL_VAL_E ); + } }memcpy (cpg->sram +SRAM_CONFIG , &op,sizeof (struct sec_accel_config ));
PATCH 6/104 drm: integer overflow in drm_mode_dirtyfb_ioctl()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xi Wang <[email protected]>
commit a5cd335165e31db9dbab636fd29895d41da55dd2 upstream.
There is a potential integer overflow in drm_mode_dirtyfb_ioctl() if userspace passes in a large num_clips. The call to kmalloc would allocate a small buffer, and the call to fb->funcs->dirty may result in a memory corruption.
--- drivers/gpu/drm/drm_crtc.c | 4 ++++ include/drm/drm_mode.h | 2 ++ 2 files changed, 6 insertions(+)
drivers/gpu/drm/drm_crtc.c +4 -0
@@ -1868,6 +1868,10 @@ int drm_mode_dirtyfb_ioctl(struct drm_de }if (num_clips && clips_ptr) { +if (num_clips <0 || num_clips >DRM_MODE_FB_DIRTY_MAX_CLIPS ) { + ret = -EINVAL ; + goto out_err1; + } clips =kzalloc (num_clips *sizeof (*clips),GFP_KERNEL );if (!clips) { ret = -ENOMEM ;
include/drm/drm_mode.h +2 -0
@@ -233,6 +233,8 @@ struct drm_mode_fb_cmd {#define DRM_MODE_FB_DIRTY_ANNOTATE_FILL 0x02#define DRM_MODE_FB_DIRTY_FLAGS 0x03 +#define DRM_MODE_FB_DIRTY_MAX_CLIPS 256 +/* * Mark a region of a framebuffer as dirty. *
PATCH 7/104 drm/radeon/kms: fix up gpio i2c mask bits for r4xx for real
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit d724502a9d7a46f4a56a1663b1f50d2dc9d1ef40 upstream.
Fixes i2c test failures when i2c_algo_bit.bit_test=1.
The hw doesn't actually require a mask, so just set it to the default mask bits for r1xx-r4xx radeon ddc.
I missed this part the first time through.
--- drivers/gpu/drm/radeon/radeon_atombios.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/gpu/drm/radeon/radeon_atombios.c +12 -0
@@ -169,6 +169,18 @@ void radeon_atombios_i2c_init(struct rad gpio = &i2c_info->asGPIO_Info[i]; i2c.valid = false; +/* r4xx mask is technically not used by the hw, so patch in the legacy mask bits */ +if ((rdev->family ==CHIP_R420 ) || + (rdev->family ==CHIP_R423 ) || + (rdev->family ==CHIP_RV410 )) { +if ((le16_to_cpu (gpio->usClkMaskRegisterIndex) ==0x0018 ) || + (le16_to_cpu (gpio->usClkMaskRegisterIndex) ==0x0019 ) || + (le16_to_cpu (gpio->usClkMaskRegisterIndex) ==0x001a )) { + gpio->ucClkMaskShift =0x19 ; + gpio->ucDataMaskShift =0x18 ; + } + } +/* some evergreen boards have bad data for this entry */ if (ASIC_IS_DCE4 (rdev)) { if ((i == 7) &&
PATCH 8/104 drm/i915: Ivybridge still has fences!
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Vetter <[email protected]>
commit 775d17b6ca4357048f36c22151335addfe15db4b upstream.
So don't forget to restore them on resume and dump them into the error state.
--- drivers/gpu/drm/i915/i915_irq.c | 1 + drivers/gpu/drm/i915/i915_suspend.c | 2 ++ 2 files changed, 3 insertions(+)
drivers/gpu/drm/i915/i915_irq.c +1 -0
@@ -822,6 +822,7 @@ static void i915_gem_record_fences(struc/* Fences */ switch (INTEL_INFO (dev)->gen) { +case 7 :case 6 :for (i =0 ; i <16 ; i++) error->fence[i] =I915_READ64 (FENCE_REG_SANDYBRIDGE_0 + (i *8 ));
drivers/gpu/drm/i915/i915_suspend.c +2 -0
@@ -370,6 +370,7 @@ static void i915_save_modeset_reg(struct/* Fences */ switch (INTEL_INFO (dev)->gen) { +case 7 :case 6 :for (i =0 ; i <16 ; i++) dev_priv->saveFENCE[i] =I915_READ64 (FENCE_REG_SANDYBRIDGE_0 + (i *8 ));
@@ -404,6 +405,7 @@ static void i915_restore_modeset_reg(str/* Fences */ switch (INTEL_INFO (dev)->gen) { +case 7 :case 6 :for (i =0 ; i <16 ; i++)I915_WRITE64 (FENCE_REG_SANDYBRIDGE_0 + (i *8 ), dev_priv->saveFENCE[i]);
PATCH 9/104 drm/i915: Turn on a required 3D clock gating bit on Sandybridge.
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Anholt <[email protected]>
commit 406478dc911e16677fbd9c84d1d50cdffbc031ab upstream.
Fixes rendering failures in Unigine Tropics and Sanctuary and the mesa "fire" demo.
--- drivers/gpu/drm/i915/i915_reg.h | 3 +++ drivers/gpu/drm/i915/intel_display.c | 9 +++++++++ 2 files changed, 12 insertions(+)
drivers/gpu/drm/i915/i915_reg.h +3 -0
@@ -3401,6 +3401,9 @@#define GT_FIFO_FREE_ENTRIES 0x120008#define GT_FIFO_NUM_RESERVED_ENTRIES 20 +#define GEN6_UCGCTL2 0x9404 +# define GEN6_RCPBUNIT_CLOCK_GATE_DISABLE (1 << 12) +#define GEN6_RPNSWREQ 0xA008#define GEN6_TURBO_DISABLE (1<<31)#define GEN6_FREQUENCY (x) ((x)<<25)
drivers/gpu/drm/i915/intel_display.c +9 -0
@@ -7882,6 +7882,15 @@ static void gen6_init_clock_gating(strucI915_WRITE (WM2_LP_ILK ,0 );I915_WRITE (WM1_LP_ILK ,0 ); +/* According to the BSpec vol1g, bit 12 (RCPBUNIT) clock +* gating disable must be set. Failure to set it results in +* flickering pixels due to Z write ordering failures after +* some amount of runtime in the Mesa "fire" demo, and Unigine +* Sanctuary and Tropics, and apparently anything else with +* alpha test or pixel discard. +*/ +I915_WRITE (GEN6_UCGCTL2 ,GEN6_RCPBUNIT_CLOCK_GATE_DISABLE ); +/* * According to the spec the following bits should be * set in order to enable memory self-refresh and fbc:
PATCH 10/104 drm/i915: Turn on another required clock gating bit on gen6.
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Anholt <[email protected]>
commit 9ca1d10d748e56964de95e3ed80211b192f56cf4 upstream.
Unlike the previous one, I don't have known testcases it fixes. I'd rather not go through the same debug cycle on whatever testcases those might be.
--- drivers/gpu/drm/i915/i915_reg.h | 1 + drivers/gpu/drm/i915/intel_display.c | 7 ++++++- 2 files changed, 7 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/i915_reg.h +1 -0
@@ -3403,6 +3403,7 @@#define GEN6_UCGCTL2 0x9404# define GEN6_RCPBUNIT_CLOCK_GATE_DISABLE (1 << 12) +# define GEN6_RCCUNIT_CLOCK_GATE_DISABLE (1 << 11)#define GEN6_RPNSWREQ 0xA008#define GEN6_TURBO_DISABLE (1<<31)
drivers/gpu/drm/i915/intel_display.c +6 -1
@@ -7888,8 +7888,13 @@ static void gen6_init_clock_gating(struc* some amount of runtime in the Mesa "fire" demo, and Unigine * Sanctuary and Tropics, and apparently anything else with * alpha test or pixel discard. +* +* According to the spec, bit 11 (RCCUNIT) must also be set, +* but we didn't debug actual testcases to find it out. */ -I915_WRITE (GEN6_UCGCTL2 ,GEN6_RCPBUNIT_CLOCK_GATE_DISABLE ); +I915_WRITE (GEN6_UCGCTL2 , +GEN6_RCPBUNIT_CLOCK_GATE_DISABLE | +GEN6_RCCUNIT_CLOCK_GATE_DISABLE );/* * According to the spec the following bits should be
PATCH 11/104 drm/i915: Fix inconsistent backlight level during disabled
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 04b38670cf46c096705f24e92a8747d1ab89e53c upstream.
When the brightness property is inquired while the backlight is disabled, the driver returns a wrong value (zero) because it probes the value after the backlight was turned off. This caused a black screen even after the backlight is enabled again. It should return the internal backlight_level instead, so that it won't be influenced by the backlight-enable state.
--- drivers/gpu/drm/i915/intel_panel.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/gpu/drm/i915/intel_panel.c +2 -1
@@ -326,7 +326,8 @@ static int intel_panel_update_status(strstatic int intel_panel_get_brightness (struct backlight_device *bd) {struct drm_device *dev =bl_get_data (bd); -return intel_panel_get_backlight (dev); +struct drm_i915_private *dev_priv = dev->dev_private; +return dev_priv->backlight_level; }static const struct backlight_ops intel_panel_bl_ops = {
PATCH 12/104 PCI hotplug: shpchp: dont blindly claim non-AMD 0x7450 device IDs
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bjorn Helgaas <[email protected]>
commit 4cac2eb158c6da0c761689345c6cc5df788a6292 upstream.
Previously we claimed device ID 0x7450, regardless of the vendor, which is clearly wrong. Now we'll claim that device ID only for AMD.
I suspect this was just a typo in the original code, but it's possible this change will break shpchp on non-7450 AMD bridges. If so, we'll have to fix them as we find them.
Reference: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638863
--- drivers/pci/hotplug/shpchp_core.c | 4 ++-- drivers/pci/hotplug/shpchp_hpc.c | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-)
drivers/pci/hotplug/shpchp_core.c +2 -2
@@ -278,8 +278,8 @@ static int get_adapter_status (struct hostatic int is_shpc_capable (struct pci_dev *dev) { -if ((dev->vendor ==PCI_VENDOR_ID_AMD ) || (dev->device == -PCI_DEVICE_ID_AMD_GOLAM_7450 )) +if (dev->vendor ==PCI_VENDOR_ID_AMD && + dev->device ==PCI_DEVICE_ID_AMD_GOLAM_7450 )return 1 ;if (!pci_find_capability (dev,PCI_CAP_ID_SHPC ))return 0 ;
drivers/pci/hotplug/shpchp_hpc.c +2 -2
@@ -944,8 +944,8 @@ int shpc_init(struct controller *ctrl, s ctrl->pci_dev = pdev;/* pci_dev of the P2P bridge */ ctrl_dbg (ctrl,"Hotplug Controller:\n" ); -if ((pdev->vendor ==PCI_VENDOR_ID_AMD ) || (pdev->device == -PCI_DEVICE_ID_AMD_GOLAM_7450 )) { +if (pdev->vendor ==PCI_VENDOR_ID_AMD && + pdev->device ==PCI_DEVICE_ID_AMD_GOLAM_7450 ) {/* amd shpc driver doesn't use Base Offset; assume 0 */ ctrl->mmio_base =pci_resource_start (pdev,0 ); ctrl->mmio_size =pci_resource_len (pdev,0 );
PATCH 13/104 drm/radeon/kms: fix up gpio i2c mask bits for r4xx
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 6c47e5c23aa2a7c54ad7ac13af4bd56cd9e703bf upstream.
Fixes i2c test failures when i2c_algo_bit.bit_test=1.
The hw doesn't actually require a mask, so just set it to the default mask bits for r1xx-r4xx radeon ddc.
--- drivers/gpu/drm/radeon/radeon_atombios.c | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/gpu/drm/radeon/radeon_atombios.c +12 -0
@@ -85,6 +85,18 @@ static inline struct radeon_i2c_bus_recfor (i =0 ; i < num_indices; i++) { gpio = &i2c_info->asGPIO_Info[i]; +/* r4xx mask is technically not used by the hw, so patch in the legacy mask bits */ +if ((rdev->family ==CHIP_R420 ) || + (rdev->family ==CHIP_R423 ) || + (rdev->family ==CHIP_RV410 )) { +if ((le16_to_cpu (gpio->usClkMaskRegisterIndex) ==0x0018 ) || + (le16_to_cpu (gpio->usClkMaskRegisterIndex) ==0x0019 ) || + (le16_to_cpu (gpio->usClkMaskRegisterIndex) ==0x001a )) { + gpio->ucClkMaskShift =0x19 ; + gpio->ucDataMaskShift =0x18 ; + } + } +/* some evergreen boards have bad data for this entry */ if (ASIC_IS_DCE4 (rdev)) { if ((i == 7) &&
PATCH 14/104 viafb: correct sync polarity for OLPC DCON
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Drake <[email protected]>
commit a32839696a8eef813a1aff604fbad9a32dff6c95 upstream.
While the OLPC display appears to be able to handle either positive or negative sync, the Display Controller only recognises positive sync.
This brings viafb (for XO-1.5) in line with lxfb (for XO-1) and fixes a recent regression where the XO-1.5 DCON could no longer be frozen. Thanks to Florian Tobias Schandinat for helping identify the fix.
Test case: from a vt,
echo 1 > /sys/devices/platform/dcon/freeze
should cause the current screen contents to freeze, rather than garbage being displayed.
--- drivers/video/via/share.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/video/via/share.h +2 -2
@@ -557,8 +557,8 @@#define M1200X720_R60_VSP POSITIVE/* 1200x900@60 Sync Polarity (DCON) */ -#define M1200X900_R60_HSP NEGATIVE -#define M1200X900_R60_VSP NEGATIVE +#define M1200X900_R60_HSP POSITIVE +#define M1200X900_R60_VSP POSITIVE/* 1280x600@60 Sync Polarity (GTF Mode) */ #define M1280x600_R60_HSP NEGATIVE
PATCH 15/104 ARM: pxa: fix inconsistent CONFIG_USB_PXA27X
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Haojian Zhuang <[email protected]>
commit c0a39151a4055332897cba615623d3de2f3896df upstream.
Since CONFIG_USB_GADGET_PXA27X and other macros are renamed to CONFIG_USB_PXA27X. Update them in arch/arm/mach-pxa and arch/arm/configs to keep consistent.
--- arch/arm/configs/ezx_defconfig | 2 +- arch/arm/configs/imote2_defconfig | 2 +- arch/arm/configs/magician_defconfig | 2 +- arch/arm/configs/zeus_defconfig | 2 +- arch/arm/mach-pxa/balloon3.c | 2 +- arch/arm/mach-pxa/colibri-pxa320.c | 2 +- arch/arm/mach-pxa/gumstix.c | 2 +- arch/arm/mach-pxa/include/mach/palm27x.h | 4 ++-- arch/arm/mach-pxa/palm27x.c | 4 ++-- arch/arm/mach-pxa/palmtc.c | 2 +- arch/arm/mach-pxa/vpac270.c | 2 +- 11 files changed, 13 insertions(+), 13 deletions(-)
arch/arm/configs/ezx_defconfig +1 -1
@@ -287,7 +287,7 @@ CONFIG_USB=y # CONFIG_USB_DEVICE_CLASS is not set CONFIG_USB_OHCI_HCD=y CONFIG_USB_GADGET=y -CONFIG_USB_GADGET_PXA27X=y +CONFIG_USB_PXA27X=y CONFIG_USB_ETH=m # CONFIG_USB_ETH_RNDIS is not set CONFIG_MMC=y
arch/arm/configs/imote2_defconfig +1 -1
@@ -263,7 +263,7 @@ CONFIG_USB=y # CONFIG_USB_DEVICE_CLASS is not set CONFIG_USB_OHCI_HCD=y CONFIG_USB_GADGET=y -CONFIG_USB_GADGET_PXA27X=y +CONFIG_USB_PXA27X=y CONFIG_USB_ETH=m # CONFIG_USB_ETH_RNDIS is not set CONFIG_MMC=y
arch/arm/configs/magician_defconfig +1 -1
@@ -132,7 +132,7 @@ CONFIG_USB_MON=m CONFIG_USB_OHCI_HCD=y CONFIG_USB_GADGET=y CONFIG_USB_GADGET_VBUS_DRAW=500 -CONFIG_USB_GADGET_PXA27X=y +CONFIG_USB_PXA27X=y CONFIG_USB_ETH=m # CONFIG_USB_ETH_RNDIS is not set CONFIG_USB_GADGETFS=m
arch/arm/configs/zeus_defconfig +1 -1
@@ -140,7 +140,7 @@ CONFIG_USB_SERIAL=m CONFIG_USB_SERIAL_GENERIC=y CONFIG_USB_SERIAL_MCT_U232=m CONFIG_USB_GADGET=m -CONFIG_USB_GADGET_PXA27X=y +CONFIG_USB_PXA27X=y CONFIG_USB_ETH=m CONFIG_USB_GADGETFS=m CONFIG_USB_FILE_STORAGE=m
arch/arm/mach-pxa/balloon3.c +1 -1
@@ -307,7 +307,7 @@ static inline void balloon3_mmc_init(voi/****************************************************************************** * USB Gadget ******************************************************************************/ -#if defined(CONFIG_USB_GADGET_PXA27X )||defined(CONFIG_USB_GADGET_PXA27X_MODULE ) +#if defined(CONFIG_USB_PXA27X )||defined(CONFIG_USB_PXA27X_MODULE )static void balloon3_udc_command (int cmd) {if (cmd ==PXA2XX_UDC_CMD_CONNECT )
arch/arm/mach-pxa/colibri-pxa320.c +1 -1
@@ -146,7 +146,7 @@ static void __init colibri_pxa320_init_estatic inline void __init colibri_pxa320_init_eth (void ) {}#endif /* CONFIG_AX88796 */ -#if defined(CONFIG_USB_GADGET_PXA27X )||defined(CONFIG_USB_GADGET_PXA27X_MODULE ) +#if defined(CONFIG_USB_PXA27X )||defined(CONFIG_USB_PXA27X_MODULE )static struct gpio_vbus_mach_info colibri_pxa320_gpio_vbus_info = { .gpio_vbus =mfp_to_gpio (MFP_PIN_GPIO96 ), .gpio_pullup = -1,
arch/arm/mach-pxa/gumstix.c +1 -1
@@ -106,7 +106,7 @@ static void __init gumstix_mmc_init(void }#endif -#ifdef CONFIG_USB_GADGET_PXA25X +#ifdef CONFIG_USB_PXA25X static struct gpio_vbus_mach_info gumstix_udc_info = { .gpio_vbus = GPIO_GUMSTIX_USB_GPIOn, .gpio_pullup = GPIO_GUMSTIX_USB_GPIOx,
arch/arm/mach-pxa/include/mach/palm27x.h +2 -2
@@ -37,8 +37,8 @@ extern void __init palm27x_lcd_init(intstatic inline void palm27x_lcd_init (int power,struct pxafb_mode_info *mode) {}#endif -#if defined(CONFIG_USB_GADGET_PXA27X ) || \ - defined(CONFIG_USB_GADGET_PXA27X_MODULE ) +#if defined(CONFIG_USB_PXA27X ) || \ + defined(CONFIG_USB_PXA27X_MODULE )extern void __init palm27x_udc_init (int vbus,int pullup,int vbus_inverted);#else
arch/arm/mach-pxa/palm27x.c +2 -2
@@ -164,8 +164,8 @@ void __init palm27x_lcd_init(int power,/****************************************************************************** * USB Gadget ******************************************************************************/ -#if defined(CONFIG_USB_GADGET_PXA27X ) || \ - defined(CONFIG_USB_GADGET_PXA27X_MODULE ) +#if defined(CONFIG_USB_PXA27X ) || \ + defined(CONFIG_USB_PXA27X_MODULE )static struct gpio_vbus_mach_info palm27x_udc_info = { .gpio_vbus_inverted =1 , };
arch/arm/mach-pxa/palmtc.c +1 -1
@@ -338,7 +338,7 @@ static inline void palmtc_mkp_init(void)/****************************************************************************** * UDC ******************************************************************************/ -#if defined(CONFIG_USB_GADGET_PXA25X )||defined(CONFIG_USB_GADGET_PXA25X_MODULE ) +#if defined(CONFIG_USB_PXA25X )||defined(CONFIG_USB_PXA25X_MODULE )static struct gpio_vbus_mach_info palmtc_udc_info = { .gpio_vbus =GPIO_NR_PALMTC_USB_DETECT_N , .gpio_vbus_inverted = 1,
arch/arm/mach-pxa/vpac270.c +1 -1
@@ -343,7 +343,7 @@ static inline void vpac270_uhc_init(void/****************************************************************************** * USB Gadget ******************************************************************************/ -#if defined(CONFIG_USB_GADGET_PXA27X )||defined(CONFIG_USB_GADGET_PXA27X_MODULE ) +#if defined(CONFIG_USB_PXA27X )||defined(CONFIG_USB_PXA27X_MODULE )static struct gpio_vbus_mach_info vpac270_gpio_vbus_info = { .gpio_vbus =GPIO41_VPAC270_UDC_DETECT , .gpio_pullup = -1,
PATCH 16/104 arm: mx28: fix bit operation in clock setting
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wolfram Sang <[email protected]>
commit c2735391fbc68feae10d6d14e60956c8106e725f upstream.
reg | (1 << clk->enable_shift) always evaluates to true. Switch it to & which makes much more sense. Same fix as 13be9f00 (ARM i.MX28: fix bit operation) at a different location.
--- arch/arm/mach-mxs/clock-mx28.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/mach-mxs/clock-mx28.c +1 -1
@@ -404,7 +404,7 @@ static int name##_set_rate(struct clk *c reg = __raw_readl(CLKCTRL_BASE_ADDR + HW_CLKCTRL_##dr); \ reg &= ~BM_CLKCTRL_##dr##_DIV; \ reg |= div << BP_CLKCTRL_##dr##_DIV; \ - if (reg | (1 << clk->enable_shift)) { \ + if (reg & (1 << clk->enable_shift)) { \ pr_err("%s: clock is gated\n", __func__); \ return -EINVAL; \ } \
PATCH 17/104 ARM: OMAP: smartreflex: fix IRQ handling bug
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Felipe Balbi <[email protected]>
commit 5a4f1844c2ba21f804d7729306d9b16eaeb724a8 upstream.
Fix a bug which has been on this driver since it was added by the original commit 984aa6db which would never clear IRQSTATUS bits.
--- arch/arm/mach-omap2/smartreflex.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/mach-omap2/smartreflex.c +1 -1
@@ -137,7 +137,7 @@ static irqreturn_t sr_interrupt(int irq,sr_write_reg (sr_info,ERRCONFIG_V1 , status); }else if (sr_info->ip_type ==SR_TYPE_V2 ) {/* Read the status bits */ -sr_read_reg (sr_info,IRQSTATUS ); + status =sr_read_reg (sr_info,IRQSTATUS );/* Clear them by writing back */ sr_write_reg (sr_info,IRQSTATUS , status);
PATCH 18/104 ARM: OMAP: hwmod: Fix the addr space, irq, dma count APIs
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: sricharan <[email protected]>
commit cc1b0765da6078b906772b79ff211b88cc0ae958 upstream.
The address spaces, irqs and dma reqs count APIs return the number of corresponding entries in a hwmod including a additional null value or a -1 terminator in the structure introduced recently. More information here:
- 212738a4: omap_hwmod: use a terminator record with omap_hwmod_mpu_irqs arrays
- 78183f3f: omap_hwmod: use a null structure record to terminate omap_hwmod_addr_space arrays
- bc614958: omap_hwmod: use a terminator record with omap_hwmod_dma_info arrays
The issue with irqs and dma info was originally reported by Benoit Cousson.
The devices which have multiple hwmods and use device_build_ss are broken with this, as their resources are populated with a extra null value, subsequently the probe fails. So fix the API not to include the array terminator in the count.
--- arch/arm/mach-omap2/omap_hwmod.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/arm/mach-omap2/omap_hwmod.c +3 -3
@@ -749,7 +749,7 @@ static int _count_mpu_irqs(struct omap_h ohii = &oh->mpu_irqs[i++]; }while (ohii->irq !=-1 ); -return i; +return i-1 ; }/**
@@ -772,7 +772,7 @@ static int _count_sdma_reqs(struct omap_ ohdi = &oh->sdma_reqs[i++]; }while (ohdi->dma_req !=-1 ); -return i; +return i-1 ; }/**
@@ -795,7 +795,7 @@ static int _count_ocp_if_addr_spaces(str mem = &os->addr[i++]; }while (mem->pa_start != mem->pa_end); -return i; +return i-1 ; }/**
PATCH 19/104 ARM: OMAP2: select ARM_AMBA if OMAP3_EMU is defined
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ming Lei <[email protected]>
commit a8a6565c7615cab3608d75af95b5c8a3522cd7c4 upstream.
This patch selects ARM_AMBA if OMAP3_EMU is defined because OC_ETM depends on ARM_AMBA, so fix the link failure[1].
[1],arch/arm/kernel/built-in.o: In function `etm_remove':/home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:609: undefined reference to amba_release_regions' arch/arm/kernel/built-in.o: In function etb_remove':/home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:409: undefined reference to amba_release_regions' arch/arm/kernel/built-in.o: In function etm_init':/home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:640: undefined reference to amba_driver_register' /home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:646: undefined reference to amba_driver_register' /home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:648: undefined reference to amba_driver_unregister' arch/arm/kernel/built-in.o: In function etm_probe':/home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:545: undefined reference to amba_request_regions' /home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:595: undefined reference to amba_release_regions' arch/arm/kernel/built-in.o: In function `etb_probe':/home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:347: undefined reference to amba_request_regions' /home/tom/git/omap/linux-2.6-omap/arch/arm/kernel/etm.c:392: undefined reference to amba_release_regions' arch/arm/mach-omap2/built-in.o: In function `emu_init':/home/tom/git/omap/linux-2.6-omap/arch/arm/mach-omap2/emu.c:62:
undefined reference to `amba_device_register' /home/tom/git/omap/linux-2.6-omap/arch/arm/mach-omap2/emu.c:63:
undefined reference to `amba_device_register'
make: *** [.tmp_vmlinux1] Error 1
making modules
--- arch/arm/mach-omap2/Kconfig | 1 + 1 file changed, 1 insertion(+)
arch/arm/mach-omap2/Kconfig +1 -0
@@ -329,6 +329,7 @@ config MACH_OMAP4_PANDA config OMAP3_EMU bool "OMAP3 debugging peripherals" depends on ARCH_OMAP3 + select ARM_AMBA select OC_ETM help Say Y here to enable debugging hardware of omap3
PATCH 20/104 ARM: OMAP: PM: only register TWL with voltage layer when device is present
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kevin Hilman <[email protected]>
commit 46232a3622c6e33605906ee6690dfef372925f53 upstream.
Current code registers voltage layer details for TWL PMIC even when a TWL has not been registered. Fix this to only register the TWL with voltage layer when the TWL PMIC is initialized by board-level code.
--- arch/arm/mach-omap2/pm.c | 6 ++---- arch/arm/mach-omap2/twl-common.c | 11 +++++++++++ arch/arm/mach-omap2/twl-common.h | 3 +++ 3 files changed, 16 insertions(+), 4 deletions(-)
arch/arm/mach-omap2/pm.c +2 -4
@@ -23,6 +23,7 @@#include "powerdomain.h" #include "clockdomain.h" #include "pm.h" +#include "twl-common.h" static struct omap_device_pm_latency *pm_lats;
@@ -251,11 +252,8 @@ postcore_initcall(omap2_common_pm_init);static int __init omap2_common_pm_late_init (void ) { -/* Init the OMAP TWL parameters */ -omap3_twl_init (); -omap4_twl_init (); -/* Init the voltage layer */ +omap_pmic_late_init ();omap_voltage_late_init ();/* Initialize the voltages */
arch/arm/mach-omap2/twl-common.c +11 -0
@@ -30,6 +30,7 @@#include <plat/usb.h> #include "twl-common.h" +#include "pm.h" static struct i2c_board_info __initdata pmic_i2c_board_info = { .addr =0x48 ,
@@ -48,6 +49,16 @@ void __init omap_pmic_init(int bus, u32omap_register_i2c_bus (bus, clkrate, &pmic_i2c_board_info,1 ); } +void __init omap_pmic_late_init (void ) +{ +/* Init the OMAP TWL parameters (if PMIC has been registerd) */ +if (!pmic_i2c_board_info.irq) +return ; + +omap3_twl_init (); +omap4_twl_init (); +} +#if defined(CONFIG_ARCH_OMAP3 )static struct twl4030_usb_data omap3_usb_pdata = { .usb_mode = T2_USB_MODE_ULPI,
arch/arm/mach-omap2/twl-common.h +3 -0
@@ -1,6 +1,8 @@#ifndef __OMAP_PMIC_COMMON__#define __OMAP_PMIC_COMMON__ +#include <plat/irqs.h> +#define TWL_COMMON_PDATA_USB (1 << 0)#define TWL_COMMON_PDATA_BCI (1 << 1)#define TWL_COMMON_PDATA_MADC (1 << 2)
@@ -30,6 +32,7 @@ struct twl4030_platform_data;void omap_pmic_init (int bus,u32 clkrate,const char *pmic_type,int pmic_irq,struct twl4030_platform_data *pmic_data); +void omap_pmic_late_init (void );static inline void omap2_pmic_init (const char *pmic_type,struct twl4030_platform_data *pmic_data)
PATCH 21/104 ARM: 7161/1: errata: no automatic store buffer drain
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Will Deacon <[email protected]>
commit 11ed0ba1754841316d4095478944300acf19acc3 upstream.
This patch implements a workaround for PL310 erratum 769419. On revisions of the PL310 prior to r3p2, the Store Buffer does not automatically drain. This can cause normal, non-cacheable writes to be retained when the memory system is idle, leading to suboptimal I/O performance for drivers using coherent DMA.
This patch adds an optional wmb() call to the cpu_idle loop. On systems with an outer cache, this causes an explicit flush of the store buffer.
--- arch/arm/Kconfig | 12 ++++++++++++ arch/arm/kernel/process.c | 3 +++ 2 files changed, 15 insertions(+)
arch/arm/Kconfig +12 -0
@@ -1297,6 +1297,18 @@ config ARM_ERRATA_764369 relevant cache maintenance functions and sets a specific bit in the diagnostic control register of the SCU. +config PL310_ERRATA_769419 + bool "PL310 errata: no automatic Store Buffer drain" + depends on CACHE_L2X0 + help + On revisions of the PL310 prior to r3p2, the Store Buffer does + not automatically drain. This can cause normal, non-cacheable + writes to be retained when the memory system is idle, leading + to suboptimal I/O performance for drivers using coherent DMA. + This option adds a write barrier to the cpu_idle loop so that, + on systems with an outer cache, the store buffer is drained + explicitly. + endmenu source "arch/arm/common/Kconfig"
arch/arm/kernel/process.c +3 -0
@@ -192,6 +192,9 @@ void cpu_idle(void)#endif local_irq_disable (); +#ifdef CONFIG_PL310_ERRATA_769419 +wmb (); +#endif if (hlt_counter) {local_irq_enable ();cpu_relax ();
PATCH 22/104 ALSA: hda - Fix jack-detection control of VT1708
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 187d333edc0a8e1bb507900ce89853ffe3bd2c84 upstream.
VT1708 has no support for unsolicited events per jack-plug, the driver implements the workq for polling the jack-detection. The mixer element "Jack Detect" was supposed to control this behavior on/off, but this doesn't work properly as is now. The workq is always started and the HP automute is always enabled.
This patch fixes the jack-detect control behavior by triggering / stopping the work appropriately at the state change. Also the work checks the internal state to continue scheduling or not.
--- sound/pci/hda/patch_via.c | 76 ++++++++++++++++++++++++++-------------------- 1 file changed, 43 insertions(+), 33 deletions(-)
sound/pci/hda/patch_via.c +43 -33
@@ -207,6 +207,7 @@ struct via_spec {/* work to check hp jack state */ struct hda_codec *codec;struct delayed_work vt1708_hp_work; +int hp_work_active;int vt1708_jack_detect;int vt1708_hp_present;
@@ -304,27 +305,35 @@ enum {static void analog_low_current_mode (struct hda_codec *codec);static bool is_aa_path_mute (struct hda_codec *codec); -static void vt1708_start_hp_work (struct via_spec *spec) +#define hp_detect_with_aa (codec) \ + (snd_hda_get_bool_hint(codec, "analog_loopback_hp_detect") == 1 && \ + !is_aa_path_mute(codec)) + +static void vt1708_stop_hp_work (struct via_spec *spec) {if (spec->codec_type !=VT1708 || spec->autocfg.hp_pins[0 ] ==0 )return ; -snd_hda_codec_write (spec->codec,0x1 ,0 ,0xf81 , - !spec->vt1708_jack_detect); -if (!delayed_work_pending (&spec->vt1708_hp_work)) -schedule_delayed_work (&spec->vt1708_hp_work, -msecs_to_jiffies (100 )); +if (spec->hp_work_active) { +snd_hda_codec_write (spec->codec,0x1 ,0 ,0xf81 ,1 ); +cancel_delayed_work_sync (&spec->vt1708_hp_work); + spec->hp_work_active =0 ; + } } -static void vt1708_stop_hp_work (struct via_spec *spec) +static void vt1708_update_hp_work (struct via_spec *spec) {if (spec->codec_type !=VT1708 || spec->autocfg.hp_pins[0 ] ==0 )return ; -if (snd_hda_get_bool_hint (spec->codec,"analog_loopback_hp_detect" ) ==1 - && !is_aa_path_mute (spec->codec)) -return ; -snd_hda_codec_write (spec->codec,0x1 ,0 ,0xf81 , - !spec->vt1708_jack_detect); -cancel_delayed_work_sync (&spec->vt1708_hp_work); +if (spec->vt1708_jack_detect && + (spec->active_streams ||hp_detect_with_aa (spec->codec))) { +if (!spec->hp_work_active) { +snd_hda_codec_write (spec->codec,0x1 ,0 ,0xf81 ,0 ); +schedule_delayed_work (&spec->vt1708_hp_work, +msecs_to_jiffies (100 )); + spec->hp_work_active =1 ; + } + }else if (!hp_detect_with_aa (spec->codec)) +vt1708_stop_hp_work (spec); }static void set_widgets_power_state (struct hda_codec *codec)
@@ -342,12 +351,7 @@ static int analog_input_switch_put(strucset_widgets_power_state (codec);analog_low_current_mode (snd_kcontrol_chip (kcontrol)); -if (snd_hda_get_bool_hint (codec,"analog_loopback_hp_detect" ) ==1 ) { -if (is_aa_path_mute (codec)) -vt1708_start_hp_work (codec->spec); -else -vt1708_stop_hp_work (codec->spec); - } +vt1708_update_hp_work (codec->spec);return change; }
@@ -1153,7 +1157,7 @@ static int via_playback_multi_pcm_prepar spec->cur_dac_stream_tag = stream_tag; spec->cur_dac_format = format;mutex_unlock (&spec->config_mutex); -vt1708_start_hp_work (spec); +vt1708_update_hp_work (spec);return 0 ; }
@@ -1173,7 +1177,7 @@ static int via_playback_hp_pcm_prepare(s spec->cur_hp_stream_tag = stream_tag; spec->cur_hp_format = format;mutex_unlock (&spec->config_mutex); -vt1708_start_hp_work (spec); +vt1708_update_hp_work (spec);return 0 ; }
@@ -1187,7 +1191,7 @@ static int via_playback_multi_pcm_cleanusnd_hda_multi_out_analog_cleanup (codec, &spec->multiout); spec->active_streams &= ~STREAM_MULTI_OUT ;mutex_unlock (&spec->config_mutex); -vt1708_stop_hp_work (spec); +vt1708_update_hp_work (spec);return 0 ; }
@@ -1202,7 +1206,7 @@ static int via_playback_hp_pcm_cleanup(ssnd_hda_codec_setup_stream (codec, spec->hp_dac_nid,0 ,0 ,0 ); spec->active_streams &= ~STREAM_INDEP_HP ;mutex_unlock (&spec->config_mutex); -vt1708_stop_hp_work (spec); +vt1708_update_hp_work (spec);return 0 ; }
@@ -1632,7 +1636,8 @@ static void via_hp_automute(struct hda_cint nums;struct via_spec *spec = codec->spec; -if (!spec->hp_independent_mode && spec->autocfg.hp_pins[0 ]) +if (!spec->hp_independent_mode && spec->autocfg.hp_pins[0 ] && + (spec->codec_type !=VT1708 || spec->vt1708_jack_detect)) present =snd_hda_jack_detect (codec, spec->autocfg.hp_pins[0 ]);if (spec->smart51_enabled)
@@ -2599,8 +2604,6 @@ static int vt1708_jack_detect_get(structif (spec->codec_type !=VT1708 )return 0 ; - spec->vt1708_jack_detect = - !((snd_hda_codec_read (codec,0x1 ,0 ,0xf84 ,0 ) >>8 ) &0x1 ); ucontrol->value.integer.value[0 ] = spec->vt1708_jack_detect;return 0 ; }
@@ -2610,18 +2613,22 @@ static int vt1708_jack_detect_put(struct {struct hda_codec *codec =snd_kcontrol_chip (kcontrol);struct via_spec *spec = codec->spec; -int change; +int val;if (spec->codec_type !=VT1708 )return 0 ; - spec->vt1708_jack_detect = ucontrol->value.integer.value[0 ]; - change = (0x1 & (snd_hda_codec_read (codec,0x1 ,0 ,0xf84 ,0 ) >>8 )) - == !spec->vt1708_jack_detect; -if (spec->vt1708_jack_detect) { + val = !!ucontrol->value.integer.value[0 ]; +if (spec->vt1708_jack_detect == val) +return 0 ; + spec->vt1708_jack_detect = val; +if (spec->vt1708_jack_detect && +snd_hda_get_bool_hint (codec,"analog_loopback_hp_detect" ) !=1 ) {mute_aa_path (codec,1 );notify_aa_path_ctls (codec); } -return change; +via_hp_automute (codec); +vt1708_update_hp_work (spec); +return 1 ; }static const struct snd_kcontrol_new vt1708_jack_detect_ctl = {
@@ -2758,6 +2765,7 @@ static int via_init(struct hda_codec *covia_auto_init_unsol_event (codec);via_hp_automute (codec); +vt1708_update_hp_work (spec);return 0 ; }
@@ -2774,7 +2782,9 @@ static void vt1708_update_hp_jack_state( spec->vt1708_hp_present ^=1 ;via_hp_automute (spec->codec); } -vt1708_start_hp_work (spec); +if (spec->vt1708_jack_detect) +schedule_delayed_work (&spec->vt1708_hp_work, +msecs_to_jiffies (100 )); }static int get_mux_nids (struct hda_codec *codec)
PATCH 23/104 ALSA: lx6464es - fix device communication via command bus
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tim Blechmann <[email protected]>
commit a29878553a9a7b4c06f93c7e383527cf014d4ceb upstream.
commit 6175ddf06b6172046a329e3abfd9c901a43efd2e optimized the mem*io functions that have been used to send commands to the device. these optimizations somehow corrupted the communication with the lx6464es, that resulted the device to be unusable with kernels after 2.6.33.
this patch emulates the memcpy_*_io functions via a loop to avoid these problems.
LKML-Reference: <[email protected]>
--- sound/pci/lx6464es/lx_core.c | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-)
sound/pci/lx6464es/lx_core.c +12 -4
@@ -80,8 +80,12 @@ unsigned long lx_dsp_reg_read(struct lx6void lx_dsp_reg_readbuf (struct lx6464es *chip,int port,u32 *data,u32 len) { -void __iomem *address =lx_dsp_register (chip, port); -memcpy_fromio (data, address, len*sizeof (u32)); +u32 __iomem *address =lx_dsp_register (chip, port); +int i; + +/* we cannot use memcpy_fromio */ +for (i =0 ; i != len; ++i) + data[i] =ioread32 (address + i); }
@@ -94,8 +98,12 @@ void lx_dsp_reg_write(struct lx6464es *cvoid lx_dsp_reg_writebuf (struct lx6464es *chip,int port,const u32 *data,u32 len) { -void __iomem *address =lx_dsp_register (chip, port); -memcpy_toio (address, data, len*sizeof (u32)); +u32 __iomem *address =lx_dsp_register (chip, port); +int i; + +/* we cannot use memcpy_to */ +for (i =0 ; i != len; ++i) +iowrite32 (data[i], address + i); }
PATCH 24/104 ALSA: hda/realtek - Fix missing inits of item indices for auto-mic
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 6759dc323826c2c806c998cd93945c5476688dd2 upstream.
When the imux entries are rebuilt in alc_rebuild_imux_for_auto_mic(), the initialization of index field is missing. It may work without it casually when the original imux was created by the auto-parser, but it's definitely broken in the case of static configs where no imux was parsed beforehand. Because of this, the auto-mic switching doesn't work properly on some model options.
This patch adds the missing initialization of index field.
--- sound/pci/hda/patch_realtek.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
sound/pci/hda/patch_realtek.c +13 -1
@@ -1023,8 +1023,20 @@ static bool alc_rebuild_imux_for_auto_mi spec->imux_pins[2 ] = spec->dock_mic_pin;for (i =0 ; i <3 ; i++) {strcpy (imux->items[i].label, texts[i]); -if (spec->imux_pins[i]) +if (spec->imux_pins[i]) { +hda_nid_t pin = spec->imux_pins[i]; +int c; +for (c =0 ; c < spec->num_adc_nids; c++) { +hda_nid_t cap = spec->capsrc_nids ? + spec->capsrc_nids[c] : spec->adc_nids[c]; +int idx =get_connection_index (codec, cap, pin); +if (idx >=0 ) { + imux->items[i].index = idx; +break ; + } + } imux->num_items = i +1 ; + } } spec->num_mux_defs =1 ; spec->input_mux = imux;
PATCH 25/104 ASoC: sta32x: preserve coefficient RAM
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johannes Stezenbach <[email protected]>
commit 54dc6cabe684375b3cf549c7b0545613d694aba8 upstream.
The coefficient RAM must be saved in a shadow so it can be restored when the codec is powered on using regulator_bulk_enable().
--- sound/soc/codecs/sta32x.c | 63 +++++++++++++++++++++++++++++++++++++++++++++- sound/soc/codecs/sta32x.h | 1 2 files changed, 63 insertions(+), 1 deletion(-)
sound/soc/codecs/sta32x.c +62 -1
@@ -76,6 +76,8 @@ struct sta32x_priv {unsigned int mclk;unsigned int format; + +u32 coef_shadow[STA32X_COEF_COUNT ]; }; static const DECLARE_TLV_DB_SCALE(mvol_tlv, -12700, 50, 1);
@@ -227,6 +229,7 @@ static int sta32x_coefficient_put(struct struct snd_ctl_elem_value *ucontrol) {struct snd_soc_codec *codec =snd_kcontrol_chip (kcontrol); +struct sta32x_priv *sta32x =snd_soc_codec_get_drvdata (codec);int numcoef = kcontrol->private_value >>16 ;int index = kcontrol->private_value &0xffff ;unsigned int cfud;
@@ -239,6 +242,11 @@ static int sta32x_coefficient_put(structsnd_soc_write (codec,STA32X_CFUD , cfud);snd_soc_write (codec,STA32X_CFADDR2 , index); +for (i =0 ; i < numcoef && (index + i <STA32X_COEF_COUNT ); i++) + sta32x->coef_shadow[index + i] = + (ucontrol->value.bytes.data[3 * i] <<16 ) + | (ucontrol->value.bytes.data[3 * i +1 ] <<8 ) + | (ucontrol->value.bytes.data[3 * i +2 ]);for (i =0 ; i <3 * numcoef; i++)snd_soc_write (codec,STA32X_B1CF1 + i, ucontrol->value.bytes.data[i]);
@@ -252,6 +260,48 @@ static int sta32x_coefficient_put(structreturn 0 ; } +int sta32x_sync_coef_shadow (struct snd_soc_codec *codec) +{ +struct sta32x_priv *sta32x =snd_soc_codec_get_drvdata (codec); +unsigned int cfud; +int i; + +/* preserve reserved bits in STA32X_CFUD */ + cfud =snd_soc_read (codec,STA32X_CFUD ) &0xf0 ; + +for (i =0 ; i <STA32X_COEF_COUNT ; i++) { +snd_soc_write (codec,STA32X_CFADDR2 , i); +snd_soc_write (codec,STA32X_B1CF1 , + (sta32x->coef_shadow[i] >>16 ) &0xff ); +snd_soc_write (codec,STA32X_B1CF2 , + (sta32x->coef_shadow[i] >>8 ) &0xff ); +snd_soc_write (codec,STA32X_B1CF3 , + (sta32x->coef_shadow[i]) &0xff ); +/* chip documentation does not say if the bits are +* self-clearing, so do it explicitly */ +snd_soc_write (codec,STA32X_CFUD , cfud); +snd_soc_write (codec,STA32X_CFUD , cfud |0x01 ); + } +return 0 ; +} + +int sta32x_cache_sync (struct snd_soc_codec *codec) +{ +unsigned int mute; +int rc; + +if (!codec->cache_sync) +return 0 ; + +/* mute during register sync */ + mute =snd_soc_read (codec,STA32X_MMUTE ); +snd_soc_write (codec,STA32X_MMUTE , mute |STA32X_MMUTE_MMUTE ); +sta32x_sync_coef_shadow (codec); + rc =snd_soc_cache_sync (codec); +snd_soc_write (codec,STA32X_MMUTE , mute); +return rc; +} +#define SINGLE_COEF (xname, index) \ { .iface = SNDRV_CTL_ELEM_IFACE_MIXER, .name = xname, \ .info = sta32x_coefficient_info, \
@@ -657,7 +707,7 @@ static int sta32x_set_bias_level(structreturn ret; } -snd_soc_cache_sync (codec); +sta32x_cache_sync (codec); }/* Power up to mute */
@@ -792,6 +842,17 @@ static int sta32x_probe(struct snd_soc_c STA32X_CxCFG_OM_MASK, 2 << STA32X_CxCFG_OM_SHIFT); +/* initialize coefficient shadow RAM with reset values */ +for (i =4 ; i <=49 ; i +=5 ) + sta32x->coef_shadow[i] =0x400000 ; +for (i =50 ; i <=54 ; i++) + sta32x->coef_shadow[i] =0x7fffff ; + sta32x->coef_shadow[55 ] =0x5a9df7 ; + sta32x->coef_shadow[56 ] =0x7fffff ; + sta32x->coef_shadow[59 ] =0x7fffff ; + sta32x->coef_shadow[60 ] =0x400000 ; + sta32x->coef_shadow[61 ] =0x400000 ; +sta32x_set_bias_level (codec,SND_SOC_BIAS_STANDBY );/* Bias level configuration will have done an extra enable */ regulator_bulk_disable (ARRAY_SIZE (sta32x->supplies), sta32x->supplies);
sound/soc/codecs/sta32x.h +1 -0
@@ -19,6 +19,7 @@/* STA326 register addresses */ #define STA32X_REGISTER_COUNT 0x2d +#define STA32X_COEF_COUNT 62#define STA32X_CONFA 0x00#define STA32X_CONFB 0x01
PATCH 26/104 ASoC: fsl_ssi: properly initialize the sysfs attribute object
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Timur Tabi <[email protected]>
commit 0f768a7235d3dfb6f4833030a95a06419df089cb upstream.
Commit 6992f533 ("sysfs: Use one lockdep class per sysfs attribute") requires 'struct attribute' objects to be initialized with sysfs_attr_init().
--- sound/soc/fsl/fsl_ssi.c | 1 + 1 file changed, 1 insertion(+)
sound/soc/fsl/fsl_ssi.c +1 -0
@@ -703,6 +703,7 @@ static int __devinit fsl_ssi_probe(struc/* Initialize the the device_attribute structure */ dev_attr = &ssi_private->dev_attr; +sysfs_attr_init (&dev_attr->attr); dev_attr->attr.name ="statistics" ; dev_attr->attr.mode =S_IRUGO ; dev_attr->show = fsl_sysfs_ssi_show;
PATCH 27/104 ASoC: wm8753: Skip noop reconfiguration of DAI mode
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Timo Juhani Lindfors <[email protected]>
commit 2391a0e06789a3f1718dee30b282562f7ed28c87 upstream.
This patch makes it possible to set DAI mode to its currently applied value even if codec is active. This is necessary to allow
aplay -t raw -r 44100 -f S16_LE -c 2 < /dev/urandom & alsactl store -f backup.state
alsactl restore -f backup.state
to work without returning errors. This patch is based on a patch sent by Klaus Kurzmann <[email protected]>.
--- sound/soc/codecs/wm8753.c | 3 +++ 1 file changed, 3 insertions(+)
sound/soc/codecs/wm8753.c +3 -0
@@ -189,6 +189,9 @@ static int wm8753_set_dai(struct snd_kcostruct wm8753_priv *wm8753 =snd_soc_codec_get_drvdata (codec);u16 ioctl; +if (wm8753->dai_func == ucontrol->value.integer.value[0 ]) +return 0 ; +if (codec->active)return -EBUSY ;
PATCH 28/104 ASoC: Ensure WM8731 register cache is synced when resuming from disabled
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mark Brown <[email protected]>
commit ed3e80c4c991a52f9fce3421536a78e331ae0949 upstream.
--- sound/soc/codecs/wm8731.c | 1 + 1 file changed, 1 insertion(+)
sound/soc/codecs/wm8731.c +1 -0
@@ -463,6 +463,7 @@ static int wm8731_set_bias_level(structsnd_soc_write (codec,WM8731_PWR ,0xffff );regulator_bulk_disable (ARRAY_SIZE (wm8731->supplies), wm8731->supplies); + codec->cache_sync =1 ;break ; } codec->dapm.bias_level = level;
PATCH 29/104 SUNRPC: Ensure we return EAGAIN in xs_nospace if congestion is cleared
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Trond Myklebust <[email protected]>
commit 24ca9a847791fd53d9b217330b15f3c285827a18 upstream.
By returning '0' instead of 'EAGAIN' when the tests in xs_nospace() fail to find evidence of socket congestion, we are making the RPC engine believe that the message was incorrectly sent and so it disconnects the socket instead of just retrying.
The bug appears to have been introduced by commit 5e3771ce2d6a69e10fcc870cdf226d121d868491 (SUNRPC: Ensure that xs_nospace return values are propagated).
--- net/sunrpc/xprtsock.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
net/sunrpc/xprtsock.c +1 -2
@@ -496,7 +496,7 @@ static int xs_nospace(struct rpc_task *tstruct rpc_rqst *req = task->tk_rqstp;struct rpc_xprt *xprt = req->rq_xprt; struct sock_xprt *transport = container_of(xprt, struct sock_xprt, xprt); -int ret =0 ; +int ret = -EAGAIN ; dprintk("RPC: %5u xmit incomplete (%u left of %u)\n", task->tk_pid, req->rq_slen - req->rq_bytes_sent,
@@ -508,7 +508,6 @@ static int xs_nospace(struct rpc_task *t/* Don't race with disconnect */ if (xprt_connected (xprt)) {if (test_bit (SOCK_ASYNC_NOSPACE , &transport->sock->flags)) { - ret = -EAGAIN ;/* * Notify TCP that we're limited by the application * window size
PATCH 30/104 ext4: fix racy use-after-free in ext4_end_io_dio()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tejun Heo <[email protected]>
commit 4c81f045c0bd2cbb78cc6446a4cd98038fe11a2e upstream.
ext4_end_io_dio() queues io_end->work and then clears iocb->private; however, io_end->work calls aio_complete() which frees the iocb object. If that slab object gets reallocated, then ext4_end_io_dio() can end up clearing someone else's iocb->private, this use-after-free can cause a leak of a struct ext4_io_end_t structure.
Detected and tested with slab poisoning.
[ Note: Can also reproduce using 12 fio's against 12 file systems with the
following configuration file:
[global]
direct=1
ioengine=libaio
iodepth=1
bs=4k
ba=4k
size=128m
[create]
filename=${TESTDIR}
rw=write-- tytso ]
Google-Bug-Id: 5354697
--- fs/ext4/inode.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/inode.c +1 -1
@@ -2656,8 +2656,8 @@ out:spin_unlock_irqrestore (&ei->i_completed_io_lock, flags);/* queue the work to convert unwritten extents to written */ -queue_work (wq, &io_end->work); iocb->private =NULL ; +queue_work (wq, &io_end->work);/* XXX: probably should move into the real I/O completion handler */ inode_dio_done (inode);
PATCH 31/104 rtlwifi: fix lps_lock deadlock
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stanislaw Gruszka <[email protected]>
commit e55b32c110b025ce07b40227f620e99700bf8741 upstream.
rtl_lps_leave can be called from interrupt context, so we have to disable interrupts when taking lps_lock.
Below is full lockdep info about deadlock:
[ 93.815269] =================================
[ 93.815390] [ INFO: inconsistent lock state ]
[ 93.815472] 2.6.41.1-3.offch.fc15.x86_64.debug #1
[ 93.815556] ---------------------------------
[ 93.815635] inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
[ 93.815743] swapper/0 [HC0[0]:SC1[1]:HE1:SE0] takes:
[ 93.815832] (&(&rtlpriv->locks.lps_lock)->rlock){+.?...}, at: [<ffffffffa025dad6>] rtl_lps_leave+0x26/0x103 [rtlwifi]
[ 93.815947] {SOFTIRQ-ON-W} state was registered at:
[ 93.815947] [<ffffffff8108e10d>] __lock_acquire+0x369/0xd0c
[ 93.815947] [<ffffffff8108efb3>] lock_acquire+0xf3/0x13e
[ 93.815947] [<ffffffff814e981d>] _raw_spin_lock+0x45/0x79
[ 93.815947] [<ffffffffa025de34>] rtl_swlps_rf_awake+0x5a/0x76 [rtlwifi]
[ 93.815947] [<ffffffffa025aec0>] rtl_op_config+0x12a/0x32a [rtlwifi]
[ 93.815947] [<ffffffffa01d614b>] ieee80211_hw_config+0x124/0x129 [mac80211]
[ 93.815947] [<ffffffffa01e0af3>] ieee80211_dynamic_ps_disable_work+0x32/0x47 [mac80211]
[ 93.815947] [<ffffffff81075aa5>] process_one_work+0x205/0x3e7
[ 93.815947] [<ffffffff81076753>] worker_thread+0xda/0x15d
[ 93.815947] [<ffffffff8107a119>] kthread+0xa8/0xb0
[ 93.815947] [<ffffffff814f3184>] kernel_thread_helper+0x4/0x10
[ 93.815947] irq event stamp: 547822
[ 93.815947] hardirqs last enabled at (547822): [<ffffffff814ea1a7>] _raw_spin_unlock_irqrestore+0x45/0x61
[ 93.815947] hardirqs last disabled at (547821): [<ffffffff814e9987>] _raw_spin_lock_irqsave+0x22/0x8e
[ 93.815947] softirqs last enabled at (547790): [<ffffffff810623ed>] _local_bh_enable+0x13/0x15
[ 93.815947] softirqs last disabled at (547791): [<ffffffff814f327c>] call_softirq+0x1c/0x30
[ 93.815947]
[ 93.815947] other info that might help us debug this:
[ 93.815947] Possible unsafe locking scenario:
[ 93.815947]
[ 93.815947] CPU0
[ 93.815947] ----
[ 93.815947] lock(&(&rtlpriv->locks.lps_lock)->rlock);
[ 93.815947] <Interrupt>
[ 93.815947] lock(&(&rtlpriv->locks.lps_lock)->rlock);
[ 93.815947]
[ 93.815947] *** DEADLOCK ***
[ 93.815947]
[ 93.815947] no locks held by swapper/0.
[ 93.815947]
[ 93.815947] stack backtrace:
[ 93.815947] Pid: 0, comm: swapper Not tainted 2.6.41.1-3.offch.fc15.x86_64.debug #1
[ 93.815947] Call Trace:
[ 93.815947] <IRQ> [<ffffffff814dfd00>] print_usage_bug+0x1e7/0x1f8
[ 93.815947] [<ffffffff8101a849>] ? save_stack_trace+0x2c/0x49
[ 93.815947] [<ffffffff8108d55c>] ? print_irq_inversion_bug.part.18+0x1a0/0x1a0
[ 93.815947] [<ffffffff8108dc8a>] mark_lock+0x106/0x220
[ 93.815947] [<ffffffff8108e099>] __lock_acquire+0x2f5/0xd0c
[ 93.815947] [<ffffffff810152af>] ? native_sched_clock+0x34/0x36
[ 93.830125] [<ffffffff810152ba>] ? sched_clock+0x9/0xd
[ 93.830125] [<ffffffff81080181>] ? sched_clock_local+0x12/0x75
[ 93.830125] [<ffffffffa025dad6>] ? rtl_lps_leave+0x26/0x103 [rtlwifi]
[ 93.830125] [<ffffffff8108efb3>] lock_acquire+0xf3/0x13e
[ 93.830125] [<ffffffffa025dad6>] ? rtl_lps_leave+0x26/0x103 [rtlwifi]
[ 93.830125] [<ffffffff814e981d>] _raw_spin_lock+0x45/0x79
[ 93.830125] [<ffffffffa025dad6>] ? rtl_lps_leave+0x26/0x103 [rtlwifi]
[ 93.830125] [<ffffffff81422467>] ? skb_dequeue+0x62/0x6d
[ 93.830125] [<ffffffffa025dad6>] rtl_lps_leave+0x26/0x103 [rtlwifi]
[ 93.830125] [<ffffffffa025f677>] _rtl_pci_ips_leave_tasklet+0xe/0x10 [rtlwifi]
[ 93.830125] [<ffffffff8106281f>] tasklet_action+0x8d/0xee
[ 93.830125] [<ffffffff810629ce>] __do_softirq+0x112/0x25a
[ 93.830125] [<ffffffff814f327c>] call_softirq+0x1c/0x30
[ 93.830125] [<ffffffff81010bf6>] do_softirq+0x4b/0xa1
[ 93.830125] [<ffffffff81062d7d>] irq_exit+0x5d/0xcf
[ 93.830125] [<ffffffff814f3b7e>] do_IRQ+0x8e/0xa5
[ 93.830125] [<ffffffff814ea533>] common_interrupt+0x73/0x73
[ 93.830125] <EOI> [<ffffffff8108b825>] ? trace_hardirqs_off+0xd/0xf
[ 93.830125] [<ffffffff812bb6d5>] ? intel_idle+0xe5/0x10c
[ 93.830125] [<ffffffff812bb6d1>] ? intel_idle+0xe1/0x10c
[ 93.830125] [<ffffffff813f8d5e>] cpuidle_idle_call+0x11c/0x1fe
[ 93.830125] [<ffffffff8100e2ef>] cpu_idle+0xab/0x101
[ 93.830125] [<ffffffff814c6373>] rest_init+0xd7/0xde
[ 93.830125] [<ffffffff814c629c>] ? csum_partial_copy_generic+0x16c/0x16c
[ 93.830125] [<ffffffff81d4bbb0>] start_kernel+0x3dd/0x3ea
[ 93.830125] [<ffffffff81d4b2c4>] x86_64_start_reservations+0xaf/0xb3
[ 93.830125] [<ffffffff81d4b140>] ? early_idt_handlers+0x140/0x140
[ 93.830125] [<ffffffff81d4b3ca>] x86_64_start_kernel+0x102/0x111Resolves:
https://bugzilla.redhat.com/show_bug.cgi?id=755154
--- drivers/net/wireless/rtlwifi/ps.c | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-)
drivers/net/wireless/rtlwifi/ps.c +9 -8
@@ -394,7 +394,7 @@ void rtl_lps_enter(struct ieee80211_hw *if (mac->link_state !=MAC80211_LINKED )return ; -spin_lock (&rtlpriv->locks.lps_lock); +spin_lock_irq (&rtlpriv->locks.lps_lock);/* Idle for a while if we connect to AP a while ago. */ if (mac->cnt_after_linked >=2 ) {
@@ -406,7 +406,7 @@ void rtl_lps_enter(struct ieee80211_hw * } } -spin_unlock (&rtlpriv->locks.lps_lock); +spin_unlock_irq (&rtlpriv->locks.lps_lock); }/*Leave the leisure power save mode.*/
@@ -415,8 +415,9 @@ void rtl_lps_leave(struct ieee80211_hw *struct rtl_priv *rtlpriv =rtl_priv (hw);struct rtl_ps_ctl *ppsc =rtl_psc (rtl_priv (hw));struct rtl_hal *rtlhal =rtl_hal (rtl_priv (hw)); +unsigned long flags; -spin_lock (&rtlpriv->locks.lps_lock); +spin_lock_irqsave (&rtlpriv->locks.lps_lock, flags);if (ppsc->fwctrl_lps) {if (ppsc->dot11_psmode !=EACTIVE ) {
@@ -437,7 +438,7 @@ void rtl_lps_leave(struct ieee80211_hw *rtl_lps_set_psmode (hw,EACTIVE ); } } -spin_unlock (&rtlpriv->locks.lps_lock); +spin_unlock_irqrestore (&rtlpriv->locks.lps_lock, flags); }/* For sw LPS*/
@@ -538,9 +539,9 @@ void rtl_swlps_rf_awake(struct ieee80211RT_CLEAR_PS_LEVEL (ppsc,RT_PS_LEVEL_ASPM ); } -spin_lock (&rtlpriv->locks.lps_lock); +spin_lock_irq (&rtlpriv->locks.lps_lock);rtl_ps_set_rf_state (hw,ERFON ,RF_CHANGE_BY_PS ); -spin_unlock (&rtlpriv->locks.lps_lock); +spin_unlock_irq (&rtlpriv->locks.lps_lock); }void rtl_swlps_rfon_wq_callback (void *data)
@@ -573,9 +574,9 @@ void rtl_swlps_rf_sleep(struct ieee80211if (rtlpriv->link_info.busytraffic)return ; -spin_lock (&rtlpriv->locks.lps_lock); +spin_lock_irq (&rtlpriv->locks.lps_lock);rtl_ps_set_rf_state (hw,ERFSLEEP ,RF_CHANGE_BY_PS ); -spin_unlock (&rtlpriv->locks.lps_lock); +spin_unlock_irq (&rtlpriv->locks.lps_lock);if (ppsc->reg_rfps_level &RT_RF_OFF_LEVL_ASPM && !RT_IN_PS_LEVEL (ppsc,RT_PS_LEVEL_ASPM )) {
PATCH 32/104 genirq: fix regression in irqfixup, irqpoll
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Edward Donovan <[email protected]>
commit 52553ddffad76ccf192d4dd9ce88d5818f57f62a upstream.
Commit fa27271bc8d2("genirq: Fixup poll handling") introduced a regression that broke irqfixup/irqpoll for some hardware configurations.
Amidst reorganizing 'try_one_irq', that patch removed a test that checked for 'action->handler' returning IRQ_HANDLED, before acting on the interrupt. Restoring this test back returns the functionality lost since 2.6.39. In the current set of tests, after 'action' is set, it must precede '!action->next' to take effect.
With this and my previous patch to irq/spurious.c, c75d720fca8a, all IRQ regressions that I have encountered are fixed.
--- kernel/irq/spurious.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
kernel/irq/spurious.c +3 -1
@@ -84,7 +84,9 @@ static int try_one_irq(int irq, struct i*/ action = desc->action;if (!action || !(action->flags &IRQF_SHARED ) || - (action->flags & __IRQF_TIMER) || !action->next) + (action->flags & __IRQF_TIMER) || + (action->handler (irq, action->dev_id) ==IRQ_HANDLED ) || + !action->next) goto out;/* Already running on another processor */
PATCH 33/104 regulator: aat2870: Fix the logic of checking if no id is matched in aat2870_get_regulator
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Axel Lin <[email protected]>
commit d4d6373c1109b11c8118340be97ae31b8f94d66a upstream.
In current implementation, the pointer ri is not NULL if no id is matched. Fix it by checking i == ARRAY_SIZE(aat2870_regulators) if no id is matched.
--- drivers/regulator/aat2870-regulator.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/regulator/aat2870-regulator.c +1 -1
@@ -159,7 +159,7 @@ static struct aat2870_regulator *aat2870break ; } -if (!ri) +if (i ==ARRAY_SIZE (aat2870_regulators))return NULL ; ri->enable_addr =AAT2870_LDO_EN ;
PATCH 34/104 regulator: twl: fix twl4030 support for smps regulators
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tero Kristo <[email protected]>
commit ba305e31e88ea5c2f598ff9fbc5424711a429e30 upstream.
SMPS regulator voltage control differs from the one of the LDO ones. Current TWL code was using LDO regulator ops for controlling the SMPS regulators, which fails. This was fixed fixed by adding separate regulator type which uses correct logic and calculations for the voltage levels.
--- drivers/regulator/twl-regulator.c | 46 ++++++++++++++++++++++++++++++++++++-- 1 file changed, 44 insertions(+), 2 deletions(-)
drivers/regulator/twl-regulator.c +44 -2
@@ -71,6 +71,7 @@ struct twlreg_info {#define VREG_TYPE 1#define VREG_REMAP 2#define VREG_DEDICATED 3/* LDO control */ +#define VREG_VOLTAGE_SMPS_4030 9/* TWL6030 register offsets */ #define VREG_TRANS 1#define VREG_STATE 2
@@ -514,6 +515,32 @@ static struct regulator_ops twl4030ldo_o .get_status = twl4030reg_get_status, }; +static int +twl4030smps_set_voltage (struct regulator_dev *rdev,int min_uV,int max_uV, +unsigned *selector) +{ +struct twlreg_info *info =rdev_get_drvdata (rdev); +int vsel =DIV_ROUND_UP (min_uV -600000 ,12500 ); + +twlreg_write (info,TWL_MODULE_PM_RECEIVER ,VREG_VOLTAGE_SMPS_4030 , + vsel); +return 0 ; +} + +static int twl4030smps_get_voltage (struct regulator_dev *rdev) +{ +struct twlreg_info *info =rdev_get_drvdata (rdev); +int vsel =twlreg_read (info,TWL_MODULE_PM_RECEIVER , +VREG_VOLTAGE_SMPS_4030 ); + +return vsel *12500 +600000 ; +} + +static struct regulator_ops twl4030smps_ops = { + .set_voltage = twl4030smps_set_voltage, + .get_voltage = twl4030smps_get_voltage, +}; +static int twl6030ldo_list_voltage (struct regulator_dev *rdev,unsigned index) {struct twlreg_info *info =rdev_get_drvdata (rdev);
@@ -856,6 +883,21 @@ static struct regulator_ops twlsmps_ops }, \ } +#define TWL4030_ADJUSTABLE_SMPS (label, offset, num, turnon_delay, remap_conf) \ + { \ + .base = offset, \ + .id = num, \ + .delay = turnon_delay, \ + .remap = remap_conf, \ + .desc = { \ + .name = #label, \ + .id = TWL4030_REG_##label, \ + .ops = &twl4030smps_ops, \ + .type = REGULATOR_VOLTAGE, \ + .owner = THIS_MODULE, \ + }, \ + } +#define TWL6030_ADJUSTABLE_LDO (label, offset, min_mVolts, max_mVolts) { \ .base = offset, \ .min_mV = min_mVolts, \
@@ -947,8 +989,8 @@ static struct twlreg_info twl_regs[] = {TWL4030_ADJUSTABLE_LDO (VINTANA2 ,0x43 ,12 ,100 ,0x08 ),TWL4030_FIXED_LDO (VINTDIG ,0x47 ,1500 ,13 ,100 ,0x08 ),TWL4030_ADJUSTABLE_LDO (VIO ,0x4b ,14 ,1000 ,0x08 ), -TWL4030_ADJUSTABLE_LDO (VDD1 ,0x55 ,15 ,1000 ,0x08 ), -TWL4030_ADJUSTABLE_LDO (VDD2 ,0x63 ,16 ,1000 ,0x08 ), +TWL4030_ADJUSTABLE_SMPS (VDD1 ,0x55 ,15 ,1000 ,0x08 ), +TWL4030_ADJUSTABLE_SMPS (VDD2 ,0x63 ,16 ,1000 ,0x08 ),TWL4030_FIXED_LDO (VUSB1V5 ,0x71 ,1500 ,17 ,100 ,0x08 ),TWL4030_FIXED_LDO (VUSB1V8 ,0x74 ,1800 ,18 ,100 ,0x08 ), TWL4030_FIXED_LDO(VUSB3V1, 0x77, 3100, 19, 150, 0x08),
PATCH 35/104 cgroup_freezer: fix freezing groups with stopped tasks
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michal Hocko <[email protected]>
commit 884a45d964dd395eda945842afff5e16bcaedf56 upstream.
2d3cbf8b (cgroup_freezer: update_freezer_state() does incorrect state transitions) removed is_task_frozen_enough and replaced it with a simple frozen call. This, however, breaks freezing for a group with stopped tasks because those cannot be frozen and so the group remains in CGROUP_FREEZING state (update_if_frozen doesn't count stopped tasks) and never reaches CGROUP_FROZEN.
Let's add is_task_frozen_enough back and use it at the original locations (update_if_frozen and try_to_freeze_cgroup). Semantically we consider stopped tasks as frozen enough so we should consider both cases when testing frozen tasks.
Testcase:
mkdir /dev/freezer
mount -t cgroup -o freezer none /dev/freezer
mkdir /dev/freezer/foo
sleep 1h &
pid=$!
kill -STOP $pid
echo $pid > /dev/freezer/foo/tasks
echo FROZEN > /dev/freezer/foo/freezer.state
while true
do
cat /dev/freezer/foo/freezer.state [ "`cat /dev/freezer/foo/freezer.state`" = "FROZEN" ] && break sleep 1
done
echo OK
--- kernel/cgroup_freezer.c | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-)
kernel/cgroup_freezer.c +9 -2
@@ -153,6 +153,13 @@ static void freezer_destroy(struct cgroukfree (cgroup_freezer (cgroup)); } +/* task is frozen or will freeze immediately when next it gets woken */ +static bool is_task_frozen_enough (struct task_struct *task) +{ +return frozen (task) || + (task_is_stopped_or_traced (task) &&freezing (task)); +} +/* * The call to cgroup_lock() in the freezer.state write method prevents * a write to that file racing against an attach, and hence the
@@ -231,7 +238,7 @@ static void update_if_frozen(struct cgrocgroup_iter_start (cgroup, &it);while ((task =cgroup_iter_next (cgroup, &it))) { ntotal++; -if (frozen (task)) +if (is_task_frozen_enough (task)) nfrozen++; }
@@ -284,7 +291,7 @@ static int try_to_freeze_cgroup(struct cwhile ((task =cgroup_iter_next (cgroup, &it))) {if (!freeze_task (task, true))continue ; -if (frozen (task)) +if (is_task_frozen_enough (task))continue ;if (!freezing (task) && !freezer_should_skip (task)) num_cant_freeze_now++;
PATCH 36/104 timekeeping: add arch_offset hook to ktime_get functions
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hector Palacios <[email protected]>
commit d004e024058a0eaca097513ce62cbcf978913e0a upstream.
ktime_get and ktime_get_ts were calling timekeeping_get_ns() but later they were not calling arch_gettimeoffset() so architectures using this mechanism returned 0 ns when calling these functions.
This happened for example when running Busybox's ping which calls syscall(__NR_clock_gettime, CLOCK_MONOTONIC, ts) which eventually calls ktime_get. As a result the returned ping travel time was zero.
--- kernel/time/timekeeping.c | 4 ++++ 1 file changed, 4 insertions(+)
kernel/time/timekeeping.c +4 -0
@@ -249,6 +249,8 @@ ktime_t ktime_get(void) secs = xtime.tv_sec + wall_to_monotonic.tv_sec; nsecs = xtime.tv_nsec + wall_to_monotonic.tv_nsec; nsecs +=timekeeping_get_ns (); +/* If arch requires, add in gettimeoffset() */ + nsecs +=arch_gettimeoffset (); }while (read_seqretry (&xtime_lock, seq));/*
@@ -280,6 +282,8 @@ void ktime_get_ts(struct timespec *ts) *ts = xtime; tomono = wall_to_monotonic; nsecs =timekeeping_get_ns (); +/* If arch requires, add in gettimeoffset() */ + nsecs +=arch_gettimeoffset (); }while (read_seqretry (&xtime_lock, seq));
PATCH 37/104 hrtimer: Fix extra wakeups from __remove_hrtimer()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jeff Ohlstein <[email protected]>
commit 27c9cd7e601632b3794e1c3344d37b86917ffb43 upstream.
__remove_hrtimer() attempts to reprogram the clockevent device when the timer being removed is the next to expire. However, __remove_hrtimer() reprograms the clockevent *before* removing the timer from the timerqueue and thus when hrtimer_force_reprogram() finds the next timer to expire it finds the timer we're trying to remove.
This is especially noticeable when the system switches to NOHz mode and the system tick is removed. The timer tick is removed from the system but the clockevent is programmed to wakeup in another HZ anyway.
Silence the extra wakeup by removing the timer from the timerqueue before calling hrtimer_force_reprogram() so that we actually program the clockevent for the next timer to expire.
This was broken by 998adc3 "hrtimers: Convert hrtimers to use timerlist infrastructure".
--- kernel/hrtimer.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
kernel/hrtimer.c +4 -2
@@ -885,10 +885,13 @@ static void __remove_hrtimer(struct hrtistruct hrtimer_clock_base *base, unsigned long newstate, int reprogram) { + struct timerqueue_node *next_timer;if (!(timer->state &HRTIMER_STATE_ENQUEUED )) goto out; -if (&timer->node ==timerqueue_getnext (&base->active)) { + next_timer =timerqueue_getnext (&base->active); +timerqueue_del (&base->active, &timer->node); +if (&timer->node == next_timer) {#ifdef CONFIG_HIGH_RES_TIMERS /* Reprogram the clock event device. if enabled */ if (reprogram &&hrtimer_hres_active ()) {
@@ -901,7 +904,6 @@ static void __remove_hrtimer(struct hrti }#endif } -timerqueue_del (&base->active, &timer->node);if (!timerqueue_getnext (&base->active)) base->cpu_base->active_bases &= ~(1 << base->index); out:
PATCH 38/104 clocksource: Avoid selecting mult values that might overflow when adjusted
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: John Stultz <[email protected]>
commit d65670a78cdbfae94f20a9e05ec705871d7cdf2b upstream.
For some frequencies, the clocks_calc_mult_shift() function will unfortunately select mult values very close to 0xffffffff. This has the potential to overflow when NTP adjusts the clock, adding to the mult value.
This patch adds a clocksource.maxadj value, which provides an approximation of an 11% adjustment(NTP limits adjustments to 500ppm and the tick adjustment is limited to 10%), which could be made to the clocksource.mult value. This is then used to both check that the current mult value won't overflow/underflow, as well as warning us if the timekeeping_adjust() code pushes over that 11% boundary.
v2: Fix max_adjustment calculation, and improve WARN_ONCE messages.
v3: Don't warn before maxadj has actually been set
--- include/linux/clocksource.h | 3 +- kernel/time/clocksource.c | 58 ++++++++++++++++++++++++++++++++++++-------- kernel/time/timekeeping.c | 7 +++++ 3 files changed, 57 insertions(+), 11 deletions(-)
include/linux/clocksource.h +2 -1
@@ -156,6 +156,7 @@ extern u64 timecounter_cyc2time(struct t* @mult: cycle to nanosecond multiplier * @shift: cycle to nanosecond divisor (power of two) * @max_idle_ns: max idle time permitted by the clocksource (nsecs) +* @maxadj maximum adjustment value to mult (~11%) * @flags: flags describing special properties * @archdata: arch-specific data * @suspend: suspend function for the clocksource, if necessary
@@ -172,7 +173,7 @@ struct clocksource {u32 mult;u32 shift;u64 max_idle_ns; - +u32 maxadj;#ifdef CONFIG_ARCH_CLOCKSOURCE_DATA struct arch_clocksource_data archdata;#endif
kernel/time/clocksource.c +48 -10
98 lines not on this page · raw message
kernel/time/timekeeping.c +7 -0
@@ -824,6 +824,13 @@ static void timekeeping_adjust(s64 offse }else return ; +WARN_ONCE (timekeeper.clock->maxadj && + (timekeeper.mult + adj > timekeeper.clock->mult + + timekeeper.clock->maxadj), +"Adjusting %s more then 11%% (%ld vs %ld)\n" , + timekeeper.clock->name, (long )timekeeper.mult + adj, + (long )timekeeper.clock->mult + + timekeeper.clock->maxadj); timekeeper.mult += adj; timekeeper.xtime_interval += interval; timekeeper.xtime_nsec -= offset;
PATCH 39/104 p54spi: Add missing spin_lock_init
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: =?UTF-8?q?Michael=20B=C3=BCsch?= <[email protected]>
commit 32d3a3922d617a5a685a5e2d24b20d0e88f192a9 upstream.
The tx_lock is not initialized properly. Add spin_lock_init().
--- drivers/net/wireless/p54/p54spi.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/wireless/p54/p54spi.c +1 -0
@@ -657,6 +657,7 @@ static int __devinit p54spi_probe(structinit_completion (&priv->fw_comp);INIT_LIST_HEAD (&priv->tx_pending);mutex_init (&priv->mutex); +spin_lock_init (&priv->tx_lock);SET_IEEE80211_DEV (hw, &spi->dev); priv->common.open = p54spi_op_start; priv->common.stop = p54spi_op_stop;
PATCH 40/104 p54spi: Fix workqueue deadlock
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: =?UTF-8?q?Michael=20B=C3=BCsch?= <[email protected]>
commit 2d1618170eb493d18f66f2ac03775409a6fb97c6 upstream.
priv->work must not be synced while priv->mutex is locked, because the mutex is taken in the work handler.
Move cancel_work_sync down to after the device shutdown code. This is safe, because the work handler checks fw_state and bails out early in case of a race.
--- drivers/net/wireless/p54/p54spi.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/wireless/p54/p54spi.c +2 -2
@@ -589,8 +589,6 @@ static void p54spi_op_stop(struct ieee80WARN_ON (priv->fw_state !=FW_STATE_READY ); -cancel_work_sync (&priv->work); -p54spi_power_off (priv);spin_lock_irqsave (&priv->tx_lock, flags);INIT_LIST_HEAD (&priv->tx_pending);
@@ -598,6 +596,8 @@ static void p54spi_op_stop(struct ieee80 priv->fw_state =FW_STATE_OFF ;mutex_unlock (&priv->mutex); + +cancel_work_sync (&priv->work); }static int __devinit p54spi_probe (struct spi_device *spi)
PATCH 41/104 rt2x00: Fix efuse EEPROM reading on PPC32.
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gertjan van Wingerde <[email protected]>
commit 68fa64ef606bcee688fce46d07aa68f175070156 upstream.
Fix __le32 to __le16 conversion of the first word of an 8-word block of EEPROM read via the efuse method.
--- drivers/net/wireless/rt2x00/rt2800lib.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/wireless/rt2x00/rt2800lib.c +1 -1
@@ -3699,7 +3699,7 @@ static void rt2800_efuse_read(struct rt2/* Apparently the data is read from end to start */ rt2800_register_read_lock (rt2x00dev,EFUSE_DATA3 , ®);/* The returned value is in CPU order, but eeprom is le */ - rt2x00dev->eeprom[i] =cpu_to_le32 (reg); + *(u32 *)&rt2x00dev->eeprom[i] =cpu_to_le32 (reg);rt2800_register_read_lock (rt2x00dev,EFUSE_DATA2 , ®); *(u32 *)&rt2x00dev->eeprom[i +2 ] =cpu_to_le32 (reg);rt2800_register_read_lock (rt2x00dev,EFUSE_DATA1 , ®);
PATCH 42/104 nl80211: fix MAC address validation
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eliad Peller <[email protected]>
commit e007b857e88097c96c45620bf3b04a4e309053d1 upstream.
MAC addresses have a fixed length. The current policy allows passing < ETH_ALEN bytes, which might result in reading beyond the buffer.
--- net/wireless/nl80211.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/wireless/nl80211.c +2 -2
@@ -83,8 +83,8 @@ static const struct nla_policy nl80211_p [NL80211_ATTR_IFINDEX] = { .type = NLA_U32 }, [NL80211_ATTR_IFNAME] = { .type = NLA_NUL_STRING, .len = IFNAMSIZ-1 }, - [NL80211_ATTR_MAC] = { .type = NLA_BINARY, .len = ETH_ALEN }, - [NL80211_ATTR_PREV_BSSID] = { .type = NLA_BINARY, .len = ETH_ALEN }, + [NL80211_ATTR_MAC] = { .len = ETH_ALEN }, + [NL80211_ATTR_PREV_BSSID] = { .len = ETH_ALEN }, [NL80211_ATTR_KEY] = { .type = NLA_NESTED, }, [NL80211_ATTR_KEY_DATA] = { .type = NLA_BINARY,
PATCH 43/104 cfg80211: fix regulatory NULL dereference
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johannes Berg <[email protected]>
commit de3584bd62d87b4c250129fbc46ca52c80330add upstream.
By the time userspace returns with a response to the regulatory domain request, the wiphy causing the request might have gone away. If this is so, reject the update but mark the request as having been processed anyway.
--- net/wireless/reg.c | 4 ++++ 1 file changed, 4 insertions(+)
net/wireless/reg.c +4 -0
@@ -2026,6 +2026,10 @@ static int __set_regdom(const struct iee } request_wiphy =wiphy_idx_to_wiphy (last_request->wiphy_idx); +if (!request_wiphy) { +reg_set_request_processed (); +return -ENODEV ; + }if (!last_request->intersect) {int r;
PATCH 44/104 mac80211: dont stop a single aggregation session twice
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johannes Berg <[email protected]>
commit 24f50a9d165745fd0701c6e089d35f58a229ea69 upstream.
Nikolay noticed (by code review) that mac80211 can attempt to stop an aggregation session while it is already being stopped. So to fix it, check whether stop is already being done and bail out if so.
Also move setting the STOPPING state into the lock so things are properly atomic.
--- net/mac80211/agg-tx.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
net/mac80211/agg-tx.c +8 -2
@@ -162,6 +162,12 @@ int ___ieee80211_stop_tx_ba_session(strureturn -ENOENT ; } +/* if we're already stopping ignore any new requests to stop */ +if (test_bit (HT_AGG_STATE_STOPPING , &tid_tx->state)) { +spin_unlock_bh (&sta->lock); +return -EALREADY ; + } +if (test_bit (HT_AGG_STATE_WANT_START , &tid_tx->state)) {/* not even started yet! */ ieee80211_assign_tid_tx (sta, tid,NULL );
@@ -170,6 +176,8 @@ int ___ieee80211_stop_tx_ba_session(strureturn 0 ; } +set_bit (HT_AGG_STATE_STOPPING , &tid_tx->state); +spin_unlock_bh (&sta->lock);#ifdef CONFIG_MAC80211_HT_DEBUG
@@ -177,8 +185,6 @@ int ___ieee80211_stop_tx_ba_session(stru sta->sta.addr, tid);#endif /* CONFIG_MAC80211_HT_DEBUG */ -set_bit (HT_AGG_STATE_STOPPING , &tid_tx->state); -del_timer_sync (&tid_tx->addba_resp_timer);/*
PATCH 45/104 mac80211: fix race between the AGG SM and the Tx data path
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Emmanuel Grumbach <[email protected]>
commit 2a1e0fd175dcfd72096ba9291d31e3b1b5342e60 upstream.
When a packet is supposed to sent be as an a-MPDU, mac80211 sets IEEE80211_TX_CTL_AMPDU to let the driver know. On the other hand, mac80211 configures the driver for aggregration with the ampdu_action callback.
There is race between these two mechanisms since the following scenario can occur when the BA agreement is torn down:
Tx softIRQ drv configuration
========== =================
check OPERATIONAL bit
Set the TX_CTL_AMPDU bit in the packet
clear OPERATIONAL bit stop Tx AGG
Pass Tx packet to the driver.
In that case the driver would get a packet with TX_CTL_AMPDU set although it has already been notified that the BA session has been torn down.
To fix this, we need to synchronize all the Qdisc activity after we cleared the OPERATIONAL bit. After that step, all the following packets will be buffered until the driver reports it is ready to get new packets for this RA / TID. This buffering allows not to run into another race that would send packets with TX_CTL_AMPDU unset while the driver hasn't been requested to tear down the BA session yet.
This race occurs in practice and iwlwifi complains with a WARN_ON when it happens.
--- net/mac80211/agg-tx.c | 14 ++++++++++++++ 1 file changed, 14 insertions(+)
net/mac80211/agg-tx.c +14 -0
@@ -194,6 +194,20 @@ int ___ieee80211_stop_tx_ba_session(stru*/ clear_bit (HT_AGG_STATE_OPERATIONAL , &tid_tx->state); +/* +* There might be a few packets being processed right now (on +* another CPU) that have already gotten past the aggregation +* check when it was still OPERATIONAL and consequently have +* IEEE80211_TX_CTL_AMPDU set. In that case, this code might +* call into the driver at the same time or even before the +* TX paths calls into it, which could confuse the driver. +* +* Wait for all currently running TX paths to finish before +* telling the driver. New packets will not go through since +* the aggregation session is no longer OPERATIONAL. +*/ +synchronize_net (); + tid_tx->stop_initiator = initiator; tid_tx->tx_stop = tx;
PATCH 46/104 xfs: dont serialise direct IO reads on page cache checks
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dave Chinner <[email protected]>
commit 0c38a2512df272b14ef4238b476a2e4f70da1479 upstream.
There is no need to grab the i_mutex of the IO lock in exclusive mode if we don't need to invalidate the page cache. Taking these locks on every direct IO effective serialises them as taking the IO lock in exclusive mode has to wait for all shared holders to drop the lock. That only happens when IO is complete, so effective it prevents dispatch of concurrent direct IO reads to the same inode.
Fix this by taking the IO lock shared to check the page cache state, and only then drop it and take the IO lock exclusively if there is work to be done. Hence for the normal direct IO case, no exclusive locking will occur.
--- fs/xfs/xfs_file.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
fs/xfs/xfs_file.c +14 -3
@@ -317,7 +317,19 @@ xfs_file_aio_read(if (XFS_FORCED_SHUTDOWN (mp))return -EIO ; -if (unlikely (ioflags &IO_ISDIRECT )) { +/* +* Locking is a bit tricky here. If we take an exclusive lock +* for direct IO, we effectively serialise all new concurrent +* read IO to this file and block it behind IO that is currently in +* progress because IO in progress holds the IO lock shared. We only +* need to hold the lock exclusive to blow away the page cache, so +* only take lock exclusively if the page cache needs invalidation. +* This allows the normal direct IO case of no page cache pages to +* proceeed concurrently without serialisation. +*/ +xfs_rw_ilock (ip,XFS_IOLOCK_SHARED ); +if ((ioflags &IO_ISDIRECT ) && inode->i_mapping->nrpages) { +xfs_rw_iunlock (ip,XFS_IOLOCK_SHARED );xfs_rw_ilock (ip,XFS_IOLOCK_EXCL );if (inode->i_mapping->nrpages) {
@@ -330,8 +342,7 @@ xfs_file_aio_read( } }xfs_rw_ilock_demote (ip,XFS_IOLOCK_EXCL ); - }else -xfs_rw_ilock (ip,XFS_IOLOCK_SHARED ); + }trace_xfs_file_read (ip, size, iocb->ki_pos, ioflags);
PATCH 47/104 xfs: avoid direct I/O write vs buffered I/O race
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Hellwig <[email protected]>
commit c58cb165bd44de8aaee9755a144136ae743be116 upstream.
Currently a buffered reader or writer can add pages to the pagecache while we are waiting for the iolock in xfs_file_dio_aio_write. Prevent this by re-checking mapping->nrpages after we got the iolock, and if nessecary upgrade the lock to exclusive mode. To simplify this a bit only take the ilock inside of xfs_file_aio_write_checks.
--- fs/xfs/xfs_file.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
fs/xfs/xfs_file.c +14 -3
@@ -677,6 +677,7 @@ xfs_file_aio_write_checks(xfs_fsize_t new_size;int error =0 ; +xfs_rw_ilock (ip,XFS_ILOCK_EXCL ); error =generic_write_checks (file, pos, count,S_ISBLK (inode->i_mode));if (error) {xfs_rw_iunlock (ip,XFS_ILOCK_EXCL | *iolock);
@@ -768,14 +769,24 @@ xfs_file_dio_aio_write( *iolock =XFS_IOLOCK_EXCL ; else *iolock =XFS_IOLOCK_SHARED ; -xfs_rw_ilock (ip,XFS_ILOCK_EXCL | *iolock); +xfs_rw_ilock (ip, *iolock); ret =xfs_file_aio_write_checks (file, &pos, &count, iolock);if (ret)return ret; +/* +* Recheck if there are cached pages that need invalidate after we got +* the iolock to protect against other threads adding new pages while +* we were waiting for the iolock. +*/ +if (mapping->nrpages && *iolock ==XFS_IOLOCK_SHARED ) { +xfs_rw_iunlock (ip, *iolock); + *iolock =XFS_IOLOCK_EXCL ; +xfs_rw_ilock (ip, *iolock); + } +if (mapping->nrpages) { -WARN_ON (*iolock !=XFS_IOLOCK_EXCL ); ret = -xfs_flushinval_pages (ip, (pos &PAGE_CACHE_MASK ),-1 ,FI_REMAPF_LOCKED );if (ret)
@@ -820,7 +831,7 @@ xfs_file_buffered_aio_write(size_t count = ocount; *iolock =XFS_IOLOCK_EXCL ; -xfs_rw_ilock (ip,XFS_ILOCK_EXCL | *iolock); +xfs_rw_ilock (ip, *iolock); ret =xfs_file_aio_write_checks (file, &pos, &count, iolock);if (ret)
PATCH 48/104 xfs: Return -EIO when xfs_vn_getattr() failed
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mitsuo Hayasaka <[email protected]>
commit ed32201e65e15f3e6955cb84cbb544b08f81e5a5 upstream.
An attribute of inode can be fetched via xfs_vn_getattr() in XFS. Currently it returns EIO, not negative value, when it failed. As a result, the system call returns not negative value even though an error occured. The stat(2), ls and mv commands cannot handle this error and do not work correctly.
This patch fixes this bug, and returns -EIO, not EIO when an error is detected in xfs_vn_getattr().
--- fs/xfs/xfs_iops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/xfs/xfs_iops.c +1 -1
@@ -465,7 +465,7 @@ xfs_vn_getattr(trace_xfs_getattr (ip);if (XFS_FORCED_SHUTDOWN (mp)) -return XFS_ERROR (EIO ); +return -XFS_ERROR (EIO ); stat->size =XFS_ISIZE (ip); stat->dev = inode->i_sb->s_dev;
PATCH 49/104 xfs: fix buffer flushing during unmount
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Hellwig <[email protected]>
commit 87c7bec7fc3377b3873eb3a0f4b603981ea16ebb upstream.
The code to flush buffers in the umount code is a bit iffy: we first flush all delwri buffers out, but then might be able to queue up a new one when logging the sb counts. On a normal shutdown that one would get flushed out when doing the synchronous superblock write in xfs_unmountfs_writesb, but we skip that one if the filesystem has been shut down.
Fix this by moving the delwri list flushing until just before unmounting the log, and while we're at it also remove the superflous delwri list and buffer lru flusing for the rt and log device that can never have cached or delwri buffers.
--- fs/xfs/xfs_buf.h | 1 - fs/xfs/xfs_mount.c | 29 ++++++++++------------------- 2 files changed, 10 insertions(+), 20 deletions(-)
fs/xfs/xfs_buf.h +0 -1
@@ -320,7 +320,6 @@ extern struct list_head *xfs_get_buftarg#define xfs_getsize_buftarg (buftarg) block_size((buftarg)->bt_bdev)#define xfs_readonly_buftarg (buftarg) bdev_read_only((buftarg)->bt_bdev) -#define xfs_binval (buftarg) xfs_flush_buftarg(buftarg, 1)#define XFS_bflush (buftarg) xfs_flush_buftarg(buftarg, 1)#endif /* __XFS_BUF_H__ */
fs/xfs/xfs_mount.c +10 -19
@@ -44,9 +44,6 @@#include "xfs_trace.h" -STATIC void xfs_unmountfs_wait(xfs_mount_t *); - -#ifdef HAVE_PERCPU_SB STATIC void xfs_icsb_balance_counter(xfs_mount_t *, xfs_sb_field_t,int );
@@ -1496,11 +1493,6 @@ xfs_unmountfs(*/ xfs_log_force (mp,XFS_LOG_SYNC ); -xfs_binval (mp->m_ddev_targp); -if (mp->m_rtdev_targp) { -xfs_binval (mp->m_rtdev_targp); - } -/* * Unreserve any blocks we have so that when we unmount we don't account * the reserved free space as used. This is really only necessary for
@@ -1526,7 +1518,16 @@ xfs_unmountfs(xfs_warn (mp,"Unable to update superblock counters. " "Freespace may not be correct on next mount." );xfs_unmountfs_writesb (mp); -xfs_unmountfs_wait (mp);/* wait for async bufs */ + +/* +* Make sure all buffers have been flushed and completed before +* unmounting the log. +*/ + error =xfs_flush_buftarg (mp->m_ddev_targp,1 ); +if (error) +xfs_warn (mp,"%d busy buffers during unmount." , error); +xfs_wait_buftarg (mp->m_ddev_targp); +xfs_log_unmount_write (mp);xfs_log_unmount (mp);xfs_uuid_unmount (mp);
@@ -1537,16 +1538,6 @@ xfs_unmountfs(xfs_free_perag (mp); } -STATIC void -xfs_unmountfs_wait (xfs_mount_t *mp) -{ -if (mp->m_logdev_targp != mp->m_ddev_targp) -xfs_wait_buftarg (mp->m_logdev_targp); -if (mp->m_rtdev_targp) -xfs_wait_buftarg (mp->m_rtdev_targp); -xfs_wait_buftarg (mp->m_ddev_targp); -} -int xfs_fs_writable (xfs_mount_t *mp) {
PATCH 50/104 xfs: Fix possible memory corruption in xfs_readlink
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Carlos Maiolino <[email protected]>
commit b52a360b2aa1c59ba9970fb0f52bbb093fcc7a24 upstream.
Fixes a possible memory corruption when the link is larger than MAXPATHLEN and XFS_DEBUG is not enabled. This also remove the S_ISLNK assert, since the inode mode is checked previously in xfs_readlink_by_handle() and via VFS.
Updated to address concerns raised by Ben Hutchings about the loose attention paid to 32- vs 64-bit values, and the lack of handling a potentially negative pathlen value:
- Changed type of "pathlen" to be xfs_fsize_t, to match that of ip->i_d.di_size
- Added checking for a negative pathlen to the too-long pathlen test, and generalized the message that gets reported in that case to reflect the change
As a result, if a negative pathlen were encountered, this function would return EFSCORRUPTED (and would fail an assertion for a debug build)--just as would a too-long pathlen.
--- fs/xfs/xfs_vnodeops.c | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
fs/xfs/xfs_vnodeops.c +10 -4
@@ -113,7 +113,7 @@ xfs_readlink( char *link) {xfs_mount_t *mp = ip->i_mount; -int pathlen; +xfs_fsize_t pathlen;int error =0 ;trace_xfs_readlink (ip);
@@ -123,13 +123,19 @@ xfs_readlink(xfs_ilock (ip,XFS_ILOCK_SHARED ); -ASSERT (S_ISLNK (ip->i_d.di_mode)); -ASSERT (ip->i_d.di_size <=MAXPATHLEN ); - pathlen = ip->i_d.di_size;if (!pathlen) goto out; +if (pathlen <0 || pathlen >MAXPATHLEN ) { +xfs_alert (mp,"%s: inode (%llu) bad symlink length (%lld)" , + __func__, (unsigned long long ) ip->i_ino, + (long long ) pathlen); +ASSERT (0 ); +return XFS_ERROR (EFSCORRUPTED ); + } + +if (ip->i_df.if_flags &XFS_IFINLINE ) {memcpy (link, ip->i_df.if_u1.if_data, pathlen); link[pathlen] ='\0' ;
PATCH 51/104 xfs: use doalloc flag in xfs_qm_dqattach_one()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mitsuo Hayasaka <[email protected]>
commit db3e74b582915d66e10b0c73a62763418f54c340 upstream.
The doalloc arg in xfs_qm_dqattach_one() is a flag that indicates whether a new area to handle quota information will be allocated if needed. Originally, it was passed to xfs_qm_dqget(), but has been removed by the following commit (probably by mistake):
commit 8e9b6e7fa4544ea8a0e030c8987b918509c8ff47 Author: Christoph Hellwig <[email protected]> Date: Sun Feb 8 21:51:42 2009 +0100 xfs: remove the unused XFS_QMOPT_DQLOCK flag
As the result, xfs_qm_dqget() called from xfs_qm_dqattach_one() never allocates the new area even if it is needed.
This patch gives the doalloc arg to xfs_qm_dqget() in xfs_qm_dqattach_one() to fix this problem.
--- fs/xfs/xfs_qm.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/xfs/xfs_qm.c +2 -1
@@ -674,7 +674,8 @@ xfs_qm_dqattach_one(* disk and we didn't ask it to allocate; * ESRCH if quotas got turned off suddenly. */ - error =xfs_qm_dqget (ip->i_mount, ip, id, type,XFS_QMOPT_DOWARN , &dqp); + error =xfs_qm_dqget (ip->i_mount, ip, id, type, + doalloc |XFS_QMOPT_DOWARN , &dqp);if (error)return error;
PATCH 52/104 SCSI: Silencing killing requests for dead queue
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hannes Reinecke <[email protected]>
commit 745718132c3c7cac98a622b610e239dcd5217f71 upstream.
When we tear down a device we try to flush all outstanding commands in scsi_free_queue(). However the check in scsi_request_fn() is imperfect as it only signals that we _might start_ aborting commands, not that we've actually aborted some.
So move the printk inside the scsi_kill_request function, this will also give us a hint about which commands are aborted.
--- drivers/scsi/scsi_lib.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/scsi/scsi_lib.c +2 -1
@@ -1408,6 +1408,8 @@ static void scsi_kill_request(struct reqblk_start_request (req); +scmd_printk (KERN_INFO , cmd,"killing request\n" ); + sdev = cmd->device; starget =scsi_target (sdev); shost = sdev->host;
@@ -1489,7 +1491,6 @@ static void scsi_request_fn(struct requestruct request *req;if (!sdev) { -printk ("scsi: killing requests for dead queue\n" );while ((req =blk_peek_request (q)) !=NULL )scsi_kill_request (req, q);return ;
PATCH 53/104 hugetlb: release pages in the error path of hugetlb_cow()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hillf Danton <[email protected]>
commit ea4039a34c4c206d015d34a49d0b00868e37db1d upstream.
If we fail to prepare an anon_vma, the {new, old}_page should be released, or they will leak.
--- mm/hugetlb.c | 2 ++ 1 file changed, 2 insertions(+)
mm/hugetlb.c +2 -0
@@ -2422,6 +2422,8 @@ retry_avoidcopy:* anon_vma prepared. */ if (unlikely (anon_vma_prepare (vma))) { +page_cache_release (new_page); +page_cache_release (old_page);/* Caller expects lock to be held */ spin_lock (&mm->page_table_lock);return VM_FAULT_OOM ;
PATCH 54/104 bridge: correct IPv6 checksum after pull
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: stephen hemminger <[email protected]>
commit fa2da8cdae1dd64f78fc915ca1d1a4a93c71e7cb upstream.
Bridge multicast snooping of ICMPv6 would incorrectly report a checksum problem when used with Ethernet devices like sky2 that use CHECKSUM_COMPLETE. When bytes are removed from skb, the computed checksum needs to be adjusted.
--- net/bridge/br_multicast.c | 2 ++ 1 file changed, 2 insertions(+)
net/bridge/br_multicast.c +2 -0
@@ -1501,6 +1501,8 @@ static int br_multicast_ipv6_rcv(struct__skb_pull (skb2, offset);skb_reset_transport_header (skb2); +skb_postpull_rcsum (skb2,skb_network_header (skb2), +skb_network_header_len (skb2)); icmp6_type =icmp6_hdr (skb2)->icmp6_type;
PATCH 55/104 iwlwifi: allow pci_enable_msi fail
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wey-Yi Guy <[email protected]>
commit 8a39ef8ba0fa0410d71db8e981e887fe4fdeca88 upstream.
Continue the init process even fail to enable msi
out_iounmap is no longer used, remove it
--- drivers/net/wireless/iwlwifi/iwl-pci.c | 8 +++----- 1 file changed, 3 insertions(+), 5 deletions(-)
drivers/net/wireless/iwlwifi/iwl-pci.c +3 -5
@@ -442,10 +442,9 @@ static int iwl_pci_probe(struct pci_devpci_write_config_byte (pdev,PCI_CFG_RETRY_TIMEOUT ,0x00 ); err =pci_enable_msi (pdev); -if (err) { -dev_printk (KERN_ERR , &pdev->dev,"pci_enable_msi failed" ); - goto out_iounmap; - } +if (err) +dev_printk (KERN_ERR , &pdev->dev, +"pci_enable_msi failed(0X%x)" , err);/* TODO: Move this away, not needed if not MSI */ /* enable rfkill interrupt: hw bug w/a */
@@ -466,7 +465,6 @@ static int iwl_pci_probe(struct pci_dev out_disable_msi:pci_disable_msi (pdev); -out_iounmap:pci_iounmap (pdev, pci_bus->hw_base); out_pci_release_regions:pci_set_drvdata (pdev,NULL );
PATCH 56/104 drm/radeon/kms: add some new pci ids
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 2ed4d9d648cbd4fb1c232a646dbdbdfdd373ca94 upstream.
--- include/drm/drm_pciids.h | 8 ++++++++ 1 file changed, 8 insertions(+)
include/drm/drm_pciids.h +8 -0
@@ -197,6 +197,14 @@ {0x1002, 0x6770, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_CAICOS|RADEON_NEW_MEMMAP}, \ {0x1002, 0x6778, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_CAICOS|RADEON_NEW_MEMMAP}, \ {0x1002, 0x6779, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_CAICOS|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6840, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6841, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6842, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6843, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6849, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6850, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6858, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_NEW_MEMMAP}, \ + {0x1002, 0x6859, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_TURKS|RADEON_NEW_MEMMAP}, \ {0x1002, 0x6880, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_CYPRESS|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP}, \ {0x1002, 0x6888, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_CYPRESS|RADEON_NEW_MEMMAP}, \ {0x1002, 0x6889, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_CYPRESS|RADEON_NEW_MEMMAP}, \
PATCH 57/104 drm/radeon/kms: add some loop timeouts in pageflip code
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit f64964796dedca340608fb1075ab6baad5625851 upstream.
Avoid infinite loops waiting for surface updates if a GPU reset happens while waiting for a page flip.
See:
https://bugs.freedesktop.org/show_bug.cgi?id=43191
--- drivers/gpu/drm/radeon/evergreen.c | 7 ++++++- drivers/gpu/drm/radeon/r100.c | 7 ++++++- drivers/gpu/drm/radeon/rs600.c | 7 ++++++- drivers/gpu/drm/radeon/rv770.c | 7 ++++++- 4 files changed, 24 insertions(+), 4 deletions(-)
drivers/gpu/drm/radeon/evergreen.c +6 -1
@@ -82,6 +82,7 @@ u32 evergreen_page_flip(struct radeon_de {struct radeon_crtc *radeon_crtc = rdev->mode_info.crtcs[crtc_id];u32 tmp =RREG32 (EVERGREEN_GRPH_UPDATE + radeon_crtc->crtc_offset); +int i;/* Lock the graphics update lock */ tmp |=EVERGREEN_GRPH_UPDATE_LOCK ;
@@ -99,7 +100,11 @@ u32 evergreen_page_flip(struct radeon_de (u32)crtc_base);/* Wait for update_pending to go high. */ -while (!(RREG32 (EVERGREEN_GRPH_UPDATE + radeon_crtc->crtc_offset) &EVERGREEN_GRPH_SURFACE_UPDATE_PENDING )); +for (i =0 ; i < rdev->usec_timeout; i++) { +if (RREG32 (EVERGREEN_GRPH_UPDATE + radeon_crtc->crtc_offset) &EVERGREEN_GRPH_SURFACE_UPDATE_PENDING ) +break ; +udelay (1 ); + }DRM_DEBUG ("Update pending now high. Unlocking vupdate_lock.\n" );/* Unlock the lock, so double-buffering can take place inside vblank */
drivers/gpu/drm/radeon/r100.c +6 -1
@@ -84,13 +84,18 @@ u32 r100_page_flip(struct radeon_device {struct radeon_crtc *radeon_crtc = rdev->mode_info.crtcs[crtc_id];u32 tmp = ((u32 )crtc_base) |RADEON_CRTC_OFFSET__OFFSET_LOCK ; +int i;/* Lock the graphics update lock */ /* update the scanout addresses */ WREG32 (RADEON_CRTC_OFFSET + radeon_crtc->crtc_offset, tmp);/* Wait for update_pending to go high. */ -while (!(RREG32 (RADEON_CRTC_OFFSET + radeon_crtc->crtc_offset) &RADEON_CRTC_OFFSET__GUI_TRIG_OFFSET )); +for (i =0 ; i < rdev->usec_timeout; i++) { +if (RREG32 (RADEON_CRTC_OFFSET + radeon_crtc->crtc_offset) &RADEON_CRTC_OFFSET__GUI_TRIG_OFFSET ) +break ; +udelay (1 ); + }DRM_DEBUG ("Update pending now high. Unlocking vupdate_lock.\n" );/* Unlock the lock, so double-buffering can take place inside vblank */
drivers/gpu/drm/radeon/rs600.c +6 -1
@@ -62,6 +62,7 @@ u32 rs600_page_flip(struct radeon_device {struct radeon_crtc *radeon_crtc = rdev->mode_info.crtcs[crtc_id];u32 tmp =RREG32 (AVIVO_D1GRPH_UPDATE + radeon_crtc->crtc_offset); +int i;/* Lock the graphics update lock */ tmp |=AVIVO_D1GRPH_UPDATE_LOCK ;
@@ -74,7 +75,11 @@ u32 rs600_page_flip(struct radeon_device (u32)crtc_base);/* Wait for update_pending to go high. */ -while (!(RREG32 (AVIVO_D1GRPH_UPDATE + radeon_crtc->crtc_offset) &AVIVO_D1GRPH_SURFACE_UPDATE_PENDING )); +for (i =0 ; i < rdev->usec_timeout; i++) { +if (RREG32 (AVIVO_D1GRPH_UPDATE + radeon_crtc->crtc_offset) &AVIVO_D1GRPH_SURFACE_UPDATE_PENDING ) +break ; +udelay (1 ); + }DRM_DEBUG ("Update pending now high. Unlocking vupdate_lock.\n" );/* Unlock the lock, so double-buffering can take place inside vblank */
drivers/gpu/drm/radeon/rv770.c +6 -1
@@ -47,6 +47,7 @@ u32 rv770_page_flip(struct radeon_device {struct radeon_crtc *radeon_crtc = rdev->mode_info.crtcs[crtc_id];u32 tmp =RREG32 (AVIVO_D1GRPH_UPDATE + radeon_crtc->crtc_offset); +int i;/* Lock the graphics update lock */ tmp |=AVIVO_D1GRPH_UPDATE_LOCK ;
@@ -66,7 +67,11 @@ u32 rv770_page_flip(struct radeon_device (u32)crtc_base);/* Wait for update_pending to go high. */ -while (!(RREG32 (AVIVO_D1GRPH_UPDATE + radeon_crtc->crtc_offset) &AVIVO_D1GRPH_SURFACE_UPDATE_PENDING )); +for (i =0 ; i < rdev->usec_timeout; i++) { +if (RREG32 (AVIVO_D1GRPH_UPDATE + radeon_crtc->crtc_offset) &AVIVO_D1GRPH_SURFACE_UPDATE_PENDING ) +break ; +udelay (1 ); + }DRM_DEBUG ("Update pending now high. Unlocking vupdate_lock.\n" );/* Unlock the lock, so double-buffering can take place inside vblank */
PATCH 58/104 ALSA: hda - Fix S3/S4 problem on machines with VREF-pin mute-LED
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Charles Chin <[email protected]>
commit 88d686027bb43f585914c77dd363f6e817b42c2a upstream.
The verb command in stac92xx_post_suspend caused the audio to stop working after resuming from S3 mode on HP laptops with the VREF-pin mute-LED control. Removing relevant post_suspend registering.
Although removing D3 on AFG is no optimal solution, the impact should be small in comparison with the broken S3/S4.
--- sound/pci/hda/patch_sigmatel.c | 18 ------------------ 1 file changed, 18 deletions(-)
sound/pci/hda/patch_sigmatel.c +0 -18
@@ -5035,20 +5035,6 @@ static int stac92xx_pre_resume(struct hdreturn 0 ; } -static int stac92xx_post_suspend (struct hda_codec *codec) -{ -struct sigmatel_spec *spec = codec->spec; -if (spec->gpio_led >8 ) { -/* with vref-out pin used for mute led control -* codec AFG is prevented from D3 state, but on -* system suspend it can (and should) be used -*/ -snd_hda_codec_read (codec, codec->afg,0 , -AC_VERB_SET_POWER_STATE ,AC_PWRST_D3 ); - } -return 0 ; -} -static void stac92xx_set_power_state (struct hda_codec *codec,hda_nid_t fg,unsigned int power_state) {
@@ -5655,8 +5641,6 @@ again: }else { codec->patch_ops.set_power_state = stac92xx_set_power_state; - codec->patch_ops.post_suspend = - stac92xx_post_suspend; } codec->patch_ops.pre_resume = stac92xx_pre_resume; codec->patch_ops.check_power_status =
@@ -5978,8 +5962,6 @@ again: }else { codec->patch_ops.set_power_state = stac92xx_set_power_state; - codec->patch_ops.post_suspend = - stac92xx_post_suspend; } codec->patch_ops.pre_resume = stac92xx_pre_resume; codec->patch_ops.check_power_status =
PATCH 59/104 ASoC: Fix wrong define for AD1836_ADC_WORD_OFFSET
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Axel Lin <[email protected]>
commit 72531c9434fa884d20cb3c36fcec83752f32fdf4 upstream.
According to the datasheet:
The BIT[5:4] of ADC Control Register 2 is to control the word width.
00 = 25 Bits
01 = 20 Bits
10 = 16 Bits
11 = InvalidThus, the AD1836_ADC_WORD_OFFSET should be defined as 4.
--- sound/soc/codecs/ad1836.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/ad1836.h +1 -1
@@ -34,7 +34,7 @@#define AD1836_ADC_CTRL2 13#define AD1836_ADC_WORD_LEN_MASK 0x30 -#define AD1836_ADC_WORD_OFFSET 5 +#define AD1836_ADC_WORD_OFFSET 4#define AD1836_ADC_SERFMT_MASK (7 << 6)#define AD1836_ADC_SERFMT_PCK256 (0x4 << 6)#define AD1836_ADC_SERFMT_PCK128 (0x5 << 6)
PATCH 60/104 firmware: Sigma: Prevent out of bounds memory access
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit 4f718a29fe4908c2cea782f751e9805319684e2b upstream.
The SigmaDSP firmware loader currently does not perform enough boundary size checks when processing the firmware. As a result it is possible that a malformed firmware can cause an out of bounds memory access.
This patch adds checks which ensure that both the action header and the payload are completely inside the firmware data boundaries before processing them.
--- drivers/firmware/sigma.c | 76 ++++++++++++++++++++++++++++++++++------------- include/linux/sigma.h | 5 --- 2 files changed, 55 insertions(+), 26 deletions(-)
drivers/firmware/sigma.c +55 -21
@@ -14,13 +14,34 @@#include <linux/module.h> #include <linux/sigma.h> -/* Return: 0==OK, <0==error, =1 ==no more actions */ +static size_t sigma_action_size (struct sigma_action *sa) +{ +size_t payload =0 ; + +switch (sa->instr) { +case SIGMA_ACTION_WRITEXBYTES : +case SIGMA_ACTION_WRITESINGLE : +case SIGMA_ACTION_WRITESAFELOAD : + payload =sigma_action_len (sa); +break ; +default : +break ; + } + + payload =ALIGN (payload,2 ); + +return payload +sizeof (struct sigma_action ); +} + +/* +* Returns a negative error value in case of an error, 0 if processing of +* the firmware should be stopped after this action, 1 otherwise. +*/ static int -process_sigma_action (struct i2c_client *client,struct sigma_firmware *ssfw) +process_sigma_action (struct i2c_client *client,struct sigma_action *sa) { -struct sigma_action *sa = (void *)(ssfw->fw->data + ssfw->pos);size_t len =sigma_action_len (sa); -int ret =0 ; +int ret;pr_debug ("%s: instr:%i addr:%#x len:%zu\n" , __func__, sa->instr, sa->addr, len);
@@ -29,44 +50,50 @@ process_sigma_action(struct i2c_client *case SIGMA_ACTION_WRITEXBYTES :case SIGMA_ACTION_WRITESINGLE :case SIGMA_ACTION_WRITESAFELOAD : -if (ssfw->fw->size < ssfw->pos + len) -return -EINVAL ; ret =i2c_master_send (client, (void *)&sa->addr, len);if (ret <0 )return -EINVAL ;break ; -case SIGMA_ACTION_DELAY : - ret =0 ;udelay (len); len =0 ;break ; -case SIGMA_ACTION_END : -return 1 ; - +return 0 ;default :return -EINVAL ; } -/* when arrive here ret=0 or sent data */ - ssfw->pos +=sigma_action_size (sa, len); -return ssfw->pos == ssfw->fw->size; +return 1 ; }static int process_sigma_actions (struct i2c_client *client,struct sigma_firmware *ssfw) { -pr_debug ("%s: processing %p\n" , __func__, ssfw); +struct sigma_action *sa; +size_t size; +int ret; + +while (ssfw->pos +sizeof (*sa) <= ssfw->fw->size) { + sa = (struct sigma_action *)(ssfw->fw->data + ssfw->pos); + + size =sigma_action_size (sa); + ssfw->pos += size; +if (ssfw->pos > ssfw->fw->size || size ==0 ) +break ; + + ret =process_sigma_action (client, sa); -while (1 ) { -int ret =process_sigma_action (client, ssfw);pr_debug ("%s: action returned %i\n" , __func__, ret); -if (ret ==1 ) -return 0 ; -else if (ret) + +if (ret <=0 )return ret; } + +if (ssfw->pos != ssfw->fw->size) +return -EINVAL ; + +return 0 ; }int process_sigma_firmware (struct i2c_client *client,const char *name)
@@ -89,7 +116,14 @@ int process_sigma_firmware(struct i2c_cl/* then verify the header */ ret = -EINVAL ; -if (fw->size <sizeof (*ssfw_head)) + +/* +* Reject too small or unreasonable large files. The upper limit has been +* chosen a bit arbitrarily, but it should be enough for all practical +* purposes and having the limit makes it easier to avoid integer +* overflows later in the loading process. +*/ +if (fw->size <sizeof (*ssfw_head) || fw->size >=0x4000000 ) goto done; ssfw_head = (void *)fw->data;
include/linux/sigma.h +0 -5
@@ -50,11 +50,6 @@ static inline u32 sigma_action_len(struc return (sa->len_hi << 16) | sa->len; } -static inline size_t sigma_action_size (struct sigma_action *sa,u32 payload_len) -{ -return sizeof (*sa) + payload_len + (payload_len %2 ); -} -extern int process_sigma_firmware (struct i2c_client *client,const char *name);#endif
PATCH 61/104 firmware: Sigma: Skip header during CRC generation
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit c56935bdc0a8edf50237d3b0205133a5b0adc604 upstream.
The firmware header is not part of the CRC, so skip it. Otherwise the firmware will be rejected due to non-matching CRCs.
--- drivers/firmware/sigma.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/firmware/sigma.c +2 -1
@@ -130,7 +130,8 @@ int process_sigma_firmware(struct i2c_clif (memcmp (ssfw_head->magic,SIGMA_MAGIC ,ARRAY_SIZE (ssfw_head->magic))) goto done; - crc =crc32 (0 , fw->data, fw->size); + crc =crc32 (0 , fw->data +sizeof (*ssfw_head), + fw->size -sizeof (*ssfw_head));pr_debug ("%s: crc=%x\n" , __func__, crc);if (crc != ssfw_head->crc) goto done;
PATCH 62/104 firmware: Sigma: Fix endianess issues
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lars-Peter Clausen <[email protected]>
commit bda63586bc5929e97288cdb371bb6456504867ed upstream.
Currently the SigmaDSP firmware loader only works correctly on little-endian systems. Fix this by using the proper endianess conversion functions.
--- drivers/firmware/sigma.c | 2 +- include/linux/sigma.h | 8 ++++---- 2 files changed, 5 insertions(+), 5 deletions(-)
drivers/firmware/sigma.c +1 -1
@@ -133,7 +133,7 @@ int process_sigma_firmware(struct i2c_cl crc =crc32 (0 , fw->data +sizeof (*ssfw_head), fw->size -sizeof (*ssfw_head));pr_debug ("%s: crc=%x\n" , __func__, crc); -if (crc != ssfw_head->crc) +if (crc !=le32_to_cpu (ssfw_head->crc)) goto done; ssfw.pos =sizeof (*ssfw_head);
include/linux/sigma.h +4 -4
@@ -24,7 +24,7 @@ struct sigma_firmware {struct sigma_firmware_header {unsigned char magic[7 ];u8 version; -u32 crc; +__le32 crc; };enum {
@@ -40,14 +40,14 @@ enum {struct sigma_action {u8 instr;u8 len_hi; -u16 len; -u16 addr; +__le16 len; +__be16 addr;unsigned char payload[]; };static inline u32 sigma_action_len (struct sigma_action *sa) { -return (sa->len_hi <<16 ) | sa->len; +return (sa->len_hi <<16 ) |le16_to_cpu (sa->len); }extern int process_sigma_firmware (struct i2c_client *client,const char *name);
PATCH 63/104 staging:rts_pstor:Complete scanning_done variable
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: wwang <[email protected]>
commit f7364ba04b0961f3a1f978bbe77102606801e35f upstream.
Complete scanning_done variable if rtsx-scan thread created failed.
--- drivers/staging/rts_pstor/rtsx.c | 1 + 1 file changed, 1 insertion(+)
drivers/staging/rts_pstor/rtsx.c +1 -0
@@ -1015,6 +1015,7 @@ static int __devinit rtsx_probe(struct p th =kthread_create (rtsx_scan_thread, dev,"rtsx-scan" );if (IS_ERR (th)) {printk (KERN_ERR "Unable to start the device-scanning thread\n" ); +complete (&dev->scanning_done);quiesce_and_remove_host (dev); err =PTR_ERR (th); goto errout;
PATCH 64/104 staging: usbip: bugfix for deadlock
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bart Westgeest <[email protected]>
commit 438957f8d4a84daa7fa5be6978ad5897a2e9e5e5 upstream.
Interrupts must be disabled prior to calling usb_hcd_unlink_urb_from_ep. If interrupts are not disabled, it can potentially lead to a deadlock. The deadlock is readily reproduceable on a slower (ARM based) device such as the TI Pandaboard.
--- drivers/staging/usbip/vhci_rx.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
drivers/staging/usbip/vhci_rx.c +6 -4
@@ -68,6 +68,7 @@ static void vhci_recv_ret_submit(struct {struct usbip_device *ud = &vdev->ud;struct urb *urb; +unsigned long flags;spin_lock (&vdev->priv_lock); urb =pickup_urb_and_free_priv (vdev, pdu->base.seqnum);
@@ -101,9 +102,9 @@ static void vhci_recv_ret_submit(structusbip_dbg_vhci_rx ("now giveback urb %p\n" , urb); -spin_lock (&the_controller->lock); +spin_lock_irqsave (&the_controller->lock, flags);usb_hcd_unlink_urb_from_ep (vhci_to_hcd (the_controller), urb); -spin_unlock (&the_controller->lock); +spin_unlock_irqrestore (&the_controller->lock, flags);usb_hcd_giveback_urb (vhci_to_hcd (the_controller), urb, urb->status);
@@ -141,6 +142,7 @@ static void vhci_recv_ret_unlink(struct {struct vhci_unlink *unlink;struct urb *urb; +unsigned long flags;usbip_dump_header (pdu);
@@ -170,9 +172,9 @@ static void vhci_recv_ret_unlink(struct urb->status = pdu->u.ret_unlink.status;pr_info ("urb->status %d\n" , urb->status); -spin_lock (&the_controller->lock); +spin_lock_irqsave (&the_controller->lock, flags);usb_hcd_unlink_urb_from_ep (vhci_to_hcd (the_controller), urb); -spin_unlock (&the_controller->lock); +spin_unlock_irqrestore (&the_controller->lock, flags);usb_hcd_giveback_urb (vhci_to_hcd (the_controller), urb, urb->status);
PATCH 65/104 staging: comedi: fix oops for USB DAQ devices.
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bernd Porr <[email protected]>
commit 3ffab428f40849ed5f21bcfd7285bdef7902f9ca upstream.
This fixes kernel oops when an USB DAQ device is plugged out while it's communicating with the userspace software.
--- drivers/staging/comedi/comedi_fops.c | 73 +++++++++++++++++++++++++---------- 1 file changed, 54 insertions(+), 19 deletions(-)
drivers/staging/comedi/comedi_fops.c +54 -19
@@ -1452,9 +1452,6 @@ static struct vm_operations_struct comedstatic int comedi_mmap (struct file *file,struct vm_area_struct *vma) {const unsigned minor =iminor (file->f_dentry->d_inode); -struct comedi_device_file_info *dev_file_info = -comedi_get_device_file_info (minor); -struct comedi_device *dev = dev_file_info->device;struct comedi_async *async =NULL ;unsigned long start = vma->vm_start;unsigned long size;
@@ -1462,6 +1459,15 @@ static int comedi_mmap(struct file *fileint i;int retval;struct comedi_subdevice *s; +struct comedi_device_file_info *dev_file_info; +struct comedi_device *dev; + + dev_file_info =comedi_get_device_file_info (minor); +if (dev_file_info ==NULL ) +return -ENODEV ; + dev = dev_file_info->device; +if (dev ==NULL ) +return -ENODEV ;mutex_lock (&dev->mutex);if (!dev->attached) {
@@ -1528,11 +1534,17 @@ static unsigned int comedi_poll(struct f {unsigned int mask =0 ;const unsigned minor =iminor (file->f_dentry->d_inode); -struct comedi_device_file_info *dev_file_info = -comedi_get_device_file_info (minor); -struct comedi_device *dev = dev_file_info->device;struct comedi_subdevice *read_subdev;struct comedi_subdevice *write_subdev; +struct comedi_device_file_info *dev_file_info; +struct comedi_device *dev; + dev_file_info =comedi_get_device_file_info (minor); + +if (dev_file_info ==NULL ) +return -ENODEV ; + dev = dev_file_info->device; +if (dev ==NULL ) +return -ENODEV ;mutex_lock (&dev->mutex);if (!dev->attached) {
@@ -1578,9 +1590,15 @@ static ssize_t comedi_write(struct fileint n, m, count =0 , retval =0 ;DECLARE_WAITQUEUE (wait, current);const unsigned minor =iminor (file->f_dentry->d_inode); -struct comedi_device_file_info *dev_file_info = -comedi_get_device_file_info (minor); -struct comedi_device *dev = dev_file_info->device; +struct comedi_device_file_info *dev_file_info; +struct comedi_device *dev; + dev_file_info =comedi_get_device_file_info (minor); + +if (dev_file_info ==NULL ) +return -ENODEV ; + dev = dev_file_info->device; +if (dev ==NULL ) +return -ENODEV ;if (!dev->attached) {DPRINTK ("no driver configured on comedi%i\n" , dev->minor);
@@ -1683,9 +1701,15 @@ static ssize_t comedi_read(struct file *int n, m, count =0 , retval =0 ;DECLARE_WAITQUEUE (wait, current);const unsigned minor =iminor (file->f_dentry->d_inode); -struct comedi_device_file_info *dev_file_info = -comedi_get_device_file_info (minor); -struct comedi_device *dev = dev_file_info->device; +struct comedi_device_file_info *dev_file_info; +struct comedi_device *dev; + dev_file_info =comedi_get_device_file_info (minor); + +if (dev_file_info ==NULL ) +return -ENODEV ; + dev = dev_file_info->device; +if (dev ==NULL ) +return -ENODEV ;if (!dev->attached) {DPRINTK ("no driver configured on comedi%i\n" , dev->minor);
@@ -1885,11 +1909,17 @@ ok:static int comedi_close (struct inode *inode,struct file *file) {const unsigned minor =iminor (inode); -struct comedi_device_file_info *dev_file_info = -comedi_get_device_file_info (minor); -struct comedi_device *dev = dev_file_info->device;struct comedi_subdevice *s =NULL ;int i; +struct comedi_device_file_info *dev_file_info; +struct comedi_device *dev; + dev_file_info =comedi_get_device_file_info (minor); + +if (dev_file_info ==NULL ) +return -ENODEV ; + dev = dev_file_info->device; +if (dev ==NULL ) +return -ENODEV ;mutex_lock (&dev->mutex);
@@ -1923,10 +1953,15 @@ static int comedi_close(struct inode *instatic int comedi_fasync (int fd,struct file *file,int on) {const unsigned minor =iminor (file->f_dentry->d_inode); -struct comedi_device_file_info *dev_file_info = -comedi_get_device_file_info (minor); - -struct comedi_device *dev = dev_file_info->device; +struct comedi_device_file_info *dev_file_info; +struct comedi_device *dev; + dev_file_info =comedi_get_device_file_info (minor); + +if (dev_file_info ==NULL ) +return -ENODEV ; + dev = dev_file_info->device; +if (dev ==NULL ) +return -ENODEV ;return fasync_helper (fd, file, on, &dev->async_queue); }
PATCH 66/104 Staging: comedi: fix mmap_count
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Federico Vaga <[email protected]>
commit df30b21cb0eed5ba8a8e0cdfeebc66ba8cde821d upstream.
In comedi_fops, mmap_count is decremented at comedi_vm_ops->close but it is not incremented at comedi_vm_ops->open. This may result in a negative counter. The patch introduces the open method to keep the counter consistent.
The bug was triggerd by this sample code:
mmap(0, ...., comedi_fd);
fork();
exit(0);--- drivers/staging/comedi/comedi_fops.c | 19 +++++++++++++++++-- 1 file changed, 17 insertions(+), 2 deletions(-)
drivers/staging/comedi/comedi_fops.c +17 -2
@@ -1432,7 +1432,21 @@ static int do_cancel(struct comedi_devicreturn ret; } -static void comedi_unmap (struct vm_area_struct *area) + +static void comedi_vm_open (struct vm_area_struct *area) +{ +struct comedi_async *async; +struct comedi_device *dev; + + async = area->vm_private_data; + dev = async->subdevice->device; + +mutex_lock (&dev->mutex); + async->mmap_count++; +mutex_unlock (&dev->mutex); +} + +static void comedi_vm_close (struct vm_area_struct *area) {struct comedi_async *async;struct comedi_device *dev;
@@ -1446,7 +1460,8 @@ static void comedi_unmap(struct vm_area_ }static struct vm_operations_struct comedi_vm_ops = { - .close = comedi_unmap, + .open = comedi_vm_open, + .close = comedi_vm_close, };static int comedi_mmap (struct file *file,struct vm_area_struct *vma)
PATCH 67/104 Staging: comedi: fix signal handling in read and write
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Federico Vaga <[email protected]>
commit 6a9ce6b654e491981f6ef7e214cbd4f63e033848 upstream.
After sleeping on a wait queue, signal_pending(current) should be checked (not before sleeping).
--- drivers/staging/comedi/comedi_fops.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/staging/comedi/comedi_fops.c +2 -2
@@ -1673,11 +1673,11 @@ static ssize_t comedi_write(struct file retval = -EAGAIN ;break ; } +schedule ();if (signal_pending (current)) { retval = -ERESTARTSYS ;break ; } -schedule ();if (!s->busy)break ;if (s->busy != file) {
@@ -1780,11 +1780,11 @@ static ssize_t comedi_read(struct file * retval = -EAGAIN ;break ; } +schedule ();if (signal_pending (current)) { retval = -ERESTARTSYS ;break ; } -schedule ();if (!s->busy) { retval =0 ;break ;
PATCH 68/104 usb: musb: PM: fix context save/restore in suspend/resume path
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kevin Hilman <[email protected]>
commit 5d193ce8f1fa7c67c7fd7be2c03ef31eed344a4f upstream.
Currently the driver tries to save context in the suspend path, but will cause an abort if the device is already runtime suspended. This happens, for example, if MUSB loaded/compiled-in, in host mode, but no USB devices are attached. MUSB will be runtime suspended, but then attempting a system suspend will crash due to the context save being attempted while the device is disabled.
On OMAP, as of v3.1, the driver's ->runtime_suspend() callback will be called late in the suspend path (by the PM domain layer) if the driver is not already runtime suspended, ensuring a full shutdown.
Therefore, the context save is not needed in the ->suspend() method since it will be called in the ->runtime_suspend() method anyways (similarily for resume.)
NOTE: this leaves the suspend/resume methods basically empty (with
some FIXMEs and comments, but I'll leave it to the maintainers to decide whether to remove them.
--- drivers/usb/musb/musb_core.c | 6 ------ 1 file changed, 6 deletions(-)
drivers/usb/musb/musb_core.c +0 -6
@@ -2302,18 +2302,12 @@ static int musb_suspend(struct device *d*/ } -musb_save_context (musb); -spin_unlock_irqrestore (&musb->lock, flags);return 0 ; }static int musb_resume_noirq (struct device *dev) { -struct musb *musb =dev_to_musb (dev); - -musb_restore_context (musb); -/* for static cmos like DaVinci, register values were preserved * unless for some reason the whole soc powered down or the USB * module got reset through the PSC (vs just being disabled).
PATCH 69/104 USB: whci-hcd: fix endian conversion in qset_clear()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 8746c83d538cab273d335acb2be226d096f4a5af upstream.
qset->qh.link is an __le64 field and we should be using cpu_to_le64() to fill it.
--- drivers/usb/host/whci/qset.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/host/whci/qset.c +1 -1
@@ -124,7 +124,7 @@ void qset_clear(struct whc *whc, struct { qset->td_start = qset->td_end = qset->ntds =0 ; - qset->qh.link =cpu_to_le32 (QH_LINK_NTDS (8 ) |QH_LINK_T ); + qset->qh.link =cpu_to_le64 (QH_LINK_NTDS (8 ) |QH_LINK_T ); qset->qh.status = qset->qh.status &QH_STATUS_SEQ_MASK ; qset->qh.err_count =0 ; qset->qh.scratch[0 ] =0 ;
PATCH 70/104 HID: Correct General touch PID
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Benjamin Tissoires <[email protected]>
commit b1807719f6acdf18cc4bde3b5400d05d77801494 upstream.
Genera Touch told us that 0001 is their single point device and 0003 is the multitouch one. Apparently, we made the tests someone having a prototype, and not the final product. They said it should be safe to do the switch.
This partially reverts 5572da0 ("HID: hid-mulitouch: add support for the 'Sensing Win7-TwoFinger'").
--- drivers/hid/hid-core.c | 2 +- drivers/hid/hid-ids.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
drivers/hid/hid-core.c +1 -1
@@ -1728,8 +1728,8 @@ static const struct hid_device_id hid_ig { HID_USB_DEVICE(USB_VENDOR_ID_ESSENTIAL_REALITY, USB_DEVICE_ID_ESSENTIAL_REALITY_P5) }, { HID_USB_DEVICE(USB_VENDOR_ID_ETT, USB_DEVICE_ID_TC5UH) }, { HID_USB_DEVICE(USB_VENDOR_ID_ETT, USB_DEVICE_ID_TC4UM) }, + { HID_USB_DEVICE(USB_VENDOR_ID_GENERAL_TOUCH, 0x0001) }, { HID_USB_DEVICE(USB_VENDOR_ID_GENERAL_TOUCH, 0x0002) }, - { HID_USB_DEVICE(USB_VENDOR_ID_GENERAL_TOUCH, 0x0003) }, { HID_USB_DEVICE(USB_VENDOR_ID_GENERAL_TOUCH, 0x0004) }, { HID_USB_DEVICE(USB_VENDOR_ID_GLAB, USB_DEVICE_ID_4_PHIDGETSERVO_30) }, { HID_USB_DEVICE(USB_VENDOR_ID_GLAB, USB_DEVICE_ID_1_PHIDGETSERVO_30) },
drivers/hid/hid-ids.h +1 -1
@@ -266,7 +266,7 @@#define USB_DEVICE_ID_GAMERON_DUAL_PCS_ADAPTOR 0x0002#define USB_VENDOR_ID_GENERAL_TOUCH 0x0dfc -#define USB_DEVICE_ID_GENERAL_TOUCH_WIN7_TWOFINGERS 0x0001 +#define USB_DEVICE_ID_GENERAL_TOUCH_WIN7_TWOFINGERS 0x0003#define USB_VENDOR_ID_GLAB 0x06c2#define USB_DEVICE_ID_4_PHIDGETSERVO_30 0x0038
PATCH 71/104 usb: ftdi_sio: add PID for Propox ISPcable III
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marcin Kościelnicki <[email protected]>
commit 307369b0ca06b27b511b61714e335ddfccf19c4f upstream.
--- drivers/usb/serial/ftdi_sio.c | 1 + drivers/usb/serial/ftdi_sio_ids.h | 1 + 2 files changed, 2 insertions(+)
drivers/usb/serial/ftdi_sio.c +1 -0
@@ -735,6 +735,7 @@ static struct usb_device_id id_table_com { USB_DEVICE(TML_VID, TML_USB_SERIAL_PID) }, { USB_DEVICE(FTDI_VID, FTDI_ELSTER_UNICOM_PID) }, { USB_DEVICE(FTDI_VID, FTDI_PROPOX_JTAGCABLEII_PID) }, + { USB_DEVICE(FTDI_VID, FTDI_PROPOX_ISPCABLEIII_PID) }, { USB_DEVICE(OLIMEX_VID, OLIMEX_ARM_USB_OCD_PID), .driver_info = (kernel_ulong_t)&ftdi_jtag_quirk }, { USB_DEVICE(OLIMEX_VID, OLIMEX_ARM_USB_OCD_H_PID),
drivers/usb/serial/ftdi_sio_ids.h +1 -0
@@ -112,6 +112,7 @@/* Propox devices */ #define FTDI_PROPOX_JTAGCABLEII_PID 0xD738 +#define FTDI_PROPOX_ISPCABLEIII_PID 0xD739/* Lenz LI-USB Computer Interface. */ #define FTDI_LENZ_LIUSB_PID 0xD780
PATCH 72/104 usb: option: add Huawei E353 controlling interfaces
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dirk Nehring <[email protected]>
commit 46b1848360c8e634e0b063932a1261062fa0f7d6 upstream.
This patch creates the missing controlling devices for the Huawei E353 HSPA+ stick.
--- drivers/usb/serial/option.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/usb/serial/option.c +3 -0
@@ -657,6 +657,9 @@ static const struct usb_device_id option { USB_DEVICE_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_K4511, 0xff, 0x01, 0x31) }, { USB_DEVICE_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_K4511, 0xff, 0x01, 0x32) }, { USB_DEVICE_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_E353, 0xff, 0x01, 0x01) }, + { USB_DEVICE_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_E353, 0xff, 0x01, 0x02) }, + { USB_DEVICE_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_E353, 0xff, 0x01, 0x03) }, + { USB_DEVICE_AND_INTERFACE_INFO(HUAWEI_VENDOR_ID, HUAWEI_PRODUCT_E353, 0xff, 0x01, 0x08) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V640) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V620) }, { USB_DEVICE(NOVATELWIRELESS_VENDOR_ID, NOVATELWIRELESS_PRODUCT_V740) },
PATCH 73/104 usb: option: add SIMCom SIM5218
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Veli-Pekka Peltola <[email protected]>
commit ec0cd94d881ca89cc9fb61d00d0f4b2b52e605b3 upstream.
Tested with SIM5218EVB-KIT evaluation kit.
--- drivers/usb/serial/option.c | 1 + 1 file changed, 1 insertion(+)
drivers/usb/serial/option.c +1 -0
@@ -746,6 +746,7 @@ static const struct usb_device_id option { USB_DEVICE(KYOCERA_VENDOR_ID, KYOCERA_PRODUCT_KPC680) }, { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x6000)}, /* ZTE AC8700 */ { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x6613)}, /* Onda H600/ZTE MF330 */ + { USB_DEVICE(QUALCOMM_VENDOR_ID, 0x9000)}, /* SIMCom SIM5218 */ { USB_DEVICE(CMOTECH_VENDOR_ID, CMOTECH_PRODUCT_6280) }, /* BP3-USB & BP3-EXT HSDPA */ { USB_DEVICE(CMOTECH_VENDOR_ID, CMOTECH_PRODUCT_6008) }, { USB_DEVICE(TELIT_VENDOR_ID, TELIT_PRODUCT_UC864E) },
PATCH 74/104 USB: usb-storage: unusual_devs entry for Kingston DT 101 G2
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Qinglin Ye <[email protected]>
commit cec28a5428793b6bc64e56687fb239759d6da74e upstream.
Kingston DT 101 G2 replies a wrong tag while transporting, add an unusal_devs entry to ignore the tag validation.
--- drivers/usb/storage/unusual_devs.h | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/usb/storage/unusual_devs.h +7 -0
@@ -1854,6 +1854,13 @@ UNUSUAL_DEV( 0x1370, 0x6828, 0x0110, 0x USB_SC_DEVICE, USB_PR_DEVICE, NULL, US_FL_IGNORE_RESIDUE ), +/* Reported by Qinglin Ye <[email protected]> */ +UNUSUAL_DEV (0x13fe ,0x3600 ,0x0100 ,0x0100 , +"Kingston" , +"DT 101 G2" , +USB_SC_DEVICE ,USB_PR_DEVICE ,NULL , +US_FL_BULK_IGNORE_TAG ), +/* Reported by Francesco Foresti <[email protected]> */ UNUSUAL_DEV( 0x14cd, 0x6600, 0x0201, 0x0201, "Super Top",
PATCH 75/104 IB: Fix RCU lockdep splats
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
commit 580da35a31f91a594f3090b7a2c39b85cb051a12 upstream.
Commit f2c31e32b37 ("net: fix NULL dereferences in check_peer_redir()") forgot to take care of infiniband uses of dst neighbours.
Many thanks to Marc Aurele who provided a nice bug report and feedback.
--- drivers/infiniband/core/addr.c | 9 ++++++--- drivers/infiniband/hw/cxgb3/iwch_cm.c | 4 ++++ drivers/infiniband/hw/cxgb4/cm.c | 4 ++++ drivers/infiniband/hw/mlx4/qp.c | 2 +- drivers/infiniband/hw/nes/nes_cm.c | 6 ++++-- drivers/infiniband/ulp/ipoib/ipoib_main.c | 18 +++++++++++------- drivers/infiniband/ulp/ipoib/ipoib_multicast.c | 6 ++++-- 7 files changed, 34 insertions(+), 15 deletions(-)
drivers/infiniband/core/addr.c +6 -3
@@ -215,7 +215,9 @@ static int addr4_resolve(struct sockaddr neigh =neigh_lookup (&arp_tbl, &rt->rt_gateway, rt->dst.dev);if (!neigh || !(neigh->nud_state &NUD_VALID )) { +rcu_read_lock ();neigh_event_send (dst_get_neighbour (&rt->dst),NULL ); +rcu_read_unlock (); ret = -ENODATA ;if (neigh) goto release;
@@ -273,15 +275,16 @@ static int addr6_resolve(struct sockaddr goto put; } +rcu_read_lock (); neigh =dst_get_neighbour (dst);if (!neigh || !(neigh->nud_state &NUD_VALID )) {if (neigh)neigh_event_send (neigh,NULL ); ret = -ENODATA ; - goto put; + }else { + ret =rdma_copy_addr (addr, dst->dev, neigh->ha); } - - ret =rdma_copy_addr (addr, dst->dev, neigh->ha); +rcu_read_unlock (); put:dst_release (dst);return ret;
drivers/infiniband/hw/cxgb3/iwch_cm.c +4 -0
@@ -1365,8 +1365,10 @@ static int pass_accept_req(struct t3cdev goto reject; } dst = &rt->dst; +rcu_read_lock (); neigh =dst_get_neighbour (dst); l2t =t3_l2t_get (tdev, neigh, neigh->dev); +rcu_read_unlock ();if (!l2t) { printk(KERN_ERR MOD "%s - failed to allocate l2t entry!\n", __func__);
@@ -1936,10 +1938,12 @@ int iwch_connect(struct iw_cm_id *cm_id, } ep->dst = &rt->dst; +rcu_read_lock (); neigh =dst_get_neighbour (ep->dst);/* get a l2t entry */ ep->l2t =t3_l2t_get (ep->com.tdev, neigh, neigh->dev); +rcu_read_unlock ();if (!ep->l2t) { printk(KERN_ERR MOD "%s - cannot alloc l2e.\n", __func__); err = -ENOMEM ;
drivers/infiniband/hw/cxgb4/cm.c +4 -0
@@ -1358,6 +1358,7 @@ static int pass_accept_req(struct c4iw_d goto reject; } dst = &rt->dst; +rcu_read_lock (); neigh =dst_get_neighbour (dst);if (neigh->dev->flags &IFF_LOOPBACK ) { pdev =ip_dev_find (&init_net, peer_ip);
@@ -1384,6 +1385,7 @@ static int pass_accept_req(struct c4iw_d rss_qid = dev->rdev.lldi.rxq_ids[cxgb4_port_idx (neigh->dev) * step]; } +rcu_read_unlock ();if (!l2t) { printk(KERN_ERR MOD "%s - failed to allocate l2t entry!\n", __func__);
@@ -1909,6 +1911,7 @@ int c4iw_connect(struct iw_cm_id *cm_id, } ep->dst = &rt->dst; +rcu_read_lock (); neigh =dst_get_neighbour (ep->dst);/* get a l2t entry */
@@ -1945,6 +1948,7 @@ int c4iw_connect(struct iw_cm_id *cm_id, ep->rss_qid = ep->com.dev->rdev.lldi.rxq_ids[cxgb4_port_idx (neigh->dev) * step]; } +rcu_read_unlock ();if (!ep->l2t) { printk(KERN_ERR MOD "%s - cannot alloc l2e.\n", __func__); err = -ENOMEM ;
drivers/infiniband/hw/mlx4/qp.c +1 -1
@@ -1309,7 +1309,7 @@ static int build_mlx_header(struct mlx4_int is_eth;int is_vlan =0 ;int is_grh; -u16 vlan; +u16 vlan =0 ; send_size =0 ;for (i =0 ; i < wr->num_sge; ++i)
drivers/infiniband/hw/nes/nes_cm.c +4 -2
@@ -1150,9 +1150,11 @@ static int nes_addr_resolve_neigh(structneigh_release (neigh); } -if ((neigh ==NULL ) || (!(neigh->nud_state &NUD_VALID ))) +if ((neigh ==NULL ) || (!(neigh->nud_state &NUD_VALID ))) { +rcu_read_lock ();neigh_event_send (dst_get_neighbour (&rt->dst),NULL ); - +rcu_read_unlock (); + }ip_rt_put (rt);return rc; }
drivers/infiniband/ulp/ipoib/ipoib_main.c +11 -7
@@ -555,6 +555,7 @@ static int path_rec_start(struct net_devreturn 0 ; } +/* called with rcu_read_lock */ static void neigh_add_path (struct sk_buff *skb,struct net_device *dev) {struct ipoib_dev_priv *priv =netdev_priv (dev);
@@ -636,6 +637,7 @@ err_drop:spin_unlock_irqrestore (&priv->lock, flags); } +/* called with rcu_read_lock */ static void ipoib_path_lookup (struct sk_buff *skb,struct net_device *dev) {struct ipoib_dev_priv *priv =netdev_priv (skb->dev);
@@ -720,13 +722,14 @@ static int ipoib_start_xmit(struct sk_bustruct neighbour *n =NULL ;unsigned long flags; +rcu_read_lock ();if (likely (skb_dst (skb))) n =dst_get_neighbour (skb_dst (skb));if (likely (n)) {if (unlikely (!*to_ipoib_neigh (n))) {ipoib_path_lookup (skb, dev); -return NETDEV_TX_OK ; + goto unlock; } neigh = *to_ipoib_neigh (n);
@@ -749,17 +752,17 @@ static int ipoib_start_xmit(struct sk_buipoib_neigh_free (dev, neigh);spin_unlock_irqrestore (&priv->lock, flags);ipoib_path_lookup (skb, dev); -return NETDEV_TX_OK ; + goto unlock; }if (ipoib_cm_get (neigh)) {if (ipoib_cm_up (neigh)) {ipoib_cm_send (dev, skb,ipoib_cm_get (neigh)); -return NETDEV_TX_OK ; + goto unlock; } }else if (neigh->ah) {ipoib_send (dev, skb, neigh->ah,IPOIB_QPN (n->ha)); -return NETDEV_TX_OK ; + goto unlock; }if (skb_queue_len (&neigh->queue) <IPOIB_MAX_PATH_REC_QUEUE ) {
@@ -793,13 +796,14 @@ static int ipoib_start_xmit(struct sk_bu phdr->hwaddr + 4);dev_kfree_skb_any (skb); ++dev->stats.tx_dropped; -return NETDEV_TX_OK ; + goto unlock; }unicast_arp_send (skb, dev, phdr); } } - +unlock: +rcu_read_unlock ();return NETDEV_TX_OK ; }
@@ -837,7 +841,7 @@ static int ipoib_hard_header(struct sk_b dst =skb_dst (skb); n =NULL ;if (dst) - n =dst_get_neighbour (dst); + n =dst_get_neighbour_raw (dst);if ((!dst || !n) && daddr) {struct ipoib_pseudoheader *phdr = (struct ipoib_pseudoheader *)skb_push (skb,sizeof *phdr);
drivers/infiniband/ulp/ipoib/ipoib_multicast.c +4 -2
@@ -265,7 +265,7 @@ static int ipoib_mcast_join_finish(struc skb->dev = dev;if (dst) - n =dst_get_neighbour (dst); + n =dst_get_neighbour_raw (dst);if (!dst || !n) {/* put pseudoheader back on for next time */ skb_push (skb,sizeof (struct ipoib_pseudoheader ));
@@ -721,6 +721,8 @@ out:if (mcast && mcast->ah) {struct dst_entry *dst =skb_dst (skb);struct neighbour *n =NULL ; + +rcu_read_lock ();if (dst) n =dst_get_neighbour (dst);if (n && !*to_ipoib_neigh (n)) {
@@ -733,7 +735,7 @@ out:list_add_tail (&neigh->list, &mcast->neigh_list); } } - +rcu_read_unlock ();spin_unlock_irqrestore (&priv->lock, flags);ipoib_send (dev, skb, mcast->ah,IB_MULTICAST_QPN );return ;
PATCH 76/104 USB: EHCI: fix HUB TT scheduling issue with iso transfer
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Poussevin <[email protected]>
commit 811c926c538f7e8d3c08b630dd5844efd7e000f6 upstream.
The current TT scheduling doesn't allow to play and then record on a full-speed device connected to a high speed hub.
The IN iso stream can only start on the first uframe (0-2 for a 165 us) because of CSPLIT transactions.
For the OUT iso stream there no such restriction. uframe 0-5 are possible.
The idea of this patch is that the first uframe are precious (for IN TT iso stream) and we should allocate the last uframes first if possible.
For that we reverse the order of uframe allocation (last uframe first).
Here an example :
hid interrupt stream
----------------------------------------------------------------------
uframe | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
----------------------------------------------------------------------max_tt_usecs | 125 | 125 | 125 | 125 | 125 | 125 | 30 | 0 |
----------------------------------------------------------------------
used usecs on a frame | 13 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
----------------------------------------------------------------------
iso OUT stream
----------------------------------------------------------------------
uframe | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
----------------------------------------------------------------------max_tt_usecs | 125 | 125 | 125 | 125 | 125 | 125 | 30 | 0 |
----------------------------------------------------------------------
used usecs on a frame | 13 | 125 | 39 | 0 | 0 | 0 | 0 | 0 |
----------------------------------------------------------------------
There no place for iso IN stream (uframe 0-2 are used) and we got "cannot submit datapipe for urb 0, error -28: not enough bandwidth" error.
With the patch this become.
iso OUT stream
----------------------------------------------------------------------
uframe | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
----------------------------------------------------------------------max_tt_usecs | 125 | 125 | 125 | 125 | 125 | 125 | 30 | 0 |
----------------------------------------------------------------------
used usecs on a frame | 13 | 0 | 0 | 0 | 125 | 39 | 0 | 0 |
----------------------------------------------------------------------
iso IN stream
----------------------------------------------------------------------
uframe | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 |
----------------------------------------------------------------------max_tt_usecs | 125 | 125 | 125 | 125 | 125 | 125 | 30 | 0 |
----------------------------------------------------------------------
used usecs on a frame | 13 | 0 | 125 | 40 | 125 | 39 | 0 | 0 |
----------------------------------------------------------------------
--- drivers/usb/host/ehci-sched.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)
drivers/usb/host/ehci-sched.c +10 -5
@@ -1480,10 +1480,15 @@ iso_stream_schedule (/* NOTE: assumes URB_ISO_ASAP, to limit complexity/bugs */ -/* find a uframe slot with enough bandwidth */ - next = start + period; -for (; start < next; start++) { - +/* find a uframe slot with enough bandwidth. +* Early uframes are more precious because full-speed +* iso IN transfers can't use late uframes, +* and therefore they should be allocated last. +*/ + next = start; + start += period; + do { + start--; /* check schedule: enough space? */ if (stream->highspeed) { if (itd_slot_ok(ehci, mod, start,
@@ -1496,7 +1501,7 @@ iso_stream_schedule ( start, sched, period))break ; } - } + }while (start > next);/* no room in the schedule */ if (start == next) {
PATCH 77/104 EHCI : Fix a regression in the ISO scheduler
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matthieu CASTET <[email protected]>
commit e3420901eba65b1c46bed86d360e3a8685d20734 upstream.
Fix a regression that was introduced by commit 811c926c538f7e8d3c08b630dd5844efd7e000f6 (USB: EHCI: fix HUB TT scheduling issue with iso transfer).
We detect an error if next == start, but this means uframe 0 can't be allocated anymore for iso transfer...
--- drivers/usb/host/ehci-sched.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-)
drivers/usb/host/ehci-sched.c +5 -4
@@ -1476,6 +1476,7 @@ iso_stream_schedule (* jump until after the queue is primed. */ else { +int done =0 ; start =SCHEDULE_SLOP + (now & ~0x07 );/* NOTE: assumes URB_ISO_ASAP, to limit complexity/bugs */
@@ -1493,18 +1494,18 @@ iso_stream_schedule (if (stream->highspeed) {if (itd_slot_ok (ehci, mod, start, stream->usecs, period)) -break ; + done =1 ; }else {if ((start %8 ) >=6 )continue ;if (sitd_slot_ok (ehci, mod, stream, start, sched, period)) -break ; + done =1 ; } - }while (start > next); + }while (start > next && !done);/* no room in the schedule */ -if (start == next) { +if (!done) {ehci_dbg (ehci,"iso resched full %p (now %d max %d)\n" , urb, now, now + mod); status = -ENOSPC ;
PATCH 78/104 xHCI: fix bug in xhci_clear_command_ring()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andiry Xu <[email protected]>
commit 158886cd2cf4599e04f9b7e10cb767f5f39b14f1 upstream.
When system enters suspend, xHCI driver clears command ring by writing zero to all the TRBs. However, this also writes zero to the Link TRB, and the ring is mangled. This may cause driver accesses wrong memory address and the result is unpredicted.
When clear the command ring, keep the last Link TRB intact, only clear its cycle bit. This should fix the "command ring full" issue reported by Oliver Neukum.
This should be backported to stable kernels as old as 2.6.37, since the commit 89821320 "xhci: Fix command ring replay after resume" is merged.
--- drivers/usb/host/xhci.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/usb/host/xhci.c +4 -1
@@ -657,7 +657,10 @@ static void xhci_clear_command_ring(stru ring = xhci->cmd_ring; seg = ring->deq_seg;do { -memset (seg->trbs,0 ,SEGMENT_SIZE ); +memset (seg->trbs,0 , +sizeof (union xhci_trb ) * (TRBS_PER_SEGMENT -1 )); + seg->trbs[TRBS_PER_SEGMENT -1 ].link.control &= +cpu_to_le32 (~TRB_CYCLE ); seg = seg->next; }while (seg != ring->deq_seg);
PATCH 79/104 sched, x86: Avoid unnecessary overflow in sched_clock
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Salman Qazi <[email protected]>
commit 4cecf6d401a01d054afc1e5f605bcbfe553cb9b9 upstream.
(Added the missing signed-off-by line)
In hundreds of days, the __cycles_2_ns calculation in sched_clock has an overflow. cyc * per_cpu(cyc2ns, cpu) exceeds 64 bits, causing the final value to become zero. We can solve this without losing any precision.
We can decompose TSC into quotient and remainder of division by the scale factor, and then use this to convert TSC into nanoseconds.
--- arch/x86/include/asm/timer.h | 23 ++++++++++++++++++++++- 1 file changed, 22 insertions(+), 1 deletion(-)
arch/x86/include/asm/timer.h +22 -1
@@ -32,6 +32,22 @@ extern int no_timer_check;* ([email protected]) * * [email protected] "math is hard, lets go shopping!" +* +* In: +* +* ns = cycles * cyc2ns_scale / SC +* +* Although we may still have enough bits to store the value of ns, +* in some cases, we may not have enough bits to store cycles * cyc2ns_scale, +* leading to an incorrect result. +* +* To avoid this, we can decompose 'cycles' into quotient and remainder +* of division by SC. Then, +* +* ns = (quot * SC + rem) * cyc2ns_scale / SC +* = quot * cyc2ns_scale + (rem * cyc2ns_scale) / SC +* +* - [email protected] */ DECLARE_PER_CPU(unsigned long, cyc2ns);
@@ -41,9 +57,14 @@ DECLARE_PER_CPU(unsigned long long, cyc2static inline unsigned long long __cycles_2_ns (unsigned long long cyc) { +unsigned long long quot; +unsigned long long rem;int cpu =smp_processor_id ();unsigned long long ns =per_cpu (cyc2ns_offset, cpu); - ns += cyc *per_cpu (cyc2ns, cpu) >>CYC2NS_SCALE_FACTOR ; + quot = (cyc >>CYC2NS_SCALE_FACTOR ); + rem = cyc & ((1ULL <<CYC2NS_SCALE_FACTOR ) -1 ); + ns += quot *per_cpu (cyc2ns, cpu) + + ((rem *per_cpu (cyc2ns, cpu)) >>CYC2NS_SCALE_FACTOR );return ns; }
PATCH 80/104 x86/mpparse: Account for bus types other than ISA and PCI
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Bjorn Helgaas <[email protected]>
commit 9e6866686bdf2dcf3aeb0838076237ede532dcc8 upstream.
In commit f8924e770e04 ("x86: unify mp_bus_info"), the 32-bit and 64-bit versions of MP_bus_info were rearranged to match each other better. Unfortunately it introduced a regression: prior to that change we used to always set the mp_bus_not_pci bit, then clear it if we found a PCI bus. After it, we set mp_bus_not_pci for ISA buses, clear it for PCI buses, and leave it alone otherwise.
In the cases of ISA and PCI, there's not much difference. But ISA is not the only non-PCI bus, so it's better to always set mp_bus_not_pci and clear it only for PCI.
Without this change, Dan's Dell PowerEdge 4200 panics on boot with a log indicating interrupt routing trouble unless the "noapic" option is supplied. With this change, the machine boots reliably without "noapic".
Fixes http://bugs.debian.org/586494
--- arch/x86/kernel/mpparse.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kernel/mpparse.c +1 -1
@@ -95,8 +95,8 @@ static void __init MP_bus_info(struct mp }#endif +set_bit (m->busid, mp_bus_not_pci);if (strncmp (str,BUSTYPE_ISA ,sizeof (BUSTYPE_ISA ) -1 ) ==0 ) { -set_bit (m->busid, mp_bus_not_pci);#if defined(CONFIG_EISA ) || defined(CONFIG_MCA ) mp_bus_id_to_type[m->busid] =MP_BUS_ISA ;#endif
PATCH 81/104 x86: Fix "Acer Aspire 1" reboot hang
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Chubb <[email protected]>
commit 1ef03890969932e9359b9a4c658f7f87771910ac upstream.
Looks like on some Acer Aspire 1s with older bioses, reboot via bios fails. It works on my machine, (with BIOS version 0.3310) but not on some others (BIOS version 0.3309).
There's a log of problems at:
https://bbs.archlinux.org/viewtopic.php?id=124136
This patch adds a different callback to the reboot quirk table, to allow rebooting via keybaord controller.
--- arch/x86/kernel/reboot.c | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-)
arch/x86/kernel/reboot.c +11 -2
@@ -124,7 +124,7 @@ __setup("reboot=", reboot_setup);*/ /* -* Some machines require the "reboot=b" commandline option, +* Some machines require the "reboot=b" or "reboot=k" commandline options, * this quirk makes that automatic. */ static int __init set_bios_reboot (const struct dmi_system_id *d)
@@ -136,6 +136,15 @@ static int __init set_bios_reboot(constreturn 0 ; } +static int __init set_kbd_reboot (const struct dmi_system_id *d) +{ +if (reboot_type !=BOOT_KBD ) { + reboot_type =BOOT_KBD ; +printk (KERN_INFO "%s series board detected. Selecting KBD-method for reboot.\n" , d->ident); + } +return 0 ; +} +static struct dmi_system_id __initdata reboot_dmi_table[] = { {/* Handle problems with rebooting on Dell E520's */ .callback = set_bios_reboot,
@@ -295,7 +304,7 @@ static struct dmi_system_id __initdata r }, }, {/* Handle reboot issue on Acer Aspire one */ - .callback = set_bios_reboot, + .callback = set_kbd_reboot, .ident = "Acer Aspire One A110", .matches = { DMI_MATCH(DMI_SYS_VENDOR, "Acer"),
PATCH 82/104 x86/paravirt: PTE updates in k(un)map_atomic need to be synchronous, regardless of lazy_mmu mode
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Konrad Rzeszutek Wilk <[email protected]>
commit 2cd1c8d4dc7ecca9e9431e2dabe41ae9c7d89e51 upstream.
Fix an outstanding issue that has been reported since 2.6.37. Under a heavy loaded machine processing "fork()" calls could crash with:
BUG: unable to handle kernel paging request at f573fc8c IP: [<c01abc54>] swap_count_continued+0x104/0x180 *pdpt = 000000002a3b9027 *pde = 0000000001bed067 *pte = 0000000000000000 Oops: 0000 [#1] SMP Modules linked in:
Pid: 1638, comm: apache2 Not tainted 3.0.4-linode37 #1
EIP: 0061:[<c01abc54>] EFLAGS: 00210246 CPU: 3 EIP is at swap_count_continued+0x104/0x180
.. snip..
Call Trace: [<c01ac222>] ? __swap_duplicate+0xc2/0x160 [<c01040f7>] ? pte_mfn_to_pfn+0x87/0xe0 [<c01ac2e4>] ? swap_duplicate+0x14/0x40 [<c01a0a6b>] ? copy_pte_range+0x45b/0x500 [<c01a0ca5>] ? copy_page_range+0x195/0x200 [<c01328c6>] ? dup_mmap+0x1c6/0x2c0 [<c0132cf8>] ? dup_mm+0xa8/0x130 [<c013376a>] ? copy_process+0x98a/0xb30 [<c013395f>] ? do_fork+0x4f/0x280 [<c01573b3>] ? getnstimeofday+0x43/0x100 [<c010f770>] ? sys_clone+0x30/0x40 [<c06c048d>] ? ptregs_clone+0x15/0x48 [<c06bfb71>] ? syscall_call+0x7/0xb
The problem is that in copy_page_range() we turn lazy mode on, and then in swap_entry_free() we call swap_count_continued() which ends up in:
map = kmap_atomic(page, KM_USER0) + offset;
and then later we touch *map.
Since we are running in batched mode (lazy) we don't actually set up the PTE mappings and the kmap_atomic is not done synchronously and ends up trying to dereference a page that has not been set.
Looking at kmap_atomic_prot_pfn(), it uses 'arch_flush_lazy_mmu_mode' and doing the same in kmap_atomic_prot() and __kunmap_atomic() makes the problem go away.
Interestingly, commit b8bcfe997e4615 ("x86/paravirt: remove lazy mode in interrupts") removed part of this to fix an interrupt issue - but it went to far and did not consider this scenario.
--- arch/x86/mm/highmem_32.c | 2 ++ 1 file changed, 2 insertions(+)
arch/x86/mm/highmem_32.c +2 -0
@@ -45,6 +45,7 @@ void *kmap_atomic_prot(struct page *page vaddr =__fix_to_virt (FIX_KMAP_BEGIN + idx);BUG_ON (!pte_none (*(kmap_pte-idx)));set_pte (kmap_pte-idx,mk_pte (page, prot)); +arch_flush_lazy_mmu_mode ();return (void *)vaddr; }
@@ -88,6 +89,7 @@ void __kunmap_atomic(void *kvaddr)*/ kpte_clear_flush (kmap_pte-idx, vaddr);kmap_atomic_idx_pop (); +arch_flush_lazy_mmu_mode (); }#ifdef CONFIG_DEBUG_HIGHMEM else {
PATCH 83/104 perf/x86: Fix PEBS instruction unwind
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Zijlstra <[email protected]>
commit 57d1c0c03c6b48b2b96870d831b9ce6b917f53ac upstream.
Masami spotted that we always try to decode the instruction stream as 64bit instructions when running a 64bit kernel, this doesn't work for ia32-compat proglets.
Use TIF_IA32 to detect if we need to use the 32bit instruction decoder.
--- arch/x86/kernel/cpu/perf_event_intel_ds.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
arch/x86/kernel/cpu/perf_event_intel_ds.c +5 -1
@@ -508,6 +508,7 @@ static int intel_pmu_pebs_fixup_ip(strucunsigned long from = cpuc->lbr_entries[0 ].from;unsigned long old_to, to = cpuc->lbr_entries[0 ].to;unsigned long ip = regs->ip; +int is_64bit =0 ;/* * We don't need to fixup if the PEBS assist is fault like
@@ -559,7 +560,10 @@ static int intel_pmu_pebs_fixup_ip(struc }else kaddr = (void *)to; -kernel_insn_init (&insn, kaddr); +#ifdef CONFIG_X86_64 + is_64bit =kernel_ip (to) || !test_thread_flag (TIF_IA32 ); +#endif +insn_init (&insn, kaddr, is_64bit);insn_get_length (&insn); to += insn.length; }while (to < ip);
PATCH 84/104 oprofile, x86: Fix crash when unloading module (nmi timer mode)
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Robert Richter <[email protected]>
commit 97f7f8189fe54e3cfe324ef9ad35064f3d2d3bff upstream.
If oprofile uses the nmi timer interrupt there is a crash while unloading the module. The bug can be triggered with oprofile build as module and kernel parameter nolapic set. This patch fixes this.
oprofile: using NMI timer interrupt.
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 IP: [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58 PGD 42dbca067 PUD 41da6a067 PMD 0 Oops: 0002 [#1] PREEMPT SMP CPU 5 Modules linked in: oprofile(-) [last unloaded: oprofile]
Pid: 2518, comm: modprobe Not tainted 3.1.0-rc7-00019-gb2fb49d #19 Advanced Micro Device Anaheim/Anaheim
RIP: 0010:[<ffffffff8123c226>] [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58 RSP: 0018:ffff88041ef71e98 EFLAGS: 00010296 RAX: 0000000000000000 RBX: ffffffffa0017100 RCX: dead000000200200 RDX: 0000000000000000 RSI: dead000000100100 RDI: ffffffff8178c620 RBP: ffff88041ef71ea8 R08: 0000000000000001 R09: 0000000000000082 R10: 0000000000000000 R11: ffff88041ef71de8 R12: 0000000000000080 R13: fffffffffffffff5 R14: 0000000000000001 R15: 0000000000610210 FS: 00007fc902f20700(0000) GS:ffff88042fd40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000008 CR3: 000000041cdb6000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process modprobe (pid: 2518, threadinfo ffff88041ef70000, task ffff88041d348040) Stack: ffff88041ef71eb8 ffffffffa0017790 ffff88041ef71eb8 ffffffffa0013532 ffff88041ef71ec8 ffffffffa00132d6 ffff88041ef71ed8 ffffffffa00159b2 ffff88041ef71f78 ffffffff81073115 656c69666f72706f 0000000000610200 Call Trace: [<ffffffffa0013532>] op_nmi_exit+0x15/0x17 [oprofile] [<ffffffffa00132d6>] oprofile_arch_exit+0xe/0x10 [oprofile] [<ffffffffa00159b2>] oprofile_exit+0x1e/0x20 [oprofile] [<ffffffff81073115>] sys_delete_module+0x1c3/0x22f [<ffffffff811bf09e>] ? trace_hardirqs_on_thunk+0x3a/0x3f [<ffffffff8148070b>] system_call_fastpath+0x16/0x1b Code: 20 c6 78 81 e8 c5 cc 23 00 48 8b 13 48 8b 43 08 48 be 00 01 10 00 00 00 ad de 48 b9 00 02 20 00 00 00 ad de 48 c7 c7 20 c6 78 81 89 42 08 48 89 10 48 89 33 48 89 4b 08 e8 a6 c0 23 00 5a 5b RIP [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58 RSP <ffff88041ef71e98> CR2: 0000000000000008 ---[ end trace 43a541a52956b7b0 ]---
--- arch/x86/oprofile/init.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
arch/x86/oprofile/init.c +5 -2
@@ -21,6 +21,7 @@ extern int op_nmi_timer_init(struct oproextern void op_nmi_exit (void );extern void x86_backtrace (struct pt_regs *const regs,unsigned int depth); +static int nmi_timer;int __init oprofile_arch_init (struct oprofile_operations *ops) {
@@ -31,8 +32,9 @@ int __init oprofile_arch_init(struct opr#ifdef CONFIG_X86_LOCAL_APIC ret =op_nmi_init (ops);#endif + nmi_timer = (ret !=0 );#ifdef CONFIG_X86_IO_APIC -if (ret <0 ) +if (nmi_timer) ret =op_nmi_timer_init (ops);#endif ops->backtrace = x86_backtrace;
@@ -44,6 +46,7 @@ int __init oprofile_arch_init(struct oprvoid oprofile_arch_exit (void ) {#ifdef CONFIG_X86_LOCAL_APIC -op_nmi_exit (); +if (!nmi_timer) +op_nmi_exit ();#endif }
PATCH 85/104 add missing .set function for NT_S390_LAST_BREAK regset
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Martin Schwidefsky <[email protected]>
commit b934069c991355d27a053a932591c77960f4e414 upstream.
The last breaking event address is a read-only value, the regset misses the .set function. If a PTRACE_SETREGSET is done for NT_S390_LAST_BREAK we get an oops due to a branch to zero:
Kernel BUG at 0000000000000002 verbose debug info unavailable illegal operation: 0001 #1 SMP ... Call Trace: (<0000000000158294> ptrace_regset+0x184/0x188) <00000000001595b6> ptrace_request+0x37a/0x4fc <0000000000109a78> arch_ptrace+0x108/0x1fc <00000000001590d6> SyS_ptrace+0xaa/0x12c <00000000005c7a42> sysc_noemu+0x16/0x1c <000003fffd5ec10c> 0x3fffd5ec10c
Last Breaking-Event-Address:
<0000000000158242> ptrace_regset+0x132/0x188
Add a nop .set function to prevent the branch to zero.
--- arch/s390/kernel/ptrace.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
arch/s390/kernel/ptrace.c +18 -0
@@ -897,6 +897,14 @@ static int s390_last_break_get(struct tareturn 0 ; } +static int s390_last_break_set (struct task_struct *target, +const struct user_regset *regset, +unsigned int pos,unsigned int count, +const void *kbuf,const void __user *ubuf) +{ +return 0 ; +} +#endif static const struct user_regset s390_regsets[] = {
@@ -923,6 +931,7 @@ static const struct user_regset s390_reg .size = sizeof(long), .align = sizeof(long), .get = s390_last_break_get, + .set = s390_last_break_set, },#endif };
@@ -1080,6 +1089,14 @@ static int s390_compat_last_break_get(streturn 0 ; } +static int s390_compat_last_break_set (struct task_struct *target, +const struct user_regset *regset, +unsigned int pos,unsigned int count, +const void *kbuf,const void __user *ubuf) +{ +return 0 ; +} +static const struct user_regset s390_compat_regsets[] = { [REGSET_GENERAL ] = { .core_note_type =NT_PRSTATUS ,
@@ -1103,6 +1120,7 @@ static const struct user_regset s390_com .size = sizeof(long), .align = sizeof(long), .get = s390_compat_last_break_get, + .set = s390_compat_last_break_set, }, [REGSET_GENERAL_EXTENDED] = { .core_note_type = NT_S390_HIGH_GPRS,
PATCH 86/104 mac80211: fill rate filter for internal scan requests
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Simon Wunderlich <[email protected]>
commit c72e8d335e2c6a309b6281f2abcf491f37b8b92b upstream.
The rates bitmap for internal scan requests shoud be filled, otherwise there will be probe requests with zero rates supported.
--- net/mac80211/main.c | 6 ++++++ 1 file changed, 6 insertions(+)
net/mac80211/main.c +6 -0
@@ -742,6 +742,12 @@ int ieee80211_register_hw(struct ieee802if (!local->int_scan_req)return -ENOMEM ; +for (band =0 ; band <IEEE80211_NUM_BANDS ; band++) { +if (!local->hw.wiphy->bands[band]) +continue ; + local->int_scan_req->rates[band] = (u32) -1 ; + } +/* if low-level driver supports AP, we also support VLAN */ if (local->hw.wiphy->interface_modes &BIT (NL80211_IFTYPE_AP )) { hw->wiphy->interface_modes |=BIT (NL80211_IFTYPE_AP_VLAN );
PATCH 87/104 mac80211: fix race condition caused by late addBA response
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nikolay Martynov <[email protected]>
Upstream commit d305a6557b2c4dca0110f05ffe745b1ef94adb80.
If addBA responses comes in just after addba_resp_timer has expired mac80211 will still accept it and try to open the aggregation session. This causes drivers to be confused and in some cases even crash.
This patch fixes the race condition and makes sure that if addba_resp_timer has expired addBA response is not longer accepted and we do not try to open half-closed session.
--- net/mac80211/agg-tx.c | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-)
net/mac80211/agg-tx.c +16 -1
@@ -792,12 +792,27 @@ void ieee80211_process_addba_resp(struct goto out; } -del_timer (&tid_tx->addba_resp_timer); +del_timer_sync (&tid_tx->addba_resp_timer);#ifdef CONFIG_MAC80211_HT_DEBUG printk (KERN_DEBUG "switched off addBA timer for tid %d\n" , tid);#endif +/* +* addba_resp_timer may have fired before we got here, and +* caused WANT_STOP to be set. If the stop then was already +* processed further, STOPPING might be set. +*/ +if (test_bit (HT_AGG_STATE_WANT_STOP , &tid_tx->state) || +test_bit (HT_AGG_STATE_STOPPING , &tid_tx->state)) { +#ifdef CONFIG_MAC80211_HT_DEBUG +printk (KERN_DEBUG +"got addBA resp for tid %d but we already gave up\n" , + tid); +#endif + goto out; + } +if (le16_to_cpu (mgmt->u.action.u.addba_resp.status) ==WLAN_STATUS_SUCCESS ) {/*
PATCH 88/104 cfg80211: fix race on init and driver registration
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Luis R. Rodriguez" <[email protected]>
commit a042994dd377d86bff9446ee76151ceb6267c9ba upstream.
There is a theoretical race that if hit will trigger a crash. The race is between when we issue the first regulatory hint, regulatory_hint_core(), gets processed by the workqueue and between when the first device gets registered to the wireless core. This is not easy to reproduce but it was easy to do so through the regulatory simulator I have been working on. This is a port of the fix I implemented there [1].
[1] https://github.com/mcgrof/regsim/commit/a246ccf81f059cb662eee288aa13100f631e4cc8
--- net/wireless/reg.c | 43 +++++++++++++++++++++++++++---------------- 1 file changed, 27 insertions(+), 16 deletions(-)
net/wireless/reg.c +27 -16
@@ -57,8 +57,17 @@ #define REG_DBG_PRINT(args...)#endif +static struct regulatory_request core_request_world = { + .initiator =NL80211_REGDOM_SET_BY_CORE , + .alpha2[0 ] ='0' , + .alpha2[1 ] ='0' , + .intersect = false, + .processed = true, + .country_ie_env =ENVIRON_ANY , +}; +/* Receipt of information from last regulatory request */ -static struct regulatory_request *last_request; +static struct regulatory_request *last_request = &core_request_world;/* To trigger userspace events */ static struct platform_device *reg_pdev;
@@ -150,7 +159,7 @@ static char user_alpha2[2];module_param (ieee80211_regdom, charp,0444 );MODULE_PARM_DESC (ieee80211_regdom,"IEEE 802.11 regulatory domain code" ); -static void reset_regdomains (void ) +static void reset_regdomains (bool full_reset) {/* avoid freeing static information or freeing something twice */ if (cfg80211_regdomain == cfg80211_world_regdom)
@@ -165,6 +174,13 @@ static void reset_regdomains(void) cfg80211_world_regdom = &world_regdom; cfg80211_regdomain =NULL ; + +if (!full_reset) +return ; + +if (last_request != &core_request_world) +kfree (last_request); + last_request = &core_request_world; }/*
@@ -175,7 +191,7 @@ static void update_world_regdomain(const {BUG_ON (!last_request); -reset_regdomains (); +reset_regdomains (false); cfg80211_world_regdom = rd; cfg80211_regdomain = rd;
@@ -1396,7 +1412,8 @@ static int __regulatory_hint(struct wiph } new_request: -kfree (last_request); +if (last_request != &core_request_world) +kfree (last_request); last_request = pending_request; last_request->intersect = intersect;
@@ -1566,9 +1583,6 @@ static int regulatory_hint_core(const ch {struct regulatory_request *request; -kfree (last_request); - last_request =NULL ; - request =kzalloc (sizeof (struct regulatory_request ),GFP_KERNEL );if (!request)
@@ -1766,7 +1780,7 @@ static void restore_regulatory_settings(mutex_lock (&cfg80211_mutex);mutex_lock (®_mutex); -reset_regdomains (); +reset_regdomains (true);restore_alpha2 (alpha2, reset_user);/*
@@ -2035,7 +2049,7 @@ static int __set_regdom(const struct ieeint r;if (last_request->initiator !=NL80211_REGDOM_SET_BY_DRIVER ) { -reset_regdomains (); +reset_regdomains (false); cfg80211_regdomain = rd;return 0 ; }
@@ -2056,7 +2070,7 @@ static int __set_regdom(const struct ieeif (r)return r; -reset_regdomains (); +reset_regdomains (false); cfg80211_regdomain = rd;return 0 ; }
@@ -2081,7 +2095,7 @@ static int __set_regdom(const struct iee rd =NULL ; -reset_regdomains (); +reset_regdomains (false); cfg80211_regdomain = intersected_rd;return 0 ;
@@ -2101,7 +2115,7 @@ static int __set_regdom(const struct ieekfree (rd); rd =NULL ; -reset_regdomains (); +reset_regdomains (false); cfg80211_regdomain = intersected_rd;return 0 ;
@@ -2254,11 +2268,8 @@ void /* __init_or_exit */ regulatory_eximutex_lock (&cfg80211_mutex);mutex_lock (®_mutex); -reset_regdomains (); - -kfree (last_request); +reset_regdomains (true); - last_request =NULL ;dev_set_uevent_suppress (®_pdev->dev, true);platform_device_unregister (reg_pdev);
PATCH 89/104 cfg80211: amend regulatory NULL dereference fix
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Luis R. Rodriguez" <[email protected]>
commit 0bac71af6e66dc798bf07d0c0dd14ee5503362f9 upstream.
Johannes' patch for "cfg80211: fix regulatory NULL dereference" broke user regulaotry hints and it did not address the fact that last_request was left populated even if the previous regulatory hint was stale due to the wiphy disappearing.
Fix user reguluatory hints by only bailing out if for those regulatory hints where a request_wiphy is expected. The stale last_request considerations are addressed through the previous fixes on last_request where we reset the last_request to a static world regdom request upon reset_regdomains(). In this case though we further enhance the effect by simply restoring reguluatory settings completely.
--- net/wireless/reg.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
net/wireless/reg.c +4 -2
@@ -2040,8 +2040,10 @@ static int __set_regdom(const struct iee } request_wiphy =wiphy_idx_to_wiphy (last_request->wiphy_idx); -if (!request_wiphy) { -reg_set_request_processed (); +if (!request_wiphy && + (last_request->initiator ==NL80211_REGDOM_SET_BY_DRIVER || + last_request->initiator ==NL80211_REGDOM_SET_BY_COUNTRY_IE )) { +schedule_delayed_work (®_timeout,0 );return -ENODEV ; }
PATCH 90/104 genirq: Fix race condition when stopping the irq thread
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ido Yariv <[email protected]>
commit 550acb19269d65f32e9ac4ddb26c2b2070e37f1c upstream.
In irq_wait_for_interrupt(), the should_stop member is verified before setting the task's state to TASK_INTERRUPTIBLE and calling schedule(). In case kthread_stop sets should_stop and wakes up the process after should_stop is checked by the irq thread but before the task's state is changed, the irq thread might never exit:
kthread_stop irq_wait_for_interrupt
------------ ----------------------
...
... while (!kthread_should_stop()) {kthread->should_stop = 1;wake_up_process(k);wait_for_completion(&kthread->exited);
...
set_current_state(TASK_INTERRUPTIBLE);
...
schedule();
}Fix this by checking if the thread should stop after modifying the task's state.
[ tglx: Simplified it a bit ]
--- kernel/irq/manage.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
kernel/irq/manage.c +4 -1
@@ -620,8 +620,9 @@ static irqreturn_t irq_nested_primary_hastatic int irq_wait_for_interrupt (struct irqaction *action) { +set_current_state (TASK_INTERRUPTIBLE ); +while (!kthread_should_stop ()) { -set_current_state (TASK_INTERRUPTIBLE );if (test_and_clear_bit (IRQTF_RUNTHREAD , &action->thread_flags)) {
@@ -629,7 +630,9 @@ static int irq_wait_for_interrupt(structreturn 0 ; }schedule (); +set_current_state (TASK_INTERRUPTIBLE ); } +__set_current_state (TASK_RUNNING );return -1 ; }
PATCH 91/104 slab, lockdep: Fix silly bug
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Zijlstra <[email protected]>
commit 52cef189165d74a5d6030184a8e05595194c69ca upstream.
Commit 30765b92 ("slab, lockdep: Annotate the locks before using them") moves the init_lock_keys() call from after g_cpucache_up = FULL, to before it. And overlooks the fact that init_node_lock_keys() tests for it and ignores everything !FULL.
Introduce a LATE stage and change the lockdep test to be <LATE.
--- mm/slab.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
mm/slab.c +4 -1
@@ -595,6 +595,7 @@ static enum {PARTIAL_AC ,PARTIAL_L3 ,EARLY , +LATE , FULL } g_cpucache_up;
@@ -671,7 +672,7 @@ static void init_node_lock_keys(int q) {struct cache_sizes *s = malloc_sizes; -if (g_cpucache_up !=FULL ) +if (g_cpucache_up <LATE )return ;for (s = malloc_sizes; s->cs_size !=ULONG_MAX ; s++) {
@@ -1666,6 +1667,8 @@ void __init kmem_cache_init_late(void) {struct kmem_cache *cachep; + g_cpucache_up =LATE ; +/* Annotate slab for lockdep -- annotate the malloc caches */ init_lock_keys ();
PATCH 92/104 iwlwifi: do not re-configure HT40 after associated
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wey-Yi Guy <[email protected]>
commit 34a5b4b6af104cf18eb50748509528b9bdbc4036 upstream.
The ht40 setting should not change after association unless channel switch
This fix a problem we are seeing which cause uCode assert because driver sending invalid information and make uCode confuse
Here is the firmware assert message:
kernel: iwlagn 0000:03:00.0: Microcode SW error detected. Restarting 0x82000000.
kernel: iwlagn 0000:03:00.0: Loaded firmware version: 17.168.5.3 build 42301
kernel: iwlagn 0000:03:00.0: Start IWL Error Log Dump:
kernel: iwlagn 0000:03:00.0: Status: 0x000512E4, count: 6
kernel: iwlagn 0000:03:00.0: 0x00002078 | ADVANCED_SYSASSERT
kernel: iwlagn 0000:03:00.0: 0x00009514 | uPc
kernel: iwlagn 0000:03:00.0: 0x00009496 | branchlink1
kernel: iwlagn 0000:03:00.0: 0x00009496 | branchlink2
kernel: iwlagn 0000:03:00.0: 0x0000D1F2 | interruptlink1
kernel: iwlagn 0000:03:00.0: 0x00000000 | interruptlink2
kernel: iwlagn 0000:03:00.0: 0x01008035 | data1
kernel: iwlagn 0000:03:00.0: 0x0000C90F | data2
kernel: iwlagn 0000:03:00.0: 0x000005A7 | line
kernel: iwlagn 0000:03:00.0: 0x5080B520 | beacon time
kernel: iwlagn 0000:03:00.0: 0xCC515AE0 | tsf low
kernel: iwlagn 0000:03:00.0: 0x00000003 | tsf hi
kernel: iwlagn 0000:03:00.0: 0x00000000 | time gp1
kernel: iwlagn 0000:03:00.0: 0x29703BF0 | time gp2
kernel: iwlagn 0000:03:00.0: 0x00000000 | time gp3
kernel: iwlagn 0000:03:00.0: 0x000111A8 | uCode version
kernel: iwlagn 0000:03:00.0: 0x000000B0 | hw version
kernel: iwlagn 0000:03:00.0: 0x00480303 | board version
kernel: iwlagn 0000:03:00.0: 0x09E8004E | hcmd
kernel: iwlagn 0000:03:00.0: CSR values:
kernel: iwlagn 0000:03:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
kernel: iwlagn 0000:03:00.0: CSR_HW_IF_CONFIG_REG: 0X00480303
kernel: iwlagn 0000:03:00.0: CSR_INT_COALESCING: 0X0000ff40
kernel: iwlagn 0000:03:00.0: CSR_INT: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_INT_MASK: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_FH_INT_STATUS: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_GPIO_IN: 0X00000030
kernel: iwlagn 0000:03:00.0: CSR_RESET: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_GP_CNTRL: 0X080403c5
kernel: iwlagn 0000:03:00.0: CSR_HW_REV: 0X000000b0
kernel: iwlagn 0000:03:00.0: CSR_EEPROM_REG: 0X07d60ffd
kernel: iwlagn 0000:03:00.0: CSR_EEPROM_GP: 0X90000001
kernel: iwlagn 0000:03:00.0: CSR_OTP_GP_REG: 0X00030001
kernel: iwlagn 0000:03:00.0: CSR_GIO_REG: 0X00080044
kernel: iwlagn 0000:03:00.0: CSR_GP_UCODE_REG: 0X000093bb
kernel: iwlagn 0000:03:00.0: CSR_GP_DRIVER_REG: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP1: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_UCODE_DRV_GP2: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_LED_REG: 0X00000078
kernel: iwlagn 0000:03:00.0: CSR_DRAM_INT_TBL_REG: 0X88214dd2
kernel: iwlagn 0000:03:00.0: CSR_GIO_CHICKEN_BITS: 0X27800200
kernel: iwlagn 0000:03:00.0: CSR_ANA_PLL_CFG: 0X00000000
kernel: iwlagn 0000:03:00.0: CSR_HW_REV_WA_REG: 0X0001001a
kernel: iwlagn 0000:03:00.0: CSR_DBG_HPET_MEM_REG: 0Xffff0010
kernel: iwlagn 0000:03:00.0: FH register values:
kernel: iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X21316d00
kernel: iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X021479c0
kernel: iwlagn 0000:03:00.0: FH_RSCSR_CHNL0_WPTR: 0X00000060
kernel: iwlagn 0000:03:00.0: FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X80819104
kernel: iwlagn 0000:03:00.0: FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
kernel: iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_STATUS_REG: 0X07030000
kernel: iwlagn 0000:03:00.0: FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
kernel: iwlagn 0000:03:00.0: FH_TSSR_TX_STATUS_REG: 0X07ff0001
kernel: iwlagn 0000:03:00.0: FH_TSSR_TX_ERROR_REG: 0X00000000
kernel: iwlagn 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
kernel: ------------[ cut here ]------------
WARNING: at net/mac80211/util.c:1208 ieee80211_reconfig+0x1f1/0x407() kernel: Hardware name: 4290W4H kernel: Pid: 1896, comm: kworker/0:0 Not tainted 3.1.0 #2 kernel: Call Trace: kernel: [<ffffffff81036558>] ? warn_slowpath_common+0x73/0x87 kernel: [<ffffffff813b8966>] ? ieee80211_reconfig+0x1f1/0x407 kernel: [<ffffffff8139e8dc>] ? ieee80211_recalc_smps_work+0x32/0x32 kernel: [<ffffffff8139e95a>] ? ieee80211_restart_work+0x7e/0x87 kernel: [<ffffffff810472fa>] ? process_one_work+0x1c8/0x2e3 kernel: [<ffffffff810480c9>] ? worker_thread+0x17a/0x23a kernel: [<ffffffff81047f4f>] ? manage_workers.clone.18+0x15b/0x15b kernel: [<ffffffff81047f4f>] ? manage_workers.clone.18+0x15b/0x15b kernel: [<ffffffff8104ba97>] ? kthread+0x7a/0x82 kernel: [<ffffffff813d21b4>] ? kernel_thread_helper+0x4/0x10 kernel: [<ffffffff8104ba1d>] ? kthread_flush_work_fn+0x11/0x11 kernel: [<ffffffff813d21b0>] ? gs_change+0xb/0xb
--- drivers/net/wireless/iwlwifi/iwl-agn-rxon.c | 36 +++++++++++++++++----------- drivers/net/wireless/iwlwifi/iwl-agn.c | 18 ++------------ drivers/net/wireless/iwlwifi/iwl-agn.h | 2 + 3 files changed, 28 insertions(+), 28 deletions(-)
drivers/net/wireless/iwlwifi/iwl-agn-rxon.c +23 -13
@@ -542,6 +542,24 @@ int iwlagn_commit_rxon(struct iwl_priv *return 0 ; } +void iwlagn_config_ht40 (struct ieee80211_conf *conf, +struct iwl_rxon_context *ctx) +{ +if (conf_is_ht40_minus (conf)) { + ctx->ht.extension_chan_offset = +IEEE80211_HT_PARAM_CHA_SEC_BELOW ; + ctx->ht.is_40mhz = true; + }else if (conf_is_ht40_plus (conf)) { + ctx->ht.extension_chan_offset = +IEEE80211_HT_PARAM_CHA_SEC_ABOVE ; + ctx->ht.is_40mhz = true; + }else { + ctx->ht.extension_chan_offset = +IEEE80211_HT_PARAM_CHA_SEC_NONE ; + ctx->ht.is_40mhz = false; + } +} +int iwlagn_mac_config (struct ieee80211_hw *hw,u32 changed) {struct iwl_priv *priv = hw->priv;
@@ -600,19 +618,11 @@ int iwlagn_mac_config(struct ieee80211_h ctx->ht.enabled =conf_is_ht (conf);if (ctx->ht.enabled) { -if (conf_is_ht40_minus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_BELOW ; - ctx->ht.is_40mhz = true; - }else if (conf_is_ht40_plus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_ABOVE ; - ctx->ht.is_40mhz = true; - }else { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_NONE ; - ctx->ht.is_40mhz = false; - } +/* if HT40 is used, it should not change +* after associated except channel switch */ +if (iwl_is_associated_ctx (ctx) && + !ctx->ht.is_40mhz) +iwlagn_config_ht40 (conf, ctx); }else ctx->ht.is_40mhz = false;
drivers/net/wireless/iwlwifi/iwl-agn.c +3 -15
@@ -3075,21 +3075,9 @@ static void iwlagn_mac_channel_switch(st/* Configure HT40 channels */ ctx->ht.enabled =conf_is_ht (conf); -if (ctx->ht.enabled) { -if (conf_is_ht40_minus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_BELOW ; - ctx->ht.is_40mhz = true; - }else if (conf_is_ht40_plus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_ABOVE ; - ctx->ht.is_40mhz = true; - }else { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_NONE ; - ctx->ht.is_40mhz = false; - } - }else +if (ctx->ht.enabled) +iwlagn_config_ht40 (conf, ctx); +else ctx->ht.is_40mhz = false;if ((le16_to_cpu (ctx->staging.channel) != ch))
drivers/net/wireless/iwlwifi/iwl-agn.h +2 -0
@@ -135,6 +135,8 @@ void iwlagn_bss_info_changed(struct ieeestruct ieee80211_vif *vif, struct ieee80211_bss_conf *bss_conf, u32 changes); +void iwlagn_config_ht40 (struct ieee80211_conf *conf, +struct iwl_rxon_context *ctx);/* uCode */ void iwlagn_rx_calib_result(struct iwl_priv *priv,
Re: [092/104] iwlwifi: do not re-configure HT40 after associated
Hi Greg,
Just found out this might also needed for 3.0.
I am not sure it will apply, should I submit separated patch?
Thanks
Wey
Quoted 194 lines · Greg KH
3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wey-Yi Guy <[email protected]>
commit
34a5b4b6af104cf18eb50748509528b9bdbc4036upstream.The ht40 setting should not change after association unless channel switch
This fix a problem we are seeing which cause uCode assert because driver sending invalid information and make uCode confuse
Here is the firmware assert message:
kernel: iwlagn 0000:03:00.0: Microcode SW error detected. Restarting0x82000000.
kernel: iwlagn 0000:03:00.0: Loaded firmware version: 17.168.5.3 build 42301
kernel: iwlagn 0000:03:00.0: Start IWL Error Log Dump:
kernel: iwlagn 0000:03:00.0: Status:0x000512E4, count: 6
kernel: iwlagn 0000:03:00.0:0x00002078|ADVANCED_SYSASSERT
kernel: iwlagn 0000:03:00.0:0x00009514| uPc
kernel: iwlagn 0000:03:00.0:0x00009496| branchlink1
kernel: iwlagn 0000:03:00.0:0x00009496| branchlink2
kernel: iwlagn 0000:03:00.0:0x0000D1F2| interruptlink1
kernel: iwlagn 0000:03:00.0:0x00000000| interruptlink2
kernel: iwlagn 0000:03:00.0:0x01008035| data1
kernel: iwlagn 0000:03:00.0:0x0000C90F| data2
kernel: iwlagn 0000:03:00.0:0x000005A7| line
kernel: iwlagn 0000:03:00.0:0x5080B520| beacon time
kernel: iwlagn 0000:03:00.0:0xCC515AE0| tsf low
kernel: iwlagn 0000:03:00.0:0x00000003| tsf hi
kernel: iwlagn 0000:03:00.0:0x00000000| time gp1
kernel: iwlagn 0000:03:00.0:0x29703BF0| time gp2
kernel: iwlagn 0000:03:00.0:0x00000000| time gp3
kernel: iwlagn 0000:03:00.0:0x000111A8| uCode version
kernel: iwlagn 0000:03:00.0:0x000000B0| hw version
kernel: iwlagn 0000:03:00.0:0x00480303| board version
kernel: iwlagn 0000:03:00.0:0x09E8004E| hcmd
kernel: iwlagn 0000:03:00.0: CSR values:
kernel: iwlagn 0000:03:00.0: (2nd byte ofCSR_INT_COALESCINGisCSR_INT_PERIODIC_REG)
kernel: iwlagn 0000:03:00.0:CSR_HW_IF_CONFIG_REG:0X00480303
kernel: iwlagn 0000:03:00.0:CSR_INT_COALESCING:0X0000ff40
kernel: iwlagn 0000:03:00.0:CSR_INT:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_INT_MASK:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_FH_INT_STATUS:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_GPIO_IN:0X00000030
kernel: iwlagn 0000:03:00.0:CSR_RESET:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_GP_CNTRL:0X080403c5
kernel: iwlagn 0000:03:00.0:CSR_HW_REV:0X000000b0
kernel: iwlagn 0000:03:00.0:CSR_EEPROM_REG:0X07d60ffd
kernel: iwlagn 0000:03:00.0:CSR_EEPROM_GP:0X90000001
kernel: iwlagn 0000:03:00.0:CSR_OTP_GP_REG:0X00030001
kernel: iwlagn 0000:03:00.0:CSR_GIO_REG:0X00080044
kernel: iwlagn 0000:03:00.0:CSR_GP_UCODE_REG:0X000093bb
kernel: iwlagn 0000:03:00.0:CSR_GP_DRIVER_REG:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_UCODE_DRV_GP1:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_UCODE_DRV_GP2:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_LED_REG:0X00000078
kernel: iwlagn 0000:03:00.0:CSR_DRAM_INT_TBL_REG:0X88214dd2
kernel: iwlagn 0000:03:00.0:CSR_GIO_CHICKEN_BITS:0X27800200
kernel: iwlagn 0000:03:00.0:CSR_ANA_PLL_CFG:0X00000000
kernel: iwlagn 0000:03:00.0:CSR_HW_REV_WA_REG:0X0001001a
kernel: iwlagn 0000:03:00.0:CSR_DBG_HPET_MEM_REG:0Xffff0010
kernel: iwlagn 0000:03:00.0: FH register values:
kernel: iwlagn 0000:03:00.0:FH_RSCSR_CHNL0_STTS_WPTR_REG:0X21316d00
kernel: iwlagn 0000:03:00.0:FH_RSCSR_CHNL0_RBDCB_BASE_REG:0X021479c0
kernel: iwlagn 0000:03:00.0:FH_RSCSR_CHNL0_WPTR:0X00000060
kernel: iwlagn 0000:03:00.0:FH_MEM_RCSR_CHNL0_CONFIG_REG:0X80819104
kernel: iwlagn 0000:03:00.0:FH_MEM_RSSR_SHARED_CTRL_REG:0X000000fc
kernel: iwlagn 0000:03:00.0:FH_MEM_RSSR_RX_STATUS_REG:0X07030000
kernel: iwlagn 0000:03:00.0:FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV:0X00000000
kernel: iwlagn 0000:03:00.0:FH_TSSR_TX_STATUS_REG:0X07ff0001
kernel: iwlagn 0000:03:00.0:FH_TSSR_TX_ERROR_REG:0X00000000
kernel: iwlagn 0000:03:00.0: Start IWL Event Log Dump: display last 20 entries
kernel: ------------[ cut here ]------------WARNING: at net/mac80211/util.c:1208 ieee80211_reconfig+0x1f1/0x407() kernel: Hardware name: 4290W4H kernel: Pid: 1896, comm: kworker/0:0 Not tainted 3.1.0 #2 kernel: Call Trace: kernel: [<ffffffff81036558>] ? warn_slowpath_common+0x73/0x87 kernel: [<ffffffff813b8966>] ? ieee80211_reconfig+0x1f1/0x407 kernel: [<ffffffff8139e8dc>] ? ieee80211_recalc_smps_work+0x32/0x32 kernel: [<ffffffff8139e95a>] ? ieee80211_restart_work+0x7e/0x87 kernel: [<ffffffff810472fa>] ? process_one_work+0x1c8/0x2e3 kernel: [<ffffffff810480c9>] ? worker_thread+0x17a/0x23a kernel: [<ffffffff81047f4f>] ? manage_workers.clone.18+0x15b/0x15b kernel: [<ffffffff81047f4f>] ? manage_workers.clone.18+0x15b/0x15b kernel: [<ffffffff8104ba97>] ? kthread+0x7a/0x82 kernel: [<ffffffff813d21b4>] ? kernel_thread_helper+0x4/0x10 kernel: [<ffffffff8104ba1d>] ? kthread_flush_work_fn+0x11/0x11 kernel: [<ffffffff813d21b0>] ? gs_change+0xb/0xbReported-by Udo Steinberg <[email protected]>Signed-off-by Wey-Yi Guy <[email protected]>Signed-off-by John W. Linville <[email protected]>Signed-off-by Greg Kroah-Hartman <[email protected]>--- drivers/net/wireless/iwlwifi/iwl-agn-rxon.c | 36 +++++++++++++++++----------- drivers/net/wireless/iwlwifi/iwl-agn.c | 18 ++------------ drivers/net/wireless/iwlwifi/iwl-agn.h | 2 + 3 files changed, 28 insertions(+), 28 deletions(-)drivers/net/wireless/iwlwifi/iwl-agn-rxon.c +23
-13@@ -542,6 +542,24 @@ int iwlagn_commit_rxon(struct iwl_priv *return 0 ; } +void iwlagn_config_ht40 (struct ieee80211_conf *conf, +struct iwl_rxon_context *ctx) +{ +if (conf_is_ht40_minus (conf)) { + ctx->ht.extension_chan_offset = +IEEE80211_HT_PARAM_CHA_SEC_BELOW ; + ctx->ht.is_40mhz = true; + }else if (conf_is_ht40_plus (conf)) { + ctx->ht.extension_chan_offset = +IEEE80211_HT_PARAM_CHA_SEC_ABOVE ; + ctx->ht.is_40mhz = true; + }else { + ctx->ht.extension_chan_offset = +IEEE80211_HT_PARAM_CHA_SEC_NONE ; + ctx->ht.is_40mhz = false; + } +} +int iwlagn_mac_config (struct ieee80211_hw *hw,u32 changed) {struct iwl_priv *priv = hw->priv;@@ -600,19 +618,11 @@ int iwlagn_mac_config(struct ieee80211_h ctx->ht.enabled =conf_is_ht (conf);if (ctx->ht.enabled) { -if (conf_is_ht40_minus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_BELOW ; - ctx->ht.is_40mhz = true; - }else if (conf_is_ht40_plus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_ABOVE ; - ctx->ht.is_40mhz = true; - }else { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_NONE ; - ctx->ht.is_40mhz = false; - } +/* if HT40 is used, it should not change +* after associated except channel switch */ +if (iwl_is_associated_ctx (ctx) && + !ctx->ht.is_40mhz) +iwlagn_config_ht40 (conf, ctx); }else ctx->ht.is_40mhz = false;drivers/net/wireless/iwlwifi/iwl-agn.c +3
-15@@ -3075,21 +3075,9 @@ static void iwlagn_mac_channel_switch(st/* Configure HT40 channels */ ctx->ht.enabled =conf_is_ht (conf); -if (ctx->ht.enabled) { -if (conf_is_ht40_minus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_BELOW ; - ctx->ht.is_40mhz = true; - }else if (conf_is_ht40_plus (conf)) { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_ABOVE ; - ctx->ht.is_40mhz = true; - }else { - ctx->ht.extension_chan_offset = -IEEE80211_HT_PARAM_CHA_SEC_NONE ; - ctx->ht.is_40mhz = false; - } - }else +if (ctx->ht.enabled) +iwlagn_config_ht40 (conf, ctx); +else ctx->ht.is_40mhz = false;if ((le16_to_cpu (ctx->staging.channel) != ch))drivers/net/wireless/iwlwifi/iwl-agn.h +2
-0@@ -135,6 +135,8 @@ void iwlagn_bss_info_changed(struct ieeestruct ieee80211_vif *vif, struct ieee80211_bss_conf *bss_conf, u32 changes); +void iwlagn_config_ht40 (struct ieee80211_conf *conf, +struct iwl_rxon_context *ctx);/* uCode */ void iwlagn_rx_calib_result(struct iwl_priv *priv,
Re: [092/104] iwlwifi: do not re-configure HT40 after associated
Quoted 4 lines · Wey-Yi
Hi Greg,
Just found out this might also needed for 3.0.
I am not sure it will apply, should I submit separated patch?
As it didn't apply, yes, please send a patch for this to [email protected].
thanks,
greg k-h
PATCH 93/104 iwlagn: fix HW crypto for TX-only keys
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Johannes Berg <[email protected]>
commit 274b89ca3b006926cb9b45d78ab5906f4c0fc0aa upstream.
Group keys in IBSS or AP mode are not programmed into the device since we give the key to it with every TX packet. However, we do need mac80211 to create the MMIC & PN in all cases. Move the code around to set the key flags all the time. We set them even when the key is removed again but that is obviously harmless.
--- drivers/net/wireless/iwlwifi/iwl-agn-sta.c | 5 ----- drivers/net/wireless/iwlwifi/iwl-agn.c | 11 +++++++++++ 2 files changed, 11 insertions(+), 5 deletions(-)
drivers/net/wireless/iwlwifi/iwl-agn-sta.c +0 -5
@@ -440,9 +440,6 @@ int iwl_set_dynamic_key(struct iwl_privswitch (keyconf->cipher) {case WLAN_CIPHER_SUITE_TKIP : - keyconf->flags |=IEEE80211_KEY_FLAG_GENERATE_MMIC ; - keyconf->flags |=IEEE80211_KEY_FLAG_GENERATE_IV ; -if (sta) addr = sta->addr;else /* station mode case only */
@@ -455,8 +452,6 @@ int iwl_set_dynamic_key(struct iwl_priv seq.tkip.iv32, p1k, CMD_SYNC);break ;case WLAN_CIPHER_SUITE_CCMP : - keyconf->flags |=IEEE80211_KEY_FLAG_GENERATE_IV ; -/* fall through */ case WLAN_CIPHER_SUITE_WEP40 :case WLAN_CIPHER_SUITE_WEP104 : ret = iwlagn_send_sta_key(priv, keyconf, sta_id,
drivers/net/wireless/iwlwifi/iwl-agn.c +11 -0
@@ -2793,6 +2793,17 @@ static int iwlagn_mac_set_key(struct ieereturn -EOPNOTSUPP ; } +switch (key->cipher) { +case WLAN_CIPHER_SUITE_TKIP : + key->flags |=IEEE80211_KEY_FLAG_GENERATE_MMIC ; +/* fall through */ +case WLAN_CIPHER_SUITE_CCMP : + key->flags |=IEEE80211_KEY_FLAG_GENERATE_IV ; +break ; +default : +break ; + } +/* * We could program these keys into the hardware as well, but we * don't expect much multicast traffic in IBSS and having keys
PATCH 94/104 ftrace: Remove force undef config value left for testing
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Steven Rostedt <[email protected]>
commit c7c6ec8becaf742b223c7b491f4893014be23a07 upstream.
A forced undef of a config value was used for testing and was accidently left in during the final commit. This causes x86 to run slower than needed while running function tracing as well as causes the function graph selftest to fail when DYNMAIC_FTRACE is not set. This is because the code in MCOUNT expects the ftrace code to be processed with the config value set that happened to be forced not set.
The forced config option was left in by:
commit 6331c28c962561aee59e5a493b7556a4bb585957
ftrace: Fix dynamic selftest failure on some archs
--- kernel/trace/ftrace.c | 1 - 1 file changed, 1 deletion(-)
kernel/trace/ftrace.c +0 -1
@@ -151,7 +151,6 @@ void clear_ftrace_function(void) ftrace_pid_function = ftrace_stub; } -#undef CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST#ifndef CONFIG_HAVE_FUNCTION_TRACE_MCOUNT_TEST /* * For those archs that do not test ftrace_trace_stop in their
PATCH 95/104 trace_events_filter: Use rcu_assign_pointer() when setting ftrace_event_call->filter
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tejun Heo <[email protected]>
commit d3d9acf646679c1981032b0985b386d12fccc60c upstream.
ftrace_event_call->filter is sched RCU protected but didn't use rcu_assign_pointer(). Use it.
TODO: Add proper __rcu annotation to call->filter and all its users.
-v2: Use RCU_INIT_POINTER() for %NULL clearing as suggested by Eric.
--- kernel/trace/trace_events_filter.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
kernel/trace/trace_events_filter.c +3 -3
@@ -1766,7 +1766,7 @@ static int replace_system_preds(struct e* replace the filter for the call. */ filter = call->filter; - call->filter = filter_item->filter; +rcu_assign_pointer (call->filter, filter_item->filter); filter_item->filter = filter; fail = false;
@@ -1821,7 +1821,7 @@ int apply_event_filter(struct ftrace_eve filter = call->filter;if (!filter) goto out_unlock; - call->filter =NULL ; +RCU_INIT_POINTER (call->filter,NULL );/* Make sure the filter is not being used */ synchronize_sched ();__free_filter (filter);
@@ -1862,7 +1862,7 @@ out:* string */ tmp = call->filter; - call->filter = filter; +rcu_assign_pointer (call->filter, filter);if (tmp) {/* Make sure the call is done with the filter */ synchronize_sched ();
PATCH 96/104 rtc: Disable the alarm in the hardware
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rabin Vincent <[email protected]>
commit c0afabd3d553c521e003779c127143ffde55a16f upstream.
Currently, the RTC code does not disable the alarm in the hardware.
This means that after a sequence such as the one below (the files are in the RTC sysfs), the box will boot up after 2 minutes even though we've asked for the alarm to be turned off.
# echo $((`cat since_epoch`)+120) > wakealarm # echo 0 > wakealarm # poweroff
Fix this by disabling the alarm when there are no timers to run.
--- drivers/rtc/interface.c | 44 ++++++++++++++++++++++++++++++++++---------- 1 file changed, 34 insertions(+), 10 deletions(-)
drivers/rtc/interface.c +34 -10
@@ -318,6 +318,20 @@ int rtc_read_alarm(struct rtc_device *rt }EXPORT_SYMBOL_GPL (rtc_read_alarm); +static int ___rtc_set_alarm (struct rtc_device *rtc,struct rtc_wkalrm *alarm) +{ +int err; + +if (!rtc->ops) + err = -ENODEV ; +else if (!rtc->ops->set_alarm) + err = -EINVAL ; +else + err = rtc->ops->set_alarm (rtc->dev.parent, alarm); + +return err; +} +static int __rtc_set_alarm (struct rtc_device *rtc,struct rtc_wkalrm *alarm) {struct rtc_time tm;
@@ -341,14 +355,7 @@ static int __rtc_set_alarm(struct rtc_de* over right here, before we set the alarm. */ -if (!rtc->ops) - err = -ENODEV ; -else if (!rtc->ops->set_alarm) - err = -EINVAL ; -else - err = rtc->ops->set_alarm (rtc->dev.parent, alarm); - -return err; +return ___rtc_set_alarm (rtc, alarm); }int rtc_set_alarm (struct rtc_device *rtc,struct rtc_wkalrm *alarm)
@@ -762,6 +769,20 @@ static int rtc_timer_enqueue(struct rtc_return 0 ; } +static void rtc_alarm_disable (struct rtc_device *rtc) +{ +struct rtc_wkalrm alarm; +struct rtc_time tm; + +__rtc_read_time (rtc, &tm); + + alarm.time =rtc_ktime_to_tm (ktime_add (rtc_tm_to_ktime (tm), +ktime_set (300 ,0 ))); + alarm.enabled =0 ; + +___rtc_set_alarm (rtc, &alarm); +} +/** * rtc_timer_remove - Removes a rtc_timer from the rtc_device timerqueue * @rtc rtc device
@@ -783,8 +804,10 @@ static void rtc_timer_remove(struct rtc_struct rtc_wkalrm alarm;int err; next =timerqueue_getnext (&rtc->timerqueue); -if (!next) +if (!next) { +rtc_alarm_disable (rtc);return ; + } alarm.time =rtc_ktime_to_tm (next->expires); alarm.enabled =1 ; err =__rtc_set_alarm (rtc, &alarm);
@@ -846,7 +869,8 @@ again: err =__rtc_set_alarm (rtc, &alarm);if (err == -ETIME ) goto again; - } + }else +rtc_alarm_disable (rtc);mutex_unlock (&rtc->ops_lock); }
Re: [096/104] rtc: Disable the alarm in the hardware
Hi Greg,
Quoted 13 lines · Greg KH
3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rabin Vincent <[email protected]>
commit
c0afabd3d553c521e003779c127143ffde55a16fupstream.Currently, the RTC code does not disable the alarm in the hardware.
This means that after a sequence such as the one below (the files are in the RTC sysfs), the box will boot up after 2 minutes even though we've asked for the alarm to be turned off.
[...]
Quoted 1 line
Fix this by disabling the alarm when there are no timers to run.
Seems to cause a regression. On the affected kernels (e.g., 3.1.5, 3.1.6, and 3.2-rc7) the patch has exactly the opposite of what you'd expect --- the affected machines automatically power on a few minutes after shutdown if and only if the patch is applied.
The affected machines all seem to be Toshiba Portege laptops.
Antonio-M. Corbi Bellot: Toshiba Portege R500
Marco Santos: Toshiba Portege Z830
Christophe Vu-Brugier: Toshiba Portege R830
Christophe tried reverting the above patch and the symptoms went away. See http://bugs.debian.org/652869 for details. Please consider reverting the patch from stable until this is resolved.
Thanks,
Jonathan
Re: [096/104] rtc: Disable the alarm in the hardware
Quoted 27 lines · Jonathan Nieder
Hi Greg,
Quoted 13 lines · Greg KH
3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rabin Vincent <[email protected]>
commit
c0afabd3d553c521e003779c127143ffde55a16fupstream.Currently, the RTC code does not disable the alarm in the hardware.
This means that after a sequence such as the one below (the files are in the RTC sysfs), the box will boot up after 2 minutes even though we've asked for the alarm to be turned off.
[...]
Quoted 1 line
Fix this by disabling the alarm when there are no timers to run.
Seems to cause a regression. On the affected kernels (e.g., 3.1.5, 3.1.6, and 3.2-rc7) the patch has exactly the opposite of what you'd expect --- the affected machines automatically power on a few minutes after shutdown if and only if the patch is applied.
The affected machines all seem to be Toshiba Portege laptops.
Quoted 7 lines
Antonio-M. Corbi Bellot: Toshiba Portege R500
Marco Santos: Toshiba Portege Z830
Christophe Vu-Brugier: Toshiba Portege R830Christophe tried reverting the above patch and the symptoms went away. See http://bugs.debian.org/652869 for details. Please consider reverting the patch from stable until this is resolved.
Is it also reverted (or fixed), in Linus's tree as well?
thanks,
greg k-h
Re: [096/104] rtc: Disable the alarm in the hardware
Quoted 5 lines · Greg KH
Quoted 5 lines
Quoted 3 lines · Greg KH
From: Rabin Vincent <[email protected]>
commit
c0afabd3d553c521e003779c127143ffde55a16fupstream.
[...]
Quoted 1 line
Is it also reverted (or fixed), in Linus's tree as well?
I don't see any relevant commits, no. Here's another relevant thread:
http://thread.gmane.org/gmane.linux.kernel/1233322/focus=1234433
Rabin, what do you think? Should c0afabd3 be reverted from mainline, or is there another fix ready?
Thanks,
Jonathan
PATCH 97/104 rtc: Fix some bugs that allowed accumulating time drift in suspend/resume
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: =?UTF-8?q?Arve=20Hj=C3=B8nnev=C3=A5g?= <[email protected]>
commit 6a8943d9ec2567572fca25cf69ad45844d0141a3 upstream.
The current code checks if abs(delta_delta.tv_sec) is greater or equal to two before it discards the old delta value, but this can trigger at close to -1 seconds since -1.000000001 seconds is stored as tv_sec -2 and tv_nsec 999999999 in a normalized timespec.
rtc_resume had an early return check if the rtc value had not changed since rtc_suspend. This effectivly stops time for the duration of the short sleep. Check if sleep_time is positive after all the adjustments have been applied instead since this allows the old_system adjustment in rtc_suspend to have an effect even for short sleep cycles.
--- drivers/rtc/class.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
drivers/rtc/class.c +5 -5
@@ -66,7 +66,7 @@ static int rtc_suspend(struct device *de*/ delta =timespec_sub (old_system, old_rtc); delta_delta =timespec_sub (delta, old_delta); -if (abs (delta_delta.tv_sec) >=2 ) { +if (delta_delta.tv_sec <-2 || delta_delta.tv_sec >=2 ) {/* * if delta_delta is too large, assume time correction * has occured and set old_delta to the current delta.
@@ -100,9 +100,8 @@ static int rtc_resume(struct device *devrtc_tm_to_time (&tm, &new_rtc.tv_sec); new_rtc.tv_nsec =0 ; -if (new_rtc.tv_sec <= old_rtc.tv_sec) { -if (new_rtc.tv_sec < old_rtc.tv_sec) -pr_debug ("%s: time travel!\n" ,dev_name (&rtc->dev)); +if (new_rtc.tv_sec < old_rtc.tv_sec) { +pr_debug ("%s: time travel!\n" ,dev_name (&rtc->dev));return 0 ; }
@@ -119,7 +118,8 @@ static int rtc_resume(struct device *dev sleep_time =timespec_sub (sleep_time,timespec_sub (new_system, old_system)); -timekeeping_inject_sleeptime (&sleep_time); +if (sleep_time.tv_sec >=0 ) +timekeeping_inject_sleeptime (&sleep_time);return 0 ; }
PATCH 98/104 tracing: fix event_subsystem ref counting
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ilya Dryomov <[email protected]>
commit cb59974742aea24adf6637eb0c4b8e7b48bca6fb upstream.
Fix a bug introduced by e9dbfae5, which prevents event_subsystem from ever being released.
Ref_count was added to keep track of subsystem users, not for counting events. Subsystem is created with ref_count = 1, so there is no need to increment it for every event, we have nr_events for that. Fix this by touching ref_count only when we actually have a new user - subsystem_open().
--- kernel/trace/trace_events.c | 1 - 1 file changed, 1 deletion(-)
kernel/trace/trace_events.c +0 -1
@@ -1078,7 +1078,6 @@ event_subsystem_dir(const char *name, st/* First see if we did not already create this dir */ list_for_each_entry (system, &event_subsystems, list) {if (strcmp (system->name, name) ==0 ) { -__get_system (system); system->nr_events++;return system->entry; }
PATCH 99/104 tick-broadcast: Stop active broadcast device when replacing it
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Gleixner <[email protected]>
commit c1be84309c58b1e7c6d626e28fba41a22b364c3d upstream.
When a better rated broadcast device is installed, then the current active device is not disabled, which results in two running broadcast devices.
--- kernel/time/tick-broadcast.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/time/tick-broadcast.c +1 -1
@@ -71,7 +71,7 @@ int tick_check_broadcast_device(struct c (dev->features & CLOCK_EVT_FEAT_C3STOP))return 0 ; -clockevents_exchange_device (NULL , dev); +clockevents_exchange_device (tick_broadcast_device.evtdev, dev); tick_broadcast_device.evtdev = dev;if (!cpumask_empty (tick_get_broadcast_mask ()))tick_broadcast_start_periodic (dev);
PATCH 100/104 perf: Fix parsing of __print_flags() in TP_printk()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Steven Rostedt <[email protected]>
commit d06c27b22aa66e48e32f03f9387328a9af9b0625 upstream.
A update is made to the sched:sched_switch event that adds some logic to the first parameter of the __print_flags() that shows the state of tasks. This change cause perf to fail parsing the flags.
A simple fix is needed to have the parser be able to process ops within the argument.
--- tools/perf/util/trace-event-parse.c | 2 ++ 1 file changed, 2 insertions(+)
tools/perf/util/trace-event-parse.c +2 -0
@@ -1537,6 +1537,8 @@ process_flags(struct event *event, struc field =malloc_or_die (sizeof (*field)); type =process_arg (event, field, &token); +while (type ==EVENT_OP ) + type =process_op (event, field, &token);if (test_type_token (type, token,EVENT_DELIM ,"," )) goto out_free;
PATCH 101/104 jump_label: jump_label_inc may return before the code is patched
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gleb Natapov <[email protected]>
commit bbbf7af4bf8fc69bc751818cf30521080fa47dcb upstream.
If cpu A calls jump_label_inc() just after atomic_add_return() is called by cpu B, atomic_inc_not_zero() will return value greater then zero and jump_label_inc() will return to a caller before jump_label_update() finishes its job on cpu B.
--- kernel/jump_label.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
kernel/jump_label.c +2 -1
@@ -66,8 +66,9 @@ void jump_label_inc(struct jump_label_kereturn ;jump_label_lock (); -if (atomic_add_return (1 , &key->enabled) ==1 ) +if (atomic_read (&key->enabled) ==0 )jump_label_update (key,JUMP_LABEL_ENABLE ); +atomic_inc (&key->enabled);jump_label_unlock (); }
PATCH 102/104 oprofile: Fix crash when unloading module (hr timer mode)
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Robert Richter <[email protected]>
commit 87121ca504fd1d963a66b3fb0c72054b0fd9a177 upstream.
Oprofile may crash in a KVM guest while unlaoding modules. This happens if oprofile_arch_init() fails and oprofile switches to the hr timer mode as a fallback. In this case oprofile_arch_exit() is called, but it never was initialized properly which causes the crash. This patch fixes this.
oprofile: using timer interrupt.
BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 IP: [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58 PGD 41da3f067 PUD 41d80e067 PMD 0 Oops: 0002 [#1] PREEMPT SMP CPU 5 Modules linked in: oprofile(-)
Pid: 2382, comm: modprobe Not tainted 3.1.0-rc7-00018-g709a39d #18 Advanced Micro Device Anaheim/Anaheim
RIP: 0010:[<ffffffff8123c226>] [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58 RSP: 0018:ffff88041de1de98 EFLAGS: 00010296 RAX: 0000000000000000 RBX: ffffffffa00060e0 RCX: dead000000200200 RDX: 0000000000000000 RSI: dead000000100100 RDI: ffffffff8178c620 RBP: ffff88041de1dea8 R08: 0000000000000001 R09: 0000000000000082 R10: 0000000000000000 R11: ffff88041de1dde8 R12: 0000000000000080 R13: fffffffffffffff5 R14: 0000000000000001 R15: 0000000000610210 FS: 00007f9ae5bef700(0000) GS:ffff88042fd40000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000008 CR3: 000000041ca44000 CR4: 00000000000006e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400 Process modprobe (pid: 2382, threadinfo ffff88041de1c000, task ffff88042db6d040) Stack: ffff88041de1deb8 ffffffffa0006770 ffff88041de1deb8 ffffffffa000251e ffff88041de1dec8 ffffffffa00022c2 ffff88041de1ded8 ffffffffa0004993 ffff88041de1df78 ffffffff81073115 656c69666f72706f 0000000000610200 Call Trace: [<ffffffffa000251e>] op_nmi_exit+0x15/0x17 [oprofile] [<ffffffffa00022c2>] oprofile_arch_exit+0xe/0x10 [oprofile] [<ffffffffa0004993>] oprofile_exit+0x13/0x15 [oprofile] [<ffffffff81073115>] sys_delete_module+0x1c3/0x22f [<ffffffff811bf09e>] ? trace_hardirqs_on_thunk+0x3a/0x3f [<ffffffff8148070b>] system_call_fastpath+0x16/0x1b Code: 20 c6 78 81 e8 c5 cc 23 00 48 8b 13 48 8b 43 08 48 be 00 01 10 00 00 00 ad de 48 b9 00 02 20 00 00 00 ad de 48 c7 c7 20 c6 78 81 89 42 08 48 89 10 48 89 33 48 89 4b 08 e8 a6 c0 23 00 5a 5b RIP [<ffffffff8123c226>] unregister_syscore_ops+0x41/0x58 RSP <ffff88041de1de98> CR2: 0000000000000008 ---[ end trace 06d4e95b6aa3b437 ]---
--- drivers/oprofile/oprof.c | 29 ++++++++++++++++++++++++----- drivers/oprofile/timer_int.c | 1 + 2 files changed, 25 insertions(+), 5 deletions(-)
drivers/oprofile/oprof.c +24 -5
@@ -239,26 +239,45 @@ int oprofile_set_ulong(unsigned long *adreturn err; } +static int timer_mode; +static int __init oprofile_init (void ) {int err; +/* always init architecture to setup backtrace support */ err =oprofile_arch_init (&oprofile_ops); -if (err <0 || timer) { -printk (KERN_INFO "oprofile: using timer interrupt.\n" ); + + timer_mode = err || timer;/* fall back to timer mode on errors */ +if (timer_mode) { +if (!err) +oprofile_arch_exit (); err =oprofile_timer_init (&oprofile_ops);if (err)return err; } -return oprofilefs_register (); + + err =oprofilefs_register (); +if (!err) +return 0 ; + +/* failed */ +if (timer_mode) +oprofile_timer_exit (); +else +oprofile_arch_exit (); + +return err; } static void __exit oprofile_exit(void) { -oprofile_timer_exit ();oprofilefs_unregister (); -oprofile_arch_exit (); +if (timer_mode) +oprofile_timer_exit (); +else +oprofile_arch_exit (); }
drivers/oprofile/timer_int.c +1 -0
@@ -110,6 +110,7 @@ int oprofile_timer_init(struct oprofile_ ops->start = oprofile_hrtimer_start; ops->stop = oprofile_hrtimer_stop; ops->cpu_type ="timer" ; +printk (KERN_INFO "oprofile: using timer interrupt.\n" );return 0 ; }
PATCH 103/104 clocksource: Fix bug with max_deferment margin calculation
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Yang Honggang (Joseph)" <[email protected]>
commit b1f919664d04a8d0ba29cb76673c7ca3325a2006 upstream.
In order to leave a margin of 12.5% we should >> 3 not >> 5.
--- kernel/time/clocksource.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/time/clocksource.c +2 -2
@@ -550,7 +550,7 @@ static u64 clocksource_max_deferment(str* note a margin of 12.5% is used because this can be computed with * a shift, versus say 10% which would require division. */ -return max_nsecs - (max_nsecs >>5 ); +return max_nsecs - (max_nsecs >>3 ); }#ifndef CONFIG_ARCH_USES_GETTIMEOFFSET
@@ -671,7 +671,7 @@ void __clocksource_updatefreq_scale(stru* ~ 0.06ppm granularity for NTP. We apply the same 12.5% * margin as we do in clocksource_max_deferment() */ - sec = (cs->mask - (cs->mask >>5 )); + sec = (cs->mask - (cs->mask >>3 ));do_div (sec, freq);do_div (sec, scale);if (!sec)
PATCH 104/104 clockevents: Set noop handler in clockevents_exchange_device()
In reply to Greg KH3.1-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Gleixner <[email protected]>
commit de28f25e8244c7353abed8de0c7792f5f883588c upstream.
If a device is shutdown, then there might be a pending interrupt, which will be processed after we reenable interrupts, which causes the original handler to be run. If the old handler is the (broadcast) periodic handler the shutdown state might hang the kernel completely.
--- kernel/time/clockevents.c | 1 + 1 file changed, 1 insertion(+)
kernel/time/clockevents.c +1 -0
@@ -286,6 +286,7 @@ void clockevents_exchange_device(struct* released list and do a notify add later. */ if (old) { + old->event_handler = clockevents_handle_noop;clockevents_set_mode (old,CLOCK_EVT_MODE_UNUSED );list_del (&old->list);list_add (&old->list, &clockevents_released);
Quoted 6 lines · Greg KH
This is the start of the stable review cycle for the 3.1.5 release. There are 104 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let us know. If anyone is a maintainer of the proper subsystem, and wants to add a Signed-off-by: line to the patch, please respond with it.
Quoted 6 lines
Responses should be made by Friday, December 9, 2011, 17:00:00 UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.1.5-rc1.gzand the diffstat can be found below.
I forgot a number of networking patches, so there is an -rc2 patch now at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.1.5-rc2.gz
and the diffstat for it is below.
thanks,
greg k-h
Makefile | 4 +- arch/arm/Kconfig | 12 ++ arch/arm/configs/ezx_defconfig | 2 +- arch/arm/configs/imote2_defconfig | 2 +- arch/arm/configs/magician_defconfig | 2 +- arch/arm/configs/zeus_defconfig | 2 +- arch/arm/kernel/process.c | 3 + arch/arm/mach-mxs/clock-mx28.c | 2 +- arch/arm/mach-omap2/Kconfig | 1 + arch/arm/mach-omap2/omap_hwmod.c | 6 +- arch/arm/mach-omap2/pm.c | 6 +- arch/arm/mach-omap2/smartreflex.c | 2 +- arch/arm/mach-omap2/twl-common.c | 11 ++ arch/arm/mach-omap2/twl-common.h | 3 + arch/arm/mach-pxa/balloon3.c | 2 +- arch/arm/mach-pxa/colibri-pxa320.c | 2 +- arch/arm/mach-pxa/gumstix.c | 2 +- arch/arm/mach-pxa/include/mach/palm27x.h | 4 +- arch/arm/mach-pxa/palm27x.c | 4 +- arch/arm/mach-pxa/palmtc.c | 2 +- arch/arm/mach-pxa/vpac270.c | 2 +- arch/s390/kernel/ptrace.c | 18 +++ arch/x86/include/asm/timer.h | 23 ++++- arch/x86/kernel/cpu/perf_event_intel_ds.c | 6 +- arch/x86/kernel/mpparse.c | 2 +- arch/x86/kernel/reboot.c | 13 ++- arch/x86/mm/highmem_32.c | 2 + arch/x86/oprofile/init.c | 7 +- drivers/crypto/mv_cesa.c | 12 +- drivers/firmware/sigma.c | 81 +++++++++---- drivers/gpu/drm/drm_crtc.c | 4 + drivers/gpu/drm/i915/i915_irq.c | 1 + drivers/gpu/drm/i915/i915_reg.h | 4 + drivers/gpu/drm/i915/i915_suspend.c | 2 + drivers/gpu/drm/i915/intel_display.c | 14 ++ drivers/gpu/drm/i915/intel_panel.c | 3 +- drivers/gpu/drm/radeon/evergreen.c | 7 +- drivers/gpu/drm/radeon/r100.c | 7 +- drivers/gpu/drm/radeon/radeon_atombios.c | 24 ++++ drivers/gpu/drm/radeon/rs600.c | 7 +- drivers/gpu/drm/radeon/rv770.c | 7 +- drivers/hid/hid-core.c | 2 +- drivers/hid/hid-ids.h | 2 +- drivers/i2c/algos/i2c-algo-bit.c | 4 +- drivers/infiniband/core/addr.c | 9 +- drivers/infiniband/hw/cxgb3/iwch_cm.c | 4 + drivers/infiniband/hw/cxgb4/cm.c | 4 + drivers/infiniband/hw/mlx4/qp.c | 2 +- drivers/infiniband/hw/nes/nes_cm.c | 6 +- drivers/infiniband/ulp/ipoib/ipoib_main.c | 18 ++- drivers/infiniband/ulp/ipoib/ipoib_multicast.c | 6 +- drivers/net/wireless/iwlwifi/iwl-agn-rxon.c | 36 ++++-- drivers/net/wireless/iwlwifi/iwl-agn-sta.c | 5 - drivers/net/wireless/iwlwifi/iwl-agn.c | 29 ++--- drivers/net/wireless/iwlwifi/iwl-agn.h | 2 + drivers/net/wireless/iwlwifi/iwl-pci.c | 8 +- drivers/net/wireless/p54/p54spi.c | 5 +- drivers/net/wireless/rt2x00/rt2800lib.c | 2 +- drivers/net/wireless/rtlwifi/ps.c | 17 ++-- drivers/oprofile/oprof.c | 29 ++++- drivers/oprofile/timer_int.c | 1 + drivers/pci/hotplug/shpchp_core.c | 4 +- drivers/pci/hotplug/shpchp_hpc.c | 4 +- drivers/regulator/aat2870-regulator.c | 2 +- drivers/regulator/twl-regulator.c | 46 +++++++- drivers/rtc/class.c | 10 +- drivers/rtc/interface.c | 44 ++++++-- drivers/s390/net/qeth_l3_main.c | 7 + drivers/scsi/scsi_lib.c | 3 +- drivers/staging/comedi/comedi_fops.c | 94 +++++++++++---- drivers/staging/rts_pstor/rtsx.c | 1 + drivers/staging/usbip/vhci_rx.c | 10 +- drivers/usb/host/ehci-sched.c | 22 ++-- drivers/usb/host/whci/qset.c | 2 +- drivers/usb/host/xhci.c | 5 +- drivers/usb/musb/musb_core.c | 6 - drivers/usb/serial/ftdi_sio.c | 1 + drivers/usb/serial/ftdi_sio_ids.h | 1 + drivers/usb/serial/option.c | 4 + drivers/usb/storage/unusual_devs.h | 7 + drivers/video/via/share.h | 4 +- fs/ecryptfs/crypto.c | 26 ++-- fs/ecryptfs/ecryptfs_kernel.h | 5 +- fs/ecryptfs/file.c | 23 ++++- fs/ecryptfs/inode.c | 52 +++++---- fs/ext4/inode.c | 2 +- fs/xfs/xfs_buf.h | 1 - fs/xfs/xfs_file.c | 34 +++++- fs/xfs/xfs_iops.c | 2 +- fs/xfs/xfs_mount.c | 29 ++--- fs/xfs/xfs_qm.c | 3 +- fs/xfs/xfs_vnodeops.c | 14 ++- include/drm/drm_mode.h | 2 + include/drm/drm_pciids.h | 8 ++ include/linux/clocksource.h | 3 +- include/linux/sigma.h | 13 +-- include/net/inetpeer.h | 1 + include/net/red.h | 15 +-- kernel/cgroup_freezer.c | 11 ++- kernel/hrtimer.c | 6 +- kernel/irq/manage.c | 5 +- kernel/irq/spurious.c | 4 +- kernel/jump_label.c | 3 +- kernel/time/clockevents.c | 1 + kernel/time/clocksource.c | 62 ++++++++-- kernel/time/tick-broadcast.c | 2 +- kernel/time/timekeeping.c | 11 ++ kernel/trace/ftrace.c | 1 - kernel/trace/trace_events.c | 1 - kernel/trace/trace_events_filter.c | 6 +- mm/hugetlb.c | 2 + mm/slab.c | 5 +- net/bridge/br_multicast.c | 2 + net/ipv4/ah4.c | 6 +- net/ipv4/ip_options.c | 1 + net/ipv4/route.c | 152 ++++++++++++++++-------- net/ipv6/ah6.c | 6 +- net/mac80211/agg-tx.c | 41 ++++++- net/mac80211/main.c | 6 + net/sched/sch_red.c | 4 +- net/sched/sch_teql.c | 31 +++-- net/sunrpc/xprtsock.c | 3 +- net/wireless/nl80211.c | 4 +- net/wireless/reg.c | 49 +++++--- sound/pci/hda/patch_realtek.c | 14 ++- sound/pci/hda/patch_sigmatel.c | 18 --- sound/pci/hda/patch_via.c | 76 +++++++----- sound/pci/lx6464es/lx_core.c | 16 ++- sound/soc/codecs/ad1836.h | 2 +- sound/soc/codecs/sta32x.c | 63 ++++++++++- sound/soc/codecs/sta32x.h | 1 + sound/soc/codecs/wm8731.c | 1 + sound/soc/codecs/wm8753.c | 3 + sound/soc/fsl/fsl_ssi.c | 1 + tools/perf/util/trace-event-parse.c | 2 + 135 files changed, 1171 insertions(+), 472 deletions(-)