3.4.89-stable review
Greg Kroah-Hartman
maintainercover 3.4.89-stable review
This is the start of the stable review cycle for the 3.4.89 release. There are 43 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 me know.
Responses should be made by Tue May 6 15:42:07 UTC 2014. 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.4.89-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.4.89-rc1
Aaron Sanders <[email protected]>
USB: pl2303: add ids for Hewlett-Packard HP POS pole displays
Theodore Ts'o <[email protected]>
ext4: use i_size_read in ext4_unaligned_aio()
alex chen <[email protected]>
ocfs2: do not put bh when buffer_uptodate failed
Junxiao Bi <[email protected]>
ocfs2: dlm: fix recovery hung
Junxiao Bi <[email protected]>
ocfs2: dlm: fix lock migration crash
Liu Hua <[email protected]>
hung_task: check the value of "sysctl_hung_task_timeout_sec"
Mizuma, Masayoshi <[email protected]>
mm: hugetlb: fix softlockup when a large number of hugepages are freed.
Matt Fleming <[email protected]>
sh: fix format string bug in stack tracer
Alan Stern <[email protected]>
USB: unbind all interfaces before rebinding any
Paul Gortmaker <[email protected]>
hvc: ensure hvc_init is only ever called once in hvc_console.c
Huang Rui <[email protected]>
usb: dwc3: fix wrong bit mask in dwc3_event_devt
David Cohen <[email protected]>
usb/xhci: fix compilation warning when !CONFIG_PCI && !CONFIG_PM
Igor Gnatenko <[email protected]>
xhci: extend quirk for Renesas cards
supriya karanth <[email protected]>
usb: musb: set TXMAXP and AUTOSET for full speed bulk in device mode
Jeff Mahoney <[email protected]>
reiserfs: fix race in readdir
Andy Grover <[email protected]>
target/tcm_fc: Fix use-after-free of ft_tpg
Nicholas Bellinger <[email protected]>
iscsi-target: Fix ERL=2 ASYNC_EVENT connection pointer bug
Dan Carpenter <[email protected]>
SCSI: arcmsr: upper 32 of dma address lost
Mike Marciniszyn <[email protected]>
ib_srpt: Use correct ib_sg_dma primitives
Yann Droneaud <[email protected]>
IB/ehca: Returns an error on ib_copy_to_udata() failure
Yann Droneaud <[email protected]>
IB/mthca: Return an error on ib_copy_to_udata() failure
Yann Droneaud <[email protected]>
IB/nes: Return an error on ib_copy_from_udata() failure instead of NULL
Dennis Dalessandro <[email protected]>
IB/ipath: Fix potential buffer overrun in sending diag packet routine
J. Bruce Fields <[email protected]>
nfsd4: fix setclientid encode size
J. Bruce Fields <[email protected]>
nfsd: notify_change needs elevated write count
J. Bruce Fields <[email protected]>
nfsd4: fix test_stateid error reply encoding
J. Bruce Fields <[email protected]>
nfsd4: buffer-length check for SUPPATTR_EXCLCREAT
J. Bruce Fields <[email protected]>
nfsd4: session needs room for following op to error out
Alan Stern <[email protected]>
USB: fix crash during hotplug of PCI USB controller card
H. Peter Anvin <[email protected]>
x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels
Larry Finger <[email protected]>
staging: r8712u: Fix case where ethtype was never obtained and always be checked against 0
Himangi Saraogi <[email protected]>
staging:serqt_usb2: Fix sparse warning restricted __le16 degrades to integer
David Fries <[email protected]>
w1: fix w1_send_slave dropping a slave id
Krzysztof Kozlowski <[email protected]>
mfd: max8997: Fix possible NULL pointer dereference on i2c_new_dummy error
Krzysztof Kozlowski <[email protected]>
mfd: max8998: Fix possible NULL pointer dereference on i2c_new_dummy error
Krzysztof Kozlowski <[email protected]>
mfd: max8925: Fix possible NULL pointer dereference on i2c_new_dummy error
Takashi Iwai <[email protected]>
ALSA: ice1712: Fix boundary checks in PCM pointer ops
W. Trevor King <[email protected]>
ALSA: hda - Enable beep for ASUS 1015E
Liu Hua <[email protected]>
ARM: 8030/1: ARM : kdump : add arch_crash_save_vmcoreinfo
Xiangyu Lu <[email protected]>
ARM: 8027/1: fix do_div() bug in big-endian systems
Roger Quadros <[email protected]>
ARM: OMAP3: hwmod data: Correct clock domains for USB modules
Stefan Sørensen <[email protected]>
ARM: OMAP2+: INTC: Acknowledge stuck active interrupts
Brian Austin <[email protected]>
ASoC: cs42l73: Fix mask bits for SOC_VALUE_ENUM_SINGLE
-------------
Diffstat:
Makefile | 4 +- arch/arm/include/asm/div64.h | 2 +- arch/arm/kernel/machine_kexec.c | 7 +++ arch/arm/mach-omap2/irq.c | 8 +++ arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 4 +- arch/sh/kernel/dumpstack.c | 2 +- arch/x86/kernel/ldt.c | 11 ++++ drivers/infiniband/hw/ehca/ehca_cq.c | 1 + drivers/infiniband/hw/ipath/ipath_diag.c | 66 ++++++++----------- drivers/infiniband/hw/mthca/mthca_provider.c | 1 + drivers/infiniband/hw/nes/nes_verbs.c | 2 +- drivers/infiniband/ulp/srpt/ib_srpt.c | 16 +++-- drivers/mfd/max8925-i2c.c | 9 +++ drivers/mfd/max8997.c | 18 ++++++ drivers/mfd/max8998.c | 4 ++ drivers/scsi/arcmsr/arcmsr_hba.c | 7 +-- drivers/staging/rtl8712/rtl871x_recv.c | 13 ++-- drivers/staging/serqt_usb2/serqt_usb2.c | 2 +- drivers/target/iscsi/iscsi_target.c | 4 +- drivers/target/tcm_fc/tfc_sess.c | 1 + drivers/tty/hvc/hvc_console.c | 6 +- drivers/usb/core/driver.c | 94 +++++++++++++++++----------- drivers/usb/core/hcd-pci.c | 2 +- drivers/usb/core/hub.c | 5 +- drivers/usb/core/usb.h | 2 +- drivers/usb/dwc3/core.h | 6 +- drivers/usb/host/xhci-pci.c | 4 +- drivers/usb/host/xhci.c | 6 +- drivers/usb/musb/musb_gadget.c | 22 ++++++- drivers/usb/serial/pl2303.c | 3 + drivers/usb/serial/pl2303.h | 5 +- drivers/w1/w1_netlink.c | 25 ++++---- fs/ext4/file.c | 2 +- fs/nfsd/nfs4proc.c | 9 ++- fs/nfsd/nfs4xdr.c | 5 ++ fs/nfsd/vfs.c | 9 +++ fs/ocfs2/buffer_head_io.c | 2 - fs/ocfs2/dlm/dlmrecovery.c | 29 ++++++--- fs/reiserfs/dir.c | 6 +- kernel/sysctl.c | 6 ++ mm/hugetlb.c | 1 + sound/pci/hda/patch_realtek.c | 1 + sound/pci/ice1712/ice1712.c | 15 +++-- sound/soc/codecs/cs42l73.c | 6 +- 44 files changed, 296 insertions(+), 157 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/43 ASoC: cs42l73: Fix mask bits for SOC_VALUE_ENUM_SINGLE
3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Brian Austin <[email protected]>
commit 1555b652970e541fa1cb80c61ffc696bbfb92bb7 upstream.
The mask bits values were wrong for the SOC_VALUE_ENUM_SINGLE for the mono mix controls.
--- sound/soc/codecs/cs42l73.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
sound/soc/codecs/cs42l73.c +3 -3
@@ -327,7 +327,7 @@ static const char * const cs42l73_mono_mstatic const unsigned int cs42l73_mono_mix_values[] = {0 ,1 ,2 };static const struct soc_enum spk_asp_enum = -SOC_VALUE_ENUM_SINGLE (CS42L73_MMIXCTL ,6 ,1 , +SOC_VALUE_ENUM_SINGLE (CS42L73_MMIXCTL ,6 ,3 ,ARRAY_SIZE (cs42l73_mono_mix_texts), cs42l73_mono_mix_texts, cs42l73_mono_mix_values);
@@ -345,7 +345,7 @@ static const struct snd_kcontrol_new spkSOC_DAPM_ENUM ("Route" , spk_xsp_enum);static const struct soc_enum esl_asp_enum = -SOC_VALUE_ENUM_SINGLE (CS42L73_MMIXCTL ,2 ,5 , +SOC_VALUE_ENUM_SINGLE (CS42L73_MMIXCTL ,2 ,3 ,ARRAY_SIZE (cs42l73_mono_mix_texts), cs42l73_mono_mix_texts, cs42l73_mono_mix_values);
@@ -354,7 +354,7 @@ static const struct snd_kcontrol_new eslSOC_DAPM_ENUM ("Route" , esl_asp_enum);static const struct soc_enum esl_xsp_enum = -SOC_VALUE_ENUM_SINGLE (CS42L73_MMIXCTL ,0 ,7 , +SOC_VALUE_ENUM_SINGLE (CS42L73_MMIXCTL ,0 ,3 ,ARRAY_SIZE (cs42l73_mono_mix_texts), cs42l73_mono_mix_texts, cs42l73_mono_mix_values);
Greg Kroah-Hartman
maintainerPATCH 2/43 ARM: OMAP2+: INTC: Acknowledge stuck active interrupts
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stefan Sørensen <[email protected]>
commit 698b48532539484b012fb7c4176b959d32a17d00 upstream.
When an interrupt has become active on the INTC it will stay active until it is acked, even if masked or de-asserted. The INTC_PENDING_IRQn registers are however updated and since these are used by omap_intc_handle_irq to determine which interrupt to handle, it will never see the active interrupt. This will result in a storm of useless interrupts that is only stopped when another higher priority interrupt is asserted.
Fix by sending the INTC an acknowledge if we find no interrupts to handle.
--- arch/arm/mach-omap2/irq.c | 8 ++++++++ 1 file changed, 8 insertions(+)
arch/arm/mach-omap2/irq.c +8 -0
@@ -220,6 +220,7 @@ void __init ti81xx_init_irq(void)static inline void omap_intc_handle_irq (void __iomem *base_addr,struct pt_regs *regs) {u32 irqnr; +int handled_irq =0 ; do { irqnr = readl_relaxed(base_addr + 0x98);
@@ -247,8 +248,15 @@ out:if (irqnr) { irqnr =irq_find_mapping (domain, irqnr);handle_IRQ (irqnr, regs); + handled_irq =1 ; } }while (irqnr); + +/* If an irq is masked or deasserted while active, we will +* keep ending up here with no irq handled. So remove it from +* the INTC with an ack.*/ +if (!handled_irq) +omap_ack_irq (NULL ); } asmlinkage void __exception_irq_entry omap2_intc_handle_irq(struct pt_regs *regs)
Greg Kroah-Hartman
maintainerPATCH 3/43 ARM: OMAP3: hwmod data: Correct clock domains for USB modules
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Roger Quadros <[email protected]>
commit c6c56697ae4bf1226263c19e8353343d7083f40e upstream.
OMAP3 doesn't contain "l3_init_clkdm" clock domain. Use the proper clock domains for USB Host and USB TLL modules.
Gets rid of the following warnings during boot
omap_hwmod: usb_host_hs: could not associate to clkdm l3_init_clkdm
omap_hwmod: usb_tll_hs: could not associate to clkdm l3_init_clkdm
--- arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c +2 -2
@@ -3408,7 +3408,7 @@ static struct omap_hwmod_irq_info omap3xstatic struct omap_hwmod omap3xxx_usb_host_hs_hwmod = { .name ="usb_host_hs" , .class = &omap3xxx_usb_host_hs_hwmod_class, - .clkdm_name ="l3_init_clkdm" , + .clkdm_name ="usbhost_clkdm" , .mpu_irqs = omap3xxx_usb_host_hs_irqs, .main_clk ="usbhost_48m_fck" , .prcm = {
@@ -3519,7 +3519,7 @@ static struct omap_hwmod_ocp_if *omap3xxstatic struct omap_hwmod omap3xxx_usb_tll_hs_hwmod = { .name ="usb_tll_hs" , .class = &omap3xxx_usb_tll_hs_hwmod_class, - .clkdm_name ="l3_init_clkdm" , + .clkdm_name ="core_l4_clkdm" , .mpu_irqs = omap3xxx_usb_tll_hs_irqs, .main_clk ="usbtll_fck" , .prcm = {
Greg Kroah-Hartman
maintainerPATCH 4/43 ARM: 8027/1: fix do_div() bug in big-endian systems
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Xiangyu Lu <[email protected]>
commit 80bb3ef109ff40a7593d9481c17de9bbc4d7c0e2 upstream.
In big-endian systems, "%1" get the most significant part of the value, cause the instruction to get the wrong result.
When viewing ftrace record in big-endian ARM systems, we found that the timestamp errors:
swapper-0 [001] 1325.970000: 0:120:R ==> [001] 16:120:R events/1 events/1-16 [001] 1325.970000: 16:120:S ==> [001] 0:120:R swapper swapper-0 [000] 1325.1000000: 0:120:R + [000] 15:120:R events/0 swapper-0 [000] 1325.1000000: 0:120:R ==> [000] 15:120:R events/0 swapper-0 [000] 1326.030000: 0:120:R + [000] 1150:120:R sshd swapper-0 [000] 1326.030000: 0:120:R ==> [000] 1150:120:R sshd
When viewed ftrace records, it will call the do_div(n, base) function, which achieved arch/arm/include/asm/div64.h in. When n = 10000000, base = 1000000, in do_div(n, base) will execute "umull %Q0, %R0, %1, %Q2".
--- arch/arm/include/asm/div64.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/include/asm/div64.h +1 -1
@@ -156,7 +156,7 @@/* Select the best insn combination to perform the */ \/* actual __m * __n / (__p << 64) operation. */ \if (!__c) { \ - asm ("umull %Q0, %R0, %1, %Q2\n\t" \ + asm ("umull %Q0, %R0, %Q1, %Q2\n\t" \"mov %Q0, #0" \ :"=&r" (__res) \ : "r" (__m), "r" (__n) \
Greg Kroah-Hartman
maintainerPATCH 5/43 ARM: 8030/1: ARM : kdump : add arch_crash_save_vmcoreinfo
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Liu Hua <[email protected]>
commit 56b700fd6f1e49149880fb1b6ffee0dca5be45fb upstream.
For vmcore generated by LPAE enabled kernel, user space utility such as crash needs additional infomation to parse.
So this patch add arch_crash_save_vmcoreinfo as what PAE enabled i386 linux does.
--- arch/arm/kernel/machine_kexec.c | 7 +++++++ 1 file changed, 7 insertions(+)
arch/arm/kernel/machine_kexec.c +7 -0
@@ -138,3 +138,10 @@ void machine_kexec(struct kimage *image)soft_restart (reboot_code_buffer_phys); } + +void arch_crash_save_vmcoreinfo (void ) +{ +#ifdef CONFIG_ARM_LPAE +VMCOREINFO_CONFIG (ARM_LPAE ); +#endif +}
Greg Kroah-Hartman
maintainerPATCH 6/43 ALSA: hda - Enable beep for ASUS 1015E
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "W. Trevor King" <[email protected]>
commit a4b7f21d7b42b33609df3f86992a8deff80abfaf upstream.
The lspci -nnvv output contains (wrapped for line length):
00:1b.0 Audio device [0403]:
Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
Subsystem: ASUSTeK Computer Inc. Device [1043:115d]
--- sound/pci/hda/patch_realtek.c | 1 + 1 file changed, 1 insertion(+)
sound/pci/hda/patch_realtek.c +1 -0
@@ -4323,6 +4323,7 @@ static void alc_auto_init_std(struct hdastatic const struct snd_pci_quirk beep_white_list[] = {SND_PCI_QUIRK (0x1043 ,0x103c ,"ASUS" ,1 ), +SND_PCI_QUIRK (0x1043 ,0x115d ,"ASUS" ,1 ),SND_PCI_QUIRK (0x1043 ,0x829f ,"ASUS" ,1 ),SND_PCI_QUIRK (0x1043 ,0x83ce ,"EeePC" ,1 ),SND_PCI_QUIRK (0x1043 ,0x831a ,"EeePC" ,1 ),
Greg Kroah-Hartman
maintainerPATCH 7/43 ALSA: ice1712: Fix boundary checks in PCM pointer ops
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 4f8e940095536bc002a81666a4107a581c84e9b9 upstream.
PCM pointer callbacks in ice1712 driver check the buffer size boundary wrongly between bytes and frames. This leads to PCM core warnings
like:
snd_pcm_update_hw_ptr0: 105 callbacks suppressed
ALSA pcm_lib.c:352 BUG: pcmC3D0c:0, pos = 5461, buffer size = 5461, period size = 2730
This patch fixes these checks to be placed after the proper unit conversions.
--- sound/pci/ice1712/ice1712.c | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)
sound/pci/ice1712/ice1712.c +10 -5
@@ -686,9 +686,10 @@ static snd_pcm_uframes_t snd_ice1712_plaif (!(snd_ice1712_read (ice,ICE1712_IREG_PBK_CTRL ) &1 ))return 0 ; ptr = runtime->buffer_size -inw (ice->ddma_port +4 ); + ptr =bytes_to_frames (substream->runtime, ptr);if (ptr == runtime->buffer_size) ptr =0 ; -return bytes_to_frames (substream->runtime, ptr); +return ptr; }static snd_pcm_uframes_t snd_ice1712_playback_ds_pointer (struct snd_pcm_substream *substream)
@@ -705,9 +706,10 @@ static snd_pcm_uframes_t snd_ice1712_pla addr =ICE1712_DSC_ADDR0 ; ptr =snd_ice1712_ds_read (ice, substream->number *2 , addr) - ice->playback_con_virt_addr[substream->number]; + ptr =bytes_to_frames (substream->runtime, ptr);if (ptr == substream->runtime->buffer_size) ptr =0 ; -return bytes_to_frames (substream->runtime, ptr); +return ptr; }static snd_pcm_uframes_t snd_ice1712_capture_pointer (struct snd_pcm_substream *substream)
@@ -718,9 +720,10 @@ static snd_pcm_uframes_t snd_ice1712_capif (!(snd_ice1712_read (ice,ICE1712_IREG_CAP_CTRL ) &1 ))return 0 ; ptr =inl (ICEREG (ice,CONCAP_ADDR )) - ice->capture_con_virt_addr; + ptr =bytes_to_frames (substream->runtime, ptr);if (ptr == substream->runtime->buffer_size) ptr =0 ; -return bytes_to_frames (substream->runtime, ptr); +return ptr; }static const struct snd_pcm_hardware snd_ice1712_playback = {
@@ -1114,9 +1117,10 @@ static snd_pcm_uframes_t snd_ice1712_plaif (!(inl (ICEMT (ice,PLAYBACK_CONTROL )) &ICE1712_PLAYBACK_START ))return 0 ; ptr = ice->playback_pro_size - (inw (ICEMT (ice,PLAYBACK_SIZE )) <<2 ); + ptr =bytes_to_frames (substream->runtime, ptr);if (ptr == substream->runtime->buffer_size) ptr =0 ; -return bytes_to_frames (substream->runtime, ptr); +return ptr; }static snd_pcm_uframes_t snd_ice1712_capture_pro_pointer (struct snd_pcm_substream *substream)
@@ -1127,9 +1131,10 @@ static snd_pcm_uframes_t snd_ice1712_capif (!(inl (ICEMT (ice,PLAYBACK_CONTROL )) &ICE1712_CAPTURE_START_SHADOW ))return 0 ; ptr = ice->capture_pro_size - (inw (ICEMT (ice,CAPTURE_SIZE )) <<2 ); + ptr =bytes_to_frames (substream->runtime, ptr);if (ptr == substream->runtime->buffer_size) ptr =0 ; -return bytes_to_frames (substream->runtime, ptr); +return ptr; }static const struct snd_pcm_hardware snd_ice1712_playback_pro = {
Greg Kroah-Hartman
maintainerPATCH 8/43 mfd: max8925: Fix possible NULL pointer dereference on i2c_new_dummy error
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
commit 96cf3dedc491d2f1f66cc26217f2b06b0c7b6797 upstream.
During probe the driver allocates dummy I2C devices for RTC and ADC with i2c_new_dummy() but it does not check the return value of this calls.
In case of error (i2c_new_device(): memory allocation failure or I2C address cannot be used) this function returns NULL which is later used by i2c_unregister_device().
If i2c_new_dummy() fails for RTC or ADC devices, fail also the probe for main MFD driver.
--- drivers/mfd/max8925-i2c.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/mfd/max8925-i2c.c +9 -0
@@ -156,9 +156,18 @@ static int __devinit max8925_probe(strucmutex_init (&chip->io_lock); chip->rtc =i2c_new_dummy (chip->i2c->adapter,RTC_I2C_ADDR ); +if (!chip->rtc) { +dev_err (chip->dev,"Failed to allocate I2C device for RTC\n" ); +return -ENODEV ; + }i2c_set_clientdata (chip->rtc, chip); chip->adc =i2c_new_dummy (chip->i2c->adapter,ADC_I2C_ADDR ); +if (!chip->adc) { +dev_err (chip->dev,"Failed to allocate I2C device for ADC\n" ); +i2c_unregister_device (chip->rtc); +return -ENODEV ; + }i2c_set_clientdata (chip->adc, chip);device_init_wakeup (&client->dev,1 );
Greg Kroah-Hartman
maintainerPATCH 9/43 mfd: max8998: Fix possible NULL pointer dereference on i2c_new_dummy error
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
commit ed26f87b9f71693a1d1ee85f5e6209601505080f upstream.
During probe the driver allocates dummy I2C device for RTC with i2c_new_dummy() but it does not check the return value of this call.
In case of error (i2c_new_device(): memory allocation failure or I2C address cannot be used) this function returns NULL which is later used by i2c_unregister_device().
If i2c_new_dummy() fails for RTC device, fail also the probe for main MFD driver.
--- drivers/mfd/max8998.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/mfd/max8998.c +4 -0
@@ -152,6 +152,10 @@ static int max8998_i2c_probe(struct i2c_mutex_init (&max8998->iolock); max8998->rtc =i2c_new_dummy (i2c->adapter,RTC_I2C_ADDR ); +if (!max8998->rtc) { +dev_err (&i2c->dev,"Failed to allocate I2C device for RTC\n" ); +return -ENODEV ; + }i2c_set_clientdata (max8998->rtc, max8998);max8998_irq_init (max8998);
Greg Kroah-Hartman
maintainerPATCH 10/43 mfd: max8997: Fix possible NULL pointer dereference on i2c_new_dummy error
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Krzysztof Kozlowski <[email protected]>
commit 97dc4ed3fa377ec91bb60ba98b70d645c2099384 upstream.
During probe the driver allocates dummy I2C devices for RTC, haptic and MUIC with i2c_new_dummy() but it does not check the return value of this calls.
In case of error (i2c_new_device(): memory allocation failure or I2C address cannot be used) this function returns NULL which is later used by i2c_unregister_device().
If i2c_new_dummy() fails for RTC, haptic or MUIC devices, fail also the probe for main MFD driver.
--- drivers/mfd/max8997.c | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+)
drivers/mfd/max8997.c +18 -0
@@ -149,10 +149,26 @@ static int max8997_i2c_probe(struct i2c_mutex_init (&max8997->iolock); max8997->rtc =i2c_new_dummy (i2c->adapter,I2C_ADDR_RTC ); +if (!max8997->rtc) { +dev_err (max8997->dev,"Failed to allocate I2C device for RTC\n" ); +return -ENODEV ; + }i2c_set_clientdata (max8997->rtc, max8997); + max8997->haptic =i2c_new_dummy (i2c->adapter,I2C_ADDR_HAPTIC ); +if (!max8997->haptic) { +dev_err (max8997->dev,"Failed to allocate I2C device for Haptic\n" ); + ret = -ENODEV ; + goto err_i2c_haptic; + }i2c_set_clientdata (max8997->haptic, max8997); + max8997->muic =i2c_new_dummy (i2c->adapter,I2C_ADDR_MUIC ); +if (!max8997->muic) { +dev_err (max8997->dev,"Failed to allocate I2C device for MUIC\n" ); + ret = -ENODEV ; + goto err_i2c_muic; + }i2c_set_clientdata (max8997->muic, max8997);pm_runtime_set_active (max8997->dev);
@@ -179,7 +195,9 @@ static int max8997_i2c_probe(struct i2c_ err_mfd:mfd_remove_devices (max8997->dev);i2c_unregister_device (max8997->muic); +err_i2c_muic:i2c_unregister_device (max8997->haptic); +err_i2c_haptic:i2c_unregister_device (max8997->rtc); err:kfree (max8997);
Greg Kroah-Hartman
maintainerPATCH 11/43 w1: fix w1_send_slave dropping a slave id
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Fries <[email protected]>
commit 6b355b33a64fd6d8ead2b838ec16fb9b551f71e8 upstream.
Previous logic,
if (avail > 8) {
store slave;
return;
}send data; clear;
The logic error is, if there isn't space send the buffer and clear, but the slave wasn't added to the now empty buffer loosing that slave id. It also should have been "if (avail >= 8)" because when it is 8, there is space.
Instead, if there isn't space send and clear the buffer, then there is always space for the slave id.
--- drivers/w1/w1_netlink.c | 27 ++++++++++++++------------- 1 file changed, 14 insertions(+), 13 deletions(-)
drivers/w1/w1_netlink.c +14 -13
@@ -54,28 +54,29 @@ static void w1_send_slave(struct w1_maststruct w1_netlink_msg *hdr = (struct w1_netlink_msg *)(msg +1 );struct w1_netlink_cmd *cmd = (struct w1_netlink_cmd *)(hdr +1 );int avail; +u64 *data;/* update kernel slave list */ w1_slave_found (dev, rn); avail = dev->priv_size - cmd->len; -if (avail >8 ) { -u64 *data = (void *)(cmd +1 ) + cmd->len; - - *data = rn; - cmd->len +=8 ; - hdr->len +=8 ; - msg->len +=8 ; -return ; +if (avail <8 ) { + msg->ack++; +cn_netlink_send (msg,0 ,GFP_KERNEL ); + + msg->len =sizeof (struct w1_netlink_msg ) + +sizeof (struct w1_netlink_cmd ); + hdr->len =sizeof (struct w1_netlink_cmd ); + cmd->len =0 ; } - msg->ack++; -cn_netlink_send (msg,0 ,GFP_KERNEL ); + data = (void *)(cmd +1 ) + cmd->len; - msg->len =sizeof (struct w1_netlink_msg ) +sizeof (struct w1_netlink_cmd ); - hdr->len =sizeof (struct w1_netlink_cmd ); - cmd->len =0 ; + *data = rn; + cmd->len +=8 ; + hdr->len +=8 ; + msg->len +=8 ; } static int w1_process_search_command(struct w1_master *dev, struct cn_msg *msg,
Greg Kroah-Hartman
maintainerPATCH 12/43 staging:serqt_usb2: Fix sparse warning restricted __le16 degrades to integer
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Himangi Saraogi <[email protected]>
commit abe5d64d1a74195a44cd14624f8178b9f48b7cc7 upstream.
This patch fixes the following sparse warning :drivers/staging/serqt_usb2/serqt_usb2.c:727:40: warning: restricted __le16 degrades to integer
--- drivers/staging/serqt_usb2/serqt_usb2.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/staging/serqt_usb2/serqt_usb2.c +1 -1
@@ -771,7 +771,7 @@ static int qt_startup(struct usb_serial goto startup_error; } -switch (serial->dev->descriptor.idProduct) { +switch (le16_to_cpu (serial->dev->descriptor.idProduct)) {case QUATECH_DSU100 :case QUATECH_QSU100 :case QUATECH_ESU100A :
Greg Kroah-Hartman
maintainerPATCH 13/43 staging: r8712u: Fix case where ethtype was never obtained and always be checked against 0
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Larry Finger <[email protected]>
commit f764cd68d9036498f08fe8834deb6a367b5c2542 upstream.
Zero-initializing ether_type masked that the ether type would never be obtained for 8021x packets and the comparison against eapol_type would always fail.
--- drivers/staging/rtl8712/rtl871x_recv.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
drivers/staging/rtl8712/rtl871x_recv.c +6 -7
@@ -253,7 +253,7 @@ union recv_frame *r8712_portctrl(structstruct sta_info *psta;struct sta_priv *pstapriv;union recv_frame *prtnframe; -u16 ether_type =0 ; +u16 ether_type; pstapriv = &adapter->stapriv; ptr =get_recvframe_data (precv_frame);
@@ -262,15 +262,14 @@ union recv_frame *r8712_portctrl(struct psta =r8712_get_stainfo (pstapriv, psta_addr); auth_alg = adapter->securitypriv.AuthAlgrthm;if (auth_alg ==2 ) { +/* get ether_type */ + ptr = ptr + pfhdr->attrib.hdrlen +LLC_HEADER_SIZE ; +memcpy (ðer_type, ptr,2 ); + ether_type =ntohs ((unsigned short )ether_type); +if ((psta !=NULL ) && (psta->ieee8021x_blocked)) {/* blocked * only accept EAPOL frame */ - prtnframe = precv_frame; -/*get ether_type */ - ptr = ptr + pfhdr->attrib.hdrlen + - pfhdr->attrib.iv_len +LLC_HEADER_SIZE ; -memcpy (ðer_type, ptr,2 ); - ether_type =ntohs ((unsigned short )ether_type);if (ether_type ==0x888e ) prtnframe = precv_frame;else {
Greg Kroah-Hartman
maintainerPATCH 14/43 x86-64, modify_ldt: Ban 16-bit segments on 64-bit kernels
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "H. Peter Anvin" <[email protected]>
commit b3b42ac2cbae1f3cecbb6229964a4d48af31d382 upstream.
The IRET instruction, when returning to a 16-bit segment, only restores the bottom 16 bits of the user space stack pointer. We have a software workaround for that ("espfix") for the 32-bit kernel, but it relies on a nonzero stack segment base which is not available in 32-bit mode.
Since 16-bit support is somewhat crippled anyway on a 64-bit kernel (no V86 mode), and most (if not quite all) 64-bit processors support virtualization for the users who really need it, simply reject attempts at creating a 16-bit segment when running on top of a 64-bit kernel.
--- arch/x86/kernel/ldt.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
arch/x86/kernel/ldt.c +11 -0
@@ -229,6 +229,17 @@ static int write_ldt(void __user *ptr, u } } +/* +* On x86-64 we do not support 16-bit segments due to +* IRET leaking the high bits of the kernel stack address. +*/ +#ifdef CONFIG_X86_64 +if (!ldt_info.seg_32bit) { + error = -EINVAL ; + goto out_unlock; + } +#endif +fill_ldt (&ldt, &ldt_info);if (oldmode) ldt.avl =0 ;
Greg Kroah-Hartman
maintainerPATCH 15/43 USB: fix crash during hotplug of PCI USB controller card
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alan Stern <[email protected]>
commit a2ff864b53eac9a0e9b05bfe9d1781ccd6c2af71 upstream.
The code in hcd-pci.c that matches up EHCI controllers with their companion UHCI or OHCI controllers assumes that the private drvdata fields don't get set too early. However, it turns out that this field gets set by usb_create_hcd(), before hcd-pci expects it, and this can result in a crash when two controllers are probed in parallel (as can happen when a new controller card is hotplugged).
The companions_rwsem lock was supposed to prevent this sort of thing, but usb_create_hcd() is called outside the scope of the rwsem.
A simple solution is to check that the root-hub pointer has been initialized as well as the drvdata field. This doesn't happen until usb_add_hcd() is called; that call and the check are both protected by the rwsem.
This patch should be applied to stable kernels from 3.10 onward.
--- drivers/usb/core/hcd-pci.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/usb/core/hcd-pci.c +1 -1
@@ -71,7 +71,7 @@ static void companion_common(struct pci_continue ; companion_hcd =pci_get_drvdata (companion); -if (!companion_hcd) +if (!companion_hcd || !companion_hcd->self.root_hub)continue ;/* For SET_HS_COMPANION, store a pointer to the EHCI bus in
Greg Kroah-Hartman
maintainerPATCH 16/43 nfsd4: session needs room for following op to error out
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "J. Bruce Fields" <[email protected]>
commit 4c69d5855a16f7378648c5733632628fa10431db upstream.
--- fs/nfsd/nfs4proc.c | 6 ++++++ 1 file changed, 6 insertions(+)
fs/nfsd/nfs4proc.c +6 -0
@@ -1245,6 +1245,12 @@ nfsd4_proc_compound(struct svc_rqst *rqs/* If op is non-idempotent */ if (opdesc->op_flags &OP_MODIFIES_SOMETHING ) { plen = opdesc->op_rsize_bop (rqstp, op); +/* +* If there's still another operation, make sure +* we'll have space to at least encode an error: +*/ +if (resp->opcnt < args->opcnt) + plen +=COMPOUND_ERR_SLACK_SPACE ; op->status =nfsd4_check_resp_size (resp, plen); }
Greg Kroah-Hartman
maintainerPATCH 17/43 nfsd4: buffer-length check for SUPPATTR_EXCLCREAT
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "J. Bruce Fields" <[email protected]>
commit de3997a7eeb9ea286b15879fdf8a95aae065b4f7 upstream.
This was an omission from 8c18f2052e756e7d5dea712fc6e7ed70c00e8a39 "nfsd41: SUPPATTR_EXCLCREAT attribute".
--- fs/nfsd/nfs4xdr.c | 2 ++ 1 file changed, 2 insertions(+)
fs/nfsd/nfs4xdr.c +2 -0
@@ -2410,6 +2410,8 @@ out_acl:WRITE64 (stat.ino); }if (bmval2 &FATTR4_WORD2_SUPPATTR_EXCLCREAT ) { +if ((buflen -=16 ) <0 ) + goto out_resource;WRITE32 (3 );WRITE32 (NFSD_SUPPATTR_EXCLCREAT_WORD0 );WRITE32 (NFSD_SUPPATTR_EXCLCREAT_WORD1 );
Greg Kroah-Hartman
maintainerPATCH 18/43 nfsd4: fix test_stateid error reply encoding
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "J. Bruce Fields" <[email protected]>
commit a11fcce1544df08c723d950ff0edef3adac40405 upstream.
If the entire operation fails then there's nothing to encode.
--- fs/nfsd/nfs4xdr.c | 3 +++ 1 file changed, 3 insertions(+)
fs/nfsd/nfs4xdr.c +3 -0
@@ -3408,6 +3408,9 @@ nfsd4_encode_test_stateid(struct nfsd4_cstruct nfsd4_test_stateid_id *stateid, *next;__be32 *p; +if (nfserr) +return nfserr; +RESERVE_SPACE (4 + (4 * test_stateid->ts_num_ids)); *p++ =htonl (test_stateid->ts_num_ids);
Greg Kroah-Hartman
maintainerPATCH 19/43 nfsd: notify_change needs elevated write count
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "J. Bruce Fields" <[email protected]>
commit 9f67f189939eccaa54f3d2c9cf10788abaf2d584 upstream.
Looks like this bug has been here since these write counts were introduced, not sure why it was just noticed now.
Thanks also to Jan Kara for pointing out the problem.
--- fs/nfsd/vfs.c | 9 +++++++++ 1 file changed, 9 insertions(+)
fs/nfsd/vfs.c +9 -0
@@ -406,6 +406,7 @@ nfsd_setattr(struct svc_rqst *rqstp, strumode_t ftype =0 ;__be32 err;int host_err; +bool get_write_count;int size_change =0 ;if (iap->ia_valid & (ATTR_ATIME |ATTR_MTIME |ATTR_SIZE ))
@@ -413,10 +414,18 @@ nfsd_setattr(struct svc_rqst *rqstp, strif (iap->ia_valid &ATTR_SIZE ) ftype =S_IFREG ; +/* Callers that do fh_verify should do the fh_want_write: */ + get_write_count = !fhp->fh_dentry; +/* Get inode */ err =fh_verify (rqstp, fhp, ftype, accmode);if (err) goto out; +if (get_write_count) { + host_err =fh_want_write (fhp); +if (host_err) +return nfserrno (host_err); + } dentry = fhp->fh_dentry; inode = dentry->d_inode;
Greg Kroah-Hartman
maintainerPATCH 20/43 nfsd4: fix setclientid encode size
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "J. Bruce Fields" <[email protected]>
commit 480efaee085235bb848f1063f959bf144103c342 upstream.
--- fs/nfsd/nfs4proc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/nfsd/nfs4proc.c +2 -1
@@ -1418,7 +1418,8 @@ static inline u32 nfsd4_setattr_rsize(ststatic inline u32 nfsd4_setclientid_rsize (struct svc_rqst *rqstp,struct nfsd4_op *op) { -return (op_encode_hdr_size +2 +1024 ) *sizeof (__be32); +return (op_encode_hdr_size +2 +XDR_QUADLEN (NFS4_VERIFIER_SIZE )) * +sizeof (__be32); }static inline u32 nfsd4_write_rsize (struct svc_rqst *rqstp,struct nfsd4_op *op)
Greg Kroah-Hartman
maintainerPATCH 21/43 IB/ipath: Fix potential buffer overrun in sending diag packet routine
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dennis Dalessandro <[email protected]>
commit a2cb0eb8a64adb29a99fd864013de957028f36ae upstream.
Guard against a potential buffer overrun. The size to read from the user is passed in, and due to the padding that needs to be taken into account, as well as the place holder for the ICRC it is possible to overflow the 32bit value which would cause more data to be copied from user space than is allocated in the buffer.
--- drivers/infiniband/hw/ipath/ipath_diag.c | 66 +++++++++++-------------------- 1 file changed, 25 insertions(+), 41 deletions(-)
drivers/infiniband/hw/ipath/ipath_diag.c +25 -41
@@ -326,7 +326,7 @@ static ssize_t ipath_diagpkt_write(struc size_t count, loff_t *off) { u32 __iomem *piobuf; -u32 plen, clen, pbufn; +u32 plen, pbufn, maxlen_reserve;struct ipath_diag_pkt odp;struct ipath_diag_xpkt dp;u32 *tmpbuf =NULL ;
@@ -335,51 +335,29 @@ static ssize_t ipath_diagpkt_write(strucu64 val;u32 l_state, lt_state;/* LinkState, LinkTrainingState */ -if (count <sizeof (odp)) { - ret = -EINVAL ; - goto bail; - }if (count ==sizeof (dp)) {if (copy_from_user (&dp, data,sizeof (dp))) { ret = -EFAULT ; goto bail; } - }else if (copy_from_user (&odp, data,sizeof (odp))) { - ret = -EFAULT ; + }else if (count ==sizeof (odp)) { +if (copy_from_user (&odp, data,sizeof (odp))) { + ret = -EFAULT ; + goto bail; + } + }else { + ret = -EINVAL ; goto bail; } -/* -* Due to padding/alignment issues (lessened with new struct) -* the old and new structs are the same length. We need to -* disambiguate them, which we can do because odp.len has never -* been less than the total of LRH+BTH+DETH so far, while -* dp.unit (same offset) unit is unlikely to get that high. -* Similarly, dp.data, the pointer to user at the same offset -* as odp.unit, is almost certainly at least one (512byte)page -* "above" NULL. The if-block below can be omitted if compatibility -* between a new driver and older diagnostic code is unimportant. -* compatibility the other direction (new diags, old driver) is -* handled in the diagnostic code, with a warning. -*/ -if (dp.unit >=20 && dp.data <512 ) { -/* very probable version mismatch. Fix it up */ -memcpy (&odp, &dp,sizeof (odp)); -/* We got a legacy dp, copy elements to dp */ - dp.unit = odp.unit; - dp.data = odp.data; - dp.len = odp.len; - dp.pbc_wd =0 ;/* Indicate we need to compute PBC wd */ - } -/* send count must be an exact number of dwords */ if (dp.len &3 ) { ret = -EINVAL ; goto bail; } - clen = dp.len >>2 ; + plen = dp.len >>2 ; dd =ipath_lookup (dp.unit); if (!dd || !(dd->ipath_flags & IPATH_PRESENT) ||
@@ -422,16 +400,22 @@ static ssize_t ipath_diagpkt_write(struc goto bail; } -/* need total length before first word written */ -/* +1 word is for the qword padding */ - plen =sizeof (u32) + dp.len; - -if ((plen +4 ) > dd->ipath_ibmaxlen) { +/* +* need total length before first word written, plus 2 Dwords. One Dword +* is for padding so we get the full user data when not aligned on +* a word boundary. The other Dword is to make sure we have room for the +* ICRC which gets tacked on later. +*/ + maxlen_reserve =2 *sizeof (u32); +if (dp.len > dd->ipath_ibmaxlen - maxlen_reserve) {ipath_dbg ("Pkt len 0x%x > ibmaxlen %x\n" , - plen -4 , dd->ipath_ibmaxlen); + dp.len, dd->ipath_ibmaxlen); ret = -EINVAL ; - goto bail;/* before writing pbc */ + goto bail; } + + plen =sizeof (u32) + dp.len; + tmpbuf =vmalloc (plen);if (!tmpbuf) { dev_info(&dd->pcidev->dev, "Unable to allocate tmp buffer, "
@@ -473,11 +457,11 @@ static ssize_t ipath_diagpkt_write(struc*/ if (dd->ipath_flags &IPATH_PIO_FLUSH_WC ) {ipath_flush_wc (); -__iowrite32_copy (piobuf +2 , tmpbuf, clen -1 ); +__iowrite32_copy (piobuf +2 , tmpbuf, plen -1 );ipath_flush_wc (); -__raw_writel (tmpbuf[clen -1 ], piobuf + clen +1 ); +__raw_writel (tmpbuf[plen -1 ], piobuf + plen +1 ); }else -__iowrite32_copy (piobuf +2 , tmpbuf, clen); +__iowrite32_copy (piobuf +2 , tmpbuf, plen);ipath_flush_wc ();
Greg Kroah-Hartman
maintainerPATCH 22/43 IB/nes: Return an error on ib_copy_from_udata() failure instead of NULL
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yann Droneaud <[email protected]>
commit 9d194d1025f463392feafa26ff8c2d8247f71be1 upstream.
In case of error while accessing to userspace memory, function nes_create_qp() returns NULL instead of an error code wrapped through ERR_PTR(). But NULL is not expected by ib_uverbs_create_qp(), as it check for error with IS_ERR().
As page 0 is likely not mapped, it is going to trigger an Oops when the kernel will try to dereference NULL pointer to access to struct ib_qp's fields.
In some rare cases, page 0 could be mapped by userspace, which could turn this bug to a vulnerability that could be exploited: the function pointers in struct ib_device will be under userspace total control.
This was caught when using spatch (aka. coccinelle) to rewrite calls to ib_copy_{from,to}_udata().
--- drivers/infiniband/hw/nes/nes_verbs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/infiniband/hw/nes/nes_verbs.c +1 -1
@@ -1183,7 +1183,7 @@ static struct ib_qp *nes_create_qp(strucnes_free_resource (nesadapter, nesadapter->allocated_qps, qp_num);kfree (nesqp->allocated_buffer);nes_debug (NES_DBG_QP ,"ib_copy_from_udata() Failed \n" ); -return NULL ; +return ERR_PTR (-EFAULT ); }if (req.user_wqe_buffers) { virt_wqs =1 ;
Greg Kroah-Hartman
maintainerPATCH 23/43 IB/mthca: Return an error on ib_copy_to_udata() failure
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yann Droneaud <[email protected]>
commit 08e74c4b00c30c232d535ff368554959403d0432 upstream.
In case of error when writing to userspace, the function mthca_create_cq() does not set an error code before following its error path.
This patch sets the error code to -EFAULT when ib_copy_to_udata() fails.
This was caught when using spatch (aka. coccinelle) to rewrite call to ib_copy_{from,to}_udata().
--- drivers/infiniband/hw/mthca/mthca_provider.c | 1 + 1 file changed, 1 insertion(+)
drivers/infiniband/hw/mthca/mthca_provider.c +1 -0
@@ -695,6 +695,7 @@ static struct ib_cq *mthca_create_cq(strif (context &&ib_copy_to_udata (udata, &cq->cqn,sizeof (__u32))) {mthca_free_cq (to_mdev (ibdev), cq); + err = -EFAULT ; goto err_free; }
Greg Kroah-Hartman
maintainerPATCH 24/43 IB/ehca: Returns an error on ib_copy_to_udata() failure
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yann Droneaud <[email protected]>
commit 5bdb0f02add5994b0bc17494f4726925ca5d6ba1 upstream.
In case of error when writing to userspace, function ehca_create_cq() does not set an error code before following its error path.
This patch sets the error code to -EFAULT when ib_copy_to_udata() fails.
This was caught when using spatch (aka. coccinelle) to rewrite call to ib_copy_{from,to}_udata().
--- drivers/infiniband/hw/ehca/ehca_cq.c | 1 + 1 file changed, 1 insertion(+)
drivers/infiniband/hw/ehca/ehca_cq.c +1 -0
@@ -296,6 +296,7 @@ struct ib_cq *ehca_create_cq(struct ib_d (my_cq->galpas.user.fw_handle & (PAGE_SIZE -1 ));if (ib_copy_to_udata (udata, &resp,sizeof (resp))) {ehca_err (device,"Copy to udata failed." ); + cq =ERR_PTR (-EFAULT ); goto create_cq_exit4; } }
Greg Kroah-Hartman
maintainerPATCH 25/43 ib_srpt: Use correct ib_sg_dma primitives
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mike Marciniszyn <[email protected]>
commit b076808051f2c80d38e03fb2f1294f525c7a446d upstream.
The code was incorrectly using sg_dma_address() and sg_dma_len() instead of ib_sg_dma_address() and ib_sg_dma_len().
This prevents srpt from functioning with the
Intel HCA and indeed will corrupt memory
badly.
--- drivers/infiniband/ulp/srpt/ib_srpt.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-)
drivers/infiniband/ulp/srpt/ib_srpt.c +10 -6
@@ -1078,6 +1078,7 @@ static void srpt_unmap_sg_to_ib_sge(strustatic int srpt_map_sg_to_ib_sge (struct srpt_rdma_ch *ch,struct srpt_send_ioctx *ioctx) { +struct ib_device *dev = ch->sport->sdev->device;struct se_cmd *cmd;struct scatterlist *sg, *sg_orig;int sg_cnt;
@@ -1125,7 +1126,7 @@ static int srpt_map_sg_to_ib_sge(struct db = ioctx->rbufs; tsize = cmd->data_length; - dma_len =sg_dma_len (&sg[0 ]); + dma_len =ib_sg_dma_len (dev, &sg[0 ]); riu = ioctx->rdma_ius;/*
@@ -1156,7 +1157,8 @@ static int srpt_map_sg_to_ib_sge(struct ++j;if (j < count) { sg =sg_next (sg); - dma_len =sg_dma_len (sg); + dma_len =ib_sg_dma_len ( + dev, sg); } } }else {
@@ -1193,8 +1195,8 @@ static int srpt_map_sg_to_ib_sge(struct tsize = cmd->data_length; riu = ioctx->rdma_ius; sg = sg_orig; - dma_len =sg_dma_len (&sg[0 ]); - dma_addr =sg_dma_address (&sg[0 ]); + dma_len =ib_sg_dma_len (dev, &sg[0 ]); + dma_addr =ib_sg_dma_address (dev, &sg[0 ]);/* this second loop is really mapped sg_addres to rdma_iu->ib_sge */ for (i = 0, j = 0;
@@ -1217,8 +1219,10 @@ static int srpt_map_sg_to_ib_sge(struct ++j;if (j < count) { sg =sg_next (sg); - dma_len =sg_dma_len (sg); - dma_addr =sg_dma_address (sg); + dma_len =ib_sg_dma_len ( + dev, sg); + dma_addr =ib_sg_dma_address ( + dev, sg); } } }else {
Greg Kroah-Hartman
maintainerPATCH 26/43 SCSI: arcmsr: upper 32 of dma address lost
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit e2c70425f05219b142b3a8a9489a622c736db39d upstream.
The original code always set the upper 32 bits to zero because it was doing a shift of the wrong variable.
--- drivers/scsi/arcmsr/arcmsr_hba.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
drivers/scsi/arcmsr/arcmsr_hba.c +3 -4
@@ -2500,16 +2500,15 @@ static int arcmsr_polling_ccbdone(structstatic int arcmsr_iop_confirm (struct AdapterControlBlock *acb) {uint32_t cdb_phyaddr, cdb_phyaddr_hi32; -dma_addr_t dma_coherent_handle; +/* ******************************************************************** ** here we need to tell iop 331 our freeccb.HighPart ** if freeccb.HighPart is not zero ******************************************************************** */ - dma_coherent_handle = acb->dma_coherent_handle; - cdb_phyaddr = (uint32_t )(dma_coherent_handle); - cdb_phyaddr_hi32 = (uint32_t )((cdb_phyaddr >>16 ) >>16 ); + cdb_phyaddr =lower_32_bits (acb->dma_coherent_handle); + cdb_phyaddr_hi32 =upper_32_bits (acb->dma_coherent_handle); acb->cdb_phyaddr_hi32 = cdb_phyaddr_hi32;/* ***********************************************************************
Greg Kroah-Hartman
maintainerPATCH 27/43 iscsi-target: Fix ERL=2 ASYNC_EVENT connection pointer bug
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nicholas Bellinger <[email protected]>
commit d444edc679e7713412f243b792b1f964e5cff1e1 upstream.
This patch fixes a long-standing bug in iscsit_build_conn_drop_async_message() where during ERL=2 connection recovery, a bogus conn_p pointer could end up being used to send the ISCSI_OP_ASYNC_EVENT + DROPPING_CONNECTION notifying the initiator that cmd->logout_cid has failed.
The bug was manifesting itself as an OOPs in iscsit_allocate_cmd() with a bogus conn_p pointer in iscsit_build_conn_drop_async_message().
--- drivers/target/iscsi/iscsi_target.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/target/iscsi/iscsi_target.c +3 -1
@@ -2352,6 +2352,7 @@ static void iscsit_build_conn_drop_async {struct iscsi_cmd *cmd;struct iscsi_conn *conn_p; +bool found = false;/* * Only send a Asynchronous Message on connections whos network
@@ -2360,11 +2361,12 @@ static void iscsit_build_conn_drop_asynclist_for_each_entry (conn_p, &conn->sess->sess_conn_list, conn_list) {if (conn_p->conn_state ==TARG_CONN_STATE_LOGGED_IN ) {iscsit_inc_conn_usage_count (conn_p); + found = true;break ; } } -if (!conn_p) +if (!found)return ; cmd =iscsit_allocate_cmd (conn_p,GFP_ATOMIC );
Greg Kroah-Hartman
maintainerPATCH 28/43 target/tcm_fc: Fix use-after-free of ft_tpg
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andy Grover <[email protected]>
commit 2c42be2dd4f6586728dba5c4e197afd5cfaded78 upstream.
ft_del_tpg checks tpg->tport is set before unlinking the tpg from the tport when the tpg is being removed. Set this pointer in ft_tport_create, or the unlinking won't happen in ft_del_tpg and tport->tpg will reference a deleted object.
This patch sets tpg->tport in ft_tport_create, because that's what ft_del_tpg checks, and is the only way to get back to the tport to clear tport->tpg.
The bug was occuring when:
- lport created, tport (our per-lport, per-provider context) is allocated.
tport->tpg = NULL
- tpg created
- a PRLI is received. ft_tport_create is called, tpg is found and tport->tpg is set
- tpg removed. ft_tpg is freed in ft_del_tpg. Since tpg->tport was not set, tport->tpg is not cleared and points at freed memory
- Future calls to ft_tport_create return tport via first conditional, instead of searching for new tpg by calling ft_lport_find_tpg. tport->tpg is still invalid, and will access freed memory.
see https://bugzilla.redhat.com/show_bug.cgi?id=1071340
--- drivers/target/tcm_fc/tfc_sess.c | 1 + 1 file changed, 1 insertion(+)
drivers/target/tcm_fc/tfc_sess.c +1 -0
@@ -69,6 +69,7 @@ static struct ft_tport *ft_tport_create(if (tport) { tport->tpg = tpg; + tpg->tport = tport;return tport; }
Greg Kroah-Hartman
maintainerPATCH 29/43 reiserfs: fix race in readdir
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jeff Mahoney <[email protected]>
commit 01d8885785a60ae8f4c37b0ed75bdc96d0fc6a44 upstream.
jdm-20004 reiserfs_delete_xattrs: Couldn't delete all xattrs (-2)
The -ENOENT is due to readdir calling dir_emit on the same entry twice.
If the dir_emit callback sleeps and the tree is changed underneath us, we won't be able to trust deh_offset(deh) anymore. We need to save next_pos before we might sleep so we can find the next entry.
--- fs/reiserfs/dir.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/reiserfs/dir.c +4 -2
@@ -128,6 +128,7 @@ int reiserfs_readdir_dentry(struct dentrchar *d_name;off_t d_off;ino_t d_ino; +loff_t cur_pos =deh_offset (deh);if (!de_visible (deh))/* it is hidden entry */
@@ -200,8 +201,9 @@ int reiserfs_readdir_dentry(struct dentrif (local_buf != small_buf) {kfree (local_buf); } -// next entry should be looked for with such offset - next_pos =deh_offset (deh) +1 ; + +/* deh_offset(deh) may be invalid now. */ + next_pos = cur_pos +1 ;if (item_moved (&tmp_ih, &path_to_entry)) { goto research;
Greg Kroah-Hartman
maintainerPATCH 30/43 usb: musb: set TXMAXP and AUTOSET for full speed bulk in device mode
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: supriya karanth <[email protected]>
commit bb3a2ef2eb8cfaea335dcb3426350df7f3d48069 upstream.
The TXMAXP register is not set correctly for full speed bulk case when the can_bulk_split() is used. Without this PIO transfers will not take place correctly
The "mult" factor needs to be updated correctly for the can_bulk_split() case
The AUTOSET bit in the TXCSR is not being set if the "mult" factor is greater than 0 for the High Bandwidth ISO case. But the "mult" factor is also greater than 0 in case of Full speed bulk transfers with the packet splitting in TXMAXP register
Without the AUTOSET the DMA transfers will not progress in mode1
[ [email protected] : add braces to both branches ]
--- drivers/usb/musb/musb_gadget.c | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-)
drivers/usb/musb/musb_gadget.c +19 -3
@@ -401,7 +401,19 @@ static void txstate(struct musb *musb, s csr |= (MUSB_TXCSR_DMAENAB |MUSB_TXCSR_DMAMODE |MUSB_TXCSR_MODE ); -if (!musb_ep->hb_mult) +/* +* Enable Autoset according to table +* below +* bulk_split hb_mult Autoset_Enable +* 0 0 Yes(Normal) +* 0 >0 No(High BW ISO) +* 1 0 Yes(HS bulk) +* 1 >0 Yes(FS bulk) +*/ +if (!musb_ep->hb_mult || + (musb_ep->hb_mult && +can_bulk_split (musb, + musb_ep->type))) csr |=MUSB_TXCSR_AUTOSET ; } csr &= ~MUSB_TXCSR_P_UNDERRUN ;
@@ -1100,11 +1112,15 @@ static int musb_gadget_enable(struct usb/* Set TXMAXP with the FIFO size of the endpoint * to disable double buffering mode. */ -if (musb->double_buffer_not_ok) +if (musb->double_buffer_not_ok) {musb_writew (regs,MUSB_TXMAXP , hw_ep->max_packet_sz_tx); -else + }else { +if (can_bulk_split (musb, musb_ep->type)) + musb_ep->hb_mult = (hw_ep->max_packet_sz_tx / + musb_ep->packet_sz) -1 ;musb_writew (regs,MUSB_TXMAXP , musb_ep->packet_sz | (musb_ep->hb_mult <<11 )); + } csr =MUSB_TXCSR_MODE |MUSB_TXCSR_CLRDATATOG ; if (musb_readw(regs, MUSB_TXCSR)
Greg Kroah-Hartman
maintainerPATCH 31/43 xhci: extend quirk for Renesas cards
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Igor Gnatenko <[email protected]>
commit 6db249ebefc6bf5c39f35dfaacc046d8ad3ffd70 upstream.
After suspend another Renesas PCI-X USB 3.0 card doesn't work. [root@fedora-20 ~]# lspci -vmnnd 1912:
Device: 03:00.0
Class: USB controller [0c03]
Vendor: Renesas Technology Corp. [1912]
Device: uPD720202 USB 3.0 Host Controller [0015]
SVendor: Renesas Technology Corp. [1912]
SDevice: uPD720202 USB 3.0 Host Controller [0015]
Rev: 02
ProgIf: 30
This patch should be applied to stable kernel 3.14 that contain the commit 1aa9578c1a9450fb21501c4f549f5b1edb557e6d "xhci: Fix resume issues on Renesas chips in Samsung laptops"
Reference: http://redmine.russianfedora.pro/issues/1315
--- drivers/usb/host/xhci-pci.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-)
drivers/usb/host/xhci-pci.c +1 -3
@@ -135,9 +135,7 @@ static void xhci_pci_quirks(struct devic xhci->quirks |=XHCI_TRUST_TX_LENGTH ; }if (pdev->vendor ==PCI_VENDOR_ID_RENESAS && - pdev->device ==0x0015 && - pdev->subsystem_vendor ==PCI_VENDOR_ID_SAMSUNG && - pdev->subsystem_device ==0xc0cd ) + pdev->device ==0x0015 ) xhci->quirks |=XHCI_RESET_ON_RESUME ;if (pdev->vendor ==PCI_VENDOR_ID_VIA ) xhci->quirks |=XHCI_RESET_ON_RESUME ;
Greg Kroah-Hartman
maintainerPATCH 32/43 usb/xhci: fix compilation warning when !CONFIG_PCI && !CONFIG_PM
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Cohen <[email protected]>
commit 01bb59ebffdec314da8da66266edf29529372f9b upstream.
When CONFIG_PCI and CONFIG_PM are not selected, xhci.c gets this warning:drivers/usb/host/xhci.c:409:13: warning: ‘xhci_msix_sync_irqs’ defined but not used [-Wunused-function]
Instead of creating nested #ifdefs, this patch fixes it by defining the xHCI PCI stubs as inline.
This warning has been in since 3.2 kernel and was caused by commit 421aa841a134f6a743111cf44d0c6d3b45e3cf8c "usb/xhci: hide MSI code behind PCI bars", but wasn't noticed until 3.13 when a configuration with these options was tried
--- drivers/usb/host/xhci.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/usb/host/xhci.c +3 -3
@@ -394,16 +394,16 @@ static int xhci_try_enable_msi(struct us#else -static int xhci_try_enable_msi (struct usb_hcd *hcd) +static inline int xhci_try_enable_msi (struct usb_hcd *hcd) {return 0 ; } -static void xhci_cleanup_msix (struct xhci_hcd *xhci) +static inline void xhci_cleanup_msix (struct xhci_hcd *xhci) { } -static void xhci_msix_sync_irqs (struct xhci_hcd *xhci) +static inline void xhci_msix_sync_irqs (struct xhci_hcd *xhci) { }
Greg Kroah-Hartman
maintainerPATCH 33/43 usb: dwc3: fix wrong bit mask in dwc3_event_devt
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Huang Rui <[email protected]>
commit 06f9b6e59661cee510b04513b13ea7927727d758 upstream.
Around DWC USB3 2.30a release another bit has been added to the Device-Specific Event (DEVT) Event Information (EvtInfo) bitfield.
Because of that, what used to be 8 bits long, has become 9 bits long.
Per dwc3 2.30a+ spec in the Device-Specific Event (DEVT), the field of Event Information Bits(EvtInfo) uses [24:16] bits, and it has 9 bits not 8 bits. And the following reserved field uses [31:25] bits not [31:24] bits, and it has 7 bits.
So in dwc3_event_devt, the bit mask should be:event_info [24:16] 9 bitsreserved31_25 [31:25] 7 bits
This patch makes sure that newer core releases will work fine with Linux and that we will decode the event information properly on new core releases.
[ [email protected] : improve commit log a bit ]
--- drivers/usb/dwc3/core.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/usb/dwc3/core.h +3 -3
@@ -719,15 +719,15 @@ struct dwc3_event_depevt {* 12 - VndrDevTstRcved * @reserved15_12: Reserved, not used * @event_info: Information about this event -* @reserved31_24: Reserved, not used +* @reserved31_25: Reserved, not used */ struct dwc3_event_devt {u32 one_bit:1 ;u32 device_event:7 ;u32 type:4 ;u32 reserved15_12:4 ; -u32 event_info:8 ; -u32 reserved31_24:8 ; +u32 event_info:9 ; +u32 reserved31_25:7 ; } __packed;/**
Greg Kroah-Hartman
maintainerPATCH 34/43 hvc: ensure hvc_init is only ever called once in hvc_console.c
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Paul Gortmaker <[email protected]>
commit f76a1cbed18c86e2d192455f0daebb48458965f3 upstream.
Commit 3e6c6f630a5282df8f3393a59f10eb9c56536d23 ("Delay creation of khcvd thread") moved the call of hvc_init from being a device_initcall into hvc_alloc, and used a non-null hvc_driver as indication of whether hvc_init had already been called.
The problem with this is that hvc_driver is only assigned a value at the bottom of hvc_init, and so there is a window where multiple hvc_alloc calls can be in progress at the same time and hence try and call hvc_init multiple times. Previously the use of device_init guaranteed that hvc_init was only called once.
This manifests itself as sporadic instances of two hvc_init calls racing each other, and with the loser of the race getting -EBUSY from tty_register_driver() and hence that virtual console fails:
Couldn't register hvc console driver virtio-ports vport0p1: error -16 allocating hvc for port
Here we add an atomic_t to guarantee we'll never run hvc_init twice.
--- drivers/tty/hvc/hvc_console.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/tty/hvc/hvc_console.c +5 -1
@@ -31,6 +31,7 @@#include <linux/list.h> #include <linux/module.h> #include <linux/major.h> +#include <linux/atomic.h> #include <linux/sysrq.h> #include <linux/tty.h> #include <linux/tty_flip.h>
@@ -70,6 +71,9 @@ static struct task_struct *hvc_task;/* Picks up late kicks after list walk but before schedule() */ static int hvc_kicked; +/* hvc_init is triggered from hvc_alloc, i.e. only when actually used */ +static atomic_t hvc_needs_init__read_mostly =ATOMIC_INIT (-1 ); +static int hvc_init (void );#ifdef CONFIG_MAGIC_SYSRQ
@@ -825,7 +829,7 @@ struct hvc_struct *hvc_alloc(uint32_t vtint i;/* We wait until a driver actually comes along */ -if (!hvc_driver) { +if (atomic_inc_not_zero (&hvc_needs_init)) {int err =hvc_init ();if (err)return ERR_PTR (err);
Greg Kroah-Hartman
maintainerPATCH 35/43 USB: unbind all interfaces before rebinding any
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alan Stern <[email protected]>
commit 6aec044cc2f5670cf3b143c151c8be846499bd15 upstream.
When a driver doesn't have pre_reset, post_reset, or reset_resume methods, the USB core unbinds that driver when its device undergoes a reset or a reset-resume, and then rebinds it afterward.
The existing straightforward implementation can lead to problems, because each interface gets unbound and rebound before the next interface is handled. If a driver claims additional interfaces, the claim may fail because the old binding instance may still own the additional interface when the new instance tries to claim it.
This patch fixes the problem by first unbinding all the interfaces that are marked (i.e., their needs_binding flag is set) and then rebinding all of them.
The patch also makes the helper functions in driver.c a little more uniform and adjusts some out-of-date comments.
--- drivers/usb/core/driver.c | 94 +++++++++++++++++++++++++++------------------- drivers/usb/core/hub.c | 5 +- drivers/usb/core/usb.h | 2 3 files changed, 60 insertions(+), 41 deletions(-)
drivers/usb/core/driver.c +56 -38
@@ -914,8 +914,7 @@ EXPORT_SYMBOL_GPL(usb_deregister);* it doesn't support pre_reset/post_reset/reset_resume or * because it doesn't support suspend/resume. * -* The caller must hold @intf's device's lock, but not its pm_mutex -* and not @intf->dev.sem. +* The caller must hold @intf's device's lock, but not @intf's lock. */ void usb_forced_unbind_intf (struct usb_interface *intf) {
@@ -928,16 +927,37 @@ void usb_forced_unbind_intf(struct usb_i intf->needs_binding =1 ; } +/* +* Unbind drivers for @udev's marked interfaces. These interfaces have +* the needs_binding flag set, for example by usb_resume_interface(). +* +* The caller must hold @udev's device lock. +*/ +static void unbind_marked_interfaces (struct usb_device *udev) +{ +struct usb_host_config *config; +int i; +struct usb_interface *intf; + + config = udev->actconfig; +if (config) { +for (i =0 ; i < config->desc.bNumInterfaces; ++i) { + intf = config->interface[i]; +if (intf->dev.driver && intf->needs_binding) +usb_forced_unbind_intf (intf); + } + } +} +/* Delayed forced unbinding of a USB interface driver and scan * for rebinding. * -* The caller must hold @intf's device's lock, but not its pm_mutex -* and not @intf->dev.sem. +* The caller must hold @intf's device's lock, but not @intf's lock. * * Note: Rebinds will be skipped if a system sleep transition is in * progress and the PM "complete" callback hasn't occurred yet. */ -void usb_rebind_intf (struct usb_interface *intf) +static void usb_rebind_intf (struct usb_interface *intf) {int rc;
@@ -954,68 +974,66 @@ void usb_rebind_intf(struct usb_interfac } } -#ifdef CONFIG_PM - -/* Unbind drivers for @udev's interfaces that don't support suspend/resume -* There is no check for reset_resume here because it can be determined -* only during resume whether reset_resume is needed. +/* +* Rebind drivers to @udev's marked interfaces. These interfaces have +* the needs_binding flag set. * * The caller must hold @udev's device lock. */ -static void unbind_no_pm_drivers_interfaces (struct usb_device *udev) +static void rebind_marked_interfaces (struct usb_device *udev) {struct usb_host_config *config;int i;struct usb_interface *intf; -struct usb_driver *drv; config = udev->actconfig;if (config) {for (i =0 ; i < config->desc.bNumInterfaces; ++i) { intf = config->interface[i]; - -if (intf->dev.driver) { - drv =to_usb_driver (intf->dev.driver); -if (!drv->suspend || !drv->resume) -usb_forced_unbind_intf (intf); - } +if (intf->needs_binding) +usb_rebind_intf (intf); } } } -/* Unbind drivers for @udev's interfaces that failed to support reset-resume. -* These interfaces have the needs_binding flag set by usb_resume_interface(). +/* +* Unbind all of @udev's marked interfaces and then rebind all of them. +* This ordering is necessary because some drivers claim several interfaces +* when they are first probed. * * The caller must hold @udev's device lock. */ -static void unbind_no_reset_resume_drivers_interfaces (struct usb_device *udev) +void usb_unbind_and_rebind_marked_interfaces (struct usb_device *udev) { -struct usb_host_config *config; -int i; -struct usb_interface *intf; - - config = udev->actconfig; -if (config) { -for (i =0 ; i < config->desc.bNumInterfaces; ++i) { - intf = config->interface[i]; -if (intf->dev.driver && intf->needs_binding) -usb_forced_unbind_intf (intf); - } - } +unbind_marked_interfaces (udev); +rebind_marked_interfaces (udev); } -static void do_rebind_interfaces (struct usb_device *udev) +#ifdef CONFIG_PM + +/* Unbind drivers for @udev's interfaces that don't support suspend/resume +* There is no check for reset_resume here because it can be determined +* only during resume whether reset_resume is needed. +* +* The caller must hold @udev's device lock. +*/ +static void unbind_no_pm_drivers_interfaces (struct usb_device *udev) {struct usb_host_config *config;int i;struct usb_interface *intf; +struct usb_driver *drv; config = udev->actconfig;if (config) {for (i =0 ; i < config->desc.bNumInterfaces; ++i) { intf = config->interface[i]; -if (intf->needs_binding) -usb_rebind_intf (intf); + +if (intf->dev.driver) { + drv =to_usb_driver (intf->dev.driver); +if (!drv->suspend || !drv->resume) +usb_forced_unbind_intf (intf); + } } } }
@@ -1333,7 +1351,7 @@ int usb_resume_complete(struct device *d* whose needs_binding flag is set */ if (udev->state !=USB_STATE_NOTATTACHED ) -do_rebind_interfaces (udev); +rebind_marked_interfaces (udev);return 0 ; }
@@ -1355,7 +1373,7 @@ int usb_resume(struct device *dev, pm_mepm_runtime_disable (dev);pm_runtime_set_active (dev);pm_runtime_enable (dev); -unbind_no_reset_resume_drivers_interfaces (udev); +unbind_marked_interfaces (udev); }/* Avoid PM error messages for devices disconnected while suspended
drivers/usb/core/hub.c +3 -2
@@ -4313,10 +4313,11 @@ int usb_reset_device(struct usb_device *else if (cintf->condition ==USB_INTERFACE_BOUND ) rebind =1 ; +if (rebind) + cintf->needs_binding =1 ; } -if (ret ==0 && rebind) -usb_rebind_intf (cintf); } +usb_unbind_and_rebind_marked_interfaces (udev); }usb_autosuspend_device (udev);
drivers/usb/core/usb.h +1 -1
@@ -42,7 +42,7 @@ extern int usb_match_one_id_intf(structextern int usb_match_device (struct usb_device *dev,const struct usb_device_id *id);extern void usb_forced_unbind_intf (struct usb_interface *intf); -extern void usb_rebind_intf (struct usb_interface *intf); +extern void usb_unbind_and_rebind_marked_interfaces (struct usb_device *udev);extern int usb_hub_claim_port (struct usb_device *hdev,unsigned port,void *owner);
Greg Kroah-Hartman
maintainerPATCH 36/43 sh: fix format string bug in stack tracer
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matt Fleming <[email protected]>
commit a0c32761e73c9999cbf592b702f284221fea8040 upstream.
Kees reported the following error:
arch/sh/kernel/dumpstack.c: In function 'print_trace_address':
arch/sh/kernel/dumpstack.c:118:2: error: format not a string literal and no format arguments [-Werror=format-security]
Use the "%s" format so that it's impossible to interpret 'data' as a format string.
--- arch/sh/kernel/dumpstack.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/sh/kernel/dumpstack.c +1 -1
@@ -80,7 +80,7 @@ static int print_trace_stack(void *data,*/ static void print_trace_address (void *data,unsigned long addr,int reliable) { -printk (data); +printk ("%s" , (char *)data);printk_address (addr, reliable); }
Greg Kroah-Hartman
maintainerPATCH 37/43 mm: hugetlb: fix softlockup when a large number of hugepages are freed.
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Mizuma, Masayoshi" <[email protected]>
commit 55f67141a8927b2be3e51840da37b8a2320143ed upstream.
When I decrease the value of nr_hugepage in procfs a lot, softlockup happens. It is because there is no chance of context switch during this process.
On the other hand, when I allocate a large number of hugepages, there is some chance of context switch. Hence softlockup doesn't happen during this process. So it's necessary to add the context switch in the freeing process as same as allocating process to avoid softlockup.
When I freed 12 TB hugapages with kernel-2.6.32-358.el6, the freeing process occupied a CPU over 150 seconds and following softlockup message appeared twice or more.
$ echo 6000000 > /proc/sys/vm/nr_hugepages $ cat /proc/sys/vm/nr_hugepages 6000000 $ grep ^Huge /proc/meminfo HugePages_Total: 6000000 HugePages_Free: 6000000 HugePages_Rsvd: 0 HugePages_Surp: 0 Hugepagesize: 2048 kB $ echo 0 > /proc/sys/vm/nr_hugepages
BUG: soft lockup - CPU#16 stuck for 67s! [sh:12883] ... Pid: 12883, comm: sh Not tainted 2.6.32-358.el6.x86_64 #1 Call Trace: free_pool_huge_page+0xb8/0xd0 set_max_huge_pages+0x128/0x190 hugetlb_sysctl_handler_common+0x113/0x140 hugetlb_sysctl_handler+0x1e/0x20 proc_sys_call_handler+0x97/0xd0 proc_sys_write+0x14/0x20 vfs_write+0xb8/0x1a0 sys_write+0x51/0x90 __audit_syscall_exit+0x265/0x290 system_call_fastpath+0x16/0x1b
I have not confirmed this problem with upstream kernels because I am not able to prepare the machine equipped with 12TB memory now. However I confirmed that the amount of decreasing hugepages was directly proportional to the amount of required time.
I measured required times on a smaller machine. It showed 130-145 hugepages decreased in a millisecond.
Amount of decreasing Required time Decreasing rate
hugepages (msec) (pages/msec)
------------------------------------------------------------
10,000 pages == 20GB 70 - 74 135-142
30,000 pages == 60GB 208 - 229 131-144
It means decrement of 6TB hugepages will trigger softlockup with the default threshold 20sec, in this decreasing rate.
--- mm/hugetlb.c | 1 + 1 file changed, 1 insertion(+)
mm/hugetlb.c +1 -0
@@ -1451,6 +1451,7 @@ static unsigned long set_max_huge_pages(while (min_count <persistent_huge_pages (h)) {if (!free_pool_huge_page (h, nodes_allowed,0 ))break ; +cond_resched_lock (&hugetlb_lock); }while (count <persistent_huge_pages (h)) {if (!adjust_pool_surplus (h, nodes_allowed,1 ))
Greg Kroah-Hartman
maintainerPATCH 38/43 hung_task: check the value of "sysctl_hung_task_timeout_sec"
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Liu Hua <[email protected]>
commit 80df28476505ed4e6701c3448c63c9229a50c655 upstream.
As sysctl_hung_task_timeout_sec is unsigned long, when this value is larger then LONG_MAX/HZ, the function schedule_timeout_interruptible in watchdog will return immediately without sleep and with print :
schedule_timeout: wrong timeout value ffffffffffffff83
and then the funtion watchdog will call schedule_timeout_interruptible again and again. The screen will be filled with
"schedule_timeout: wrong timeout value ffffffffffffff83"
This patch does some check and correction in sysctl, to let the function schedule_timeout_interruptible allways get the valid parameter.
--- kernel/sysctl.c | 6 ++++++ 1 file changed, 6 insertions(+)
kernel/sysctl.c +6 -0
@@ -142,6 +142,11 @@ static int min_percpu_pagelist_fract = 8static int ngroups_max =NGROUPS_MAX ;static const int cap_last_cap =CAP_LAST_CAP ; +/*this is needed for proc_doulongvec_minmax of sysctl_hung_task_timeout_secs */ +#ifdef CONFIG_DETECT_HUNG_TASK +static unsigned long hung_task_timeout_max = (LONG_MAX /HZ ); +#endif +#ifdef CONFIG_INOTIFY_USER #include <linux/inotify.h> #endif
@@ -897,6 +902,7 @@ static struct ctl_table kern_table[] = { .maxlen = sizeof(unsigned long), .mode = 0644, .proc_handler = proc_dohung_task_timeout_secs, + .extra2 = &hung_task_timeout_max, }, { .procname = "hung_task_warnings",
Greg Kroah-Hartman
maintainerPATCH 39/43 ocfs2: dlm: fix lock migration crash
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Junxiao Bi <[email protected]>
commit 34aa8dac482f1358d59110d5e3a12f4351f6acaa upstream.
This issue was introduced by commit 800deef3f6f8 ("ocfs2: use list_for_each_entry where benefical") in 2007 where it replaced list_for_each with list_for_each_entry. The variable "lock" will point to invalid data if "tmpq" list is empty and a panic will be triggered due to this. Sunil advised reverting it back, but the old version was also not right. At the end of the outer for loop, that list_for_each_entry will also set "lock" to an invalid data, then in the next loop, if the "tmpq" list is empty, "lock" will be an stale invalid data and cause the panic. So reverting the list_for_each back and reset "lock" to NULL to fix this issue.
Another concern is that this seemes can not happen because the "tmpq" list should not be empty. Let me describe how.
old lock resource owner(node 1): migratation target(node 2):
image there's lockres with a EX lock from node 2 in granted list, a NR lock from node x with convert_type EX in converting list.dlm_empty_lockres() {
dlm_pick_migration_target() {
pick node 2 as target as its lock is the first one in granted list.
}
dlm_migrate_lockres() {
dlm_mark_lockres_migrating() {
res->state |= DLM_LOCK_RES_BLOCK_DIRTY;
wait_event(dlm->ast_wq, !dlm_lockres_is_dirty(dlm, res));
//after the above code, we can not dirty lockres any more,
// so dlm_thread shuffle list will not run
downconvert lock from EX to NR
upconvert lock from NR to EX<<< migration may schedule out here, then
<<< node 2 send down convert request to convert type from EX to <<< NR, then send up convert request to convert type from NR to <<< EX, at this time, lockres granted list is empty, and two locks <<< in the converting list, node x up convert lock followed by <<< node 2 up convert lock.
// will set lockres RES_MIGRATING flag, the following
// lock/unlock can not run
dlm_lockres_release_ast(dlm, res);}
dlm_send_one_lockres()
dlm_process_recovery_data()
for (i=0; i<mres->num_locks; i++)
if (ml->node == dlm->node_num)
for (j = DLM_GRANTED_LIST; j <= DLM_BLOCKED_LIST; j++) {
list_for_each_entry(lock, tmpq, list)
if (lock) break; <<< lock is invalid as grant list is empty.
}
if (lock->ml.node != ml->node)
BUG() >>> crash here}
I see the above locks status from a vmcore of our internal bug.
--- fs/ocfs2/dlm/dlmrecovery.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-)
fs/ocfs2/dlm/dlmrecovery.c +8 -6
@@ -1752,13 +1752,13 @@ static int dlm_process_recovery_data(str struct dlm_migratable_lockres *mres) {struct dlm_migratable_lock *ml; -struct list_head *queue; +struct list_head *queue, *iter;struct list_head *tmpq =NULL ;struct dlm_lock *newlock =NULL ;struct dlm_lockstatus *lksb =NULL ;int ret =0 ;int i, j, bad; -struct dlm_lock *lock =NULL ; +struct dlm_lock *lock;u8 from =O2NM_MAX_NODES ;unsigned int added =0 ;__be64 c;
@@ -1793,14 +1793,16 @@ static int dlm_process_recovery_data(str/* MIGRATION ONLY! */ BUG_ON (!(mres->flags &DLM_MRES_MIGRATION )); + lock =NULL ;spin_lock (&res->spinlock);for (j =DLM_GRANTED_LIST ; j <=DLM_BLOCKED_LIST ; j++) { tmpq =dlm_list_idx_to_ptr (res, j); -list_for_each_entry (lock, tmpq, list) { -if (lock->ml.cookie != ml->cookie) - lock =NULL ; -else +list_for_each (iter, tmpq) { + lock =list_entry (iter, + struct dlm_lock, list); +if (lock->ml.cookie == ml->cookie)break ; + lock =NULL ; }if (lock)break ;
Greg Kroah-Hartman
maintainerPATCH 40/43 ocfs2: dlm: fix recovery hung
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Junxiao Bi <[email protected]>
commit ded2cf71419b9353060e633b59e446c42a6a2a09 upstream.
There is a race window in dlm_do_recovery() between dlm_remaster_locks() and dlm_reset_recovery() when the recovery master nearly finish the recovery process for a dead node. After the master sends FINALIZE_RECO message in dlm_remaster_locks(), another node may become the recovery master for another dead node, and then send the BEGIN_RECO message to all the nodes included the old master, in the handler of this message dlm_begin_reco_handler() of old master, dlm->reco.dead_node and dlm->reco.new_master will be set to the second dead node and the new master, then in dlm_reset_recovery(), these two variables will be reset to default value. This will cause new recovery master can not finish the recovery process and hung, at last the whole cluster will hung for recovery.
old recovery master: new recovery master:dlm_remaster_locks()
become recovery master for another dead node. dlm_send_begin_reco_message()dlm_begin_reco_handler()
{
if (dlm->reco.state & DLM_RECO_STATE_FINALIZE) {
return -EAGAIN;
}
dlm_set_reco_master(dlm, br->node_idx);
dlm_set_reco_dead_node(dlm, br->dead_node);
}dlm_reset_recovery()
{
dlm_set_reco_dead_node(dlm, O2NM_INVALID_NODE_NUM); dlm_set_reco_master(dlm, O2NM_INVALID_NODE_NUM);
}
will hang in dlm_remaster_locks() for request dlm locks info
Before send FINALIZE_RECO message, recovery master should set DLM_RECO_STATE_FINALIZE for itself and clear it after the recovery done, this can break the race windows as the BEGIN_RECO messages will not be handled before DLM_RECO_STATE_FINALIZE flag is cleared.
A similar race may happen between new recovery master and normal node which is in dlm_finalize_reco_handler(), also fix it.
--- fs/ocfs2/dlm/dlmrecovery.c | 15 +++++++++++++-- 1 file changed, 13 insertions(+), 2 deletions(-)
fs/ocfs2/dlm/dlmrecovery.c +13 -2
@@ -540,7 +540,10 @@ master_here:/* success! see if any other nodes need recovery */ mlog (0 ,"DONE mastering recovery of %s:%u here(this=%u)!\n" , dlm->name, dlm->reco.dead_node, dlm->node_num); -dlm_reset_recovery (dlm); +spin_lock (&dlm->spinlock); +__dlm_reset_recovery (dlm); + dlm->reco.state &= ~DLM_RECO_STATE_FINALIZE ; +spin_unlock (&dlm->spinlock); }dlm_end_recovery (dlm);
@@ -698,6 +701,14 @@ static int dlm_remaster_locks(struct dlmif (all_nodes_done) {int ret; +/* Set this flag on recovery master to avoid +* a new recovery for another dead node start +* before the recovery is not done. That may +* cause recovery hung.*/ +spin_lock (&dlm->spinlock); + dlm->reco.state |=DLM_RECO_STATE_FINALIZE ; +spin_unlock (&dlm->spinlock); +/* all nodes are now in DLM_RECO_NODE_DATA_DONE state * just send a finalize message to everyone and * clean up */
@@ -2872,8 +2883,8 @@ int dlm_finalize_reco_handler(struct o2nBUG (); } dlm->reco.state &= ~DLM_RECO_STATE_FINALIZE ; +__dlm_reset_recovery (dlm);spin_unlock (&dlm->spinlock); -dlm_reset_recovery (dlm);dlm_kick_recovery_thread (dlm);break ;default :
Greg Kroah-Hartman
maintainerPATCH 41/43 ocfs2: do not put bh when buffer_uptodate failed
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: alex chen <[email protected]>
commit f7cf4f5bfe073ad792ab49c04f247626b3e38db6 upstream.
Do not put bh when buffer_uptodate failed in ocfs2_write_block and ocfs2_write_super_or_backup, because it will put bh in b_end_io. Otherwise it will hit a warning "VFS: brelse: Trying to free free buffer".
--- fs/ocfs2/buffer_head_io.c | 2 -- 1 file changed, 2 deletions(-)
fs/ocfs2/buffer_head_io.c +0 -2
@@ -90,7 +90,6 @@ int ocfs2_write_block(struct ocfs2_super* information for this bh as it's not marked locally * uptodate. */ ret = -EIO ; -put_bh (bh);mlog_errno (ret); }
@@ -420,7 +419,6 @@ int ocfs2_write_super_or_backup(struct oif (!buffer_uptodate (bh)) { ret = -EIO ; -put_bh (bh);mlog_errno (ret); }
Greg Kroah-Hartman
maintainerPATCH 42/43 ext4: use i_size_read in ext4_unaligned_aio()
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Theodore Ts'o <[email protected]>
commit 6e6358fc3c3c862bfe9a5bc029d3f8ce43dc9765 upstream.
We haven't taken i_mutex yet, so we need to use i_size_read().
--- fs/ext4/file.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/ext4/file.c +1 -1
@@ -80,7 +80,7 @@ ext4_unaligned_aio(struct inode *inode,size_t count =iov_length (iov, nr_segs);loff_t final_size = pos + count; -if (pos >= inode->i_size) +if (pos >=i_size_read (inode))return 0 ;if ((pos & blockmask) || (final_size & blockmask))
Greg Kroah-Hartman
maintainerPATCH 43/43 USB: pl2303: add ids for Hewlett-Packard HP POS pole displays
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Aaron Sanders <[email protected]>
commit b16c02fbfb963fa2941b7517ebf1f8a21946775e upstream.
Add device ids to pl2303 for the Hewlett-Packard HP POS pole displays:
LD960: 03f0:0B39
LCM220: 03f0:3139
LCM960: 03f0:3239
[ Johan: fix indentation and sort PIDs numerically ]
--- drivers/usb/serial/pl2303.c | 3 +++ drivers/usb/serial/pl2303.h | 5 ++++- 2 files changed, 7 insertions(+), 1 deletion(-)
drivers/usb/serial/pl2303.c +3 -0
@@ -86,6 +86,9 @@ static const struct usb_device_id id_tab { USB_DEVICE(YCCABLE_VENDOR_ID, YCCABLE_PRODUCT_ID) }, { USB_DEVICE(SUPERIAL_VENDOR_ID, SUPERIAL_PRODUCT_ID) }, { USB_DEVICE(HP_VENDOR_ID, HP_LD220_PRODUCT_ID) }, + { USB_DEVICE(HP_VENDOR_ID, HP_LD960_PRODUCT_ID) }, + { USB_DEVICE(HP_VENDOR_ID, HP_LCM220_PRODUCT_ID) }, + { USB_DEVICE(HP_VENDOR_ID, HP_LCM960_PRODUCT_ID) }, { USB_DEVICE(CRESSI_VENDOR_ID, CRESSI_EDY_PRODUCT_ID) }, { USB_DEVICE(ZEAGLE_VENDOR_ID, ZEAGLE_N2ITION3_PRODUCT_ID) }, { USB_DEVICE(SONY_VENDOR_ID, SONY_QN3USB_PRODUCT_ID) },
drivers/usb/serial/pl2303.h +4 -1
@@ -121,8 +121,11 @@#define SUPERIAL_VENDOR_ID 0x5372#define SUPERIAL_PRODUCT_ID 0x2303 -/* Hewlett-Packard LD220-HP POS Pole Display */ +/* Hewlett-Packard POS Pole Displays */ #define HP_VENDOR_ID 0x03f0 +#define HP_LD960_PRODUCT_ID 0x0b39 +#define HP_LCM220_PRODUCT_ID 0x3139 +#define HP_LCM960_PRODUCT_ID 0x3239#define HP_LD220_PRODUCT_ID 0x3524/* Cressi Edy (diving computer) PC interface */
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.89 release. There are 43 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 me know.
Responses should be made by Tue May 6 15:42:07 UTC 2014. Anything received after that time might be too late.
Build results:
total: 120 pass: 97 skipped: 18 fail: 5
Qemu tests all passed.
There is one new failure, unicore32:defconfig. This is a new build target which fails for all releases in my tests, so the failure is undesirable but not surprising. Overall results are as expected.
Details are at http://server.roeck-us.net:8010/builders.
Guenter
Greg Kroah-Hartman
maintainerQuoted 13 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.89 release. There are 43 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 me know.
Responses should be made by Tue May 6 15:42:07 UTC 2014. Anything received after that time might be too late.
Build results:
total: 120 pass: 97 skipped: 18 fail: 5
Quoted 7 lines
Qemu tests all passed.
There is one new failure, unicore32:defconfig. This is a new build target which fails for all releases in my tests, so the failure is undesirable but not surprising. Overall results are as expected.
Details are at http://server.roeck-us.net:8010/builders.
Great, thanks for testing.
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.89 release. There are 43 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 me know.
Responses should be made by Tue May 6 15:42:07 UTC 2014. Anything received after that time might be too late.
Quoted 8 lines
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.4.89-rc1.gzand the diffstat can be found below.
thanks,
greg k-h
Compiled and booted on my test systems. No dmesg regressions.
-- Shuah
Signature · 4 lines
Shuah Khan Senior Linux Kernel Developer - Open Source Group Samsung Research America(Silicon Valley) [email protected] | (970) 672-0658
Greg Kroah-Hartman
maintainerQuoted 13 lines · Shuah Khan
Quoted 12 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.89 release. There are 43 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 me know.
Responses should be made by Tue May 6 15:42:07 UTC 2014. 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.4.89-rc1.gzand the diffstat can be found below.
Quoted 6 lines
Quoted 4 lines
thanks,
greg k-h
Compiled and booted on my test systems. No dmesg regressions.
Thanks for testing and letting me know.
greg k-h