3.15.7-stable review
Subsystems (8)
Greg Kroah-Hartman
maintainercover 3.15.7-stable review
This is the start of the stable review cycle for the 3.15.7 release. There are 109 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 Mon Jul 28 19:02: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.15.7-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.15.7-rc1
Anton Kolesov <[email protected]>
ARC: Implement ptrace(PTRACE_GET_THREAD_AREA)
Linus Torvalds <[email protected]>
Don't trigger congestion wait on dirty-but-not-writeout pages
Emmanuel Grumbach <[email protected]>
iwlwifi: mvm: disable CTS to Self
Marek Vasut <[email protected]>
ARM: dts: imx: Add alias for ethernet controller
Sebastian Andrzej Siewior <[email protected]>
gpio: dwapb: drop irq_setup_generic_chip()
Benjamin LaHaise <[email protected]>
aio: protect reqs_available updates from changes in interrupt handlers
Or Gerlitz <[email protected]>
IB/mlx5: Enable "block multicast loopback" for kernel consumers
Michael Brown <[email protected]>
x86/efi: Include a .bss section within the PE/COFF headers
Mateusz Guzik <[email protected]>
sched: Fix possible divide by zero in avg_atom() calculation
Peter Zijlstra <[email protected]>
locking/mutex: Disable optimistic spinning on some architectures
Takashi Iwai <[email protected]>
PM / sleep: Fix request_firmware() error at resume
Steve Wise <[email protected]>
RDMA/cxgb4: Initialize the device status page
Mike Snitzer <[email protected]>
dm cache metadata: do not allow the data block size to change
Mike Snitzer <[email protected]>
dm thin metadata: do not allow the data block size to change
Ted Juan <[email protected]>
mtd: devices: elm: fix elm_context_save() and elm_context_restore() functions
Hannes Frederic Sowa <[email protected]>
random: check for increase of entropy_count because of signed conversion
Viresh Kumar <[email protected]>
cpufreq: move policy kobj to policy->cpu at resume
Peter Zijlstra <[email protected]>
x86, tsc: Fix cpufreq lockup
Amit Shah <[email protected]>
hwrng: fetch randomness only after device init
John Stultz <[email protected]>
alarmtimer: Fix bug where relative alarm timers were treated as absolute
Dave Airlie <[email protected]>
Revert "drm/i915: reverse dp link param selection, prefer fast over wide again"
Alex Deucher <[email protected]>
drm/radeon: avoid leaking edid data
Jason Wang <[email protected]>
drm/qxl: return IRQ_NONE if it was not our irq
Alex Deucher <[email protected]>
drm/radeon: set default bl level to something reasonable
Tomasz Figa <[email protected]>
irqchip: gic: Fix core ID calculation when topology is read from DT
Suravee Suthikulpanit <[email protected]>
irqchip: gic: Add binding probe for ARM GIC400
Matthias Brugger <[email protected]>
irqchip: gic: Add support for cortex a7 compatible string
Martin Lau <[email protected]>
ring-buffer: Fix polling on trace_pipe
Amitkumar Karwar <[email protected]>
mwifiex: fix Tx timeout issue
HATAYAMA Daisuke <[email protected]>
perf/x86/intel: ignore CondChgd bit to avoid false NMI handling
Jiri Olsa <[email protected]>
perf: Do not allow optimized switch for non-cloned events
Zoltan Kiss <[email protected]>
xen-netback: Fix pointer incrementation to avoid incorrect logging
Zoltan Kiss <[email protected]>
xen-netback: Fix releasing header slot on error path
Zoltan Kiss <[email protected]>
xen-netback: Fix releasing frag_list skbs in error path
Zoltan Kiss <[email protected]>
xen-netback: Fix handling frag_list on grant op error path
Eric Dumazet <[email protected]>
ipv4: fix buffer overflow in ip_options_compile()
Ben Hutchings <[email protected]>
dns_resolver: Null-terminate the right string
Manuel Schölling <[email protected]>
dns_resolver: assure that dns_query() result is null-terminated
Christoph Schulz <[email protected]>
net: ppp: don't call sk_chk_filter twice
Bjørn Mork <[email protected]>
net: huawei_cdc_ncm: add "subclass 3" devices
Christoph Schulz <[email protected]>
net: ppp: fix creating PPP pass and active filters
Sowmini Varadhan <[email protected]>
sunvnet: clean up objects created in vnet_new() on vnet_exit()
Jerry Chu <[email protected]>
net-gre-gro: Fix a bug that breaks the forwarding path
Nikolay Aleksandrov <[email protected]>
bonding: fix ad_select module param check
Christoph Schulz <[email protected]>
net: pppoe: use correct channel MTU when using Multilink PPP
Daniel Borkmann <[email protected]>
net: sctp: fix information leaks in ulpevent layer
Jon Paul Maloy <[email protected]>
tipc: clear 'next'-pointer of message fragments before reassembly
hayeswang <[email protected]>
r8152: fix r8152_csum_workaround function
Suresh Reddy <[email protected]>
be2net: set EQ DB clear-intr bit in be_open()
Ben Pfaff <[email protected]>
netlink: Fix handling of error from netlink_dump().
Thomas Fitzsimmons <[email protected]>
net: mvneta: Fix big endian issue in mvneta_txq_desc_csum()
Thomas Petazzoni <[email protected]>
net: mvneta: fix operation in 10 Mbit/s mode
Andrey Utkin <[email protected]>
appletalk: Fix socket referencing in skb
Yuchung Cheng <[email protected]>
tcp: fix false undo corner cases
dingtianhong <[email protected]>
igmp: fix the problem when mc leave group
Loic Prylli <[email protected]>
net: Fix NETDEV_CHANGE notifier usage causing spurious arp flush
Bjørn Mork <[email protected]>
net: qmi_wwan: add two Sierra Wireless/Netgear devices
Bernd Wachter <[email protected]>
net: qmi_wwan: Add ID for Telewell TW-LTE 4G v2
Edward Allcutt <[email protected]>
ipv4: icmp: Fix pMTU handling for rare case
Christoph Paasch <[email protected]>
tcp: Fix divide by zero when pushing during tcp-repair
Eric Dumazet <[email protected]>
bnx2x: fix possible panic under memory stress
Eric Dumazet <[email protected]>
vlan: free percpu stats in device destructor
Eric Dumazet <[email protected]>
net: fix sparse warning in sk_dst_set()
Eric Dumazet <[email protected]>
ipv4: irq safe sk_dst_[re]set() and ipv4_sk_update_pmtu() fix
Eric Dumazet <[email protected]>
ipv4: fix dst race in sk_dst_get()
Wei-Chun Chao <[email protected]>
net: fix UDP tunnel GSO of frag_list GRO packets
Bjørn Mork <[email protected]>
net: huawei_cdc_ncm: increase command buffer size
Mugunthan V N <[email protected]>
drivers: net: cpsw: fix dual EMAC stall when connected to same switch
Li RongQing <[email protected]>
8021q: fix a potential memory leak
Daniel Borkmann <[email protected]>
net: sctp: check proc_dointvec result in proc_sctp_do_auth
Neal Cardwell <[email protected]>
tcp: fix tcp_match_skb_to_sack() for unaligned SACK at end of an skb
Kees Cook <[email protected]>
net: filter: fix upper BPF instruction limit
Daniel Borkmann <[email protected]>
net: sctp: propagate sysctl errors from proc_do* properly
Tyler Hall <[email protected]>
slcan: Port write_wakeup deadlock fix from slip
Tyler Hall <[email protected]>
slip: Fix deadlock in write_wakeup
Dmitry Popov <[email protected]>
ip_tunnel: fix ip_tunnel_lookup
Or Gerlitz <[email protected]>
net/mlx4_en: Don't configure the HW vxlan parser when vxlan offloading isn't set
Or Gerlitz <[email protected]>
net/mlx4_core: Fix the error flow when probing with invalid VF configuration
Hugh Dickins <[email protected]>
shmem: fix splicing from a hole while it's punched
Hugh Dickins <[email protected]>
shmem: fix faulting into a hole, not taking i_mutex
Hugh Dickins <[email protected]>
shmem: fix faulting into a hole while it's punched
Emmanuel Grumbach <[email protected]>
iwlwifi: dvm: don't enable CTS to self
Oren Givon <[email protected]>
iwlwifi: update the 7265 series HW IDs
Niu Yawei <[email protected]>
quota: missing lock in dqcache_shrink_scan()
Stefan Assmann <[email protected]>
igb: do a reset on SR-IOV re-init if device is down
Todd Fujinaka <[email protected]>
igb: Workaround for i210 Errata 25: Slow System Clock
Guenter Roeck <[email protected]>
hwmon: (adt7470) Fix writes to temperature limit registers
Axel Lin <[email protected]>
hwmon: (da9052) Don't use dash in the name attribute
Axel Lin <[email protected]>
hwmon: (da9055) Don't use dash in the name attribute
David Vrabel <[email protected]>
xen/manage: fix potential deadlock when resuming the console
David Vrabel <[email protected]>
xen/balloon: set ballooned out pages as invalid in p2m
zhangwei(Jovi) <[email protected]>
tracing: Add TRACE_ITER_PRINTK flag check in __trace_puts/__trace_bputs
zhangwei(Jovi) <[email protected]>
tracing: Add ftrace_trace_stack into __trace_puts/__trace_bputs
Steven Rostedt (Red Hat) <[email protected]>
tracing: Fix graph tracer with stack tracer on other archs
Oleg Nesterov <[email protected]>
tracing: instance_rmdir() leaks ftrace_event_file->filter
Srinivas Pandruvada <[email protected]>
iio:core: Handle error when mask type is not separate
Anand Avati <[email protected]>
fuse: ignore entry-timeout on LOOKUP_REVAL
Miklos Szeredi <[email protected]>
fuse: handle large user and group ID
Miklos Szeredi <[email protected]>
fuse: avoid scheduling while atomic
Miklos Szeredi <[email protected]>
fuse: timeout comparison fix
Loic Poulain <[email protected]>
Bluetooth: Ignore H5 non-link packets in non-active state
Marcel Holtmann <[email protected]>
Revert "Bluetooth: Add a new PID/VID 0cf3/e005 for AR3012."
K. Y. Srinivasan <[email protected]>
Drivers: hv: util: Fix a bug in the KVP code
Dexuan Cui <[email protected]>
Drivers: hv: hv_fcopy: fix a race condition for SMP guest
Takashi Iwai <[email protected]>
ALSA: hda - Fix broken PM due to incomplete i915 initialization
Takashi Iwai <[email protected]>
ALSA: hda - Revert stream assignment order for Intel controllers
Hans de Goede <[email protected]>
media: gspca_pac7302: Add new usb-id for Genius i-Look 317
Abbas Raza <[email protected]>
usb: chipidea: udc: Disable auto ZLP generation on ep0
Gavin Guo <[email protected]>
usb: Check if port status is equal to RxDetect
-------------
Diffstat:
Makefile | 4 +- arch/arc/include/uapi/asm/ptrace.h | 1 + arch/arc/kernel/ptrace.c | 4 + arch/arm/Kconfig | 1 + arch/arm/boot/dts/imx25.dtsi | 1 + arch/arm/boot/dts/imx27.dtsi | 1 + arch/arm/boot/dts/imx35.dtsi | 1 + arch/arm/boot/dts/imx50.dtsi | 1 + arch/arm/boot/dts/imx51.dtsi | 1 + arch/arm/boot/dts/imx53.dtsi | 1 + arch/arm/boot/dts/imx6qdl.dtsi | 1 + arch/arm/boot/dts/imx6sl.dtsi | 1 + arch/arm64/Kconfig | 1 + arch/powerpc/Kconfig | 1 + arch/sparc/Kconfig | 1 + arch/x86/Kconfig | 1 + arch/x86/boot/header.S | 26 ++++- arch/x86/boot/tools/build.c | 38 ++++++-- arch/x86/kernel/cpu/perf_event_intel.c | 9 ++ arch/x86/kernel/tsc.c | 4 +- drivers/bluetooth/ath3k.c | 2 - drivers/bluetooth/btusb.c | 1 - drivers/bluetooth/hci_h5.c | 1 + drivers/char/hw_random/core.c | 41 ++++++-- drivers/char/random.c | 17 +++- drivers/cpufreq/cpufreq.c | 6 +- drivers/gpio/gpio-dwapb.c | 3 - drivers/gpu/drm/i915/intel_dp.c | 4 +- drivers/gpu/drm/qxl/qxl_irq.c | 3 + drivers/gpu/drm/radeon/atombios_encoders.c | 10 +- drivers/gpu/drm/radeon/radeon_display.c | 5 + drivers/hv/hv_fcopy.c | 2 +- drivers/hv/hv_kvp.c | 14 ++- drivers/hv/hv_util.c | 2 +- drivers/hwmon/adt7470.c | 6 +- drivers/hwmon/da9052-hwmon.c | 2 +- drivers/hwmon/da9055-hwmon.c | 2 +- drivers/iio/industrialio-event.c | 3 + drivers/infiniband/hw/cxgb4/device.c | 1 + drivers/infiniband/hw/mlx5/qp.c | 2 +- drivers/irqchip/irq-gic.c | 7 +- drivers/isdn/i4l/isdn_ppp.c | 28 +++--- drivers/md/dm-cache-metadata.c | 9 ++ drivers/md/dm-thin-metadata.c | 9 ++ drivers/media/usb/gspca/pac7302.c | 1 + drivers/mtd/devices/elm.c | 2 + drivers/net/bonding/bond_main.c | 2 +- drivers/net/can/slcan.c | 37 +++++-- drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 3 +- drivers/net/ethernet/emulex/benet/be_main.c | 2 +- drivers/net/ethernet/intel/igb/e1000_82575.c | 7 ++ drivers/net/ethernet/intel/igb/e1000_defines.h | 18 ++-- drivers/net/ethernet/intel/igb/e1000_hw.h | 3 + drivers/net/ethernet/intel/igb/e1000_i210.c | 66 +++++++++++++ drivers/net/ethernet/intel/igb/e1000_i210.h | 12 +++ drivers/net/ethernet/intel/igb/e1000_regs.h | 1 + drivers/net/ethernet/intel/igb/igb_main.c | 16 ++++ drivers/net/ethernet/marvell/mvneta.c | 4 +- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 2 +- drivers/net/ethernet/mellanox/mlx4/main.c | 3 +- drivers/net/ethernet/sun/sunvnet.c | 20 +++- drivers/net/ethernet/ti/cpsw.c | 7 +- drivers/net/ppp/ppp_generic.c | 30 +++--- drivers/net/ppp/pppoe.c | 2 +- drivers/net/slip/slip.c | 36 +++++-- drivers/net/slip/slip.h | 1 + drivers/net/usb/huawei_cdc_ncm.c | 10 +- drivers/net/usb/qmi_wwan.c | 3 + drivers/net/usb/r8152.c | 2 +- drivers/net/wireless/iwlwifi/dvm/rxon.c | 12 --- drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c | 8 +- drivers/net/wireless/iwlwifi/pcie/drv.c | 3 +- drivers/net/wireless/mwifiex/main.c | 1 + drivers/net/xen-netback/netback.c | 86 ++++++++++++----- drivers/usb/chipidea/udc.c | 4 +- drivers/usb/core/hub.c | 19 ++++ drivers/xen/balloon.c | 12 +-- drivers/xen/manage.c | 5 +- fs/aio.c | 7 ++ fs/fuse/dev.c | 51 +++++----- fs/fuse/dir.c | 7 +- fs/fuse/inode.c | 20 +++- fs/quota/dquot.c | 2 + include/net/sock.h | 16 ++-- kernel/Kconfig.locks | 5 +- kernel/events/core.c | 2 +- kernel/power/process.c | 1 + kernel/sched/debug.c | 2 +- kernel/time/alarmtimer.c | 20 +++- kernel/trace/ftrace.c | 4 +- kernel/trace/ring_buffer.c | 4 - kernel/trace/trace.c | 18 +++- kernel/trace/trace_events.c | 1 + mm/shmem.c | 104 +++++++++++++++++--- mm/vmscan.c | 11 +-- net/8021q/vlan_core.c | 5 +- net/8021q/vlan_dev.c | 13 ++- net/appletalk/ddp.c | 3 - net/core/dev.c | 11 ++- net/core/dst.c | 16 +++- net/core/filter.c | 2 +- net/core/skbuff.c | 3 +- net/dns_resolver/dns_query.c | 4 +- net/ipv4/af_inet.c | 3 + net/ipv4/gre_offload.c | 3 + net/ipv4/icmp.c | 2 - net/ipv4/igmp.c | 10 +- net/ipv4/ip_options.c | 4 + net/ipv4/ip_tunnel.c | 26 ++--- net/ipv4/route.c | 15 +-- net/ipv4/tcp.c | 3 +- net/ipv4/tcp_input.c | 10 +- net/ipv4/tcp_offload.c | 2 +- net/ipv4/tcp_output.c | 6 +- net/ipv6/tcpv6_offload.c | 2 +- net/netlink/af_netlink.c | 4 +- net/sctp/sysctl.c | 46 ++++----- net/sctp/ulpevent.c | 122 +++--------------------- net/tipc/bcast.c | 1 + sound/pci/hda/hda_controller.c | 3 +- sound/pci/hda/hda_intel.c | 12 +-- sound/pci/hda/hda_priv.h | 1 + 122 files changed, 893 insertions(+), 433 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/109 usb: Check if port status is equal to RxDetect
3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gavin Guo <[email protected]>
commit bb86cf569bbd7ad4dce581a37c7fbd748057e9dc upstream.
When using USB 3.0 pen drive with the [AMD] FCH USB XHCI Controller [1022:7814], the second hotplugging will experience the USB 3.0 pen drive is recognized as high-speed device. After bisecting the kernel, I found the commit number 41e7e056cdc662f704fa9262e5c6e213b4ab45dd (USB: Allow USB 3.0 ports to be disabled.) causes the bug. After doing some experiments, the bug can be fixed by avoiding executing the function hub_usb3_port_disable(). Because the port status with [AMD] FCH USB XHCI Controlleris [1022:7814] is already in RxDetect
(I tried printing out the port status before setting to Disabled state), it's reasonable to check the port status before really executing hub_usb3_port_disable().
--- drivers/usb/core/hub.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
drivers/usb/core/hub.c +19 -0
@@ -893,6 +893,25 @@ static int hub_usb3_port_disable(structif (!hub_is_superspeed (hub->hdev))return -EINVAL ; + ret =hub_port_status (hub, port1, &portstatus, &portchange); +if (ret <0 ) +return ret; + +/* +* USB controller Advanced Micro Devices, Inc. [AMD] FCH USB XHCI +* Controller [1022:7814] will have spurious result making the following +* usb 3.0 device hotplugging route to the 2.0 root hub and recognized +* as high-speed device if we set the usb 3.0 port link state to +* Disabled. Since it's already in USB_SS_PORT_LS_RX_DETECT state, we +* check the state here to avoid the bug. +*/ +if ((portstatus &USB_PORT_STAT_LINK_STATE ) == +USB_SS_PORT_LS_RX_DETECT ) { +dev_dbg (&hub->ports[port1 -1 ]->dev, +"Not disabling port; link state is RxDetect\n" ); +return ret; + } + ret =hub_set_port_link_state (hub, port1,USB_SS_PORT_LS_SS_DISABLED );if (ret)return ret;
Greg Kroah-Hartman
maintainerPATCH 2/109 usb: chipidea: udc: Disable auto ZLP generation on ep0
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Abbas Raza <[email protected]>
commit 953c66469735aed8d2ada639a72b150f01dae605 upstream.
There are 2 methods for ZLP (zero-length packet) generation:
1) In software
2) Automatic generation by device controller
1) is implemented in UDC driver and it attaches ZLP to IN packet if descriptor->size < wLength
2) can be enabled/disabled by setting ZLT bit in the QH
When gadget ffs is connected to ubuntu host, the host sends get descriptor request and wLength in setup packet is 255 while the size of descriptor which will be sent by gadget in IN packet is 64 byte. So the composite driver sets req->zero = 1.
In UDC driver following code will be executed then
if (hwreq->req.zero && hwreq->req.length
&& (hwreq->req.length % hwep->ep.maxpacket == 0))
add_td_to_list(hwep, hwreq, 0);Case-A:
So in case of ubuntu host, UDC driver will attach a ZLP to the IN packet. ubuntu host will request 255 byte in IN request, gadget will send 64 byte with ZLP and host will come to know that there is no more data. But hold on, by default ZLT=0 for endpoint 0 so hardware also tries to automatically generate the ZLP which blocks enumeration for ~6 seconds due to endpoint 0 STALL, NAKs are sent to host for any requests (OUT/PING)
Case-B:
In case when gadget ffs is connected to Apple device, Apple device sends setup packet with wLength=64. So descriptor->size = 64 and wLength=64 therefore req->zero = 0 and UDC driver will not attach any ZLP to the IN packet. Apple device requests 64 bytes, gets 64 bytes and doesn't further request for IN data. But ZLT=0 by default for endpoint 0 so hardware tries to automatically generate the ZLP which blocks enumeration for ~6 seconds due to endpoint 0 STALL, NAKs are sent to host for any requests (OUT/PING)
According to USB2.0 specs:
8.5.3.2 Variable-length Data Stage
A control pipe may have a variable-length data phase in which the host requests more data than is contained in the specified data structure. When all of the data structure is returned to the host, the function should indicate that the Data stage is ended by returning a packet that is shorter than the MaxPacketSize for the pipe. If the data structure is an exact multiple of wMaxPacketSize for the pipe, the function will return a zero-length packet to indicate the end of the Data stage.
In Case-A mentioned above:
If we disable software ZLP generation & ZLT=0 for endpoint 0 OR if software ZLP generation is not disabled but we set ZLT=1 for endpoint 0 then enumeration doesn't block for 6 seconds.
In Case-B mentioned above:
If we disable software ZLP generation & ZLT=0 for endpoint then enumeration still blocks due to ZLP automatically generated by hardware and host not needing it. But if we keep software ZLP generation enabled but we set ZLT=1 for endpoint 0 then enumeration doesn't block for 6 seconds.
So the proper solution for this issue seems to disable automatic ZLP generation by hardware (i.e by setting ZLT=1 for endpoint 0) and let software (UDC driver) handle the ZLP generation based on req->zero field.
--- drivers/usb/chipidea/udc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/usb/chipidea/udc.c +2 -2
@@ -1176,8 +1176,8 @@ static int ep_enable(struct usb_ep *ep,if (hwep->type ==USB_ENDPOINT_XFER_CONTROL ) cap |=QH_IOS ; -if (hwep->num) - cap |=QH_ZLT ; + + cap |=QH_ZLT ; cap |= (hwep->ep.maxpacket <<__ffs (QH_MAX_PKT )) &QH_MAX_PKT ;/* * For ISO-TX, we set mult at QH as the largest value, and use
Greg Kroah-Hartman
maintainerPATCH 3/109 media: gspca_pac7302: Add new usb-id for Genius i-Look 317
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit 242841d3d71191348f98310e2d2001e1001d8630 upstream.
--- drivers/media/usb/gspca/pac7302.c | 1 + 1 file changed, 1 insertion(+)
drivers/media/usb/gspca/pac7302.c +1 -0
@@ -928,6 +928,7 @@ static const struct usb_device_id device {USB_DEVICE(0x093a, 0x2620)}, {USB_DEVICE(0x093a, 0x2621)}, {USB_DEVICE(0x093a, 0x2622), .driver_info = FL_VFLIP}, + {USB_DEVICE(0x093a, 0x2623), .driver_info = FL_VFLIP}, {USB_DEVICE(0x093a, 0x2624), .driver_info = FL_VFLIP}, {USB_DEVICE(0x093a, 0x2625)}, {USB_DEVICE(0x093a, 0x2626)},
Greg Kroah-Hartman
maintainerPATCH 4/109 ALSA: hda - Revert stream assignment order for Intel controllers
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit cd50065b3be83a705635550c04e368f2a4cc44d0 upstream.
We got a regression report for 3.15.x kernels, and this turned out to be triggered by the fix for stream assignment order. On reporter's machine with Intel controller (8086:1e20) + VIA VT1802 codec, the first playback slot can't work with speaker outputs.
But the original commit was actually a fix for AMD controllers where no proper GCAP value is returned, we shouldn't revert the whole commit. Instead, in this patch, a new flag is introduced to determine the stream assignment order, and follow the old behavior for Intel controllers.
--- sound/pci/hda/hda_controller.c | 3 ++- sound/pci/hda/hda_intel.c | 2 +- sound/pci/hda/hda_priv.h | 1 + 3 files changed, 4 insertions(+), 2 deletions(-)
sound/pci/hda/hda_controller.c +2 -1
@@ -193,7 +193,8 @@ azx_assign_device(struct azx *chip, strudsp_unlock (azx_dev);return azx_dev; } -if (!res) +if (!res || + (chip->driver_caps &AZX_DCAPS_REVERSE_ASSIGN )) res = azx_dev; }dsp_unlock (azx_dev);
sound/pci/hda/hda_intel.c +1 -1
@@ -227,7 +227,7 @@ enum {/* quirks for Intel PCH */ #define AZX_DCAPS_INTEL_PCH_NOPM \ (AZX_DCAPS_SCH_SNOOP | AZX_DCAPS_BUFSIZE | \ - AZX_DCAPS_COUNT_LPIB_DELAY) + AZX_DCAPS_COUNT_LPIB_DELAY | AZX_DCAPS_REVERSE_ASSIGN)#define AZX_DCAPS_INTEL_PCH \ (AZX_DCAPS_INTEL_PCH_NOPM | AZX_DCAPS_PM_RUNTIME)
sound/pci/hda/hda_priv.h +1 -0
@@ -186,6 +186,7 @@ enum { SDI0, SDI1, SDI2, SDI3, SDO0, SDO#define AZX_DCAPS_BUFSIZE (1 << 21)/* no buffer size alignment */ #define AZX_DCAPS_ALIGN_BUFSIZE (1 << 22)/* buffer size alignment */ #define AZX_DCAPS_4K_BDLE_BOUNDARY (1 << 23)/* BDLE in 4k boundary */ +#define AZX_DCAPS_REVERSE_ASSIGN (1 << 24)/* Assign devices in reverse order */ #define AZX_DCAPS_COUNT_LPIB_DELAY (1 << 25)/* Take LPIB as delay */ #define AZX_DCAPS_PM_RUNTIME (1 << 26)/* runtime PM support */ #define AZX_DCAPS_I915_POWERWELL (1 << 27)/* HSW i915 powerwell support */
Greg Kroah-Hartman
maintainerPATCH 5/109 ALSA: hda - Fix broken PM due to incomplete i915 initialization
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 4da63c6fc426023d1a20e45508c47d7d68c6a53d upstream.
When the initialization of Intel HDMI controller fails due to missing i915 kernel symbols (e.g. HD-audio is built in while i915 is module), the driver discontinues the probe. However, since the probe was done asynchronously, the driver object still remains, thus the relevant PM ops are still called at suspend/resume. This results in the bad access to the incomplete audio card object, eventually leads to Oops or stall at PM.
This patch adds the missing checks of chip->init_failed flag at each PM callback in order to fix the problem above.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=79561
--- sound/pci/hda/hda_intel.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-)
sound/pci/hda/hda_intel.c +5 -5
@@ -590,7 +590,7 @@ static int azx_suspend(struct device *destruct azx *chip = card->private_data;struct azx_pcm *p; -if (chip->disabled) +if (chip->disabled || chip->init_failed)return 0 ;snd_power_change_state (card, SNDRV_CTL_POWER_D3hot);
@@ -622,7 +622,7 @@ static int azx_resume(struct device *devstruct snd_card *card =dev_get_drvdata (dev);struct azx *chip = card->private_data; -if (chip->disabled) +if (chip->disabled || chip->init_failed)return 0 ;if (chip->driver_caps &AZX_DCAPS_I915_POWERWELL ) {
@@ -659,7 +659,7 @@ static int azx_runtime_suspend(struct destruct snd_card *card =dev_get_drvdata (dev);struct azx *chip = card->private_data; -if (chip->disabled) +if (chip->disabled || chip->init_failed)return 0 ;if (!(chip->driver_caps &AZX_DCAPS_PM_RUNTIME ))
@@ -686,7 +686,7 @@ static int azx_runtime_resume(struct devstruct hda_codec *codec;int status; -if (chip->disabled) +if (chip->disabled || chip->init_failed)return 0 ;if (!(chip->driver_caps &AZX_DCAPS_PM_RUNTIME ))
@@ -723,7 +723,7 @@ static int azx_runtime_idle(struct devicstruct snd_card *card =dev_get_drvdata (dev);struct azx *chip = card->private_data; -if (chip->disabled) +if (chip->disabled || chip->init_failed)return 0 ; if (!power_save_controller ||
Greg Kroah-Hartman
maintainerPATCH 6/109 Drivers: hv: hv_fcopy: fix a race condition for SMP guest
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dexuan Cui <[email protected]>
commit 2ef82d24f445e82f80e235f44eb9d1bc933e3670 upstream.
We should schedule the 5s "timer work" before starting the data transfer, otherwise, the data transfer code may finish so fast on another virtual cpu that when the code(fcopy_write()) trying to cancel the 5s "timer work" can occasionally fail because the "timer work" may haven't been scheduled yet and as a result the fcopy process will be aborted wrongly by fcopy_work_func() in 5s.
Thank Liz Zhang <[email protected]> for the initial investigation on the bug.
This addresses https://bugzilla.redhat.com/show_bug.cgi?id=1118123
--- drivers/hv/hv_fcopy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hv/hv_fcopy.c +1 -1
@@ -246,8 +246,8 @@ void hv_fcopy_onchannelcallback(void *co/* * Send the information to the user-level daemon. */ -fcopy_send_data ();schedule_delayed_work (&fcopy_work,5 *HZ ); +fcopy_send_data ();return ; } icmsghdr->icflags =ICMSGHDRFLAG_TRANSACTION |ICMSGHDRFLAG_RESPONSE ;
Greg Kroah-Hartman
maintainerPATCH 7/109 Drivers: hv: util: Fix a bug in the KVP code
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: "K. Y. Srinivasan" <[email protected]>
commit 9bd2d0dfe4714dd5d7c09a93a5c9ea9e14ceb3fc upstream.
Add code to poll the channel since we process only one message at a time and the host may not interrupt us. Also increase the receive buffer size since some KVP messages are close to 8K bytes in size.
--- drivers/hv/hv_kvp.c | 14 ++++++++++++-- drivers/hv/hv_util.c | 2 +- 2 files changed, 13 insertions(+), 3 deletions(-)
drivers/hv/hv_kvp.c +12 -2
@@ -127,6 +127,15 @@ kvp_work_func(struct work_struct *dummy)kvp_respond_to_host (NULL ,HV_E_FAIL ); } +static void poll_channel (struct vmbus_channel *channel) +{ +unsigned long flags; + +spin_lock_irqsave (&channel->inbound_lock, flags); +hv_kvp_onchannelcallback (channel); +spin_unlock_irqrestore (&channel->inbound_lock, flags); +} +static int kvp_handle_handshake (struct hv_kvp_msg *msg) {int ret =1 ;
@@ -155,7 +164,7 @@ static int kvp_handle_handshake(struct hkvp_register (dm_reg_value); kvp_transaction.active = false;if (kvp_transaction.kvp_context) -hv_kvp_onchannelcallback (kvp_transaction.kvp_context); +poll_channel (kvp_transaction.kvp_context); }return ret; }
@@ -568,6 +577,7 @@ response_done:vmbus_sendpacket (channel, recv_buffer, buf_len, req_id,VM_PKT_DATA_INBAND ,0 ); +poll_channel (channel); }
@@ -603,7 +613,7 @@ void hv_kvp_onchannelcallback(void *contreturn ; } -vmbus_recvpacket (channel, recv_buffer,PAGE_SIZE *2 , &recvlen, +vmbus_recvpacket (channel, recv_buffer,PAGE_SIZE *4 , &recvlen, &requestid);if (recvlen >0 ) {
drivers/hv/hv_util.c +1 -1
@@ -319,7 +319,7 @@ static int util_probe(struct hv_device * (struct hv_util_service *)dev_id->driver_data;int ret; - srv->recv_buffer =kmalloc (PAGE_SIZE *2 ,GFP_KERNEL ); + srv->recv_buffer =kmalloc (PAGE_SIZE *4 ,GFP_KERNEL );if (!srv->recv_buffer)return -ENOMEM ;if (srv->util_init) {
Greg Kroah-Hartman
maintainerPATCH 8/109 Revert "Bluetooth: Add a new PID/VID 0cf3/e005 for AR3012."
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marcel Holtmann <[email protected]>
commit a2b23bacb315d3873ed90029fd2b68c95de734c0 upstream.
This reverts commit ca58e594da2486c1d28e7ad547d82266604ec4ce.
For some unclear reason this patch tries to add suport for the product ID 0xe005, but it ends up adding product ID 0x3005 to all the tables. This is obviously wrong and causing multiple issues.
The original patch seemed to be fine, but what ended up in 3.15 is not what the patch intended. The commit 0a3658cccdf53 is already present and adds support for this hardware. This means only revert of this broken commit is requird.
--- drivers/bluetooth/ath3k.c | 2 -- drivers/bluetooth/btusb.c | 1 - 2 files changed, 3 deletions(-)
drivers/bluetooth/ath3k.c +0 -2
@@ -90,7 +90,6 @@ static const struct usb_device_id ath3k_ { USB_DEVICE(0x0b05, 0x17d0) }, { USB_DEVICE(0x0CF3, 0x0036) }, { USB_DEVICE(0x0CF3, 0x3004) }, - { USB_DEVICE(0x0CF3, 0x3005) }, { USB_DEVICE(0x0CF3, 0x3008) }, { USB_DEVICE(0x0CF3, 0x311D) }, { USB_DEVICE(0x0CF3, 0x311E) },
@@ -140,7 +139,6 @@ static const struct usb_device_id ath3k_ { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0CF3, 0x0036), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 }, - { USB_DEVICE(0x0cf3, 0x3005), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x311D), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x311E), .driver_info = BTUSB_ATH3012 },
drivers/bluetooth/btusb.c +0 -1
@@ -160,7 +160,6 @@ static const struct usb_device_id blackl { USB_DEVICE(0x0b05, 0x17d0), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x0036), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x3004), .driver_info = BTUSB_ATH3012 }, - { USB_DEVICE(0x0cf3, 0x3005), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x3008), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x311d), .driver_info = BTUSB_ATH3012 }, { USB_DEVICE(0x0cf3, 0x311e), .driver_info = BTUSB_ATH3012 },
Greg Kroah-Hartman
maintainerPATCH 9/109 Bluetooth: Ignore H5 non-link packets in non-active state
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Loic Poulain <[email protected]>
commit 48439d501e3d9e8634bdc0c418e066870039599d upstream.
When detecting a non-link packet, h5_reset_rx() frees the Rx skb. Not returning after that will cause the upcoming h5_rx_payload() call to dereference a now NULL Rx skb and trigger a kernel oops.
--- drivers/bluetooth/hci_h5.c | 1 + 1 file changed, 1 insertion(+)
drivers/bluetooth/hci_h5.c +1 -0
@@ -406,6 +406,7 @@ static int h5_rx_3wire_hdr(struct hci_ua H5_HDR_PKT_TYPE(hdr) != HCI_3WIRE_LINK_PKT) {BT_ERR ("Non-link packet received in non-active state" );h5_reset_rx (h5); +return 0 ; } h5->rx_func = h5_rx_payload;
Greg Kroah-Hartman
maintainerPATCH 10/109 fuse: timeout comparison fix
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Miklos Szeredi <[email protected]>
commit 126b9d4365b110c157bc4cbc32540dfa66c9c85a upstream.
As suggested by checkpatch.pl, use time_before64() instead of direct comparison of jiffies64 values.
--- fs/fuse/dir.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
fs/fuse/dir.c +3 -3
@@ -198,7 +198,7 @@ static int fuse_dentry_revalidate(struct inode =ACCESS_ONCE (entry->d_inode);if (inode &&is_bad_inode (inode)) goto invalid; -else if (fuse_dentry_time (entry) <get_jiffies_64 ()) { +else if (time_before64 (fuse_dentry_time (entry),get_jiffies_64 ())) {int err;struct fuse_entry_out outarg;struct fuse_req *req;
@@ -985,7 +985,7 @@ int fuse_update_attributes(struct inodeint err;bool r; -if (fi->i_time <get_jiffies_64 ()) { +if (time_before64 (fi->i_time,get_jiffies_64 ())) { r = true; err =fuse_do_getattr (inode, stat, file); }else {
@@ -1171,7 +1171,7 @@ static int fuse_permission(struct inode ((mask & MAY_EXEC) && S_ISREG(inode->i_mode))) {struct fuse_inode *fi =get_fuse_inode (inode); -if (fi->i_time <get_jiffies_64 ()) { +if (time_before64 (fi->i_time,get_jiffies_64 ())) { refreshed = true; err =fuse_perm_getattr (inode, mask);
Greg Kroah-Hartman
maintainerPATCH 11/109 fuse: avoid scheduling while atomic
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Miklos Szeredi <[email protected]>
commit c55a01d360afafcd52bc405c044a6ebf5de436d5 upstream.
As reported by Richard Sharpe, an attempt to use fuse_notify_inval_entry() triggers complains about scheduling while atomic:
BUG: scheduling while atomic: fuse.hf/13976/0x10000001
This happens because fuse_notify_inval_entry() attempts to allocate memory with GFP_KERNEL, holding "struct fuse_copy_state" mapped by kmap_atomic().
Introduced by commit 58bda1da4b3c "fuse/dev: use atomic maps"
Fix by moving the map/unmap to just cover the actual memcpy operation.
Original patch from Maxim Patlasov <[email protected]>
--- fs/fuse/dev.c | 51 +++++++++++++++++++++++---------------------------- 1 file changed, 23 insertions(+), 28 deletions(-)
fs/fuse/dev.c +23 -28
@@ -643,9 +643,8 @@ struct fuse_copy_state {unsigned long seglen;unsigned long addr;struct page *pg; -void *mapaddr; -void *buf;unsigned len; +unsigned offset; unsigned move_pages:1; };
@@ -666,23 +665,17 @@ static void fuse_copy_finish(struct fuseif (cs->currbuf) {struct pipe_buffer *buf = cs->currbuf; -if (!cs->write) { -kunmap_atomic (cs->mapaddr); - }else { -kunmap_atomic (cs->mapaddr); +if (cs->write) buf->len =PAGE_SIZE - cs->len; - } cs->currbuf =NULL ; - cs->mapaddr =NULL ; - }else if (cs->mapaddr) { -kunmap_atomic (cs->mapaddr); + }else if (cs->pg) {if (cs->write) {flush_dcache_page (cs->pg);set_page_dirty_lock (cs->pg); }put_page (cs->pg); - cs->mapaddr =NULL ; } + cs->pg =NULL ; }/*
@@ -691,7 +684,7 @@ static void fuse_copy_finish(struct fuse*/ static int fuse_copy_fill (struct fuse_copy_state *cs) { -unsigned long offset; +struct page *page;int err;unlock_request (cs->fc, cs->req);
@@ -706,14 +699,12 @@ static int fuse_copy_fill(struct fuse_coBUG_ON (!cs->nr_segs); cs->currbuf = buf; - cs->mapaddr =kmap_atomic (buf->page); + cs->pg = buf->page; + cs->offset = buf->offset; cs->len = buf->len; - cs->buf = cs->mapaddr + buf->offset; cs->pipebufs++; cs->nr_segs--; }else { -struct page *page; -if (cs->nr_segs == cs->pipe->buffers)return -EIO ;
@@ -726,8 +717,8 @@ static int fuse_copy_fill(struct fuse_co buf->len =0 ; cs->currbuf = buf; - cs->mapaddr =kmap_atomic (page); - cs->buf = cs->mapaddr; + cs->pg = page; + cs->offset =0 ; cs->len =PAGE_SIZE ; cs->pipebufs++; cs->nr_segs++;
@@ -740,14 +731,13 @@ static int fuse_copy_fill(struct fuse_co cs->iov++; cs->nr_segs--; } - err =get_user_pages_fast (cs->addr,1 , cs->write, &cs->pg); + err =get_user_pages_fast (cs->addr,1 , cs->write, &page);if (err <0 )return err;BUG_ON (err !=1 ); - offset = cs->addr %PAGE_SIZE ; - cs->mapaddr =kmap_atomic (cs->pg); - cs->buf = cs->mapaddr + offset; - cs->len =min (PAGE_SIZE - offset, cs->seglen); + cs->pg = page; + cs->offset = cs->addr %PAGE_SIZE ; + cs->len =min (PAGE_SIZE - cs->offset, cs->seglen); cs->seglen -= cs->len; cs->addr += cs->len; }
@@ -760,15 +750,20 @@ static int fuse_copy_do(struct fuse_copy {unsigned ncpy =min (*size, cs->len);if (val) { +void *pgaddr =kmap_atomic (cs->pg); +void *buf = pgaddr + cs->offset; +if (cs->write) -memcpy (cs->buf, *val, ncpy); +memcpy (buf, *val, ncpy);else -memcpy (*val, cs->buf, ncpy); +memcpy (*val, buf, ncpy); + +kunmap_atomic (pgaddr); *val += ncpy; } *size -= ncpy; cs->len -= ncpy; - cs->buf += ncpy; + cs->offset += ncpy;return ncpy; }
@@ -874,8 +869,8 @@ static int fuse_try_move_page(struct fus out_fallback_unlock:unlock_page (newpage); out_fallback: - cs->mapaddr =kmap_atomic (buf->page); - cs->buf = cs->mapaddr + buf->offset; + cs->pg = buf->page; + cs->offset = buf->offset; err =lock_request (cs->fc, cs->req);if (err)
Greg Kroah-Hartman
maintainerPATCH 12/109 fuse: handle large user and group ID
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Miklos Szeredi <[email protected]>
commit 233a01fa9c4c7c41238537e8db8434667ff28a2f upstream.
If the number in "user_id=N" or "group_id=N" mount options was larger than INT_MAX then fuse returned EINVAL.
Fix this to handle all valid uid/gid values.
--- fs/fuse/inode.c | 20 ++++++++++++++++---- 1 file changed, 16 insertions(+), 4 deletions(-)
fs/fuse/inode.c +16 -4
@@ -478,6 +478,17 @@ static const match_table_t tokens = { {OPT_ERR, NULL} }; +static int fuse_match_uint (substring_t *s,unsigned int *res) +{ +int err = -ENOMEM ; +char *buf =match_strdup (s); +if (buf) { + err =kstrtouint (buf,10 , res); +kfree (buf); + } +return err; +} +static int parse_fuse_opt (char *opt,struct fuse_mount_data *d,int is_bdev) {char *p;
@@ -488,6 +499,7 @@ static int parse_fuse_opt(char *opt, strwhile ((p =strsep (&opt,"," )) !=NULL ) {int token;int value; +unsigned uv;substring_t args[MAX_OPT_ARGS ];if (!*p)continue ;
@@ -511,18 +523,18 @@ static int parse_fuse_opt(char *opt, strbreak ;case OPT_USER_ID : -if (match_int (&args[0 ], &value)) +if (fuse_match_uint (&args[0 ], &uv))return 0 ; - d->user_id =make_kuid (current_user_ns (), value); + d->user_id =make_kuid (current_user_ns (), uv);if (!uid_valid (d->user_id))return 0 ; d->user_id_present =1 ;break ;case OPT_GROUP_ID : -if (match_int (&args[0 ], &value)) +if (fuse_match_uint (&args[0 ], &uv))return 0 ; - d->group_id =make_kgid (current_user_ns (), value); + d->group_id =make_kgid (current_user_ns (), uv);if (!gid_valid (d->group_id))return 0 ; d->group_id_present =1 ;
Greg Kroah-Hartman
maintainerPATCH 13/109 fuse: ignore entry-timeout on LOOKUP_REVAL
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Anand Avati <[email protected]>
commit 154210ccb3a871e631bf39fdeb7a8731d98af87b upstream.
The following test case demonstrates the bug:
sh# mount -t glusterfs localhost:meta-test /mnt/one
sh# mount -t glusterfs localhost:meta-test /mnt/two
sh# echo stuff > /mnt/one/file; rm -f /mnt/two/file; echo stuff > /mnt/one/file
bash: /mnt/one/file: Stale file handle
sh# echo stuff > /mnt/one/file; rm -f /mnt/two/file; sleep 1; echo stuff > /mnt/one/file
On the second open() on /mnt/one, FUSE would have used the old nodeid (file handle) trying to re-open it. Gluster is returning -ESTALE. The ESTALE propagates back to namei.c:filename_lookup() where lookup is re-attempted with LOOKUP_REVAL. The right behavior now, would be for FUSE to ignore the entry-timeout and and do the up-call revalidation. Instead FUSE is ignoring LOOKUP_REVAL, succeeding the revalidation (because entry-timeout has not passed), and open() is again retried on the old file handle and finally the ESTALE is going back to the application.
Fix: if revalidation is happening with LOOKUP_REVAL, then ignore entry-timeout and always do the up-call.
--- fs/fuse/dir.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/fuse/dir.c +2 -1
@@ -198,7 +198,8 @@ static int fuse_dentry_revalidate(struct inode =ACCESS_ONCE (entry->d_inode);if (inode &&is_bad_inode (inode)) goto invalid; -else if (time_before64 (fuse_dentry_time (entry),get_jiffies_64 ())) { +else if (time_before64 (fuse_dentry_time (entry),get_jiffies_64 ()) || + (flags &LOOKUP_REVAL )) {int err;struct fuse_entry_out outarg;struct fuse_req *req;
Greg Kroah-Hartman
maintainerPATCH 14/109 iio:core: Handle error when mask type is not separate
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Srinivas Pandruvada <[email protected]>
commit 78b3321610bf920d7fceb1a0236faa881be0bcf3 upstream.
When event spec is shared by multiple channels, which has definition for mask_shared_by_type, iio_device_register_eventset fails.
For example:
static const struct iio_event_spec iio_dummy_events[] = {
{
.type = IIO_EV_TYPE_THRESH,
.dir = IIO_EV_DIR_RISING, .mask_separate = BIT(IIO_EV_INFO_ENABLE), .mask_shared_by_type = BIT(IIO_EV_INFO_VALUE),
}, {
.type = IIO_EV_TYPE_THRESH,
.dir = IIO_EV_DIR_FALLING, .mask_separate = BIT(IIO_EV_INFO_ENABLE),a .mask_shared_by_type = BIT(IIO_EV_INFO_VALUE),
}
};
If two channels use this event spec, this will result in error.
This change handles EBUSY error similar to iio_device_add_info_mask_type().
--- drivers/iio/industrialio-event.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/iio/industrialio-event.c +3 -0
@@ -341,6 +341,9 @@ static int iio_device_add_event(struct i &indio_dev->event_interface->dev_attr_list);kfree (postfix); +if ((ret == -EBUSY ) && (shared_by !=IIO_SEPARATE )) +continue ; +if (ret)return ret;
Greg Kroah-Hartman
maintainerPATCH 15/109 tracing: instance_rmdir() leaks ftrace_event_file->filter
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oleg Nesterov <[email protected]>
commit 2448e3493cb3874baa90725c87869455ebf11cd2 upstream.
instance_rmdir() path destroys the event files but forgets to free file->filter. Change remove_event_file_dir() to free_event_filter().
--- kernel/trace/trace_events.c | 1 + 1 file changed, 1 insertion(+)
kernel/trace/trace_events.c +1 -0
@@ -470,6 +470,7 @@ static void remove_event_file_dir(structlist_del (&file->list);remove_subsystem (file->system); +free_event_filter (file->filter);kmem_cache_free (file_cachep, file); }
Greg Kroah-Hartman
maintainerPATCH 16/109 tracing: Fix graph tracer with stack tracer on other archs
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: "Steven Rostedt (Red Hat)" <[email protected]>
commit 5f8bf2d263a20b986225ae1ed7d6759dc4b93af9 upstream.
Running my ftrace tests on PowerPC, it failed the test that checks if function_graph tracer is affected by the stack tracer. It was. Looking into this, I found that the update_function_graph_func() must be called even if the trampoline function is not changed. This is because archs like PowerPC do not support ftrace_ops being passed by assembly and instead uses a helper function (what the trampoline function points to). Since this function is not changed even when multiple ftrace_ops are added to the code, the test that falls out before calling update_function_graph_func() will miss that the update must still be done.
Call update_function_graph_function() for all calls to update_ftrace_function()
--- kernel/trace/ftrace.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/trace/ftrace.c +2 -2
@@ -325,12 +325,12 @@ static void update_ftrace_function(void) func = ftrace_ops_list_func; } +update_function_graph_func (); +/* If there's no change, then do nothing more here */ if (ftrace_trace_function == func)return ; -update_function_graph_func (); -/* * If we are using the list function, it doesn't care * about the function_trace_ops.
Greg Kroah-Hartman
maintainerPATCH 17/109 tracing: Add ftrace_trace_stack into __trace_puts/__trace_bputs
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: "zhangwei(Jovi)" <[email protected]>
commit 8abfb8727f4a724d31f9ccfd8013fbd16d539445 upstream.
Currently trace option stacktrace is not applicable for trace_printk with constant string argument, the reason is in __trace_puts/__trace_bputs ftrace_trace_stack is missing.
In contrast, when using trace_printk with non constant string argument(will call into __trace_printk/__trace_bprintk), then trace option stacktrace is workable, this inconstant result will confuses users a lot.
--- kernel/trace/trace.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
kernel/trace/trace.c +10 -2
@@ -466,6 +466,9 @@ int __trace_puts(unsigned long ip, conststruct print_entry *entry;unsigned long irq_flags;int alloc; +int pc; + + pc =preempt_count ();if (unlikely (tracing_selftest_running || tracing_disabled))return 0 ;
@@ -475,7 +478,7 @@ int __trace_puts(unsigned long ip, constlocal_save_flags (irq_flags); buffer = global_trace.trace_buffer.buffer; event =trace_buffer_lock_reserve (buffer,TRACE_PRINT , alloc, - irq_flags,preempt_count ()); + irq_flags, pc);if (!event)return 0 ;
@@ -492,6 +495,7 @@ int __trace_puts(unsigned long ip, const entry->buf[size] ='\0' ;__buffer_unlock_commit (buffer, event); +ftrace_trace_stack (buffer, irq_flags,4 , pc);return size; }
@@ -509,6 +513,9 @@ int __trace_bputs(unsigned long ip, consstruct bputs_entry *entry;unsigned long irq_flags;int size =sizeof (struct bputs_entry ); +int pc; + + pc =preempt_count ();if (unlikely (tracing_selftest_running || tracing_disabled))return 0 ;
@@ -516,7 +523,7 @@ int __trace_bputs(unsigned long ip, conslocal_save_flags (irq_flags); buffer = global_trace.trace_buffer.buffer; event =trace_buffer_lock_reserve (buffer,TRACE_BPUTS , size, - irq_flags,preempt_count ()); + irq_flags, pc);if (!event)return 0 ;
@@ -525,6 +532,7 @@ int __trace_bputs(unsigned long ip, cons entry->str = str;__buffer_unlock_commit (buffer, event); +ftrace_trace_stack (buffer, irq_flags,4 , pc);return 1 ; }
Greg Kroah-Hartman
maintainerPATCH 18/109 tracing: Add TRACE_ITER_PRINTK flag check in __trace_puts/__trace_bputs
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: "zhangwei(Jovi)" <[email protected]>
commit f0160a5a2912267c02cfe692eac955c360de5fdf upstream.
The TRACE_ITER_PRINTK check in __trace_puts/__trace_bputs is missing, so add it, to be consistent with __trace_printk/__trace_bprintk. Those functions are all called by the same function: trace_printk().
--- kernel/trace/trace.c | 6 ++++++ 1 file changed, 6 insertions(+)
kernel/trace/trace.c +6 -0
@@ -468,6 +468,9 @@ int __trace_puts(unsigned long ip, constint alloc;int pc; +if (!(trace_flags &TRACE_ITER_PRINTK )) +return 0 ; + pc =preempt_count ();if (unlikely (tracing_selftest_running || tracing_disabled))
@@ -515,6 +518,9 @@ int __trace_bputs(unsigned long ip, consint size =sizeof (struct bputs_entry );int pc; +if (!(trace_flags &TRACE_ITER_PRINTK )) +return 0 ; + pc =preempt_count ();if (unlikely (tracing_selftest_running || tracing_disabled))
Greg Kroah-Hartman
maintainerPATCH 19/109 xen/balloon: set ballooned out pages as invalid in p2m
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Vrabel <[email protected]>
commit fb9a0c443691ceaab3daba966bbbd9f5ff3aa26f upstream.
Since cd9151e26d31048b2b5e00fd02e110e07d2200c9 (xen/balloon: set a mapping for ballooned out pages), a ballooned out page had its entry in the p2m set to the MFN of one of the scratch pages. This means that the p2m will contain many entries pointing to the same MFN.
During a domain save, these many-to-one entries are not identified as such and the scratch page is saved multiple times. On restore the ballooned pages are populated with new frames and the domain may use up its allocation before all pages can be restored.
Since the original fix only needed to keep a mapping for the ballooned page it is safe to set ballooned out pages as INVALID_P2M_ENTRY in the p2m (as they were before). Thus preventing them from being saved and re-populated on restore.
--- drivers/xen/balloon.c | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-)
drivers/xen/balloon.c +5 -7
@@ -426,20 +426,18 @@ static enum bp_state decrease_reservatio* p2m are consistent. */ if (!xen_feature (XENFEAT_auto_translated_physmap)) { -unsigned long p; -struct page *scratch_page =get_balloon_scratch_page (); -if (!PageHighMem (page)) { +struct page *scratch_page =get_balloon_scratch_page (); + ret =HYPERVISOR_update_va_mapping ( (unsigned long )__va (pfn <<PAGE_SHIFT ),pfn_pte (page_to_pfn (scratch_page),PAGE_KERNEL_RO ),0 );BUG_ON (ret); - } - p =page_to_pfn (scratch_page); -__set_phys_to_machine (pfn,pfn_to_mfn (p)); -put_balloon_scratch_page (); +put_balloon_scratch_page (); + } +__set_phys_to_machine (pfn,INVALID_P2M_ENTRY ); }#endif
Greg Kroah-Hartman
maintainerPATCH 20/109 xen/manage: fix potential deadlock when resuming the console
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: David Vrabel <[email protected]>
commit 1b6478231c6f5f844185acb32045cf195028cfce upstream.
Calling xen_console_resume() in xen_suspend() causes a warning because it locks irq_mapping_update_lock (a mutex) and this may sleep. If a userspace process is using the evtchn device then this mutex may be locked at the point of the stop_machine() call and xen_console_resume() would then deadlock.
Resuming the console after stop_machine() returns avoids this deadlock.
--- drivers/xen/manage.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/xen/manage.c +4 -1
@@ -109,7 +109,6 @@ static int xen_suspend(void *data)if (!si->cancelled) {xen_irq_resume (); -xen_console_resume ();xen_timer_resume (); }
@@ -166,6 +165,10 @@ static void do_suspend(void) err =stop_machine (xen_suspend, &si,cpumask_of (0 )); +/* Resume console as early as possible. */ +if (!si.cancelled) +xen_console_resume (); +raw_notifier_call_chain (&xen_resume_notifier,0 ,NULL );dpm_resume_start (si.cancelled ?PMSG_THAW :PMSG_RESTORE );
Greg Kroah-Hartman
maintainerPATCH 21/109 hwmon: (da9055) Dont use dash in the name attribute
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Axel Lin <[email protected]>
commit 6b00f440dd678d786389a7100a2e03fe44478431 upstream.
Dashes are not allowed in hwmon name attributes. Use "da9055" instead of "da9055-hwmon".
--- drivers/hwmon/da9055-hwmon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/da9055-hwmon.c +1 -1
@@ -204,7 +204,7 @@ static ssize_t da9055_hwmon_show_name(ststruct device_attribute *devattr, char *buf) { - return sprintf(buf, "da9055-hwmon\n"); + return sprintf(buf, "da9055\n"); } static ssize_t show_label(struct device *dev,
Greg Kroah-Hartman
maintainerPATCH 22/109 hwmon: (da9052) Dont use dash in the name attribute
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Axel Lin <[email protected]>
commit ee14b644daaa58afe1e91bb9ebd9cf1b18d1f5fa upstream.
Dashes are not allowed in hwmon name attributes. Use "da9052" instead of "da9052-hwmon".
--- drivers/hwmon/da9052-hwmon.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/hwmon/da9052-hwmon.c +1 -1
@@ -194,7 +194,7 @@ static ssize_t da9052_hwmon_show_name(ststruct device_attribute *devattr, char *buf) { - return sprintf(buf, "da9052-hwmon\n"); + return sprintf(buf, "da9052\n"); } static ssize_t show_label(struct device *dev,
Greg Kroah-Hartman
maintainerPATCH 23/109 hwmon: (adt7470) Fix writes to temperature limit registers
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Guenter Roeck <[email protected]>
commit de12d6f4b10b21854441f5242dcb29ea96181e58 upstream.
Temperature limit registers are signed. Limits therefore need to be clamped to (-128, 127) degrees C and not to (0, 255) degrees C.
Without this fix, writing a limit of 128 degrees C sets the actual limit to -128 degrees C.
--- drivers/hwmon/adt7470.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/hwmon/adt7470.c +3 -3
@@ -515,7 +515,7 @@ static ssize_t set_temp_min(struct devicreturn -EINVAL ; temp =DIV_ROUND_CLOSEST (temp,1000 ); - temp =clamp_val (temp,0 ,255 ); + temp =clamp_val (temp,-128 ,127 );mutex_lock (&data->lock); data->temp_min[attr->index] = temp;
@@ -549,7 +549,7 @@ static ssize_t set_temp_max(struct devicreturn -EINVAL ; temp =DIV_ROUND_CLOSEST (temp,1000 ); - temp =clamp_val (temp,0 ,255 ); + temp =clamp_val (temp,-128 ,127 );mutex_lock (&data->lock); data->temp_max[attr->index] = temp;
@@ -826,7 +826,7 @@ static ssize_t set_pwm_tmin(struct devicreturn -EINVAL ; temp =DIV_ROUND_CLOSEST (temp,1000 ); - temp =clamp_val (temp,0 ,255 ); + temp =clamp_val (temp,-128 ,127 );mutex_lock (&data->lock); data->pwm_tmin[attr->index] = temp;
Greg Kroah-Hartman
maintainerPATCH 24/109 igb: Workaround for i210 Errata 25: Slow System Clock
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Todd Fujinaka <[email protected]>
commit 948264879b6894dc389a44b99fae4f0b72932619 upstream.
On some devices, the internal PLL circuit occasionally provides the wrong clock frequency after power up. The probability of failure is less than one failure per 1000 power cycles. When the failure occurs, the internal clock frequency is around 1/20 of the correct frequency.
--- drivers/net/ethernet/intel/igb/e1000_82575.c | 7 ++ drivers/net/ethernet/intel/igb/e1000_defines.h | 18 +++--- drivers/net/ethernet/intel/igb/e1000_hw.h | 3 + drivers/net/ethernet/intel/igb/e1000_i210.c | 66 +++++++++++++++++++++++++ drivers/net/ethernet/intel/igb/e1000_i210.h | 12 ++++ drivers/net/ethernet/intel/igb/e1000_regs.h | 1 drivers/net/ethernet/intel/igb/igb_main.c | 14 +++++ 7 files changed, 113 insertions(+), 8 deletions(-)
drivers/net/ethernet/intel/igb/e1000_82575.c +7 -0
@@ -1489,6 +1489,13 @@ static s32 igb_init_hw_82575(struct e100s32 ret_val;u16 i, rar_count = mac->rar_entry_count; +if ((hw->mac.type >= e1000_i210) && + !(igb_get_flash_presence_i210 (hw))) { + ret_val =igb_pll_workaround_i210 (hw); +if (ret_val) +return ret_val; + } +/* Initialize identification LED */ ret_val =igb_id_led_init (hw);if (ret_val) {
drivers/net/ethernet/intel/igb/e1000_defines.h +10 -8
@@ -49,14 +49,15 @@#define E1000_CTRL_EXT_SDP3_DIR 0x00000800/* SDP3 Data direction */ /* Physical Func Reset Done Indication */ -#define E1000_CTRL_EXT_PFRSTD 0x00004000 -#define E1000_CTRL_EXT_LINK_MODE_MASK 0x00C00000 -#define E1000_CTRL_EXT_LINK_MODE_PCIE_SERDES 0x00C00000 -#define E1000_CTRL_EXT_LINK_MODE_1000BASE_KX 0x00400000 -#define E1000_CTRL_EXT_LINK_MODE_SGMII 0x00800000 -#define E1000_CTRL_EXT_LINK_MODE_GMII 0x00000000 -#define E1000_CTRL_EXT_EIAME 0x01000000 -#define E1000_CTRL_EXT_IRCA 0x00000001 +#define E1000_CTRL_EXT_PFRSTD 0x00004000 +#define E1000_CTRL_EXT_SDLPE 0X00040000/* SerDes Low Power Enable */ +#define E1000_CTRL_EXT_LINK_MODE_MASK 0x00C00000 +#define E1000_CTRL_EXT_LINK_MODE_PCIE_SERDES 0x00C00000 +#define E1000_CTRL_EXT_LINK_MODE_1000BASE_KX 0x00400000 +#define E1000_CTRL_EXT_LINK_MODE_SGMII 0x00800000 +#define E1000_CTRL_EXT_LINK_MODE_GMII 0x00000000 +#define E1000_CTRL_EXT_EIAME 0x01000000 +#define E1000_CTRL_EXT_IRCA 0x00000001/* Interrupt delay cancellation */ /* Driver loaded bit for FW */ #define E1000_CTRL_EXT_DRV_LOAD 0x10000000
@@ -65,6 +66,7 @@/* packet buffer parity error detection enabled */ /* descriptor FIFO parity error detection enable */ #define E1000_CTRL_EXT_PBA_CLR 0x80000000/* PBA Clear */ +#define E1000_CTRL_EXT_PHYPDEN 0x00100000#define E1000_I2CCMD_REG_ADDR_SHIFT 16#define E1000_I2CCMD_PHY_ADDR_SHIFT 24#define E1000_I2CCMD_OPCODE_READ 0x08000000
drivers/net/ethernet/intel/igb/e1000_hw.h +3 -0
@@ -571,4 +571,7 @@ struct net_device *igb_get_hw_dev(struct/* These functions must be implemented by drivers */ s32 igb_read_pcie_cap_reg (struct e1000_hw *hw,u32 reg,u16 *value);s32 igb_write_pcie_cap_reg (struct e1000_hw *hw,u32 reg,u16 *value); + +void igb_read_pci_cfg (struct e1000_hw *hw,u32 reg,u16 *value); +void igb_write_pci_cfg (struct e1000_hw *hw,u32 reg,u16 *value);#endif /* _E1000_HW_H_ */
drivers/net/ethernet/intel/igb/e1000_i210.c +66 -0
69 lines not on this page · raw message
drivers/net/ethernet/intel/igb/e1000_i210.h +12 -0
@@ -36,6 +36,7 @@ s32 igb_read_xmdio_reg(struct e1000_hw *s32 igb_write_xmdio_reg (struct e1000_hw *hw,u16 addr,u8 dev_addr,u16 data);s32 igb_init_nvm_params_i210 (struct e1000_hw *hw);bool igb_get_flash_presence_i210 (struct e1000_hw *hw); +s32 igb_pll_workaround_i210 (struct e1000_hw *hw);#define E1000_STM_OPCODE 0xDB00#define E1000_EEPROM_FLASH_SIZE_WORD 0x11
@@ -81,4 +82,15 @@ enum E1000_INVM_STRUCTURE_TYPE {#define NVM_LED_1_CFG_DEFAULT_I211 0x0184#define NVM_LED_0_2_CFG_DEFAULT_I211 0x200C +/* PLL Defines */ +#define E1000_PCI_PMCSR 0x44 +#define E1000_PCI_PMCSR_D3 0x03 +#define E1000_MAX_PLL_TRIES 5 +#define E1000_PHY_PLL_UNCONF 0xFF +#define E1000_PHY_PLL_FREQ_PAGE 0xFC0000 +#define E1000_PHY_PLL_FREQ_REG 0x000E +#define E1000_INVM_DEFAULT_AL 0x202F +#define E1000_INVM_AUTOLOAD 0x0A +#define E1000_INVM_PLL_WO_VAL 0x0010 +#endif
drivers/net/ethernet/intel/igb/e1000_regs.h +1 -0
@@ -69,6 +69,7 @@#define E1000_PBA 0x01000/* Packet Buffer Allocation - RW */ #define E1000_PBS 0x01008/* Packet Buffer Size */ #define E1000_EEMNGCTL 0x01010/* MNG EEprom Control */ +#define E1000_EEARBC_I210 0x12024/* EEPROM Auto Read Bus Control */ #define E1000_EEWR 0x0102C/* EEPROM Write Register - RW */ #define E1000_I2CCMD 0x01028/* SFPI2C Command Register - RW */ #define E1000_FRTIMER 0x01048/* Free Running Timer - RW */
drivers/net/ethernet/intel/igb/igb_main.c +14 -0
@@ -7204,6 +7204,20 @@ static int igb_ioctl(struct net_device * } } +void igb_read_pci_cfg (struct e1000_hw *hw,u32 reg,u16 *value) +{ +struct igb_adapter *adapter = hw->back; + +pci_read_config_word (adapter->pdev, reg, value); +} + +void igb_write_pci_cfg (struct e1000_hw *hw,u32 reg,u16 *value) +{ +struct igb_adapter *adapter = hw->back; + +pci_write_config_word (adapter->pdev, reg, *value); +} +s32 igb_read_pcie_cap_reg (struct e1000_hw *hw,u32 reg,u16 *value) {struct igb_adapter *adapter = hw->back;
Greg Kroah-Hartman
maintainerPATCH 25/109 igb: do a reset on SR-IOV re-init if device is down
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stefan Assmann <[email protected]>
commit 76252723e88681628a3dbb9c09c963e095476f73 upstream.
To properly re-initialize SR-IOV it is necessary to reset the device even if it is already down. Not doing this may result in Tx unit hangs.
--- drivers/net/ethernet/intel/igb/igb_main.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/net/ethernet/intel/igb/igb_main.c +2 -0
@@ -7581,6 +7581,8 @@ static int igb_sriov_reinit(struct pci_dif (netif_running (netdev))igb_close (netdev); +else +igb_reset (adapter);igb_clear_interrupt_scheme (adapter);
Greg Kroah-Hartman
maintainerPATCH 26/109 quota: missing lock in dqcache_shrink_scan()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Niu Yawei <[email protected]>
commit d68aab6b8f572406aa93b45ef6483934dd3b54a6 upstream.
Commit 1ab6c4997e04 (fs: convert fs shrinkers to new scan/count API) accidentally removed locking from quota shrinker. Fix it - dqcache_shrink_scan() should use dq_list_lock to protect the scan on free_dquots list.
--- fs/quota/dquot.c | 2 ++ 1 file changed, 2 insertions(+)
fs/quota/dquot.c +2 -0
@@ -702,6 +702,7 @@ dqcache_shrink_scan(struct shrinker *shrstruct dquot *dquot;unsigned long freed =0 ; +spin_lock (&dq_list_lock); head = free_dquots.prev;while (head != &free_dquots && sc->nr_to_scan) { dquot = list_entry(head, struct dquot, dq_free);
@@ -713,6 +714,7 @@ dqcache_shrink_scan(struct shrinker *shr freed++; head = free_dquots.prev; } +spin_unlock (&dq_list_lock);return freed; }
Greg Kroah-Hartman
maintainerPATCH 27/109 iwlwifi: update the 7265 series HW IDs
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Oren Givon <[email protected]>
commit b3c063ae7279981f7161e63b44f214c62f122b32 upstream.
Add one more 7265 series HW ID.
Edit one existing 7265 series HW ID.
--- drivers/net/wireless/iwlwifi/pcie/drv.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/wireless/iwlwifi/pcie/drv.c +2 -1
@@ -367,6 +367,7 @@ static DEFINE_PCI_DEVICE_TABLE(iwl_hw_ca {IWL_PCI_DEVICE(0x095A, 0x5012, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x5412, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x5410, iwl7265_2ac_cfg)}, + {IWL_PCI_DEVICE(0x095A, 0x5510, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x5400, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x1010, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x5000, iwl7265_2n_cfg)},
@@ -380,7 +381,7 @@ static DEFINE_PCI_DEVICE_TABLE(iwl_hw_ca {IWL_PCI_DEVICE(0x095A, 0x9110, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x9112, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x9210, iwl7265_2ac_cfg)}, - {IWL_PCI_DEVICE(0x095A, 0x9200, iwl7265_2ac_cfg)}, + {IWL_PCI_DEVICE(0x095B, 0x9200, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x9510, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x9310, iwl7265_2ac_cfg)}, {IWL_PCI_DEVICE(0x095A, 0x9410, iwl7265_2ac_cfg)},
Greg Kroah-Hartman
maintainerPATCH 28/109 iwlwifi: dvm: dont enable CTS to self
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Emmanuel Grumbach <[email protected]>
commit 43d826ca5979927131685cc2092c7ce862cb91cd upstream.
We should always prefer to use full RTS protection. Using CTS to self gives a meaningless improvement, but this flow is much harder for the firmware which is likely to have issues with it.
--- drivers/net/wireless/iwlwifi/dvm/rxon.c | 12 ------------ 1 file changed, 12 deletions(-)
drivers/net/wireless/iwlwifi/dvm/rxon.c +0 -12
@@ -1068,13 +1068,6 @@ int iwlagn_commit_rxon(struct iwl_priv */* recalculate basic rates */ iwl_calc_basic_rates (priv, ctx); -/* -* force CTS-to-self frames protection if RTS-CTS is not preferred -* one aggregation protection method -*/ -if (!priv->hw_params.use_rts_for_aggregation) - ctx->staging.flags |=RXON_FLG_SELF_CTS_EN ; -if ((ctx->vif && ctx->vif->bss_conf.use_short_slot) || !(ctx->staging.flags &RXON_FLG_BAND_24G_MSK )) ctx->staging.flags |=RXON_FLG_SHORT_SLOT_MSK ;
@@ -1480,11 +1473,6 @@ void iwlagn_bss_info_changed(struct ieeeelse ctx->staging.flags &= ~RXON_FLG_TGG_PROTECT_MSK ; -if (bss_conf->use_cts_prot) - ctx->staging.flags |=RXON_FLG_SELF_CTS_EN ; -else - ctx->staging.flags &= ~RXON_FLG_SELF_CTS_EN ; -memcpy (ctx->staging.bssid_addr, bss_conf->bssid,ETH_ALEN ); if (vif->type == NL80211_IFTYPE_AP ||
Greg Kroah-Hartman
maintainerPATCH 29/109 shmem: fix faulting into a hole while its punched
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hugh Dickins <[email protected]>
commit f00cdc6df7d7cfcabb5b740911e6788cb0802bdb upstream.
Trinity finds that mmap access to a hole while it's punched from shmem can prevent the madvise(MADV_REMOVE) or fallocate(FALLOC_FL_PUNCH_HOLE) from completing, until the reader chooses to stop; with the puncher's hold on i_mutex locking out all other writers until it can complete.
It appears that the tmpfs fault path is too light in comparison with its hole-punching path, lacking an i_data_sem to obstruct it; but we don't want to slow down the common case.
Extend shmem_fallocate()'s existing range notification mechanism, so shmem_fault() can refrain from faulting pages into the hole while it's punched, waiting instead on i_mutex (when safe to sleep; or repeatedly faulting when not).
--- mm/shmem.c | 56 ++++++++++++++++++++++++++++++++++++++++++++++++++++---- 1 file changed, 52 insertions(+), 4 deletions(-)
mm/shmem.c +52 -4
@@ -80,11 +80,12 @@ static struct vfsmount *shm_mnt;#define SHORT_SYMLINK_LEN 128/* -* shmem_fallocate and shmem_writepage communicate via inode->i_private -* (with i_mutex making sure that it has only one user at a time): -* we would prefer not to enlarge the shmem inode just for that. +* shmem_fallocate communicates with shmem_fault or shmem_writepage via +* inode->i_private (with i_mutex making sure that it has only one user at +* a time): we would prefer not to enlarge the shmem inode just for that. */ struct shmem_falloc { +int mode;/* FALLOC_FL mode currently operating */ pgoff_t start;/* start of range currently being fallocated */ pgoff_t next;/* the next page offset to be fallocated */ pgoff_t nr_falloced;/* how many new pages have been fallocated */
@@ -759,6 +760,7 @@ static int shmem_writepage(struct page *spin_lock (&inode->i_lock); shmem_falloc = inode->i_private;if (shmem_falloc && + !shmem_falloc->mode && index >= shmem_falloc->start && index < shmem_falloc->next) shmem_falloc->nr_unswapped++;
@@ -1233,6 +1235,44 @@ static int shmem_fault(struct vm_area_stint error;int ret =VM_FAULT_LOCKED ; +/* +* Trinity finds that probing a hole which tmpfs is punching can +* prevent the hole-punch from ever completing: which in turn +* locks writers out with its hold on i_mutex. So refrain from +* faulting pages into the hole while it's being punched, and +* wait on i_mutex to be released if vmf->flags permits. +*/ +if (unlikely (inode->i_private)) { +struct shmem_falloc *shmem_falloc; + +spin_lock (&inode->i_lock); + shmem_falloc = inode->i_private; +if (!shmem_falloc || + shmem_falloc->mode !=FALLOC_FL_PUNCH_HOLE || + vmf->pgoff < shmem_falloc->start || + vmf->pgoff >= shmem_falloc->next) + shmem_falloc =NULL ; +spin_unlock (&inode->i_lock); +/* +* i_lock has protected us from taking shmem_falloc seriously +* once return from shmem_fallocate() went back up that stack. +* i_lock does not serialize with i_mutex at all, but it does +* not matter if sometimes we wait unnecessarily, or sometimes +* miss out on waiting: we just need to make those cases rare. +*/ +if (shmem_falloc) { +if ((vmf->flags &FAULT_FLAG_ALLOW_RETRY ) && + !(vmf->flags &FAULT_FLAG_RETRY_NOWAIT )) { +up_read (&vma->vm_mm->mmap_sem); +mutex_lock (&inode->i_mutex); +mutex_unlock (&inode->i_mutex); +return VM_FAULT_RETRY ; + } +/* cond_resched? Leave that to GUP or return to user */ +return VM_FAULT_NOPAGE ; + } + } + error =shmem_getpage (inode, vmf->pgoff, &vmf->page,SGP_CACHE , &ret);if (error)return ((error == -ENOMEM ) ?VM_FAULT_OOM :VM_FAULT_SIGBUS );
@@ -1733,18 +1773,26 @@ static long shmem_fallocate(struct filemutex_lock (&inode->i_mutex); + shmem_falloc.mode = mode & ~FALLOC_FL_KEEP_SIZE ; +if (mode &FALLOC_FL_PUNCH_HOLE ) {struct address_space *mapping = file->f_mapping;loff_t unmap_start =round_up (offset,PAGE_SIZE );loff_t unmap_end =round_down (offset + len,PAGE_SIZE ) -1 ; + shmem_falloc.start = unmap_start >>PAGE_SHIFT ; + shmem_falloc.next = (unmap_end +1 ) >>PAGE_SHIFT ; +spin_lock (&inode->i_lock); + inode->i_private = &shmem_falloc; +spin_unlock (&inode->i_lock); +if ((u64 )unmap_end > (u64 )unmap_start)unmap_mapping_range (mapping, unmap_start,1 + unmap_end - unmap_start,0 );shmem_truncate_range (inode, offset, offset + len -1 );/* No need to unmap again: hole-punching leaves COWed pages */ error =0 ; - goto out; + goto undone; }/* We need to check rlimit even when FALLOC_FL_KEEP_SIZE */
Greg Kroah-Hartman
maintainerPATCH 30/109 shmem: fix faulting into a hole, not taking i_mutex
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hugh Dickins <[email protected]>
commit 8e205f779d1443a94b5ae81aa359cb535dd3021e upstream.
Commit f00cdc6df7d7 ("shmem: fix faulting into a hole while it's punched") was buggy: Sasha sent a lockdep report to remind us that grabbing i_mutex in the fault path is a no-no (write syscall may already hold i_mutex while faulting user buffer).
We tried a completely different approach (see following patch) but that proved inadequate: good enough for a rational workload, but not good enough against trinity - which forks off so many mappings of the object that contention on i_mmap_mutex while hole-puncher holds i_mutex builds into serious starvation when concurrent faults force the puncher to fall back to single-page unmap_mapping_range() searches of the i_mmap tree.
So return to the original umbrella approach, but keep away from i_mutex this time. We really don't want to bloat every shmem inode with a new mutex or completion, just to protect this unlikely case from trinity. So extend the original with wait_queue_head on stack at the hole-punch end, and wait_queue item on the stack at the fault end.
This involves further use of i_lock to guard against the races: lockdep has been happy so far, and I see fs/inode.c:unlock_new_inode() holds i_lock around wake_up_bit(), which is comparable to what we do here. i_lock is more convenient, but we could switch to shmem's info->lock.
This issue has been tagged with CVE-2014-4171, which will require commit f00cdc6df7d7 and this and the following patch to be backported: we suggest to 3.1+, though in fact the trinity forkbomb effect might go back as far as 2.6.16, when madvise(,,MADV_REMOVE) came in - or might not, since much has changed, with i_mmap_mutex a spinlock before 3.0. Anyone running trinity on 3.0 and earlier? I don't think we need care.
--- mm/shmem.c | 78 ++++++++++++++++++++++++++++++++++++++++--------------------- 1 file changed, 52 insertions(+), 26 deletions(-)
mm/shmem.c +52 -26
@@ -85,7 +85,7 @@ static struct vfsmount *shm_mnt;* a time): we would prefer not to enlarge the shmem inode just for that. */ struct shmem_falloc { -int mode;/* FALLOC_FL mode currently operating */ +wait_queue_head_t *waitq;/* faults into hole wait for punch to end */ pgoff_t start;/* start of range currently being fallocated */ pgoff_t next;/* the next page offset to be fallocated */ pgoff_t nr_falloced;/* how many new pages have been fallocated */
@@ -760,7 +760,7 @@ static int shmem_writepage(struct page *spin_lock (&inode->i_lock); shmem_falloc = inode->i_private;if (shmem_falloc && - !shmem_falloc->mode && + !shmem_falloc->waitq && index >= shmem_falloc->start && index < shmem_falloc->next) shmem_falloc->nr_unswapped++;
@@ -1239,38 +1239,58 @@ static int shmem_fault(struct vm_area_st* Trinity finds that probing a hole which tmpfs is punching can * prevent the hole-punch from ever completing: which in turn * locks writers out with its hold on i_mutex. So refrain from -* faulting pages into the hole while it's being punched, and -* wait on i_mutex to be released if vmf->flags permits. +* faulting pages into the hole while it's being punched. Although +* shmem_undo_range() does remove the additions, it may be unable to +* keep up, as each new page needs its own unmap_mapping_range() call, +* and the i_mmap tree grows ever slower to scan if new vmas are added. +* +* It does not matter if we sometimes reach this check just before the +* hole-punch begins, so that one fault then races with the punch: +* we just need to make racing faults a rare case. +* +* The implementation below would be much simpler if we just used a +* standard mutex or completion: but we cannot take i_mutex in fault, +* and bloating every shmem inode for this unlikely case would be sad. */ if (unlikely (inode->i_private)) {struct shmem_falloc *shmem_falloc;spin_lock (&inode->i_lock); shmem_falloc = inode->i_private; -if (!shmem_falloc || - shmem_falloc->mode !=FALLOC_FL_PUNCH_HOLE || - vmf->pgoff < shmem_falloc->start || - vmf->pgoff >= shmem_falloc->next) - shmem_falloc =NULL ; -spin_unlock (&inode->i_lock); -/* -* i_lock has protected us from taking shmem_falloc seriously -* once return from shmem_fallocate() went back up that stack. -* i_lock does not serialize with i_mutex at all, but it does -* not matter if sometimes we wait unnecessarily, or sometimes -* miss out on waiting: we just need to make those cases rare. -*/ -if (shmem_falloc) { +if (shmem_falloc && + shmem_falloc->waitq && + vmf->pgoff >= shmem_falloc->start && + vmf->pgoff < shmem_falloc->next) { +wait_queue_head_t *shmem_falloc_waitq; +DEFINE_WAIT (shmem_fault_wait); + + ret =VM_FAULT_NOPAGE ;if ((vmf->flags &FAULT_FLAG_ALLOW_RETRY ) && !(vmf->flags &FAULT_FLAG_RETRY_NOWAIT )) { +/* It's polite to up mmap_sem if we can */ up_read (&vma->vm_mm->mmap_sem); -mutex_lock (&inode->i_mutex); -mutex_unlock (&inode->i_mutex); -return VM_FAULT_RETRY ; + ret =VM_FAULT_RETRY ; } -/* cond_resched? Leave that to GUP or return to user */ -return VM_FAULT_NOPAGE ; + + shmem_falloc_waitq = shmem_falloc->waitq; +prepare_to_wait (shmem_falloc_waitq, &shmem_fault_wait, +TASK_UNINTERRUPTIBLE ); +spin_unlock (&inode->i_lock); +schedule (); + +/* +* shmem_falloc_waitq points into the shmem_fallocate() +* stack of the hole-punching task: shmem_falloc_waitq +* is usually invalid by the time we reach here, but +* finish_wait() does not dereference it in that case; +* though i_lock needed lest racing with wake_up_all(). +*/ +spin_lock (&inode->i_lock); +finish_wait (shmem_falloc_waitq, &shmem_fault_wait); +spin_unlock (&inode->i_lock); +return ret; } +spin_unlock (&inode->i_lock); } error =shmem_getpage (inode, vmf->pgoff, &vmf->page,SGP_CACHE , &ret);
@@ -1773,13 +1793,13 @@ static long shmem_fallocate(struct filemutex_lock (&inode->i_mutex); - shmem_falloc.mode = mode & ~FALLOC_FL_KEEP_SIZE ; -if (mode &FALLOC_FL_PUNCH_HOLE ) {struct address_space *mapping = file->f_mapping;loff_t unmap_start =round_up (offset,PAGE_SIZE );loff_t unmap_end =round_down (offset + len,PAGE_SIZE ) -1 ; +DECLARE_WAIT_QUEUE_HEAD_ONSTACK (shmem_falloc_waitq); + shmem_falloc.waitq = &shmem_falloc_waitq; shmem_falloc.start = unmap_start >>PAGE_SHIFT ; shmem_falloc.next = (unmap_end +1 ) >>PAGE_SHIFT ;spin_lock (&inode->i_lock);
@@ -1791,8 +1811,13 @@ static long shmem_fallocate(struct file 1 + unmap_end - unmap_start, 0);shmem_truncate_range (inode, offset, offset + len -1 );/* No need to unmap again: hole-punching leaves COWed pages */ + +spin_lock (&inode->i_lock); + inode->i_private =NULL ; +wake_up_all (&shmem_falloc_waitq); +spin_unlock (&inode->i_lock); error =0 ; - goto undone; + goto out; }/* We need to check rlimit even when FALLOC_FL_KEEP_SIZE */
@@ -1808,6 +1833,7 @@ static long shmem_fallocate(struct file goto out; } + shmem_falloc.waitq =NULL ; shmem_falloc.start = start; shmem_falloc.next = start; shmem_falloc.nr_falloced =0 ;
Greg Kroah-Hartman
maintainerPATCH 31/109 shmem: fix splicing from a hole while its punched
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hugh Dickins <[email protected]>
commit b1a366500bd537b50c3aad26dc7df083ec03a448 upstream.
shmem_fault() is the actual culprit in trinity's hole-punch starvation, and the most significant cause of such problems: since a page faulted is one that then appears page_mapped(), needing unmap_mapping_range() and i_mmap_mutex to be unmapped again.
But it is not the only way in which a page can be brought into a hole in the radix_tree while that hole is being punched; and Vlastimil's testing implies that if enough other processors are busy filling in the hole, then shmem_undo_range() can be kept from completing indefinitely.
shmem_file_splice_read() is the main other user of SGP_CACHE, which can instantiate shmem pagecache pages in the read-only case (without holding i_mutex, so perhaps concurrently with a hole-punch). Probably it's silly not to use SGP_READ already (using the ZERO_PAGE for holes): which ought to be safe, but might bring surprises - not a change to be rushed.
shmem_read_mapping_page_gfp() is an internal interface used by drivers/gpu/drm GEM (and next by uprobes): it should be okay. And shmem_file_read_iter() uses the SGP_DIRTY variant of SGP_CACHE, when called internally by the kernel (perhaps for a stacking filesystem, which might rely on holes to be reserved): it's unclear whether it could be provoked to keep hole-punch busy or not.
We could apply the same umbrella as now used in shmem_fault() to shmem_file_splice_read() and the others; but it looks ugly, and use over a range raises questions - should it actually be per page? can these get starved themselves?
The origin of this part of the problem is my v3.1 commit d0823576bf4b ("mm: pincer in truncate_inode_pages_range"), once it was duplicated into shmem.c. It seemed like a nice idea at the time, to ensure (barring RCU lookup fuzziness) that there's an instant when the entire hole is empty; but the indefinitely repeated scans to ensure that make it vulnerable.
Revert that "enhancement" to hole-punch from shmem_undo_range(), but retain the unproblematic rescanning when it's truncating; add a couple of comments there.
Remove the "indices[0] >= end" test: that is now handled satisfactorily by the inner loop, and mem_cgroup_uncharge_start()/end() are too light to be worth avoiding here.
But if we do not always loop indefinitely, we do need to handle the case of swap swizzled back to page before shmem_free_swap() gets it: add a retry for that case, as suggested by Konstantin Khlebnikov; and for the case of page swizzled back to swap, as suggested by Johannes Weiner.
--- mm/shmem.c | 24 +++++++++++++++--------- 1 file changed, 15 insertions(+), 9 deletions(-)
mm/shmem.c +15 -9
@@ -468,23 +468,20 @@ static void shmem_undo_range(struct inodreturn ; index = start; -for ( ; ; ) { +while (index < end) {cond_resched (); pvec.nr =find_get_entries (mapping, index,min (end - index, (pgoff_t )PAGEVEC_SIZE ), pvec.pages, indices);if (!pvec.nr) { -if (index == start || unfalloc) +/* If all gone or hole-punch or unfalloc, we're done */ +if (index == start || end !=-1 )break ; +/* But if truncating, restart to make sure all gone */ index = start;continue ; } -if ((index == start || unfalloc) && indices[0 ] >= end) { -pagevec_remove_exceptionals (&pvec); -pagevec_release (&pvec); -break ; - }mem_cgroup_uncharge_start ();for (i =0 ; i <pagevec_count (&pvec); i++) {struct page *page = pvec.pages[i];
@@ -496,8 +493,12 @@ static void shmem_undo_range(struct inodif (radix_tree_exceptional_entry (page)) {if (unfalloc)continue ; - nr_swaps_freed += !shmem_free_swap (mapping, - index, page); +if (shmem_free_swap (mapping, index, page)) { +/* Swap was replaced by page: retry */ + index--; +break ; + } + nr_swaps_freed++;continue ; }
@@ -506,6 +507,11 @@ static void shmem_undo_range(struct inodif (page->mapping == mapping) {VM_BUG_ON_PAGE (PageWriteback (page), page);truncate_inode_page (mapping, page); + }else { +/* Page was replaced by swap: retry */ +unlock_page (page); + index--; +break ; } }unlock_page (page);
Greg Kroah-Hartman
maintainerPATCH 32/109 net/mlx4_core: Fix the error flow when probing with invalid VF configuration
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Or Gerlitz <[email protected]>
[ Upstream commit 960b1f454e1ace6b76718f22828bcc3594a09422 ]
Single ported VF are currently not supported on configurations where one or both ports are IB. When we hit this case, the relevant flow in the driver didn't return error and jumped to the wrong label. Fix that.
--- drivers/net/ethernet/mellanox/mlx4/main.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/mellanox/mlx4/main.c +2 -1
@@ -2466,7 +2466,8 @@ slave_start:"with IB port. Single port VFs syntax" " is only supported when all ports " "are configured as ethernet\n"); - goto err_close; + err = -EINVAL ; + goto err_master_mfunc; }for (i =0 ; i <sizeof (nvfs)/sizeof (nvfs[0 ]); i++) {unsigned j;
Greg Kroah-Hartman
maintainerPATCH 33/109 net/mlx4_en: Dont configure the HW vxlan parser when vxlan offloading isnt set
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Or Gerlitz <[email protected]>
[ Upstream commit e326f2f13b209d56782609e833b87cb497e64b3b ]
The add_vxlan_port ndo driver code was wrongly testing whether HW vxlan offloads are supported by the device instead of checking if they are currently enabled.
This causes the driver to configure the HW parser to conduct matching for vxlan packets but since no steering rules were set, vxlan packets are dropped on RX.
Fix that by doing the right test, as done in the del_vxlan_port ndo handler.
--- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/mellanox/mlx4/en_netdev.c +1 -1
@@ -2303,7 +2303,7 @@ static void mlx4_en_add_vxlan_port(strucstruct mlx4_en_priv *priv =netdev_priv (dev);__be16 current_port; -if (!(priv->mdev->dev->caps.flags2 &MLX4_DEV_CAP_FLAG2_VXLAN_OFFLOADS )) +if (priv->mdev->dev->caps.tunnel_offload_mode !=MLX4_TUNNEL_OFFLOAD_MODE_VXLAN )return ;if (sa_family ==AF_INET6 )
Greg Kroah-Hartman
maintainerPATCH 34/109 ip_tunnel: fix ip_tunnel_lookup
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dmitry Popov <[email protected]>
[ Upstream commit e0056593b61253f1a8a9941dacda22e73b963cdc ]
This patch fixes 3 similar bugs where incoming packets might be routed into wrong non-wildcard tunnels:
1) Consider the following setup:
ip address add 1.1.1.1/24 dev eth0
ip address add 1.1.1.2/24 dev eth0
ip tunnel add ipip1 remote 2.2.2.2 local 1.1.1.1 mode ipip dev eth0 ip link set ipip1 up
Incoming ipip packets from 2.2.2.2 were routed into ipip1 even if it has dst = 1.1.1.2. Moreover even if there was wildcard tunnel like
ip tunnel add ipip0 remote 2.2.2.2 local any mode ipip dev eth0
but it was created before explicit one (with local 1.1.1.1), incoming ipip packets with src = 2.2.2.2 and dst = 1.1.1.2 were still routed into ipip1.
Same issue existed with all tunnels that use ip_tunnel_lookup (gre, vti)
2) ip address add 1.1.1.1/24 dev eth0
ip tunnel add ipip1 remote 2.2.146.85 local 1.1.1.1 mode ipip dev eth0 ip link set ipip1 up
Incoming ipip packets with dst = 1.1.1.1 were routed into ipip1, no matter what src address is. Any remote ip address which has ip_tunnel_hash = 0 raised this issue, 2.2.146.85 is just an example, there are more than 4 million of them. And again, wildcard tunnel like
ip tunnel add ipip0 remote any local 1.1.1.1 mode ipip dev eth0
wouldn't be ever matched if it was created before explicit tunnel like above.
Gre & vti tunnels had the same issue.
3) ip address add 1.1.1.1/24 dev eth0
ip tunnel add gre1 remote 2.2.146.84 local 1.1.1.1 key 1 mode gre dev eth0 ip link set gre1 up
Any incoming gre packet with key = 1 were routed into gre1, no matter what src/dst addresses are. Any remote ip address which has ip_tunnel_hash = 0 raised the issue, 2.2.146.84 is just an example, there are more than 4 million of them. Wildcard tunnel like
ip tunnel add gre2 remote any local any key 1 mode gre dev eth0
wouldn't be ever matched if it was created before explicit tunnel like above.
All this stuff happened because while looking for a wildcard tunnel we didn't check that matched tunnel is a wildcard one. Fixed.
--- net/ipv4/ip_tunnel.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
net/ipv4/ip_tunnel.c +8 -4
@@ -173,6 +173,7 @@ struct ip_tunnel *ip_tunnel_lookup(struchlist_for_each_entry_rcu (t, head, hash_node) {if (remote != t->parms.iph.daddr || + t->parms.iph.saddr !=0 || !(t->dev->flags &IFF_UP ))continue ;
@@ -189,10 +190,11 @@ struct ip_tunnel *ip_tunnel_lookup(struc head = &itn->tunnels[hash];hlist_for_each_entry_rcu (t, head, hash_node) { -if ((local != t->parms.iph.saddr && - (local != t->parms.iph.daddr || - !ipv4_is_multicast (local))) || - !(t->dev->flags &IFF_UP )) +if ((local != t->parms.iph.saddr || t->parms.iph.daddr !=0 ) && + (local != t->parms.iph.daddr || !ipv4_is_multicast (local))) +continue ; + +if (!(t->dev->flags &IFF_UP ))continue ;if (!ip_tunnel_key_match (&t->parms, flags, key))
@@ -209,6 +211,8 @@ struct ip_tunnel *ip_tunnel_lookup(struchlist_for_each_entry_rcu (t, head, hash_node) {if (t->parms.i_key != key || + t->parms.iph.saddr !=0 || + t->parms.iph.daddr !=0 || !(t->dev->flags &IFF_UP ))continue ;
Greg Kroah-Hartman
maintainerPATCH 35/109 slip: Fix deadlock in write_wakeup
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tyler Hall <[email protected]>
[ Upstream commit 661f7fda21b15ec52f57fcd397c03370acc28688 ]
Use schedule_work() to avoid potentially taking the spinlock in interrupt context.
Commit cc9fa74e2a ("slip/slcan: added locking in wakeup function") added necessary locking to the wakeup function and 367525c8c2/ddcde142be ("can:
slcan: Fix spinlock variant") converted it to spin_lock_bh() because the lock is also taken in timers.
Disabling softirqs is not sufficient, however, as tty drivers may call write_wakeup from interrupt context. This driver calls tty->ops->write() with its spinlock held, which may immediately cause an interrupt on the same CPU and subsequent spin_bug().
Simply converting to spin_lock_irq/irqsave() prevents this deadlock, but causes lockdep to point out a possible circular locking dependency between these locks:
(&(&sl->lock)->rlock){-.....}, at: slip_write_wakeup (&port_lock_key){-.....}, at: serial8250_handle_irq.part.13
The slip transmit is holding the slip spinlock when calling the tty write. This grabs the port lock. On an interrupt, the handler grabs the port lock and calls write_wakeup which grabs the slip lock. This could be a problem if a serial interrupt occurs on another CPU during the slip transmit.
To deal with these issues, don't grab the lock in the wakeup function by deferring the writeout to a workqueue. Also hold the lock during close when de-assigning the tty pointer to safely disarm the worker and timers.
This bug is easily reproducible on the first transmit when slip is used with the standard 8250 serial driver.
[<c0410b7c>] (spin_bug+0x0/0x38) from [<c006109c>] (do_raw_spin_lock+0x60/0x1d0)
r5:eab27000 r4:ec02754c
[<c006103c>] (do_raw_spin_lock+0x0/0x1d0) from [<c04185c0>] (_raw_spin_lock+0x28/0x2c)
r10:0000001f r9:eabb814c r8:eabb8140 r7:40070193 r6:ec02754c r5:eab27000 r4:ec02754c r3:00000000
[<c0418598>] (_raw_spin_lock+0x0/0x2c) from [<bf3a0220>] (slip_write_wakeup+0x50/0xe0 [slip])
r4:ec027540 r3:00000003
[<bf3a01d0>] (slip_write_wakeup+0x0/0xe0 [slip]) from [<c026e420>] (tty_wakeup+0x48/0x68)
r6:00000000 r5:ea80c480 r4:eab27000 r3:bf3a01d0
[<c026e3d8>] (tty_wakeup+0x0/0x68) from [<c028a8ec>] (uart_write_wakeup+0x2c/0x30)
r5:ed68ea90 r4:c06790d8
[<c028a8c0>] (uart_write_wakeup+0x0/0x30) from [<c028dc44>] (serial8250_tx_chars+0x114/0x170) [<c028db30>] (serial8250_tx_chars+0x0/0x170) from [<c028dffc>] (serial8250_handle_irq+0xa0/0xbc)
r6:000000c2 r5:00000060 r4:c06790d8 r3:00000000
[<c028df5c>] (serial8250_handle_irq+0x0/0xbc) from [<c02933a4>] (dw8250_handle_irq+0x38/0x64)
r7:00000000 r6:edd2f390 r5:000000c2 r4:c06790d8
[<c029336c>] (dw8250_handle_irq+0x0/0x64) from [<c028d2f4>] (serial8250_interrupt+0x44/0xc4)
r6:00000000 r5:00000000 r4:c06791c4 r3:c029336c
[<c028d2b0>] (serial8250_interrupt+0x0/0xc4) from [<c0067fe4>] (handle_irq_event_percpu+0xb4/0x2b0)
r10:c06790d8 r9:eab27000 r8:00000000 r7:00000000 r6:0000001f r5:edd52980 r4:ec53b6c0 r3:c028d2b0
[<c0067f30>] (handle_irq_event_percpu+0x0/0x2b0) from [<c006822c>] (handle_irq_event+0x4c/0x6c)
r10:c06790d8 r9:eab27000 r8:c0673ae0 r7:c05c2020 r6:ec53b6c0 r5:edd529d4 r4:edd52980
[<c00681e0>] (handle_irq_event+0x0/0x6c) from [<c006b140>] (handle_level_irq+0xe8/0x100)
r6:00000000 r5:edd529d4 r4:edd52980 r3:00022000
[<c006b058>] (handle_level_irq+0x0/0x100) from [<c00676f8>] (generic_handle_irq+0x30/0x40)
r5:0000001f r4:0000001f
[<c00676c8>] (generic_handle_irq+0x0/0x40) from [<c000f57c>] (handle_IRQ+0xd0/0x13c)
r4:ea997b18 r3:000000e0
[<c000f4ac>] (handle_IRQ+0x0/0x13c) from [<c00086c4>] (armada_370_xp_handle_irq+0x4c/0x118)
r8:000003ff r7:ea997b18 r6:ffffffff r5:60070013 r4:c0674dc0
[<c0008678>] (armada_370_xp_handle_irq+0x0/0x118) from [<c0013840>] (__irq_svc+0x40/0x70)
Exception stack(0xea997b18 to 0xea997b60)
7b00: 00000001 20070013
7b20: 00000000 0000000b 20070013 eab27000 20070013 00000000 ed10103e eab27000 7b40: c06790d8 ea997b74 ea997b60 ea997b60 c04186c0 c04186c8 60070013 ffffffff
r9:eab27000 r8:ed10103e r7:ea997b4c r6:ffffffff r5:60070013 r4:c04186c8
[<c04186a4>] (_raw_spin_unlock_irqrestore+0x0/0x54) from [<c0288fc0>] (uart_start+0x40/0x44)
r4:c06790d8 r3:c028ddd8
[<c0288f80>] (uart_start+0x0/0x44) from [<c028982c>] (uart_write+0xe4/0xf4)
r6:0000003e r5:00000000 r4:ed68ea90 r3:0000003e
[<c0289748>] (uart_write+0x0/0xf4) from [<bf3a0d20>] (sl_xmit+0x1c4/0x228 [slip])
r10:ed388e60 r9:0000003c r8:ffffffdd r7:0000003e r6:ec02754c r5:ea717eb8 r4:ec027000
[<bf3a0b5c>] (sl_xmit+0x0/0x228 [slip]) from [<c0368d74>] (dev_hard_start_xmit+0x39c/0x6d0)
r8:eaf163c0 r7:ec027000 r6:ea717eb8 r5:00000000 r4:00000000
--- drivers/net/slip/slip.c | 36 ++++++++++++++++++++++++++---------- drivers/net/slip/slip.h | 1 + 2 files changed, 27 insertions(+), 10 deletions(-)
drivers/net/slip/slip.c +26 -10
@@ -83,6 +83,7 @@#include <linux/delay.h> #include <linux/init.h> #include <linux/slab.h> +#include <linux/workqueue.h> #include "slip.h" #ifdef CONFIG_INET #include <linux/ip.h>
@@ -416,36 +417,46 @@ static void sl_encaps(struct slip *sl, u#endif } -/* -* Called by the driver when there's room for more data. If we have -* more packets to send, we send them here. -*/ -static void slip_write_wakeup (struct tty_struct *tty) +/* Write out any remaining transmit buffer. Scheduled when tty is writable */ +static void slip_transmit (struct work_struct *work) { + struct slip *sl = container_of(work, struct slip, tx_work);int actual; -struct slip *sl = tty->disc_data; +spin_lock_bh (&sl->lock);/* First make sure we're connected. */ -if (!sl || sl->magic !=SLIP_MAGIC || !netif_running (sl->dev)) +if (!sl->tty || sl->magic !=SLIP_MAGIC || !netif_running (sl->dev)) { +spin_unlock_bh (&sl->lock);return ; + } -spin_lock_bh (&sl->lock);if (sl->xleft <=0 ) {/* Now serial buffer is almost free & we can start * transmission of another packet */ sl->dev->stats.tx_packets++; -clear_bit (TTY_DO_WRITE_WAKEUP , &tty->flags); +clear_bit (TTY_DO_WRITE_WAKEUP , &sl->tty->flags);spin_unlock_bh (&sl->lock);sl_unlock (sl);return ; } - actual = tty->ops->write (tty, sl->xhead, sl->xleft); + actual = sl->tty->ops->write (sl->tty, sl->xhead, sl->xleft); sl->xleft -= actual; sl->xhead += actual;spin_unlock_bh (&sl->lock); } +/* +* Called by the driver when there's room for more data. +* Schedule the transmit. +*/ +static void slip_write_wakeup (struct tty_struct *tty) +{ +struct slip *sl = tty->disc_data; + +schedule_work (&sl->tx_work); +} +static void sl_tx_timeout (struct net_device *dev) {struct slip *sl =netdev_priv (dev);
@@ -749,6 +760,7 @@ static struct slip *sl_alloc(dev_t line) sl->magic =SLIP_MAGIC ; sl->dev = dev;spin_lock_init (&sl->lock); +INIT_WORK (&sl->tx_work, slip_transmit); sl->mode =SL_MODE_DEFAULT ;#ifdef CONFIG_SLIP_SMART /* initialize timer_list struct */
@@ -872,8 +884,12 @@ static void slip_close(struct tty_structif (!sl || sl->magic !=SLIP_MAGIC || sl->tty != tty)return ; +spin_lock_bh (&sl->lock); tty->disc_data =NULL ; sl->tty =NULL ; +spin_unlock_bh (&sl->lock); + +flush_work (&sl->tx_work);/* VSV = very important to remove timers */ #ifdef CONFIG_SLIP_SMART
drivers/net/slip/slip.h +1 -0
@@ -53,6 +53,7 @@ struct slip {struct tty_struct *tty;/* ptr to TTY structure */ struct net_device *dev;/* easy for intr handling */ spinlock_t lock; +struct work_struct tx_work;/* Flushes transmit buffer */ #ifdef SL_INCLUDE_CSLIP struct slcompress *slcomp;/* for header compression */
Greg Kroah-Hartman
maintainerPATCH 36/109 slcan: Port write_wakeup deadlock fix from slip
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tyler Hall <[email protected]>
[ Upstream commit a8e83b17536aad603fbeae4c460f2da0ee9fe6ed ]
The commit "slip: Fix deadlock in write_wakeup" fixes a deadlock caused by a change made in both slcan and slip. This is a direct port of that fix.
--- drivers/net/can/slcan.c | 37 +++++++++++++++++++++++++++---------- 1 file changed, 27 insertions(+), 10 deletions(-)
drivers/net/can/slcan.c +27 -10
@@ -52,6 +52,7 @@#include <linux/delay.h> #include <linux/init.h> #include <linux/kernel.h> +#include <linux/workqueue.h> #include <linux/can.h> #include <linux/can/skb.h>
@@ -85,6 +86,7 @@ struct slcan {struct tty_struct *tty;/* ptr to TTY structure */ struct net_device *dev;/* easy for intr handling */ spinlock_t lock; +struct work_struct tx_work;/* Flushes transmit buffer */ /* These are pointers to the malloc()ed frame buffers. */ unsigned char rbuff[SLC_MTU ];/* receiver buffer */
@@ -309,36 +311,46 @@ static void slc_encaps(struct slcan *sl, sl->dev->stats.tx_bytes += cf->can_dlc; } -/* -* Called by the driver when there's room for more data. If we have -* more packets to send, we send them here. -*/ -static void slcan_write_wakeup (struct tty_struct *tty) +/* Write out any remaining transmit buffer. Scheduled when tty is writable */ +static void slcan_transmit (struct work_struct *work) { + struct slcan *sl = container_of(work, struct slcan, tx_work);int actual; -struct slcan *sl = (struct slcan *) tty->disc_data; +spin_lock_bh (&sl->lock);/* First make sure we're connected. */ -if (!sl || sl->magic !=SLCAN_MAGIC || !netif_running (sl->dev)) +if (!sl->tty || sl->magic !=SLCAN_MAGIC || !netif_running (sl->dev)) { +spin_unlock_bh (&sl->lock);return ; + } -spin_lock_bh (&sl->lock);if (sl->xleft <=0 ) {/* Now serial buffer is almost free & we can start * transmission of another packet */ sl->dev->stats.tx_packets++; -clear_bit (TTY_DO_WRITE_WAKEUP , &tty->flags); +clear_bit (TTY_DO_WRITE_WAKEUP , &sl->tty->flags);spin_unlock_bh (&sl->lock);netif_wake_queue (sl->dev);return ; } - actual = tty->ops->write (tty, sl->xhead, sl->xleft); + actual = sl->tty->ops->write (sl->tty, sl->xhead, sl->xleft); sl->xleft -= actual; sl->xhead += actual;spin_unlock_bh (&sl->lock); } +/* +* Called by the driver when there's room for more data. +* Schedule the transmit. +*/ +static void slcan_write_wakeup (struct tty_struct *tty) +{ +struct slcan *sl = tty->disc_data; + +schedule_work (&sl->tx_work); +} +/* Send a can_frame to a TTY queue. */ static netdev_tx_t slc_xmit (struct sk_buff *skb,struct net_device *dev) {
@@ -528,6 +540,7 @@ static struct slcan *slc_alloc(dev_t lin sl->magic =SLCAN_MAGIC ; sl->dev = dev;spin_lock_init (&sl->lock); +INIT_WORK (&sl->tx_work, slcan_transmit); slcan_devs[i] = dev;return sl;
@@ -626,8 +639,12 @@ static void slcan_close(struct tty_strucif (!sl || sl->magic !=SLCAN_MAGIC || sl->tty != tty)return ; +spin_lock_bh (&sl->lock); tty->disc_data =NULL ; sl->tty =NULL ; +spin_unlock_bh (&sl->lock); + +flush_work (&sl->tx_work);/* Flush network side */ unregister_netdev (sl->dev);
Greg Kroah-Hartman
maintainerPATCH 37/109 net: sctp: propagate sysctl errors from proc_do* properly
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit ff5e92c1affe7166b3f6e7073e648ed65a6e2e59 ]
sysctl handler proc_sctp_do_hmac_alg(), proc_sctp_do_rto_min() and proc_sctp_do_rto_max() do not properly reflect some error cases when writing values via sysctl from internal proc functions such as proc_dointvec() and proc_dostring().
In all these cases we pass the test for write != 0 and partially do additional work just to notice that additional sanity checks fail and we return with hard-coded -EINVAL while proc_do* functions might also return different errors. So fix this up by simply testing a successful return of proc_do* right after calling it.
This also allows to propagate its return value onwards to the user. While touching this, also fix up some minor style issues.
--- net/sctp/sysctl.c | 43 +++++++++++++++++++++++-------------------- 1 file changed, 23 insertions(+), 20 deletions(-)
net/sctp/sysctl.c +23 -20
@@ -307,41 +307,40 @@ static int proc_sctp_do_hmac_alg(struct loff_t *ppos) {struct net *net = current->nsproxy->net_ns; -char tmp[8 ];struct ctl_table tbl; -int ret; -int changed =0 ; +bool changed = false;char *none ="none" ; +char tmp[8 ]; +int ret;memset (&tbl,0 ,sizeof (struct ctl_table ));if (write) { tbl.data = tmp; - tbl.maxlen =8 ; + tbl.maxlen =sizeof (tmp); }else { tbl.data = net->sctp.sctp_hmac_alg ? : none; tbl.maxlen =strlen (tbl.data); } - ret =proc_dostring (&tbl, write, buffer, lenp, ppos); -if (write) { + ret =proc_dostring (&tbl, write, buffer, lenp, ppos); +if (write && ret ==0 ) {#ifdef CONFIG_CRYPTO_MD5 if (!strncmp (tmp,"md5" ,3 )) { net->sctp.sctp_hmac_alg ="md5" ; - changed =1 ; + changed = true; }#endif #ifdef CONFIG_CRYPTO_SHA1 if (!strncmp (tmp,"sha1" ,4 )) { net->sctp.sctp_hmac_alg ="sha1" ; - changed =1 ; + changed = true; }#endif if (!strncmp (tmp,"none" ,4 )) { net->sctp.sctp_hmac_alg =NULL ; - changed =1 ; + changed = true; } -if (!changed) ret = -EINVAL ; }
@@ -354,11 +353,10 @@ static int proc_sctp_do_rto_min(struct c loff_t *ppos) {struct net *net = current->nsproxy->net_ns; -int new_value; -struct ctl_table tbl;unsigned int min = *(unsigned int *) ctl->extra1;unsigned int max = *(unsigned int *) ctl->extra2; -int ret; +struct ctl_table tbl; +int ret, new_value;memset (&tbl,0 ,sizeof (struct ctl_table )); tbl.maxlen =sizeof (unsigned int );
@@ -367,12 +365,15 @@ static int proc_sctp_do_rto_min(struct c tbl.data = &new_value; else tbl.data = &net->sctp.rto_min; + ret =proc_dointvec (&tbl, write, buffer, lenp, ppos); -if (write) { -if (ret || new_value > max || new_value < min) +if (write && ret ==0 ) { +if (new_value > max || new_value < min)return -EINVAL ; + net->sctp.rto_min = new_value; } +return ret; }
@@ -381,11 +382,10 @@ static int proc_sctp_do_rto_max(struct c loff_t *ppos) {struct net *net = current->nsproxy->net_ns; -int new_value; -struct ctl_table tbl;unsigned int min = *(unsigned int *) ctl->extra1;unsigned int max = *(unsigned int *) ctl->extra2; -int ret; +struct ctl_table tbl; +int ret, new_value;memset (&tbl,0 ,sizeof (struct ctl_table )); tbl.maxlen =sizeof (unsigned int );
@@ -394,12 +394,15 @@ static int proc_sctp_do_rto_max(struct c tbl.data = &new_value; else tbl.data = &net->sctp.rto_max; + ret =proc_dointvec (&tbl, write, buffer, lenp, ppos); -if (write) { -if (ret || new_value > max || new_value < min) +if (write && ret ==0 ) { +if (new_value > max || new_value < min)return -EINVAL ; + net->sctp.rto_max = new_value; } +return ret; }
Greg Kroah-Hartman
maintainerPATCH 38/109 net: filter: fix upper BPF instruction limit
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kees Cook <[email protected]>
[ Upstream commit 6f9a093b66ce7cacc110d8737c03686e80ecfda6 ]
The original checks (via sk_chk_filter) for instruction count uses ">", not ">=", so changing this in sk_convert_filter has the potential to break existing seccomp filters that used exactly BPF_MAXINSNS many instructions.
--- net/core/filter.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/core/filter.c +1 -1
@@ -872,7 +872,7 @@ int sk_convert_filter(struct sock_filterBUILD_BUG_ON (BPF_MEMWORDS *sizeof (u32) >MAX_BPF_STACK );BUILD_BUG_ON (FP_REG +1 !=MAX_BPF_REG ); -if (len <=0 || len >=BPF_MAXINSNS ) +if (len <=0 || len >BPF_MAXINSNS )return -EINVAL ;if (new_prog) {
Greg Kroah-Hartman
maintainerPATCH 39/109 tcp: fix tcp_match_skb_to_sack() for unaligned SACK at end of an skb
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Neal Cardwell <[email protected]>
[ Upstream commit 2cd0d743b05e87445c54ca124a9916f22f16742e ]
If there is an MSS change (or misbehaving receiver) that causes a SACK to arrive that covers the end of an skb but is less than one MSS, then tcp_match_skb_to_sack() was rounding up pkt_len to the full length of the skb ("Round if necessary..."), then chopping all bytes off the skb and creating a zero-byte skb in the write queue.
This was visible now because the recently simplified TLP logic in bef1909ee3ed1c ("tcp: fixing TLP's FIN recovery") could find that 0-byte skb at the end of the write queue, and now that we do not check that skb's length we could send it as a TLP probe.
Consider the following example scenario:
mss: 1000
skb: seq: 0 end_seq: 4000 len: 4000
SACK: start_seq: 3999 end_seq: 4000
The tcp_match_skb_to_sack() code will compute:
in_sack = false
pkt_len = start_seq - TCP_SKB_CB(skb)->seq = 3999 - 0 = 3999 new_len = (pkt_len / mss) * mss = (3999/1000)*1000 = 3000 new_len += mss = 4000
Previously we would find the new_len > skb->len check failing, so we would fall through and set pkt_len = new_len = 4000 and chop off pkt_len of 4000 from the 4000-byte skb, leaving a 0-byte segment afterward in the write queue.
With this new commit, we notice that the new new_len >= skb->len check succeeds, so that we return without trying to fragment.
--- net/ipv4/tcp_input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv4/tcp_input.c +1 -1
@@ -1162,7 +1162,7 @@ static int tcp_match_skb_to_sack(structunsigned int new_len = (pkt_len / mss) * mss;if (!in_sack && new_len < pkt_len) { new_len += mss; -if (new_len > skb->len) +if (new_len >= skb->len)return 0 ; } pkt_len = new_len;
Greg Kroah-Hartman
maintainerPATCH 40/109 net: sctp: check proc_dointvec result in proc_sctp_do_auth
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 24599e61b7552673dd85971cf5a35369cd8c119e ]
When writing to the sysctl field net.sctp.auth_enable, it can well be that the user buffer we handed over to proc_dointvec() via proc_sctp_do_auth() handler contains something other than integers.
In that case, we would set an uninitialized 4-byte value from the stack to net->sctp.auth_enable that can be leaked back when reading the sysctl variable, and it can unintentionally turn auth_enable on/off based on the stack content since auth_enable is interpreted as a boolean.
Fix it up by making sure proc_dointvec() returned sucessfully.
--- net/sctp/sysctl.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
net/sctp/sysctl.c +1 -2
@@ -423,8 +423,7 @@ static int proc_sctp_do_auth(struct ctl_ tbl.data = &net->sctp.auth_enable; ret =proc_dointvec (&tbl, write, buffer, lenp, ppos); - -if (write) { +if (write && ret ==0 ) {struct sock *sk = net->sctp.ctl_sock; net->sctp.auth_enable = new_value;
Greg Kroah-Hartman
maintainerPATCH 41/109 8021q: fix a potential memory leak
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Li RongQing <[email protected]>
[ Upstream commit 916c1689a09bc1ca81f2d7a34876f8d35aadd11b ]
skb_cow called in vlan_reorder_header does not free the skb when it failed, and vlan_reorder_header returns NULL to reset original skb when it is called in vlan_untag, lead to a memory leak.
--- net/8021q/vlan_core.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
net/8021q/vlan_core.c +4 -1
@@ -114,8 +114,11 @@ EXPORT_SYMBOL(vlan_dev_vlan_proto);static struct sk_buff *vlan_reorder_header (struct sk_buff *skb) { -if (skb_cow (skb,skb_headroom (skb)) <0 ) +if (skb_cow (skb,skb_headroom (skb)) <0 ) { +kfree_skb (skb);return NULL ; + } +memmove (skb->data -ETH_HLEN , skb->data -VLAN_ETH_HLEN ,2 *ETH_ALEN ); skb->mac_header +=VLAN_HLEN ;return skb;
Greg Kroah-Hartman
maintainerPATCH 42/109 drivers: net: cpsw: fix dual EMAC stall when connected to same switch
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mugunthan V N <[email protected]>
[ Upstream commit e6afea0bbf129f88dc3fc39fd0d769f9ff064172 ]
In commit 629c9a8fd0bbdfc6d702526b327470166ec39c6b (drivers: net: cpsw: Add default vlan for dual emac case also), api cpsw_add_default_vlan() also changes the port vlan which is required to seperate the ports which results in the following behavior
In Dual EMAC mode, when both the Etnernet connected is connected to same switch, it creates a loop in the switch and when a broadcast packet is received it is forwarded to the other port which stalls the whole switch and needs a reset/power cycle to the switch to recover. So intead of using the api, add only the default VLAN entry in dual EMAC case.
--- drivers/net/ethernet/ti/cpsw.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-)
drivers/net/ethernet/ti/cpsw.c +6 -1
@@ -1201,7 +1201,12 @@ static int cpsw_ndo_open(struct net_devifor_each_slave (priv, cpsw_slave_open, priv);/* Add default VLAN */ -cpsw_add_default_vlan (priv); +if (!priv->data.dual_emac) +cpsw_add_default_vlan (priv); +else +cpsw_ale_add_vlan (priv->ale, priv->data.default_vlan, +ALE_ALL_PORTS << priv->host_port, +ALE_ALL_PORTS << priv->host_port,0 ,0 );if (!cpsw_common_res_usage_state (priv)) {/* setup tx dma to fixed prio and zero offset */
Greg Kroah-Hartman
maintainerPATCH 44/109 net: fix UDP tunnel GSO of frag_list GRO packets
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Wei-Chun Chao <[email protected]>
[ Upstream commit 5882a07c72093dc3a18e2d2b129fb200686bb6ee ]
This patch fixes a kernel BUG_ON in skb_segment. It is hit when testing two VMs on openvswitch with one VM acting as VXLAN gateway.
During VXLAN packet GSO, skb_segment is called with skb->data pointing to inner TCP payload. skb_segment calls skb_network_protocol to retrieve the inner protocol. skb_network_protocol actually expects skb->data to point to MAC and it calls pskb_may_pull with ETH_HLEN. This ends up pulling in ETH_HLEN data from header tail. As a result, pskb_trim logic is skipped and BUG_ON is hit later.
Move skb_push in front of skb_network_protocol so that skb->data lines up properly.
kernel BUG at net/core/skbuff.c:2999!
Call Trace: [<ffffffff816ac412>] tcp_gso_segment+0x122/0x410 [<ffffffff816bc74c>] inet_gso_segment+0x13c/0x390 [<ffffffff8164b39b>] skb_mac_gso_segment+0x9b/0x170 [<ffffffff816b3658>] skb_udp_tunnel_segment+0xd8/0x390 [<ffffffff816b3c00>] udp4_ufo_fragment+0x120/0x140 [<ffffffff816bc74c>] inet_gso_segment+0x13c/0x390 [<ffffffff8109d742>] ? default_wake_function+0x12/0x20 [<ffffffff8164b39b>] skb_mac_gso_segment+0x9b/0x170 [<ffffffff8164b4d0>] __skb_gso_segment+0x60/0xc0 [<ffffffff8164b6b3>] dev_hard_start_xmit+0x183/0x550 [<ffffffff8166c91e>] sch_direct_xmit+0xfe/0x1d0 [<ffffffff8164bc94>] __dev_queue_xmit+0x214/0x4f0 [<ffffffff8164bf90>] dev_queue_xmit+0x10/0x20 [<ffffffff81687edb>] ip_finish_output+0x66b/0x890 [<ffffffff81688a58>] ip_output+0x58/0x90 [<ffffffff816c628f>] ? fib_table_lookup+0x29f/0x350 [<ffffffff816881c9>] ip_local_out_sk+0x39/0x50 [<ffffffff816cbfad>] iptunnel_xmit+0x10d/0x130 [<ffffffffa0212200>] vxlan_xmit_skb+0x1d0/0x330 [vxlan] [<ffffffffa02a3919>] vxlan_tnl_send+0x129/0x1a0 [openvswitch] [<ffffffffa02a2cd6>] ovs_vport_send+0x26/0xa0 [openvswitch] [<ffffffffa029931e>] do_output+0x2e/0x50 [openvswitch]
--- net/core/skbuff.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/core/skbuff.c +2 -1
@@ -2881,12 +2881,13 @@ struct sk_buff *skb_segment(struct sk_buint pos;int dummy; +__skb_push (head_skb, doffset); proto =skb_network_protocol (head_skb, &dummy);if (unlikely (!proto))return ERR_PTR (-EINVAL ); csum = !!can_checksum_protocol (features, proto); -__skb_push (head_skb, doffset); + headroom =skb_headroom (head_skb); pos =skb_headlen (head_skb);
Greg Kroah-Hartman
maintainerPATCH 45/109 ipv4: fix dst race in sk_dst_get()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit f88649721268999bdff09777847080a52004f691 ]
When IP route cache had been removed in linux-3.6, we broke assumption that dst entries were all freed after rcu grace period. DST_NOCACHE dst were supposed to be freed from dst_release(). But it appears we want to keep such dst around, either in UDP sockets or tunnels.
In sk_dst_get() we need to make sure dst refcount is not 0 before incrementing it, or else we might end up freeing a dst twice.
DST_NOCACHE set on a dst does not mean this dst can not be attached to a socket or a tunnel.
Then, before actual freeing, we need to observe a rcu grace period to make sure all other cpus can catch the fact the dst is no longer usable.
--- include/net/sock.h | 4 ++-- net/core/dst.c | 16 +++++++++++----- net/ipv4/ip_tunnel.c | 14 +++++--------- 3 files changed, 18 insertions(+), 16 deletions(-)
include/net/sock.h +2 -2
@@ -1728,8 +1728,8 @@ sk_dst_get(struct sock *sk)rcu_read_lock (); dst =rcu_dereference (sk->sk_dst_cache); -if (dst) -dst_hold (dst); +if (dst && !atomic_inc_not_zero (&dst->__refcnt)) + dst =NULL ;rcu_read_unlock ();return dst; }
net/core/dst.c +11 -5
@@ -269,6 +269,15 @@ again: }EXPORT_SYMBOL (dst_destroy); +static void dst_destroy_rcu (struct rcu_head *head) +{ + struct dst_entry *dst = container_of(head, struct dst_entry, rcu_head); + + dst =dst_destroy (dst); +if (dst) +__dst_free (dst); +} +void dst_release (struct dst_entry *dst) {if (dst) {
@@ -276,11 +285,8 @@ void dst_release(struct dst_entry *dst) newrefcnt =atomic_dec_return (&dst->__refcnt);WARN_ON (newrefcnt <0 ); -if (unlikely (dst->flags &DST_NOCACHE ) && !newrefcnt) { - dst =dst_destroy (dst); -if (dst) -__dst_free (dst); - } +if (unlikely (dst->flags &DST_NOCACHE ) && !newrefcnt) +call_rcu (&dst->rcu_head, dst_destroy_rcu); } }EXPORT_SYMBOL (dst_release);
net/ipv4/ip_tunnel.c +5 -9
@@ -73,12 +73,7 @@ static void __tunnel_dst_set(struct ip_t {struct dst_entry *old_dst; -if (dst) { -if (dst->flags &DST_NOCACHE ) - dst =NULL ; -else -dst_clone (dst); - } +dst_clone (dst); old_dst =xchg ((__force struct dst_entry **)&idst->dst, dst);dst_release (old_dst); }
@@ -108,13 +103,14 @@ static struct rtable *tunnel_rtable_get(rcu_read_lock (); dst =rcu_dereference (this_cpu_ptr (t->dst_cache)->dst); +if (dst && !atomic_inc_not_zero (&dst->__refcnt)) + dst =NULL ;if (dst) {if (dst->obsolete && dst->ops->check (dst, cookie) ==NULL ) { -rcu_read_unlock ();tunnel_dst_reset (t); -return NULL ; +dst_release (dst); + dst =NULL ; } -dst_hold (dst); }rcu_read_unlock ();return (struct rtable *)dst;
Greg Kroah-Hartman
maintainerPATCH 46/109 ipv4: irq safe sk_dst_[re]set() and ipv4_sk_update_pmtu() fix
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 7f502361531e9eecb396cf99bdc9e9a59f7ebd7f ]
We have two different ways to handle changes to sk->sk_dst
First way (used by TCP) assumes socket lock is owned by caller, and use no extra lock : __sk_dst_set() & __sk_dst_reset()
Another way (used by UDP) uses sk_dst_lock because socket lock is not always taken. Note that sk_dst_lock is not softirq safe.
These ways are not inter changeable for a given socket type.
ipv4_sk_update_pmtu(), added in linux-3.8, added a race, as it used the socket lock as synchronization, but users might be UDP sockets.
Instead of converting sk_dst_lock to a softirq safe version, use xchg() as we did for sk_rx_dst in commit e47eb5dfb296b ("udp: ipv4: do not use sk_dst_lock from softirq context")
In a follow up patch, we probably can remove sk_dst_lock, as it is only used in IPv6.
--- include/net/sock.h | 12 ++++++------ net/ipv4/route.c | 15 ++++++++------- 2 files changed, 14 insertions(+), 13 deletions(-)
include/net/sock.h +6 -6
@@ -1766,9 +1766,11 @@ __sk_dst_set(struct sock *sk, struct dststatic inline void sk_dst_set (struct sock *sk,struct dst_entry *dst) { -spin_lock (&sk->sk_dst_lock); -__sk_dst_set (sk, dst); -spin_unlock (&sk->sk_dst_lock); +struct dst_entry *old_dst; + +sk_tx_queue_clear (sk); + old_dst =xchg (&sk->sk_dst_cache, dst); +dst_release (old_dst); } static inline void
@@ -1780,9 +1782,7 @@ __sk_dst_reset(struct sock *sk)static inline void sk_dst_reset (struct sock *sk) { -spin_lock (&sk->sk_dst_lock); -__sk_dst_reset (sk); -spin_unlock (&sk->sk_dst_lock); +sk_dst_set (sk,NULL ); }struct dst_entry *__sk_dst_check (struct sock *sk,u32 cookie);
net/ipv4/route.c +8 -7
@@ -1022,7 +1022,7 @@ void ipv4_sk_update_pmtu(struct sk_buffconst struct iphdr *iph = (const struct iphdr *) skb->data;struct flowi4 fl4;struct rtable *rt; -struct dst_entry *dst; +struct dst_entry *odst =NULL ;bool new = false;bh_lock_sock (sk);
@@ -1030,16 +1030,17 @@ void ipv4_sk_update_pmtu(struct sk_buffif (!ip_sk_accept_pmtu (sk)) goto out; - rt = (struct rtable *)__sk_dst_get (sk); + odst =sk_dst_get (sk); -if (sock_owned_by_user (sk) || !rt) { +if (sock_owned_by_user (sk) || !odst) {__ipv4_sk_update_pmtu (skb, sk, mtu); goto out; }__build_flow_key (&fl4, sk, iph,0 ,0 ,0 ,0 ,0 ); -if (!__sk_dst_check (sk,0 )) { + rt = (struct rtable *)odst; +if (odst->obsolete && odst->ops->check (odst,0 ) ==NULL ) { rt =ip_route_output_flow (sock_net (sk), &fl4, sk);if (IS_ERR (rt)) goto out;
@@ -1049,8 +1050,7 @@ void ipv4_sk_update_pmtu(struct sk_buff__ip_rt_update_pmtu ((struct rtable *) rt->dst.path, &fl4, mtu); - dst =dst_check (&rt->dst,0 ); -if (!dst) { +if (!dst_check (&rt->dst,0 )) {if (new)dst_release (&rt->dst);
@@ -1062,10 +1062,11 @@ void ipv4_sk_update_pmtu(struct sk_buff }if (new) -__sk_dst_set (sk, &rt->dst); +sk_dst_set (sk, &rt->dst); out:bh_unlock_sock (sk); +dst_release (odst); }EXPORT_SYMBOL_GPL (ipv4_sk_update_pmtu);
Greg Kroah-Hartman
maintainerPATCH 47/109 net: fix sparse warning in sk_dst_set()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 5925a0555bdaf0b396a84318cbc21ba085f6c0d3 ]
sk_dst_cache has __rcu annotation, so we need a cast to avoid following sparse error :
include/net/sock.h:1774:19: warning: incorrect type in initializer (different address spaces)include/net/sock.h:1774:19: expected struct dst_entry [noderef] <asn:4>*__retinclude/net/sock.h:1774:19: got struct dst_entry *dst
--- include/net/sock.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
include/net/sock.h +1 -1
@@ -1769,7 +1769,7 @@ sk_dst_set(struct sock *sk, struct dst_estruct dst_entry *old_dst;sk_tx_queue_clear (sk); - old_dst =xchg (&sk->sk_dst_cache, dst); + old_dst =xchg ((__force struct dst_entry **)&sk->sk_dst_cache, dst);dst_release (old_dst); }
Greg Kroah-Hartman
maintainerPATCH 48/109 vlan: free percpu stats in device destructor
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit a48e5fafecfb9c0c807d7e7284b5ff884dfb7a3a ]
Madalin-Cristian reported crashs happening after a recent commit (5a4ae5f6e7d4 "vlan: unnecessary to check if vlan_pcpu_stats is NULL")
-----------------------------------------------------------------------
root@p5040ds:~# vconfig add eth8 1 root@p5040ds:~# vconfig rem eth8.1 Unable to handle kernel paging request for data at address 0x2bc88028 Faulting instruction address: 0xc058e950 Oops: Kernel access of bad area, sig: 11 [#1] SMP NR_CPUS=8 CoreNet Generic Modules linked in: CPU: 3 PID: 2167 Comm: vconfig Tainted: G W 3.16.0-rc3-00346-g65e85bf #2 task: e7264d90 ti: e2c2c000 task.ti: e2c2c000 NIP: c058e950 LR: c058ea30 CTR: c058e900 REGS: e2c2db20 TRAP: 0300 Tainted: G W (3.16.0-rc3-00346-g65e85bf) MSR: 00029002 <CE,EE,ME> CR: 48000428 XER: 20000000 DEAR: 2bc88028 ESR: 00000000 GPR00: c047299c e2c2dbd0 e7264d90 00000000 2bc88000 00000000 ffffffff 00000000 GPR08: 0000000f 00000000 000000ff 00000000 28000422 10121928 10100000 10100000 GPR16: 10100000 00000000 c07c5968 00000000 00000000 00000000 e2c2dc48 e7838000 GPR24: c07c5bac c07c58a8 e77290cc c07b0000 00000000 c05de6c0 e7838000 e2c2dc48 NIP [c058e950] vlan_dev_get_stats64+0x50/0x170 LR [c058ea30] vlan_dev_get_stats64+0x130/0x170 Call Trace: [e2c2dbd0] [ffffffea] 0xffffffea (unreliable) [e2c2dc20] [c047299c] dev_get_stats+0x4c/0x140 [e2c2dc40] [c0488ca8] rtnl_fill_ifinfo+0x3d8/0x960 [e2c2dd70] [c0489f4c] rtmsg_ifinfo+0x6c/0x110 [e2c2dd90] [c04731d4] rollback_registered_many+0x344/0x3b0 [e2c2ddd0] [c047332c] rollback_registered+0x2c/0x50 [e2c2ddf0] [c0476058] unregister_netdevice_queue+0x78/0xf0 [e2c2de00] [c058d800] unregister_vlan_dev+0xc0/0x160 [e2c2de20] [c058e360] vlan_ioctl_handler+0x1c0/0x550 [e2c2de90] [c045d11c] sock_ioctl+0x28c/0x2f0 [e2c2deb0] [c010d070] do_vfs_ioctl+0x90/0x7b0 [e2c2df20] [c010d7d0] SyS_ioctl+0x40/0x80 [e2c2df40] [c000f924] ret_from_syscall+0x0/0x3c
Fix this problem by freeing percpu stats from dev->destructor() instead of ndo_uninit()
--- net/8021q/vlan_dev.c | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-)
net/8021q/vlan_dev.c +10 -3
@@ -627,8 +627,6 @@ static void vlan_dev_uninit(struct net_dstruct vlan_dev_priv *vlan =vlan_dev_priv (dev);int i; -free_percpu (vlan->vlan_pcpu_stats); - vlan->vlan_pcpu_stats =NULL ;for (i =0 ; i <ARRAY_SIZE (vlan->egress_priority_map); i++) {while ((pm = vlan->egress_priority_map[i]) !=NULL ) { vlan->egress_priority_map[i] = pm->next;
@@ -787,6 +785,15 @@ static const struct net_device_ops vlan_ .ndo_get_lock_subclass = vlan_dev_get_lock_subclass, }; +static void vlan_dev_free (struct net_device *dev) +{ +struct vlan_dev_priv *vlan =vlan_dev_priv (dev); + +free_percpu (vlan->vlan_pcpu_stats); + vlan->vlan_pcpu_stats =NULL ; +free_netdev (dev); +} +void vlan_setup (struct net_device *dev) {ether_setup (dev);
@@ -796,7 +803,7 @@ void vlan_setup(struct net_device *dev) dev->tx_queue_len =0 ; dev->netdev_ops = &vlan_netdev_ops; - dev->destructor = free_netdev; + dev->destructor = vlan_dev_free; dev->ethtool_ops = &vlan_ethtool_ops;memset (dev->broadcast,0 ,ETH_ALEN );
Greg Kroah-Hartman
maintainerPATCH 49/109 bnx2x: fix possible panic under memory stress
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 07b0f00964def8af9321cfd6c4a7e84f6362f728 ]
While it is legal to kfree(NULL), it is not wise to use :
put_page(virt_to_head_page(NULL))
BUG: unable to handle kernel paging request at ffffeba400000000 IP: [<ffffffffc01f5928>] virt_to_head_page+0x36/0x44 [bnx2x]
--- drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c +2 -1
@@ -797,7 +797,8 @@ static void bnx2x_tpa_stop(struct bnx2xreturn ; } -bnx2x_frag_free (fp, new_data); +if (new_data) +bnx2x_frag_free (fp, new_data); drop:/* drop the packet and keep the buffer in the bin */ DP(NETIF_MSG_RX_STATUS,
Greg Kroah-Hartman
maintainerPATCH 50/109 tcp: Fix divide by zero when pushing during tcp-repair
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Paasch <[email protected]>
[ Upstream commit 5924f17a8a30c2ae18d034a86ee7581b34accef6 ]
When in repair-mode and TCP_RECV_QUEUE is set, we end up calling tcp_push with mss_now being 0. If data is in the send-queue and tcp_set_skb_tso_segs gets called, we crash because it will divide by mss_now:
[ 347.151939] divide error: 0000 [#1] SMP [ 347.152907] Modules linked in: [ 347.152907] CPU: 1 PID: 1123 Comm: packetdrill Not tainted 3.16.0-rc2 #4 [ 347.152907] Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007 [ 347.152907] task: f5b88540 ti: f3c82000 task.ti: f3c82000 [ 347.152907] EIP: 0060:[<c1601359>] EFLAGS: 00210246 CPU: 1 [ 347.152907] EIP is at tcp_set_skb_tso_segs+0x49/0xa0 [ 347.152907] EAX: 00000b67 EBX: f5acd080 ECX: 00000000 EDX: 00000000 [ 347.152907] ESI: f5a28f40 EDI: f3c88f00 EBP: f3c83d10 ESP: f3c83d00 [ 347.152907] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 347.152907] CR0: 80050033 CR2: 083158b0 CR3: 35146000 CR4: 000006b0 [ 347.152907] Stack: [ 347.152907] c167f9d9 f5acd080 000005b4 00000002 f3c83d20 c16013e6 f3c88f00 f5acd080 [ 347.152907] f3c83da0 c1603b5a f3c83d38 c10a0188 00000000 00000000 f3c83d84 c10acc85 [ 347.152907] c1ad5ec0 00000000 00000000 c1ad679c 010003e0 00000000 00000000 f3c88fc8 [ 347.152907] Call Trace: [ 347.152907] [<c167f9d9>] ? apic_timer_interrupt+0x2d/0x34 [ 347.152907] [<c16013e6>] tcp_init_tso_segs+0x36/0x50 [ 347.152907] [<c1603b5a>] tcp_write_xmit+0x7a/0xbf0 [ 347.152907] [<c10a0188>] ? up+0x28/0x40 [ 347.152907] [<c10acc85>] ? console_unlock+0x295/0x480 [ 347.152907] [<c10ad24f>] ? vprintk_emit+0x1ef/0x4b0 [ 347.152907] [<c1605716>] __tcp_push_pending_frames+0x36/0xd0 [ 347.152907] [<c15f4860>] tcp_push+0xf0/0x120 [ 347.152907] [<c15f7641>] tcp_sendmsg+0xf1/0xbf0 [ 347.152907] [<c116d920>] ? kmem_cache_free+0xf0/0x120 [ 347.152907] [<c106a682>] ? __sigqueue_free+0x32/0x40 [ 347.152907] [<c106a682>] ? __sigqueue_free+0x32/0x40 [ 347.152907] [<c114f0f0>] ? do_wp_page+0x3e0/0x850 [ 347.152907] [<c161c36a>] inet_sendmsg+0x4a/0xb0 [ 347.152907] [<c1150269>] ? handle_mm_fault+0x709/0xfb0 [ 347.152907] [<c15a006b>] sock_aio_write+0xbb/0xd0 [ 347.152907] [<c1180b79>] do_sync_write+0x69/0xa0 [ 347.152907] [<c1181023>] vfs_write+0x123/0x160 [ 347.152907] [<c1181d55>] SyS_write+0x55/0xb0 [ 347.152907] [<c167f0d8>] sysenter_do_call+0x12/0x28
This can easily be reproduced with the following packetdrill-script (the "magic" with netem, sk_pacing and limit_output_bytes is done to prevent the kernel from pushing all segments, because hitting the limit without doing this is not so easy with packetdrill):
0 socket(..., SOCK_STREAM, IPPROTO_TCP) = 3
+0 setsockopt(3, SOL_SOCKET, SO_REUSEADDR, [1], 4) = 0
+0 bind(3, ..., ...) = 0
+0 listen(3, 1) = 0
+0 < S 0:0(0) win 32792 <mss 1460>
+0 > S. 0:0(0) ack 1 <mss 1460>
+0.1 < . 1:1(0) ack 1 win 65000
+0 accept(3, ..., ...) = 4
// This forces that not all segments of the snd-queue will be pushed +0 tc qdisc add dev tun0 root netem delay 10ms
+0 sysctl -w net.ipv4.tcp_limit_output_bytes=2
+0 setsockopt(4, SOL_SOCKET, 47, [2], 4) = 0
+0 write(4,...,10000) = 10000
+0 write(4,...,10000) = 10000
// Set tcp-repair stuff, particularly TCP_RECV_QUEUE +0 setsockopt(4, SOL_TCP, 19, [1], 4) = 0
+0 setsockopt(4, SOL_TCP, 20, [1], 4) = 0
// This now will make the write push the remaining segments +0 setsockopt(4, SOL_SOCKET, 47, [20000], 4) = 0 +0 sysctl -w net.ipv4.tcp_limit_output_bytes=130000
// Now we will crash
+0 write(4,...,1000) = 1000
This happens since ec3423257508 (tcp: fix retransmission in repair mode). Prior to that, the call to tcp_push was prevented by a check for tp->repair.
The patch fixes it, by adding the new goto-label out_nopush. When exiting tcp_sendmsg and a push is not required, which is the case for tp->repair, we go to this label.
When repairing and calling send() with TCP_RECV_QUEUE, the data is actually put in the receive-queue. So, no push is required because no data has been added to the send-queue.
--- net/ipv4/tcp.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/ipv4/tcp.c +2 -1
@@ -1108,7 +1108,7 @@ int tcp_sendmsg(struct kiocb *iocb, struif (unlikely (tp->repair)) {if (tp->repair_queue ==TCP_RECV_QUEUE ) { copied =tcp_send_rcvq (sk, msg, size); - goto out; + goto out_nopush; } err = -EINVAL ;
@@ -1282,6 +1282,7 @@ wait_for_memory: out:if (copied)tcp_push (sk, flags, mss_now, tp->nonagle, size_goal); +out_nopush:release_sock (sk);return copied + copied_syn;
Greg Kroah-Hartman
maintainerPATCH 51/109 ipv4: icmp: Fix pMTU handling for rare case
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Edward Allcutt <[email protected]>
[ Upstream commit 68b7107b62983f2cff0948292429d5f5999df096 ]
Some older router implementations still send Fragmentation Needed errors with the Next-Hop MTU field set to zero. This is explicitly described as an eventuality that hosts must deal with by the standard (RFC 1191) since older standards specified that those bits must be zero.
Linux had a generic (for all of IPv4) implementation of the algorithm described in the RFC for searching a list of MTU plateaus for a good value. Commit 46517008e116 ("ipv4: Kill ip_rt_frag_needed().") removed this as part of the changes to remove the routing cache. Subsequently any Fragmentation Needed packet with a zero Next-Hop MTU has been discarded without being passed to the per-protocol handlers or notifying userspace for raw sockets.
When there is a router which does not implement RFC 1191 on an MTU limited path then this results in stalled connections since large packets are discarded and the local protocols are not notified so they never attempt to lower the pMTU.
One example I have seen is an OpenBSD router terminating IPSec tunnels. It's worth pointing out that this case is distinct from the BSD 4.2 bug which incorrectly calculated the Next-Hop MTU since the commit in question dismissed that as a valid concern.
All of the per-protocols handlers implement the simple approach from RFC 1191 of immediately falling back to the minimum value. Although this is sub-optimal it is vastly preferable to connections hanging indefinitely.
Remove the Next-Hop MTU != 0 check and allow such packets to follow the normal path.
--- net/ipv4/icmp.c | 2 -- 1 file changed, 2 deletions(-)
net/ipv4/icmp.c +0 -2
@@ -732,8 +732,6 @@ static void icmp_unreach(struct sk_buff/* fall through */ case 0 : info =ntohs (icmph->un.frag.mtu); -if (!info) - goto out; }break ;case ICMP_SR_FAILED :
Greg Kroah-Hartman
maintainerPATCH 54/109 net: Fix NETDEV_CHANGE notifier usage causing spurious arp flush
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Loic Prylli <[email protected]>
[ Upstream commit 54951194656e4853e441266fd095f880bc0398f3 ]
A bug was introduced in NETDEV_CHANGE notifier sequence causing the arp table to be sometimes spuriously cleared (including manual arp entries marked permanent), upon network link carrier changes.
The changed argument for the notifier was applied only to a single caller of NETDEV_CHANGE, missing among others netdev_state_change(). So upon net_carrier events induced by the network, which are triggering a call to netdev_state_change(), arp_netdev_event() would decide whether to clear or not arp cache based on random/junk stack values (a kind of read buffer overflow).
--- net/core/dev.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
net/core/dev.c +8 -1
@@ -148,6 +148,9 @@ struct list_head ptype_all __read_mostlystatic struct list_head offload_base__read_mostly ;static int netif_rx_internal (struct sk_buff *skb); +static int call_netdevice_notifiers_info (unsigned long val, +struct net_device *dev, +struct netdev_notifier_info *info);/* * The @dev_base_head list is protected by @dev_base_lock and the rtnl
@@ -1207,7 +1210,11 @@ EXPORT_SYMBOL(netdev_features_change);void netdev_state_change (struct net_device *dev) {if (dev->flags &IFF_UP ) { -call_netdevice_notifiers (NETDEV_CHANGE , dev); +struct netdev_notifier_change_info change_info; + + change_info.flags_changed =0 ; +call_netdevice_notifiers_info (NETDEV_CHANGE , dev, + &change_info.info);rtmsg_ifinfo (RTM_NEWLINK , dev,0 ,GFP_KERNEL ); } }
Greg Kroah-Hartman
maintainerPATCH 55/109 igmp: fix the problem when mc leave group
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: dingtianhong <[email protected]>
[ Upstream commit 52ad353a5344f1f700c5b777175bdfa41d3cd65a ]
The problem was triggered by these steps:
1) create socket, bind and then setsockopt for add mc group. mreq.imr_multiaddr.s_addr = inet_addr("255.0.0.37"); mreq.imr_interface.s_addr = inet_addr("192.168.1.2"); setsockopt(sockfd, IPPROTO_IP, IP_ADD_MEMBERSHIP, &mreq, sizeof(mreq));
2) drop the mc group for this socket.
mreq.imr_multiaddr.s_addr = inet_addr("255.0.0.37"); mreq.imr_interface.s_addr = inet_addr("0.0.0.0"); setsockopt(sockfd, IPPROTO_IP, IP_DROP_MEMBERSHIP, &mreq, sizeof(mreq));
3) and then drop the socket, I found the mc group was still used by the dev:
netstat -g
Interface RefCnt Group
--------------- ------ ---------------------
eth2 1 255.0.0.37
Normally even though the IP_DROP_MEMBERSHIP return error, the mc group still need to be released for the netdev when drop the socket, but this process was broken when route default is NULL, the reason is that:
The ip_mc_leave_group() will choose the in_dev by the imr_interface.s_addr, if input addr is NULL, the default route dev will be chosen, then the ifindex is got from the dev, then polling the inet->mc_list and return -ENODEV, but if the default route dev is NULL, the in_dev and ifIndex is both NULL, when polling the inet->mc_list, the mc group will be released from the mc_list, but the dev didn't dec the refcnt for this mc group, so when dropping the socket, the mc_list is NULL and the dev still keep this group.
v1->v2: According Hideaki's suggestion, we should align with IPv6 (RFC3493) and BSDs,
so I add the checking for the in_dev before polling the mc_list, make sure when we remove the mc group, dec the refcnt to the real dev which was using the mc address. The problem would never happened again.
--- net/ipv4/igmp.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
net/ipv4/igmp.c +6 -4
@@ -1952,6 +1952,10 @@ int ip_mc_leave_group(struct sock *sk, srtnl_lock (); in_dev =ip_mc_find_dev (net, imr); +if (!in_dev) { + ret = -ENODEV ; + goto out; + } ifindex = imr->imr_ifindex; for (imlp = &inet->mc_list; (iml = rtnl_dereference(*imlp)) != NULL;
@@ -1969,16 +1973,14 @@ int ip_mc_leave_group(struct sock *sk, s *imlp = iml->next_rcu; -if (in_dev) -ip_mc_dec_group (in_dev, group); +ip_mc_dec_group (in_dev, group);rtnl_unlock ();/* decrease mem now to avoid the memleak warning */ atomic_sub (sizeof (*iml), &sk->sk_omem_alloc);kfree_rcu (iml, rcu);return 0 ; } -if (!in_dev) - ret = -ENODEV ; +out:rtnl_unlock ();return ret; }
Greg Kroah-Hartman
maintainerPATCH 56/109 tcp: fix false undo corner cases
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Yuchung Cheng <[email protected]>
[ Upstream commit 6e08d5e3c8236e7484229e46fdf92006e1dd4c49 ]
The undo code assumes that, upon entering loss recovery, TCP
1) always retransmit something
2) the retransmission never fails locally (e.g., qdisc drop)
so undo_marker is set in tcp_enter_recovery() and undo_retrans is incremented only when tcp_retransmit_skb() is successful.
When the assumption is broken because TCP's cwnd is too small to retransmit or the retransmit fails locally. The next (DUP)ACK would incorrectly revert the cwnd and the congestion state in tcp_try_undo_dsack() or tcp_may_undo(). Subsequent (DUP)ACKs may enter the recovery state. The sender repeatedly enter and (incorrectly) exit recovery states if the retransmits continue to fail locally while receiving (DUP)ACKs.
The fix is to initialize undo_retrans to -1 and start counting on the first retransmission. Always increment undo_retrans even if the retransmissions fail locally because they couldn't cause DSACKs to undo the cwnd reduction.
--- net/ipv4/tcp_input.c | 8 ++++---- net/ipv4/tcp_output.c | 6 ++++-- 2 files changed, 8 insertions(+), 6 deletions(-)
net/ipv4/tcp_input.c +4 -4
@@ -1106,7 +1106,7 @@ static bool tcp_check_dsack(struct sock }/* D-SACK for already forgotten data... Do dumb counting. */ -if (dup_sack && tp->undo_marker && tp->undo_retrans && +if (dup_sack && tp->undo_marker && tp->undo_retrans >0 && !after (end_seq_0, prior_snd_una) &&after (end_seq_0, tp->undo_marker)) tp->undo_retrans--;
@@ -1187,7 +1187,7 @@ static u8 tcp_sacktag_one(struct sock *s/* Account D-SACK for retransmitted packet. */ if (dup_sack && (sacked &TCPCB_RETRANS )) { -if (tp->undo_marker && tp->undo_retrans && +if (tp->undo_marker && tp->undo_retrans >0 &&after (end_seq, tp->undo_marker)) tp->undo_retrans--;if (sacked &TCPCB_SACKED_ACKED )
@@ -1893,7 +1893,7 @@ static void tcp_clear_retrans_partial(st tp->lost_out =0 ; tp->undo_marker =0 ; - tp->undo_retrans =0 ; + tp->undo_retrans =-1 ; }void tcp_clear_retrans (struct tcp_sock *tp)
@@ -2664,7 +2664,7 @@ static void tcp_enter_recovery(struct so tp->prior_ssthresh =0 ; tp->undo_marker = tp->snd_una; - tp->undo_retrans = tp->retrans_out; + tp->undo_retrans = tp->retrans_out ? :-1 ;if (inet_csk (sk)->icsk_ca_state <TCP_CA_CWR ) {if (!ece_ack)
net/ipv4/tcp_output.c +4 -2
@@ -2472,8 +2472,6 @@ int tcp_retransmit_skb(struct sock *sk,if (!tp->retrans_stamp) tp->retrans_stamp =TCP_SKB_CB (skb)->when; - tp->undo_retrans +=tcp_skb_pcount (skb); -/* snd_nxt is stored to detect loss of retransmitted segment, * see tcp_input.c tcp_sacktag_write_queue(). */
@@ -2481,6 +2479,10 @@ int tcp_retransmit_skb(struct sock *sk, }else {NET_INC_STATS_BH (sock_net (sk),LINUX_MIB_TCPRETRANSFAIL ); } + +if (tp->undo_retrans <0 ) + tp->undo_retrans =0 ; + tp->undo_retrans +=tcp_skb_pcount (skb);return err; }
Greg Kroah-Hartman
maintainerPATCH 57/109 appletalk: Fix socket referencing in skb
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andrey Utkin <[email protected]>
[ Upstream commit 36beddc272c111689f3042bf3d10a64d8a805f93 ]
Setting just skb->sk without taking its reference and setting a destructor is invalid. However, in the places where this was done, skb is used in a way not requiring skb->sk setting. So dropping the setting of skb->sk.
Thanks to Eric Dumazet <[email protected]> for correct solution.
Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=79441
--- net/appletalk/ddp.c | 3 --- 1 file changed, 3 deletions(-)
net/appletalk/ddp.c +0 -3
@@ -1489,8 +1489,6 @@ static int atalk_rcv(struct sk_buff *skb goto drop;/* Queue packet (standard) */ - skb->sk = sock; -if (sock_queue_rcv_skb (sock, skb) <0 ) goto drop;
@@ -1644,7 +1642,6 @@ static int atalk_sendmsg(struct kiocb *iif (!skb) goto out; - skb->sk = sk;skb_reserve (skb, ddp_dl->header_length);skb_reserve (skb, dev->hard_header_len); skb->dev = dev;
Greg Kroah-Hartman
maintainerPATCH 58/109 net: mvneta: fix operation in 10 Mbit/s mode
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Petazzoni <[email protected]>
[ Upstream commit 4d12bc63ab5e48c1d78fa13883cf6fefcea3afb1 ]
As reported by Maggie Mae Roxas, the mvneta driver doesn't behave properly in 10 Mbit/s mode. This is due to a misconfiguration of the MVNETA_GMAC_AUTONEG_CONFIG register: bit MVNETA_GMAC_CONFIG_MII_SPEED must be set for a 100 Mbit/s speed, but cleared for a 10 Mbit/s speed, which the driver was not properly doing. This commit adjusts that by setting the MVNETA_GMAC_CONFIG_MII_SPEED bit only in 100 Mbit/s mode, and relying on the fact that all the speed related bits of this register are cleared at the beginning of the mvneta_adjust_link() function.
This problem exists since c5aff18204da0 ("net: mvneta: driver for Marvell Armada 370/XP network unit") which is the commit that introduced the mvneta driver in the kernel.
--- drivers/net/ethernet/marvell/mvneta.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/marvell/mvneta.c +1 -1
@@ -2365,7 +2365,7 @@ static void mvneta_adjust_link(struct neif (phydev->speed ==SPEED_1000 ) val |=MVNETA_GMAC_CONFIG_GMII_SPEED ; -else +else if (phydev->speed ==SPEED_100 ) val |=MVNETA_GMAC_CONFIG_MII_SPEED ;mvreg_write (pp,MVNETA_GMAC_AUTONEG_CONFIG , val);
Greg Kroah-Hartman
maintainerPATCH 59/109 net: mvneta: Fix big endian issue in mvneta_txq_desc_csum()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Thomas Fitzsimmons <[email protected]>
[ Upstream commit 0a1985879437d14bda8c90d0dae3455c467d7642 ]
This commit fixes the command value generated for CSUM calculation when running in big endian mode. The Ethernet protocol ID for IP was being unconditionally byte-swapped in the layer 3 protocol check (with swab16), which caused the mvneta driver to not function correctly in big endian mode. This patch byte-swaps the ID conditionally with htons.
--- drivers/net/ethernet/marvell/mvneta.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/marvell/mvneta.c +1 -1
@@ -1189,7 +1189,7 @@ static u32 mvneta_txq_desc_csum(int l3_o command = l3_offs <<MVNETA_TX_L3_OFF_SHIFT ; command |= ip_hdr_len <<MVNETA_TX_IP_HLEN_SHIFT ; -if (l3_proto ==swab16 (ETH_P_IP )) +if (l3_proto ==htons (ETH_P_IP )) command |=MVNETA_TXD_IP_CSUM ;else command |=MVNETA_TX_L3_IP6 ;
Greg Kroah-Hartman
maintainerPATCH 60/109 netlink: Fix handling of error from netlink_dump().
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Pfaff <[email protected]>
[ Upstream commit ac30ef832e6af0505b6f0251a6659adcfa74975e ]
netlink_dump() returns a negative errno value on error. Until now, netlink_recvmsg() directly recorded that negative value in sk->sk_err, but that's wrong since sk_err takes positive errno values. (This manifests as userspace receiving a positive return value from the recv() system call, falsely indicating success.) This bug was introduced in the commit that started checking the netlink_dump() return value, commit b44d211 (netlink:
handle errors from netlink_dump()).
Multithreaded Netlink dumps are one way to trigger this behavior in practice, as described in the commit message for the userspace workaround posted here:
http://openvswitch.org/pipermail/dev/2014-June/042339.html
This commit also fixes the same bug in netlink_poll(), introduced in commit cd1df525d (netlink: add flow control for memory mapped I/O).
--- net/netlink/af_netlink.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/netlink/af_netlink.c +2 -2
@@ -636,7 +636,7 @@ static unsigned int netlink_poll(structwhile (nlk->cb_running &&netlink_dump_space (nlk)) { err =netlink_dump (sk);if (err <0 ) { - sk->sk_err = err; + sk->sk_err = -err; sk->sk_error_report (sk);break ; }
@@ -2453,7 +2453,7 @@ static int netlink_recvmsg(struct kiocb atomic_read(&sk->sk_rmem_alloc) <= sk->sk_rcvbuf / 2) { ret =netlink_dump (sk);if (ret) { - sk->sk_err = ret; + sk->sk_err = -ret; sk->sk_error_report (sk); } }
Greg Kroah-Hartman
maintainerPATCH 61/109 be2net: set EQ DB clear-intr bit in be_open()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Suresh Reddy <[email protected]>
[ Upstream commit 4cad9f3b61c7268fa89ab8096e23202300399b5d ]
On BE3, if the clear-interrupt bit of the EQ doorbell is not set the first time it is armed, ocassionally we have observed that the EQ doesn't raise anymore interrupts even if it is in armed state.
This patch fixes this by setting the clear-interrupt bit when EQs are armed for the first time in be_open().
--- drivers/net/ethernet/emulex/benet/be_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/emulex/benet/be_main.c +1 -1
@@ -2858,7 +2858,7 @@ static int be_open(struct net_device *ne for_all_evt_queues(adapter, eqo, i) {napi_enable (&eqo->napi);be_enable_busy_poll (eqo); -be_eq_notify (adapter, eqo->q.id, true, false,0 ); +be_eq_notify (adapter, eqo->q.id, true, true,0 ); } adapter->flags |=BE_FLAGS_NAPI_ENABLED ;
Greg Kroah-Hartman
maintainerPATCH 62/109 r8152: fix r8152_csum_workaround function
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: hayeswang <[email protected]>
[ Upstream commit a91d45f1a343188793d6f2bdf1a72c64015a8255 ]
The transport offset of the IPv4 packet should be fixed and wouldn't be out of the hw limitation, so the r8152_csum_workaround() should be used for IPv6 packets.
--- drivers/net/usb/r8152.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/usb/r8152.c +1 -1
@@ -1361,7 +1361,7 @@ static void r8152_csum_workaround(structstruct sk_buff_head seg_list;struct sk_buff *segs, *nskb; - features &= ~(NETIF_F_IP_CSUM |NETIF_F_SG |NETIF_F_TSO ); + features &= ~(NETIF_F_SG |NETIF_F_IPV6_CSUM |NETIF_F_TSO6 ); segs =skb_gso_segment (skb, features);if (IS_ERR (segs) || !segs) goto drop;
Greg Kroah-Hartman
maintainerPATCH 63/109 tipc: clear next-pointer of message fragments before reassembly
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jon Paul Maloy <[email protected]>
[ Upstream commit 999417549c16dd0e3a382aa9f6ae61688db03181 ]
If the 'next' pointer of the last fragment buffer in a message is not zeroed before reassembly, we risk ending up with a corrupt message, since the reassembly function itself isn't doing this.
Currently, when a buffer is retrieved from the deferred queue of the broadcast link, the next pointer is not cleared, with the result as described above.
This commit corrects this, and thereby fixes a bug that may occur when long broadcast messages are transmitted across dual interfaces. The bug has been present since 40ba3cdf542a469aaa9083fa041656e59b109b90 ("tipc:
message reassembly using fragment chain")
This commit should be applied to both net and net-next.
--- net/tipc/bcast.c | 1 + 1 file changed, 1 insertion(+)
net/tipc/bcast.c +1 -0
@@ -536,6 +536,7 @@ receive: buf = node->bclink.deferred_head; node->bclink.deferred_head = buf->next; + buf->next =NULL ; node->bclink.deferred_size--; goto receive; }
Greg Kroah-Hartman
maintainerPATCH 64/109 net: sctp: fix information leaks in ulpevent layer
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Borkmann <[email protected]>
[ Upstream commit 8f2e5ae40ec193bc0a0ed99e95315c3eebca84ea ]
While working on some other SCTP code, I noticed that some structures shared with user space are leaking uninitialized stack or heap buffer. In particular, struct sctp_sndrcvinfo has a 2 bytes hole between .sinfo_flags and .sinfo_ppid that remains unfilled by us in sctp_ulpevent_read_sndrcvinfo() when putting this into cmsg. But also struct sctp_remote_error contains a 2 bytes hole that we don't fill but place into a skb through skb_copy_expand() via sctp_ulpevent_make_remote_error().
Both structures are defined by the IETF in RFC6458:
* Section 5.3.2. SCTP Header Information Structure:
The sctp_sndrcvinfo structure is defined below:
struct sctp_sndrcvinfo {
uint16_t sinfo_stream;
uint16_t sinfo_ssn;
uint16_t sinfo_flags;
<-- 2 bytes hole -->
uint32_t sinfo_ppid;
uint32_t sinfo_context;
uint32_t sinfo_timetolive;
uint32_t sinfo_tsn;
uint32_t sinfo_cumtsn;
sctp_assoc_t sinfo_assoc_id;
};* 6.1.3. SCTP_REMOTE_ERROR:
A remote peer may send an Operation Error message to its peer. This message indicates a variety of error conditions on an association. The entire ERROR chunk as it appears on the wire is included in an SCTP_REMOTE_ERROR event. Please refer to the SCTP specification [RFC4960] and any extensions for a list of possible error formats. An SCTP error notification has the following format:
struct sctp_remote_error {
uint16_t sre_type;
uint16_t sre_flags;
uint32_t sre_length;
uint16_t sre_error;
<-- 2 bytes hole -->
sctp_assoc_t sre_assoc_id;
uint8_t sre_data[];
};Fix this by setting both to 0 before filling them out. We also have other structures shared between user and kernel space in SCTP that contains holes (e.g. struct sctp_paddrthlds), but we copy that buffer over from user space first and thus don't need to care about it in that cases.
While at it, we can also remove lengthy comments copied from the draft, instead, we update the comment with the correct RFC number where one can look it up.
--- net/sctp/ulpevent.c | 122 ++++++---------------------------------------------- 1 file changed, 15 insertions(+), 107 deletions(-)
net/sctp/ulpevent.c +15 -107
@@ -366,9 +366,10 @@ fail:* specification [SCTP] and any extensions for a list of possible * error formats. */ -struct sctp_ulpevent *sctp_ulpevent_make_remote_error ( -const struct sctp_association *asoc,struct sctp_chunk *chunk, -__u16 flags,gfp_t gfp) +struct sctp_ulpevent * +sctp_ulpevent_make_remote_error (const struct sctp_association *asoc, +struct sctp_chunk *chunk,__u16 flags, +gfp_t gfp) {struct sctp_ulpevent *event;struct sctp_remote_error *sre;
@@ -387,8 +388,7 @@ struct sctp_ulpevent *sctp_ulpevent_make/* Copy the skb to a new skb with room for us to prepend * notification with. */ - skb =skb_copy_expand (chunk->skb,sizeof (struct sctp_remote_error ), -0 , gfp); + skb =skb_copy_expand (chunk->skb,sizeof (*sre),0 , gfp);/* Pull off the rest of the cause TLV from the chunk. */ skb_pull (chunk->skb, elen);
@@ -399,62 +399,21 @@ struct sctp_ulpevent *sctp_ulpevent_make event =sctp_skb2event (skb);sctp_ulpevent_init (event,MSG_NOTIFICATION , skb->truesize); - sre = (struct sctp_remote_error *) -skb_push (skb,sizeof (struct sctp_remote_error )); + sre = (struct sctp_remote_error *)skb_push (skb,sizeof (*sre));/* Trim the buffer to the right length. */ -skb_trim (skb,sizeof (struct sctp_remote_error ) + elen); +skb_trim (skb,sizeof (*sre) + elen); -/* Socket Extensions for SCTP -* 5.3.1.3 SCTP_REMOTE_ERROR -* -* sre_type: -* It should be SCTP_REMOTE_ERROR. -*/ +/* RFC6458, Section 6.1.3. SCTP_REMOTE_ERROR */ +memset (sre,0 ,sizeof (*sre)); sre->sre_type =SCTP_REMOTE_ERROR ; - -/* -* Socket Extensions for SCTP -* 5.3.1.3 SCTP_REMOTE_ERROR -* -* sre_flags: 16 bits (unsigned integer) -* Currently unused. -*/ sre->sre_flags =0 ; - -/* Socket Extensions for SCTP -* 5.3.1.3 SCTP_REMOTE_ERROR -* -* sre_length: sizeof (__u32) -* -* This field is the total length of the notification data, -* including the notification header. -*/ sre->sre_length = skb->len; - -/* Socket Extensions for SCTP -* 5.3.1.3 SCTP_REMOTE_ERROR -* -* sre_error: 16 bits (unsigned integer) -* This value represents one of the Operational Error causes defined in -* the SCTP specification, in network byte order. -*/ sre->sre_error = cause; - -/* Socket Extensions for SCTP -* 5.3.1.3 SCTP_REMOTE_ERROR -* -* sre_assoc_id: sizeof (sctp_assoc_t) -* -* The association id field, holds the identifier for the association. -* All notifications for a given association have the same association -* identifier. For TCP style socket, this field is ignored. -*/ sctp_ulpevent_set_owner (event, asoc); sre->sre_assoc_id =sctp_assoc2id (asoc);return event; - fail:return NULL ; }
@@ -899,7 +858,9 @@ __u16 sctp_ulpevent_get_notification_typreturn notification->sn_header.sn_type; } -/* Copy out the sndrcvinfo into a msghdr. */ +/* RFC6458, Section 5.3.2. SCTP Header Information Structure +* (SCTP_SNDRCV, DEPRECATED) +*/ void sctp_ulpevent_read_sndrcvinfo (const struct sctp_ulpevent *event,struct msghdr *msghdr) {
@@ -908,74 +869,21 @@ void sctp_ulpevent_read_sndrcvinfo(constif (sctp_ulpevent_is_notification (event))return ; -/* Sockets API Extensions for SCTP -* Section 5.2.2 SCTP Header Information Structure (SCTP_SNDRCV) -* -* sinfo_stream: 16 bits (unsigned integer) -* -* For recvmsg() the SCTP stack places the message's stream number in -* this value. -*/ +memset (&sinfo,0 ,sizeof (sinfo)); sinfo.sinfo_stream = event->stream; -/* sinfo_ssn: 16 bits (unsigned integer) -* -* For recvmsg() this value contains the stream sequence number that -* the remote endpoint placed in the DATA chunk. For fragmented -* messages this is the same number for all deliveries of the message -* (if more than one recvmsg() is needed to read the message). -*/ sinfo.sinfo_ssn = event->ssn; -/* sinfo_ppid: 32 bits (unsigned integer) -* -* In recvmsg() this value is -* the same information that was passed by the upper layer in the peer -* application. Please note that byte order issues are NOT accounted -* for and this information is passed opaquely by the SCTP stack from -* one end to the other. -*/ sinfo.sinfo_ppid = event->ppid; -/* sinfo_flags: 16 bits (unsigned integer) -* -* This field may contain any of the following flags and is composed of -* a bitwise OR of these values. -* -* recvmsg() flags: -* -* SCTP_UNORDERED - This flag is present when the message was sent -* non-ordered. -*/ sinfo.sinfo_flags = event->flags; -/* sinfo_tsn: 32 bit (unsigned integer) -* -* For the receiving side, this field holds a TSN that was -* assigned to one of the SCTP Data Chunks. -*/ sinfo.sinfo_tsn = event->tsn; -/* sinfo_cumtsn: 32 bit (unsigned integer) -* -* This field will hold the current cumulative TSN as -* known by the underlying SCTP layer. Note this field is -* ignored when sending and only valid for a receive -* operation when sinfo_flags are set to SCTP_UNORDERED. -*/ sinfo.sinfo_cumtsn = event->cumtsn; -/* sinfo_assoc_id: sizeof (sctp_assoc_t) -* -* The association handle field, sinfo_assoc_id, holds the identifier -* for the association announced in the COMMUNICATION_UP notification. -* All notifications for a given association have the same identifier. -* Ignored for one-to-one style sockets. -*/ sinfo.sinfo_assoc_id =sctp_assoc2id (event->asoc); - -/* context value that is set via SCTP_CONTEXT socket option. */ +/* Context value that is set via SCTP_CONTEXT socket option. */ sinfo.sinfo_context = event->asoc->default_rcv_context; -/* These fields are not used while receiving. */ sinfo.sinfo_timetolive =0 ;put_cmsg (msghdr,IPPROTO_SCTP ,SCTP_SNDRCV , -sizeof (struct sctp_sndrcvinfo ), (void *)&sinfo); +sizeof (sinfo), &sinfo); }/* Do accounting for bytes received and hold a reference to the association
Greg Kroah-Hartman
maintainerPATCH 65/109 net: pppoe: use correct channel MTU when using Multilink PPP
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Schulz <[email protected]>
[ Upstream commit a8a3e41c67d24eb12f9ab9680cbb85e24fcd9711 ]
The PPP channel MTU is used with Multilink PPP when ppp_mp_explode() (see ppp_generic module) tries to determine how big a fragment might be. According to RFC 1661, the MTU excludes the 2-byte PPP protocol field, see the corresponding comment and code in ppp_mp_explode():
/* * hdrlen includes the 2-byte PPP protocol field, but the * MTU counts only the payload excluding the protocol field. * (RFC1661 Section 2) */ mtu = pch->chan->mtu - (hdrlen - 2);
However, the pppoe module *does* include the PPP protocol field in the channel MTU, which is wrong as it causes the PPP payload to be 1-2 bytes too big under certain circumstances (one byte if PPP protocol compression is used, two otherwise), causing the generated Ethernet packets to be dropped. So the pppoe module has to subtract two bytes from the channel MTU. This error only manifests itself when using Multilink PPP, as otherwise the channel MTU is not used anywhere.
In the following, I will describe how to reproduce this bug. We configure two pppd instances for multilink PPP over two PPPoE links, say eth2 and eth3, with a MTU of 1492 bytes for each link and a MRRU of 2976 bytes. (This MRRU is computed by adding the two link MTUs and subtracting the MP header twice, which is 4 bytes long.) The necessary pppd statements on both sides are "multilink mtu 1492 mru 1492 mrru 2976". On the client side, we additionally need "plugin rp-pppoe.so eth2" and "plugin rp-pppoe.so eth3", respectively; on the server side, we additionally need to start two pppoe-server instances to be able to establish two PPPoE sessions, one over eth2 and one over eth3. We set the MTU of the PPP network interface to the MRRU (2976) on both sides of the connection in order to make use of the higher bandwidth. (If we didn't do that, IP fragmentation would kick in, which we want to avoid.)
Now we send a ICMPv4 echo request with a payload of 2948 bytes from client to server over the PPP link. This results in the following network packet:
2948 (echo payload)
+ 8 (ICMPv4 header)
+ 20 (IPv4 header)
---------------------
2976 (PPP payload)
These 2976 bytes do not exceed the MTU of the PPP network interface, so the IP packet is not fragmented. Now the multilink PPP code in ppp_mp_explode() prepends one protocol byte (0x21 for IPv4), making the packet one byte bigger than the negotiated MRRU. So this packet would have to be divided in three fragments. But this does not happen as each link MTU is assumed to be two bytes larger. So this packet is diveded into two fragments only, one of size 1489 and one of size 1488. Now we have for that bigger fragment:
1489 (PPP payload)
+ 4 (MP header) + 2 (PPP protocol field for the MP payload (0x3d)) + 6 (PPPoE header)
--------------------------
1501 (Ethernet payload)
This packet exceeds the link MTU and is discarded.
If one configures the link MTU on the client side to 1501, one can see the discarded Ethernet frames with tcpdump running on the client. A
ping -s 2948 -c 1 192.168.15.254
leads to the smaller fragment that is correctly received on the server side:
(tcpdump -vvvne -i eth3 pppoes and ppp proto 0x3d) 52:54:00:ad:87:fd > 52:54:00:79:5c:d0, ethertype PPPoE S (0x8864),
length 1514: PPPoE [ses 0x3] MLPPP (0x003d), length 1494: seq 0x000, Flags [end], length 1492
and to the bigger fragment that is not received on the server side:
(tcpdump -vvvne -i eth2 pppoes and ppp proto 0x3d) 52:54:00:70:9e:89 > 52:54:00:5d:6f:b0, ethertype PPPoE S (0x8864),
length 1515: PPPoE [ses 0x5] MLPPP (0x003d), length 1495: seq 0x000, Flags [begin], length 1493
With the patch below, we correctly obtain three fragments:
52:54:00:ad:87:fd > 52:54:00:79:5c:d0, ethertype PPPoE S (0x8864),
length 1514: PPPoE [ses 0x1] MLPPP (0x003d), length 1494: seq 0x000, Flags [begin], length 1492
52:54:00:70:9e:89 > 52:54:00:5d:6f:b0, ethertype PPPoE S (0x8864),
length 1514: PPPoE [ses 0x1] MLPPP (0x003d), length 1494: seq 0x000, Flags [none], length 1492
52:54:00:ad:87:fd > 52:54:00:79:5c:d0, ethertype PPPoE S (0x8864),
length 27: PPPoE [ses 0x1] MLPPP (0x003d), length 7: seq 0x000, Flags [end], length 5
And the ICMPv4 echo request is successfully received at the server side:
IP (tos 0x0, ttl 64, id 21925, offset 0, flags [DF], proto ICMP (1),
length 2976)
192.168.222.2 > 192.168.15.254: ICMP echo request, id 30530, seq 0,
length 2956The bug was introduced in commit c9aa6895371b2a257401f59d3393c9f7ac5a8698 ("[PPPOE]: Advertise PPPoE MTU") from the very beginning. This patch applies to 3.10 upwards but the fix can be applied (with minor modifications) to kernels as old as 2.6.32.
--- drivers/net/ppp/pppoe.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ppp/pppoe.c +1 -1
@@ -675,7 +675,7 @@ static int pppoe_connect(struct socket * po->chan.hdrlen = (sizeof (struct pppoe_hdr ) + dev->hard_header_len); - po->chan.mtu = dev->mtu -sizeof (struct pppoe_hdr ); + po->chan.mtu = dev->mtu -sizeof (struct pppoe_hdr ) -2 ; po->chan.private = sk; po->chan.ops = &pppoe_chan_ops;
Greg Kroah-Hartman
maintainerPATCH 66/109 bonding: fix ad_select module param check
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Nikolay Aleksandrov <[email protected]>
[ Upstream commit 548d28bd0eac840d122b691279ce9f4ce6ecbfb6 ]
Obvious copy/paste error when I converted the ad_select to the new option API. "lacp_rate" there should be "ad_select" so we can get the proper value.
API")
--- drivers/net/bonding/bond_main.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/bonding/bond_main.c +1 -1
@@ -4028,7 +4028,7 @@ static int bond_check_params(struct bond }if (ad_select) { -bond_opt_initstr (&newval, lacp_rate); +bond_opt_initstr (&newval, ad_select); valptr =bond_opt_parse (bond_opt_get (BOND_OPT_AD_SELECT ), &newval);if (!valptr) {
Greg Kroah-Hartman
maintainerPATCH 67/109 net-gre-gro: Fix a bug that breaks the forwarding path
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jerry Chu <[email protected]>
[ Upstream commit c3caf1192f904de2f1381211f564537235d50de3 ]
Fixed a bug that was introduced by my GRE-GRO patch (bf5a755f5e9186406bbf50f4087100af5bd68e40 net-gre-gro: Add GRE support to the GRO stack) that breaks the forwarding path because various GSO related fields were not set. The bug will cause on the egress path either the GSO code to fail, or a GRE-TSO capable (NETIF_F_GSO_GRE) NICs to choke. The following fix has been tested for both cases.
--- net/core/dev.c | 2 ++ net/ipv4/af_inet.c | 3 +++ net/ipv4/gre_offload.c | 3 +++ net/ipv4/tcp_offload.c | 2 +- net/ipv6/tcpv6_offload.c | 2 +- 5 files changed, 10 insertions(+), 2 deletions(-)
net/core/dev.c +2 -0
@@ -4064,6 +4064,8 @@ static void napi_reuse_skb(struct napi_s skb->vlan_tci =0 ; skb->dev = napi->dev; skb->skb_iif =0 ; + skb->encapsulation =0 ; +skb_shinfo (skb)->gso_type =0 ; skb->truesize =SKB_TRUESIZE (skb_end_offset (skb)); napi->skb = skb;
net/ipv4/af_inet.c +3 -0
@@ -1434,6 +1434,9 @@ static int inet_gro_complete(struct sk_bint proto = iph->protocol;int err = -ENOSYS ; +if (skb->encapsulation) +skb_set_inner_network_header (skb, nhoff); +csum_replace2 (&iph->check, iph->tot_len, newlen); iph->tot_len = newlen;
net/ipv4/gre_offload.c +3 -0
@@ -255,6 +255,9 @@ static int gre_gro_complete(struct sk_buint err = -ENOENT ;__be16 type; + skb->encapsulation =1 ; +skb_shinfo (skb)->gso_type =SKB_GSO_GRE ; + type = greh->protocol;if (greh->flags &GRE_KEY ) grehlen +=GRE_HEADER_SECTION ;
net/ipv4/tcp_offload.c +1 -1
@@ -310,7 +310,7 @@ static int tcp4_gro_complete(struct sk_b th->check = ~tcp_v4_check (skb->len - thoff, iph->saddr, iph->daddr,0 ); -skb_shinfo (skb)->gso_type =SKB_GSO_TCPV4 ; +skb_shinfo (skb)->gso_type |=SKB_GSO_TCPV4 ;return tcp_gro_complete (skb); }
net/ipv6/tcpv6_offload.c +1 -1
@@ -73,7 +73,7 @@ static int tcp6_gro_complete(struct sk_b th->check = ~tcp_v6_check (skb->len - thoff, &iph->saddr, &iph->daddr,0 ); -skb_shinfo (skb)->gso_type =SKB_GSO_TCPV6 ; +skb_shinfo (skb)->gso_type |=SKB_GSO_TCPV6 ;return tcp_gro_complete (skb); }
Greg Kroah-Hartman
maintainerPATCH 68/109 sunvnet: clean up objects created in vnet_new() on vnet_exit()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sowmini Varadhan <[email protected]>
[ Upstream commit a4b70a07ed12a71131cab7adce2ce91c71b37060 ]
Nothing cleans up the objects created byvnet_new(), they are completely leaked.
vnet_exit(), after doing the vio_unregister_driver() to clean up ports, should call a helper function that iterates over vnet_list and cleans up those objects. This includes unregister_netdevice() as well as free_netdev().
--- drivers/net/ethernet/sun/sunvnet.c | 20 +++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-)
drivers/net/ethernet/sun/sunvnet.c +19 -1
@@ -1083,6 +1083,24 @@ static struct vnet *vnet_find_or_create(return vp; } +static void vnet_cleanup (void ) +{ +struct vnet *vp; +struct net_device *dev; + +mutex_lock (&vnet_list_mutex); +while (!list_empty (&vnet_list)) { + vp = list_first_entry(&vnet_list, struct vnet, list); +list_del (&vp->list); + dev = vp->dev; +/* vio_unregister_driver() should have cleaned up port_list */ +BUG_ON (!list_empty (&vp->port_list)); +unregister_netdev (dev); +free_netdev (dev); + } +mutex_unlock (&vnet_list_mutex); +} +static const char *local_mac_prop ="local-mac-address" ; static struct vnet *vnet_find_parent(struct mdesc_handle *hp,
@@ -1240,7 +1258,6 @@ static int vnet_port_remove(struct vio_dkfree (port); -unregister_netdev (vp->dev); }return 0 ; }
@@ -1268,6 +1285,7 @@ static int __init vnet_init(void) static void __exit vnet_exit(void) {vio_unregister_driver (&vnet_port_driver); +vnet_cleanup (); }module_init (vnet_init);
Greg Kroah-Hartman
maintainerPATCH 69/109 net: ppp: fix creating PPP pass and active filters
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Schulz <[email protected]>
[ Upstream commit cc25eaae238ddd693aa5eaa73e565d8ff4915f6e ]
Commit 568f194e8bd16c353ad50f9ab95d98b20578a39d ("net: ppp: use sk_unattached_filter api") inadvertently changed the logic when setting PPP pass and active filters. This applies to both the generic PPP subsystem implemented by drivers/net/ppp/ppp_generic.c and the ISDN PPP subsystem implemented by drivers/isdn/i4l/isdn_ppp.c. The original code in ppp_ioctl() (or isdn_ppp_ioctl(), resp.) handling PPPIOCSPASS and PPPIOCSACTIVE allowed to remove a pass/active filter previously set by using a filter of length zero. However, with the new code this is not possible anymore as this case is not explicitly checked for, which leads to passing NULL as a filter to sk_unattached_filter_create(). This results in returning EINVAL to the caller.
Additionally, the variables ppp->pass_filter and ppp->active_filter (or is->pass_filter and is->active_filter, resp.) are not reset to NULL, although the filters they point to may have been destroyed by sk_unattached_filter_destroy(), so in this EINVAL case dangling pointers are left behind (provided the pointers were previously non-NULL).
This patch corrects both problems by checking whether the filter passed is empty or non-empty, and prevents sk_unattached_filter_create() from being called in the first case. Moreover, the pointers are always reset to NULL as soon as sk_unattached_filter_destroy() returns.
--- drivers/isdn/i4l/isdn_ppp.c | 20 ++++++++++++++++---- drivers/net/ppp/ppp_generic.c | 22 ++++++++++++++++------ 2 files changed, 32 insertions(+), 10 deletions(-)
drivers/isdn/i4l/isdn_ppp.c +16 -4
@@ -644,9 +644,15 @@ isdn_ppp_ioctl(int min, struct file *fil fprog.len = len; fprog.filter = code; -if (is->pass_filter) +if (is->pass_filter) {sk_unattached_filter_destroy (is->pass_filter); - err =sk_unattached_filter_create (&is->pass_filter, &fprog); + is->pass_filter =NULL ; + } +if (fprog.filter !=NULL ) + err =sk_unattached_filter_create (&is->pass_filter, + &fprog); +else + err =0 ;kfree (code);return err;
@@ -663,9 +669,15 @@ isdn_ppp_ioctl(int min, struct file *fil fprog.len = len; fprog.filter = code; -if (is->active_filter) +if (is->active_filter) {sk_unattached_filter_destroy (is->active_filter); - err =sk_unattached_filter_create (&is->active_filter, &fprog); + is->active_filter =NULL ; + } +if (fprog.filter !=NULL ) + err =sk_unattached_filter_create (&is->active_filter, + &fprog); +else + err =0 ;kfree (code);return err;
drivers/net/ppp/ppp_generic.c +16 -6
@@ -763,10 +763,15 @@ static long ppp_ioctl(struct file *file, };ppp_lock (ppp); -if (ppp->pass_filter) +if (ppp->pass_filter) {sk_unattached_filter_destroy (ppp->pass_filter); - err =sk_unattached_filter_create (&ppp->pass_filter, - &fprog); + ppp->pass_filter =NULL ; + } +if (fprog.filter !=NULL ) + err =sk_unattached_filter_create (&ppp->pass_filter, + &fprog); +else + err =0 ;kfree (code);ppp_unlock (ppp); }
@@ -784,10 +789,15 @@ static long ppp_ioctl(struct file *file, };ppp_lock (ppp); -if (ppp->active_filter) +if (ppp->active_filter) {sk_unattached_filter_destroy (ppp->active_filter); - err =sk_unattached_filter_create (&ppp->active_filter, - &fprog); + ppp->active_filter =NULL ; + } +if (fprog.filter !=NULL ) + err =sk_unattached_filter_create (&ppp->active_filter, + &fprog); +else + err =0 ;kfree (code);ppp_unlock (ppp); }
Greg Kroah-Hartman
maintainerPATCH 71/109 net: ppp: dont call sk_chk_filter twice
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Christoph Schulz <[email protected]>
[ Upstream commit 3916a3192793fd3c11f69d623ef0cdbdbf9ea10a ]
Commit 568f194e8bd16c353ad50f9ab95d98b20578a39d ("net: ppp: use sk_unattached_filter api") causes sk_chk_filter() to be called twice when setting a PPP pass or active filter. This applies to both the generic PPP subsystem implemented by drivers/net/ppp/ppp_generic.c and the ISDN PPP subsystem implemented by drivers/isdn/i4l/isdn_ppp.c. The first call is from within get_filter(). The second one is through the call chain
ppp_ioctl() or isdn_ppp_ioctl()
--> sk_unattached_filter_create()
--> __sk_prepare_filter()
--> sk_chk_filter()The first call from within get_filter() should be deleted as get_filter() is called just before calling sk_unattached_filter_create() later on, which eventually calls sk_chk_filter() anyway.
For 3.15.x, this proposed change is a bugfix rather than a pure optimization as in that branch, sk_chk_filter() may replace filter codes by other codes which are not recognized when executing sk_chk_filter() a second time. So with 3.15.x, if sk_chk_filter() is called twice, the second invocation may yield EINVAL (this depends on the filter codes found in the filter to be set, but because the replacement is done for frequently used codes, this is almost always the case). The net effect is that setting pass and/or active PPP filters does not work anymore, since sk_unattached_filter_create() always returns EINVAL due to the second call to sk_chk_filter(), regardless whether the filter was originally sane or not.
--- drivers/isdn/i4l/isdn_ppp.c | 8 +------- drivers/net/ppp/ppp_generic.c | 8 +------- 2 files changed, 2 insertions(+), 14 deletions(-)
drivers/isdn/i4l/isdn_ppp.c +1 -7
@@ -442,7 +442,7 @@ static int get_filter(void __user *arg, {struct sock_fprog uprog;struct sock_filter *code =NULL ; -int len, err; +int len;if (copy_from_user (&uprog, arg,sizeof (uprog)))return -EFAULT ;
@@ -458,12 +458,6 @@ static int get_filter(void __user *arg,if (IS_ERR (code))return PTR_ERR (code); - err =sk_chk_filter (code, uprog.len); -if (err) { -kfree (code); -return err; - } - *p = code;return uprog.len; }
drivers/net/ppp/ppp_generic.c +1 -7
@@ -539,7 +539,7 @@ static int get_filter(void __user *arg, {struct sock_fprog uprog;struct sock_filter *code =NULL ; -int len, err; +int len;if (copy_from_user (&uprog, arg,sizeof (uprog)))return -EFAULT ;
@@ -554,12 +554,6 @@ static int get_filter(void __user *arg,if (IS_ERR (code))return PTR_ERR (code); - err =sk_chk_filter (code, uprog.len); -if (err) { -kfree (code); -return err; - } - *p = code;return uprog.len; }
Greg Kroah-Hartman
maintainerPATCH 73/109 dns_resolver: Null-terminate the right string
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
[ Upstream commit 640d7efe4c08f06c4ae5d31b79bd8740e7f6790a ]
*_result[len] is parsed as *(_result[len]) which is not at all what we want to touch here.
--- net/dns_resolver/dns_query.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/dns_resolver/dns_query.c +1 -1
@@ -150,7 +150,7 @@ int dns_query(const char *type, const ch goto put;memcpy (*_result, upayload->data, len); - *_result[len] ='\0' ; + (*_result)[len] ='\0' ;if (_expiry) *_expiry = rkey->expiry;
Greg Kroah-Hartman
maintainerPATCH 74/109 ipv4: fix buffer overflow in ip_options_compile()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Eric Dumazet <[email protected]>
[ Upstream commit 10ec9472f05b45c94db3c854d22581a20b97db41 ]
There is a benign buffer overflow in ip_options_compile spotted by AddressSanitizer[1] :
Its benign because we always can access one extra byte in skb->head (because header is followed by struct skb_shared_info), and in this case this byte is not even used.
[28504.910798] ================================================================== [28504.912046] AddressSanitizer: heap-buffer-overflow in ip_options_compile [28504.913170] Read of size 1 by thread T15843: [28504.914026] [<ffffffff81802f91>] ip_options_compile+0x121/0x9c0 [28504.915394] [<ffffffff81804a0d>] ip_options_get_from_user+0xad/0x120 [28504.916843] [<ffffffff8180dedf>] do_ip_setsockopt.isra.15+0x8df/0x1630 [28504.918175] [<ffffffff8180ec60>] ip_setsockopt+0x30/0xa0 [28504.919490] [<ffffffff8181e59b>] tcp_setsockopt+0x5b/0x90 [28504.920835] [<ffffffff8177462f>] sock_common_setsockopt+0x5f/0x70 [28504.922208] [<ffffffff817729c2>] SyS_setsockopt+0xa2/0x140 [28504.923459] [<ffffffff818cfb69>] system_call_fastpath+0x16/0x1b [28504.924722] [28504.925106] Allocated by thread T15843: [28504.925815] [<ffffffff81804995>] ip_options_get_from_user+0x35/0x120 [28504.926884] [<ffffffff8180dedf>] do_ip_setsockopt.isra.15+0x8df/0x1630 [28504.927975] [<ffffffff8180ec60>] ip_setsockopt+0x30/0xa0 [28504.929175] [<ffffffff8181e59b>] tcp_setsockopt+0x5b/0x90 [28504.930400] [<ffffffff8177462f>] sock_common_setsockopt+0x5f/0x70 [28504.931677] [<ffffffff817729c2>] SyS_setsockopt+0xa2/0x140 [28504.932851] [<ffffffff818cfb69>] system_call_fastpath+0x16/0x1b [28504.934018] [28504.934377] The buggy address ffff880026382828 is located 0 bytes to the right [28504.934377] of 40-byte region [ffff880026382800, ffff880026382828) [28504.937144] [28504.937474] Memory state around the buggy address: [28504.938430] ffff880026382300: ........ rrrrrrrr rrrrrrrr rrrrrrrr [28504.939884] ffff880026382400: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28504.941294] ffff880026382500: .....rrr rrrrrrrr rrrrrrrr rrrrrrrr [28504.942504] ffff880026382600: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28504.943483] ffff880026382700: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28504.944511] >ffff880026382800: .....rrr rrrrrrrr rrrrrrrr rrrrrrrr [28504.945573] ^ [28504.946277] ffff880026382900: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28505.094949] ffff880026382a00: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28505.096114] ffff880026382b00: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28505.097116] ffff880026382c00: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28505.098472] ffff880026382d00: ffffffff rrrrrrrr rrrrrrrr rrrrrrrr [28505.099804] Legend: [28505.100269] f - 8 freed bytes [28505.100884] r - 8 redzone bytes [28505.101649] . - 8 allocated bytes [28505.102406] x=1..7 - x allocated bytes + (8-x) redzone bytes [28505.103637] ==================================================================
[1] https://code.google.com/p/address-sanitizer/wiki/AddressSanitizerForKernel
--- net/ipv4/ip_options.c | 4 ++++ 1 file changed, 4 insertions(+)
net/ipv4/ip_options.c +4 -0
@@ -288,6 +288,10 @@ int ip_options_compile(struct net *net, optptr++;continue ; } +if (unlikely (l <2 )) { + pp_ptr = optptr; + goto error; + } optlen = optptr[1 ];if (optlen <2 || optlen > l) { pp_ptr = optptr;
Greg Kroah-Hartman
maintainerPATCH 75/109 xen-netback: Fix handling frag_list on grant op error path
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit 1a998d3e6bc1e44f4c0bc7509bdedef8ed3845ec ]
The error handling for skb's with frag_list was completely wrong, it caused double unmap attempts to happen if the error was on the first skb. Move it to the right place in the loop.
--- drivers/net/xen-netback/netback.c | 37 ++++++++++++++++++++----------------- 1 file changed, 20 insertions(+), 17 deletions(-)
drivers/net/xen-netback/netback.c +20 -17
@@ -1007,10 +1007,16 @@ static int xenvif_tx_check_gop(struct xe {struct gnttab_map_grant_ref *gop_map = *gopp_map;u16 pending_idx =XENVIF_TX_CB (skb)->pending_idx; +/* This always points to the shinfo of the skb being checked, which +* could be either the first or the one on the frag_list +*/ struct skb_shared_info *shinfo =skb_shinfo (skb); +/* If this is non-NULL, we are currently checking the frag_list skb, and +* this points to the shinfo of the first one +*/ +struct skb_shared_info *first_shinfo =NULL ;int nr_frags = shinfo->nr_frags;int i, err; -struct sk_buff *first_skb =NULL ;/* Check status of header. */ err = (*gopp_copy)->status;
@@ -1063,31 +1069,28 @@ check_frags:xenvif_idx_unmap (vif, pending_idx); } +/* And if we found the error while checking the frag_list, unmap +* the first skb's frags +*/ +if (first_shinfo) { +for (j =0 ; j < first_shinfo->nr_frags; j++) { + pending_idx =frag_get_pending_idx (&first_shinfo->frags[j]); +xenvif_idx_unmap (vif, pending_idx); + } + } +/* Remember the error: invalidate all subsequent fragments. */ err = newerr; } -if (skb_has_frag_list (skb)) { - first_skb = skb; - skb = shinfo->frag_list; - shinfo =skb_shinfo (skb); +if (skb_has_frag_list (skb) && !first_shinfo) { + first_shinfo =skb_shinfo (skb); + shinfo =skb_shinfo (skb_shinfo (skb)->frag_list); nr_frags = shinfo->nr_frags; goto check_frags; } -/* There was a mapping error in the frag_list skb. We have to unmap -* the first skb's frags -*/ -if (first_skb && err) { -int j; - shinfo =skb_shinfo (first_skb); -for (j =0 ; j < shinfo->nr_frags; j++) { - pending_idx =frag_get_pending_idx (&shinfo->frags[j]); -xenvif_idx_unmap (vif, pending_idx); - } - } - *gopp_map = gop_map;return err; }
Greg Kroah-Hartman
maintainerPATCH 76/109 xen-netback: Fix releasing frag_list skbs in error path
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit b42cc6e421e7bf74e545483aa34b99d2a2ca6d3a ]
When the grant operations failed, the skb is freed up eventually, and it tries to release the frags, if there is any. For the main skb nr_frags is set to 0 to avoid this, but on the frag_list it iterates through the frags array, and tries to call put_page on the page pointer which contains garbage at that time.
--- drivers/net/xen-netback/netback.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/net/xen-netback/netback.c +9 -0
@@ -1498,7 +1498,16 @@ static int xenvif_tx_submit(struct xenvi/* Check the remap error code. */ if (unlikely (xenvif_tx_check_gop (vif, skb, &gop_map, &gop_copy))) { +/* If there was an error, xenvif_tx_check_gop is +* expected to release all the frags which were mapped, +* so kfree_skb shouldn't do it again +*/ skb_shinfo (skb)->nr_frags =0 ; +if (skb_has_frag_list (skb)) { +struct sk_buff *nskb = +skb_shinfo (skb)->frag_list; +skb_shinfo (nskb)->nr_frags =0 ; + }kfree_skb (skb);continue ; }
Greg Kroah-Hartman
maintainerPATCH 76/109 xen-netback: Fix releasing frag_list skbs in error path
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit b42cc6e421e7bf74e545483aa34b99d2a2ca6d3a ]
When the grant operations failed, the skb is freed up eventually, and it tries to release the frags, if there is any. For the main skb nr_frags is set to 0 to avoid this, but on the frag_list it iterates through the frags array, and tries to call put_page on the page pointer which contains garbage at that time.
--- drivers/net/xen-netback/netback.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/net/xen-netback/netback.c +9 -0
@@ -1498,7 +1498,16 @@ static int xenvif_tx_submit(struct xenvi/* Check the remap error code. */ if (unlikely (xenvif_tx_check_gop (vif, skb, &gop_map, &gop_copy))) { +/* If there was an error, xenvif_tx_check_gop is +* expected to release all the frags which were mapped, +* so kfree_skb shouldn't do it again +*/ skb_shinfo (skb)->nr_frags =0 ; +if (skb_has_frag_list (skb)) { +struct sk_buff *nskb = +skb_shinfo (skb)->frag_list; +skb_shinfo (nskb)->nr_frags =0 ; + }kfree_skb (skb);continue ; }
Greg Kroah-Hartman
maintainerPATCH 77/109 xen-netback: Fix releasing header slot on error path
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit 1b860da0404a76af8533099ffe0a965490939369 ]
This patch makes this function aware that the first frag and the header might share the same ring slot. That could happen if the first slot is bigger than PKT_PROT_LEN. Due to this the error path might release that slot twice or never, depending on the error scenario.xenvif_idx_release is also removed from xenvif_idx_unmap, and called separately.
--- drivers/net/xen-netback/netback.c | 38 +++++++++++++++++++++++++++++++++----- 1 file changed, 33 insertions(+), 5 deletions(-)
drivers/net/xen-netback/netback.c +33 -5
@@ -1016,6 +1016,8 @@ static int xenvif_tx_check_gop(struct xe*/ struct skb_shared_info *first_shinfo =NULL ;int nr_frags = shinfo->nr_frags; +const bool sharedslot = nr_frags && +frag_get_pending_idx (&shinfo->frags[0 ]) == pending_idx;int i, err;/* Check status of header. */
@@ -1028,7 +1030,10 @@ static int xenvif_tx_check_gop(struct xe (*gopp_copy)->status, pending_idx, (*gopp_copy)->source.u.ref); -xenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_ERROR ); +/* The first frag might still have this slot mapped */ +if (!sharedslot) +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_ERROR ); } check_frags:
@@ -1045,8 +1050,19 @@ check_frags: pending_idx, gop_map->handle);/* Had a previous error? Invalidate this fragment. */ -if (unlikely (err)) +if (unlikely (err)) {xenvif_idx_unmap (vif, pending_idx); +/* If the mapping of the first frag was OK, but +* the header's copy failed, and they are +* sharing a slot, send an error +*/ +if (i ==0 && sharedslot) +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_ERROR ); +else +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_OKAY ); + }continue ; }
@@ -1058,15 +1074,27 @@ check_frags: gop_map->status, pending_idx, gop_map->ref); +xenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_ERROR );/* Not the first error? Preceding frags already invalidated. */ if (err)continue ; -/* First error: invalidate preceding fragments. */ + +/* First error: if the header haven't shared a slot with the +* first frag, release it as well. +*/ +if (!sharedslot) +xenvif_idx_release (vif, +XENVIF_TX_CB (skb)->pending_idx, +XEN_NETIF_RSP_OKAY ); + +/* Invalidate preceding fragments of this skb. */ for (j =0 ; j < i; j++) { pending_idx =frag_get_pending_idx (&shinfo->frags[j]);xenvif_idx_unmap (vif, pending_idx); +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_OKAY ); }/* And if we found the error while checking the frag_list, unmap
@@ -1076,6 +1104,8 @@ check_frags:for (j =0 ; j < first_shinfo->nr_frags; j++) { pending_idx =frag_get_pending_idx (&first_shinfo->frags[j]);xenvif_idx_unmap (vif, pending_idx); +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_OKAY ); } }
@@ -1811,8 +1841,6 @@ void xenvif_idx_unmap(struct xenvif *vif tx_unmap_op.status);BUG (); } - -xenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_OKAY ); }static inline int rx_work_todo (struct xenvif *vif)
Greg Kroah-Hartman
maintainerPATCH 77/109 xen-netback: Fix releasing header slot on error path
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit 1b860da0404a76af8533099ffe0a965490939369 ]
This patch makes this function aware that the first frag and the header might share the same ring slot. That could happen if the first slot is bigger than PKT_PROT_LEN. Due to this the error path might release that slot twice or never, depending on the error scenario.xenvif_idx_release is also removed from xenvif_idx_unmap, and called separately.
--- drivers/net/xen-netback/netback.c | 38 +++++++++++++++++++++++++++++++++----- 1 file changed, 33 insertions(+), 5 deletions(-)
drivers/net/xen-netback/netback.c +33 -5
@@ -1016,6 +1016,8 @@ static int xenvif_tx_check_gop(struct xe*/ struct skb_shared_info *first_shinfo =NULL ;int nr_frags = shinfo->nr_frags; +const bool sharedslot = nr_frags && +frag_get_pending_idx (&shinfo->frags[0 ]) == pending_idx;int i, err;/* Check status of header. */
@@ -1028,7 +1030,10 @@ static int xenvif_tx_check_gop(struct xe (*gopp_copy)->status, pending_idx, (*gopp_copy)->source.u.ref); -xenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_ERROR ); +/* The first frag might still have this slot mapped */ +if (!sharedslot) +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_ERROR ); } check_frags:
@@ -1045,8 +1050,19 @@ check_frags: pending_idx, gop_map->handle);/* Had a previous error? Invalidate this fragment. */ -if (unlikely (err)) +if (unlikely (err)) {xenvif_idx_unmap (vif, pending_idx); +/* If the mapping of the first frag was OK, but +* the header's copy failed, and they are +* sharing a slot, send an error +*/ +if (i ==0 && sharedslot) +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_ERROR ); +else +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_OKAY ); + }continue ; }
@@ -1058,15 +1074,27 @@ check_frags: gop_map->status, pending_idx, gop_map->ref); +xenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_ERROR );/* Not the first error? Preceding frags already invalidated. */ if (err)continue ; -/* First error: invalidate preceding fragments. */ + +/* First error: if the header haven't shared a slot with the +* first frag, release it as well. +*/ +if (!sharedslot) +xenvif_idx_release (vif, +XENVIF_TX_CB (skb)->pending_idx, +XEN_NETIF_RSP_OKAY ); + +/* Invalidate preceding fragments of this skb. */ for (j =0 ; j < i; j++) { pending_idx =frag_get_pending_idx (&shinfo->frags[j]);xenvif_idx_unmap (vif, pending_idx); +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_OKAY ); }/* And if we found the error while checking the frag_list, unmap
@@ -1076,6 +1104,8 @@ check_frags:for (j =0 ; j < first_shinfo->nr_frags; j++) { pending_idx =frag_get_pending_idx (&first_shinfo->frags[j]);xenvif_idx_unmap (vif, pending_idx); +xenvif_idx_release (vif, pending_idx, +XEN_NETIF_RSP_OKAY ); } }
@@ -1811,8 +1841,6 @@ void xenvif_idx_unmap(struct xenvif *vif tx_unmap_op.status);BUG (); } - -xenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_OKAY ); }static inline int rx_work_todo (struct xenvif *vif)
Greg Kroah-Hartman
maintainerPATCH 78/109 xen-netback: Fix pointer incrementation to avoid incorrect logging
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit d8cfbfc4660054150ca1b7c501a8edc0771022f9 ]
Due to this pointer is increased prematurely, the error log contains rubbish.
--- drivers/net/xen-netback/netback.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/xen-netback/netback.c +1 -1
@@ -1022,7 +1022,6 @@ static int xenvif_tx_check_gop(struct xe/* Check status of header. */ err = (*gopp_copy)->status; - (*gopp_copy)++;if (unlikely (err)) {if (net_ratelimit ()) netdev_dbg(vif->dev,
@@ -1035,6 +1034,7 @@ static int xenvif_tx_check_gop(struct xexenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_ERROR ); } + (*gopp_copy)++; check_frags:for (i =0 ; i < nr_frags; i++, gop_map++) {
Greg Kroah-Hartman
maintainerPATCH 78/109 xen-netback: Fix pointer incrementation to avoid incorrect logging
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Zoltan Kiss <[email protected]>
[ Upstream commit d8cfbfc4660054150ca1b7c501a8edc0771022f9 ]
Due to this pointer is increased prematurely, the error log contains rubbish.
--- drivers/net/xen-netback/netback.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/xen-netback/netback.c +1 -1
@@ -1022,7 +1022,6 @@ static int xenvif_tx_check_gop(struct xe/* Check status of header. */ err = (*gopp_copy)->status; - (*gopp_copy)++;if (unlikely (err)) {if (net_ratelimit ()) netdev_dbg(vif->dev,
@@ -1035,6 +1034,7 @@ static int xenvif_tx_check_gop(struct xexenvif_idx_release (vif, pending_idx,XEN_NETIF_RSP_ERROR ); } + (*gopp_copy)++; check_frags:for (i =0 ; i < nr_frags; i++, gop_map++) {
Greg Kroah-Hartman
maintainerPATCH 79/109 perf: Do not allow optimized switch for non-cloned events
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jiri Olsa <[email protected]>
commit 1f9a7268c67f0290837aada443d28fd953ddca90 upstream.
The context check in perf_event_context_sched_out allows non-cloned context to be part of the optimized schedule out switch.
This could move non-cloned context into another workload child. Once this child exits, the context is closed and leaves all original (parent) events in closed state.
Any other new cloned event will have closed state and not measure anything. And probably causing other odd bugs.
--- kernel/events/core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/events/core.c +1 -1
@@ -2315,7 +2315,7 @@ static void perf_event_context_sched_out next_parent =rcu_dereference (next_ctx->parent_ctx);/* If neither context have a parent context; they cannot be clones. */ -if (!parent && !next_parent) +if (!parent || !next_parent) goto unlock;if (next_parent == ctx || next_ctx == parent || next_parent == parent) {
Greg Kroah-Hartman
maintainerPATCH 81/109 mwifiex: fix Tx timeout issue
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Amitkumar Karwar <[email protected]>
commit d76744a93246eccdca1106037e8ee29debf48277 upstream.
https://bugzilla.kernel.org/show_bug.cgi?id=70191
https://bugzilla.kernel.org/show_bug.cgi?id=77581
It is observed that sometimes Tx packet is downloaded without adding driver's txpd header. This results in firmware parsing garbage data as packet length. Sometimes firmware is unable to read the packet if length comes out as invalid. This stops further traffic and timeout occurs.
The root cause is uninitialized fields in tx_info(skb->cb) of packet used to get garbage values. In this case if MWIFIEX_BUF_FLAG_REQUEUED_PKT flag is mistakenly set, txpd header was skipped. This patch makes sure that tx_info is correctly initialized to fix the problem.
--- drivers/net/wireless/mwifiex/main.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/wireless/mwifiex/main.c +1 -0
@@ -647,6 +647,7 @@ mwifiex_hard_start_xmit(struct sk_buff * } tx_info =MWIFIEX_SKB_TXCB (skb); +memset (tx_info,0 ,sizeof (*tx_info)); tx_info->bss_num = priv->bss_num; tx_info->bss_type = priv->bss_type; tx_info->pkt_len = skb->len;
Greg Kroah-Hartman
maintainerPATCH 82/109 ring-buffer: Fix polling on trace_pipe
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Martin Lau <[email protected]>
commit 97b8ee845393701edc06e27ccec2876ff9596019 upstream.
ring_buffer_poll_wait() should always put the poll_table to its wait_queue even there is immediate data available. Otherwise, the following epoll and read sequence will eventually hang forever:
1. Put some data to make the trace_pipe ring_buffer read ready first
2. epoll_ctl(efd, EPOLL_CTL_ADD, trace_pipe_fd, ee)
3. epoll_wait()
4. read(trace_pipe_fd) till EAGAIN
5. Add some more data to the trace_pipe ring_buffer
6. epoll_wait() -> this epoll_wait() will block forever
~ During the epoll_ctl(efd, EPOLL_CTL_ADD,...) call in step 2,
ring_buffer_poll_wait() returns immediately without adding poll_table, which has poll_table->_qproc pointing to ep_poll_callback(), to its wait_queue.
~ During the epoll_wait() call in step 3 and step 6,
ring_buffer_poll_wait() cannot add ep_poll_callback() to its wait_queue because the poll_table->_qproc is NULL and it is how epoll works.
~ When there is new data available in step 6, ring_buffer does not know
it has to call ep_poll_callback() because it is not in its wait queue. Hence, block forever.
Other poll implementation seems to call poll_wait() unconditionally as the very first thing to do. For example, tcp_poll() in tcp.c.
--- kernel/trace/ring_buffer.c | 4 ---- 1 file changed, 4 deletions(-)
kernel/trace/ring_buffer.c +0 -4
@@ -616,10 +616,6 @@ int ring_buffer_poll_wait(struct ring_bustruct ring_buffer_per_cpu *cpu_buffer;struct rb_irq_work *work; -if ((cpu ==RING_BUFFER_ALL_CPUS && !ring_buffer_empty (buffer)) || - (cpu !=RING_BUFFER_ALL_CPUS && !ring_buffer_empty_cpu (buffer, cpu))) -return POLLIN |POLLRDNORM ; -if (cpu ==RING_BUFFER_ALL_CPUS ) work = &buffer->irq_work;else {
Greg Kroah-Hartman
maintainerPATCH 83/109 irqchip: gic: Add support for cortex a7 compatible string
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Matthias Brugger <[email protected]>
commit a97e8027b1d28eafe6bafe062556c1ec926a49c6 upstream.
Patch 0a68214b "ARM: DT: Add binding for GIC virtualization extentions (VGIC)" added the "arm,cortex-a7-gic" compatible string, but the corresponding IRQCHIP_DECLARE was never added to the gic driver.
To let real Cortex-A7 SoCs use it, add the necessary declaration to the device driver.
--- drivers/irqchip/irq-gic.c | 1 + 1 file changed, 1 insertion(+)
drivers/irqchip/irq-gic.c +1 -0
@@ -1073,6 +1073,7 @@ gic_of_init(struct device_node *node, st }IRQCHIP_DECLARE (cortex_a15_gic,"arm,cortex-a15-gic" , gic_of_init);IRQCHIP_DECLARE (cortex_a9_gic,"arm,cortex-a9-gic" , gic_of_init); +IRQCHIP_DECLARE (cortex_a7_gic,"arm,cortex-a7-gic" , gic_of_init);IRQCHIP_DECLARE (msm_8660_qgic,"qcom,msm-8660-qgic" , gic_of_init);IRQCHIP_DECLARE (msm_qgic2,"qcom,msm-qgic2" , gic_of_init);
Greg Kroah-Hartman
maintainerPATCH 84/109 irqchip: gic: Add binding probe for ARM GIC400
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Suravee Suthikulpanit <[email protected]>
commit 144cb08864ed44be52d8634ac69cd98e5efcf527 upstream.
Commit 3ab72f9156bb "dt-bindings: add GIC-400 binding" added the "arm,gic-400" compatible string, but the corresponding IRQCHIP_DECLARE was never added to the gic driver.
Therefore add the missing irqchip declaration for it.
Removed additional empty line and adapted commit message to mark it as fixing an issue.
--- drivers/irqchip/irq-gic.c | 1 + 1 file changed, 1 insertion(+)
drivers/irqchip/irq-gic.c +1 -0
@@ -1071,6 +1071,7 @@ gic_of_init(struct device_node *node, st gic_cnt++;return 0 ; } +IRQCHIP_DECLARE (gic_400,"arm,gic-400" , gic_of_init);IRQCHIP_DECLARE (cortex_a15_gic,"arm,cortex-a15-gic" , gic_of_init);IRQCHIP_DECLARE (cortex_a9_gic,"arm,cortex-a9-gic" , gic_of_init);IRQCHIP_DECLARE (cortex_a7_gic,"arm,cortex-a7-gic" , gic_of_init);
Greg Kroah-Hartman
maintainerPATCH 85/109 irqchip: gic: Fix core ID calculation when topology is read from DT
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Tomasz Figa <[email protected]>
commit 29e697b11853d3f83b1864ae385abdad4aa2c361 upstream.
Certain GIC implementation, namely those found on earlier, single cluster, Exynos SoCs, have registers mapped without per-CPU banking, which means that the driver needs to use different offset for each CPU.
Currently the driver calculates the offset by multiplying value returned by cpu_logical_map() by CPU offset parsed from DT. This is correct when CPU topology is not specified in DT and aforementioned function returns core ID alone. However when DT contains CPU topology, the function changes to return cluster ID as well, which is non-zero on mentioned SoCs and so breaks the calculation in GIC driver.
This patch fixes this by masking out cluster ID in CPU offset calculation so that only core ID is considered. Multi-cluster Exynos SoCs already have banked GIC implementations, so this simple fix should be enough.
--- drivers/irqchip/irq-gic.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/irqchip/irq-gic.c +4 -1
@@ -42,6 +42,7 @@#include <linux/irqchip/chained_irq.h> #include <linux/irqchip/arm-gic.h> +#include <asm/cputype.h> #include <asm/irq.h> #include <asm/exception.h> #include <asm/smp_plat.h>
@@ -954,7 +955,9 @@ void __init gic_init_bases(unsigned int }for_each_possible_cpu (cpu) { -unsigned long offset = percpu_offset *cpu_logical_map (cpu); +u32 mpidr =cpu_logical_map (cpu); +u32 core_id =MPIDR_AFFINITY_LEVEL (mpidr,0 ); +unsigned long offset = percpu_offset * core_id; *per_cpu_ptr (gic->dist_base.percpu_base, cpu) = dist_base + offset; *per_cpu_ptr (gic->cpu_base.percpu_base, cpu) = cpu_base + offset; }
Greg Kroah-Hartman
maintainerPATCH 86/109 drm/radeon: set default bl level to something reasonable
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 201bb62402e0227375c655446ea04fcd0acf7287 upstream.
If the value in the scratch register is 0, set it to the max level. This fixes an issue where the console fb blanking code calls back into the backlight driver on unblank and then sets the backlight level to 0 after the driver has already set the mode and enabled the backlight.
bugs:
https://bugs.freedesktop.org/show_bug.cgi?id=81382
https://bugs.freedesktop.org/show_bug.cgi?id=70207
--- drivers/gpu/drm/radeon/atombios_encoders.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
drivers/gpu/drm/radeon/atombios_encoders.c +7 -3
@@ -183,7 +183,6 @@ void radeon_atom_backlight_init(struct rstruct backlight_properties props;struct radeon_backlight_privdata *pdata;struct radeon_encoder_atom_dig *dig; -u8 backlight_level;char bl_name[16 ];/* Mac laptops with multiple GPUs use the gmux driver for backlight
@@ -222,12 +221,17 @@ void radeon_atom_backlight_init(struct r pdata->encoder = radeon_encoder; - backlight_level =radeon_atom_get_backlight_level_from_reg (rdev); - dig = radeon_encoder->enc_priv; dig->bl_dev = bd; bd->props.brightness =radeon_atom_backlight_get_brightness (bd); +/* Set a reasonable default here if the level is 0 otherwise +* fbdev will attempt to turn the backlight on after console +* unblanking and it will try and restore 0 which turns the backlight +* off again. +*/ +if (bd->props.brightness ==0 ) + bd->props.brightness =RADEON_MAX_BL_LEVEL ; bd->props.power =FB_BLANK_UNBLANK ;backlight_update_status (bd);
Greg Kroah-Hartman
maintainerPATCH 87/109 drm/qxl: return IRQ_NONE if it was not our irq
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Jason Wang <[email protected]>
commit fbb60fe35ad579b511de8604b06a30b43846473b upstream.
Return IRQ_NONE if it was not our irq. This is necessary for the case when qxl is sharing irq line with a device A in a crash kernel. If qxl is initialized before A and A's irq was raised during this gap, returning IRQ_HANDLED in this case will cause this irq to be raised again after EOI since kernel think it was handled but in fact it was not.
--- drivers/gpu/drm/qxl/qxl_irq.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/gpu/drm/qxl/qxl_irq.c +3 -0
@@ -33,6 +33,9 @@ irqreturn_t qxl_irq_handler(int irq, voi pending =xchg (&qdev->ram_header->int_pending,0 ); +if (!pending) +return IRQ_NONE ; +atomic_inc (&qdev->irq_received);if (pending &QXL_INTERRUPT_DISPLAY ) {
Greg Kroah-Hartman
maintainerPATCH 88/109 drm/radeon: avoid leaking edid data
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 0ac66effe7fcdee55bda6d5d10d3372c95a41920 upstream.
In some cases we fetch the edid in the detect() callback in order to determine what sort of monitor is connected. If that happens, don't fetch the edid again in the get_modes() callback or we will leak the edid.
--- drivers/gpu/drm/radeon/radeon_display.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/gpu/drm/radeon/radeon_display.c +5 -0
@@ -757,6 +757,10 @@ int radeon_ddc_get_modes(struct radeon_cstruct radeon_device *rdev = dev->dev_private;int ret =0 ; +/* don't leak the edid if we already fetched it in detect() */ +if (radeon_connector->edid) + goto got_edid; +/* on hw with routers, select right port */ if (radeon_connector->router.ddc_valid)radeon_router_select_ddc_port (radeon_connector);
@@ -795,6 +799,7 @@ int radeon_ddc_get_modes(struct radeon_c radeon_connector->edid =radeon_bios_get_hardcoded_edid (rdev); }if (radeon_connector->edid) { +got_edid:drm_mode_connector_update_edid_property (&radeon_connector->base, radeon_connector->edid); ret =drm_add_edid_modes (&radeon_connector->base, radeon_connector->edid);drm_edid_to_eld (&radeon_connector->base, radeon_connector->edid);
Greg Kroah-Hartman
maintainerPATCH 89/109 Revert "drm/i915: reverse dp link param selection, prefer fast over wide again"
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dave Airlie <[email protected]>
commit c6930992948adf0f8fc1f6ff1da51c5002a2cf95 upstream.
This reverts commit 38aecea0ccbb909d635619cba22f1891e589b434.
This breaks Haswell Thinkpad + Lenovo dock in SST mode with a HDMI monitor attached.
Before this we can 1920x1200 mode, after this we only ever get 1024x768, and a lot of deferring.
This didn't revert clean, but this should be fine.
bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1117008
--- drivers/gpu/drm/i915/intel_dp.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/i915/intel_dp.c +2 -2
@@ -833,8 +833,8 @@ intel_dp_compute_config(struct intel_enc mode_rate =intel_dp_link_required (adjusted_mode->crtc_clock, bpp); -for (lane_count = min_lane_count; lane_count <= max_lane_count; lane_count <<=1 ) { -for (clock = min_clock; clock <= max_clock; clock++) { +for (clock = min_clock; clock <= max_clock; clock++) { +for (lane_count = min_lane_count; lane_count <= max_lane_count; lane_count <<=1 ) { link_clock =drm_dp_bw_code_to_link_rate (bws[clock]); link_avail =intel_dp_max_data_rate (link_clock, lane_count);
Greg Kroah-Hartman
maintainerPATCH 90/109 alarmtimer: Fix bug where relative alarm timers were treated as absolute
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: John Stultz <[email protected]>
commit 16927776ae757d0d132bdbfabbfe2c498342bd59 upstream.
Sharvil noticed with the posix timer_settime interface, using the CLOCK_REALTIME_ALARM or CLOCK_BOOTTIME_ALARM clockid, if the users tried to specify a relative time timer, it would incorrectly be treated as absolute regardless of the state of the flags argument.
This patch corrects this, properly checking the absolute/relative flag, as well as adds further error checking that no invalid flag bits are set.
--- kernel/time/alarmtimer.c | 20 ++++++++++++++++++-- 1 file changed, 18 insertions(+), 2 deletions(-)
kernel/time/alarmtimer.c +18 -2
@@ -585,9 +585,14 @@ static int alarm_timer_set(struct k_itimstruct itimerspec *new_setting, struct itimerspec *old_setting) { + ktime_t exp; +if (!rtcdev)return -ENOTSUPP ; +if (flags & ~TIMER_ABSTIME ) +return -EINVAL ; +if (old_setting)alarm_timer_get (timr, old_setting);
@@ -597,8 +602,16 @@ static int alarm_timer_set(struct k_itim/* start the timer */ timr->it.alarm.interval =timespec_to_ktime (new_setting->it_interval); -alarm_start (&timr->it.alarm.alarmtimer, -timespec_to_ktime (new_setting->it_value)); + exp =timespec_to_ktime (new_setting->it_value); +/* Convert (if necessary) to absolute time */ +if (flags !=TIMER_ABSTIME ) { +ktime_t now; + + now = alarm_bases[timr->it.alarm.alarmtimer.type].gettime (); + exp =ktime_add (now, exp); + } + +alarm_start (&timr->it.alarm.alarmtimer, exp);return 0 ; }
@@ -730,6 +743,9 @@ static int alarm_timer_nsleep(const clocif (!alarmtimer_get_rtcdev ())return -ENOTSUPP ; +if (flags & ~TIMER_ABSTIME ) +return -EINVAL ; +if (!capable (CAP_WAKE_ALARM ))return -EPERM ;
Greg Kroah-Hartman
maintainerPATCH 91/109 hwrng: fetch randomness only after device init
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Amit Shah <[email protected]>
commit d3cc7996473a7bdd33256029988ea690754e4e2a upstream.
Commit d9e7972619334 "hwrng: add randomness to system from rng sources" added a call to rng_get_data() from the hwrng_register() function. However, some rng devices need initialization before data can be read from them.
This commit makes the call to rng_get_data() depend on no init fn pointer being registered by the device. If an init function is registered, this call is made after device init.
--- drivers/char/hw_random/core.c | 41 +++++++++++++++++++++++++++++++++-------- 1 file changed, 33 insertions(+), 8 deletions(-)
drivers/char/hw_random/core.c +33 -8
@@ -55,16 +55,35 @@ static DEFINE_MUTEX(rng_mutex);static int data_avail;static u8 *rng_buffer; +static inline int rng_get_data (struct hwrng *rng,u8 *buffer,size_t size, +int wait); +static size_t rng_buffer_size (void ) {return SMP_CACHE_BYTES <32 ?32 :SMP_CACHE_BYTES ; } +static void add_early_randomness (struct hwrng *rng) +{ +unsigned char bytes[16 ]; +int bytes_read; + + bytes_read =rng_get_data (rng, bytes,sizeof (bytes),1 ); +if (bytes_read >0 ) +add_device_randomness (bytes, bytes_read); +} +static inline int hwrng_init (struct hwrng *rng) { -if (!rng->init) -return 0 ; -return rng->init (rng); +if (rng->init) { +int ret; + + ret = rng->init (rng); +if (ret) +return ret; + } +add_early_randomness (rng); +return 0 ; }static inline void hwrng_cleanup (struct hwrng *rng)
@@ -304,8 +323,6 @@ int hwrng_register(struct hwrng *rng) {int err = -EINVAL ;struct hwrng *old_rng, *tmp; -unsigned char bytes[16 ]; -int bytes_read;if (rng->name ==NULL || (rng->data_read ==NULL && rng->read ==NULL ))
@@ -347,9 +364,17 @@ int hwrng_register(struct hwrng *rng)INIT_LIST_HEAD (&rng->list);list_add_tail (&rng->list, &rng_list); - bytes_read =rng_get_data (rng, bytes,sizeof (bytes),1 ); -if (bytes_read >0 ) -add_device_randomness (bytes, bytes_read); +if (old_rng && !rng->init) { +/* +* Use a new device's input to add some randomness to +* the system. If this rng device isn't going to be +* used right away, its init function hasn't been +* called yet; so only use the randomness from devices +* that don't need an init callback. +*/ +add_early_randomness (rng); + } + out_unlock:mutex_unlock (&rng_mutex); out:
Greg Kroah-Hartman
maintainerPATCH 92/109 x86, tsc: Fix cpufreq lockup
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Zijlstra <[email protected]>
commit 3896c329df8092661dac80f55a8c3f60136fd61a upstream.
Mauro reported that his AMD X2 using the powernow-k8 cpufreq driver locked up when doing cpu hotplug.
Because we called set_cyc2ns_scale() from the time_cpufreq_notifier() unconditionally, it gets called multiple times for each freq change, instead of only the once, when the tsc_khz value actually changes.
Because it gets called more than once, we run out of cyc2ns data slots and stall, waiting for a free one, but because we're half way offline, there's no consumers to free slots.
By placing the call inside the condition that actually changes tsc_khz we avoid superfluous calls and avoid the problem.
--- arch/x86/kernel/tsc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/x86/kernel/tsc.c +2 -2
@@ -920,9 +920,9 @@ static int time_cpufreq_notifier(struct tsc_khz =cpufreq_scale (tsc_khz_ref, ref_freq, freq->new);if (!(freq->flags &CPUFREQ_CONST_LOOPS ))mark_tsc_unstable ("cpufreq changes" ); - } -set_cyc2ns_scale (tsc_khz, freq->cpu); +set_cyc2ns_scale (tsc_khz, freq->cpu); + }return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 93/109 cpufreq: move policy kobj to policy->cpu at resume
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Viresh Kumar <[email protected]>
commit 92c14bd9477a20a83144f08c0ca25b0308bf0730 upstream.
This is only relevant to implementations with multiple clusters, where clusters have separate clock lines but all CPUs within a cluster share it.
Consider a dual cluster platform with 2 cores per cluster. During suspend we start hot unplugging CPUs in order 1 to 3. When CPU2 is removed, policy->kobj would be moved to CPU3 and when CPU3 goes down we wouldn't free policy or its kobj as we want to retain permissions/values/etc.
Now on resume, we will get CPU2 before CPU3 and will call __cpufreq_add_dev(). We will recover the old policy and update policy->cpu from 3 to 2 from update_policy_cpu().
But the kobj is still tied to CPU3 and isn't moved to CPU2. We wouldn't create a link for CPU2, but would try that for CPU3 while bringing it online. Which will report errors as CPU3 already has kobj assigned to it.
This bug got introduced with commit 42f921a, which overlooked this scenario.
To fix this, lets move kobj to the new policy->cpu while bringing first CPU of a cluster back. Also do a WARN_ON() if kobject_move failed, as we would reach here only for the first CPU of a non-boot cluster. And we can't recover from this situation, if kobject_move() fails.
--- drivers/cpufreq/cpufreq.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/cpufreq/cpufreq.c +4 -2
@@ -1139,10 +1139,12 @@ static int __cpufreq_add_dev(struct devi* the creation of a brand new one. So we need to perform this update * by invoking update_policy_cpu(). */ -if (recover_policy && cpu != policy->cpu) +if (recover_policy && cpu != policy->cpu) {update_policy_cpu (policy, cpu); -else +WARN_ON (kobject_move (&policy->kobj, &dev->kobj)); + }else { policy->cpu = cpu; + }cpumask_copy (policy->cpus,cpumask_of (cpu));
Greg Kroah-Hartman
maintainerPATCH 94/109 random: check for increase of entropy_count because of signed conversion
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hannes Frederic Sowa <[email protected]>
commit 79a8468747c5f95ed3d5ce8376a3e82e0c5857fc upstream.
The expression entropy_count -= ibytes << (ENTROPY_SHIFT + 3) could actually increase entropy_count if during assignment of the unsigned expression on the RHS (mind the -=) we reduce the value modulo 2^width(int) and assign it to entropy_count. Trinity found this.
[ Commit modified by tytso to add an additional safety check for a
negative entropy_count -- which should never happen, and to also add an additional paranoia check to prevent overly large count values to be passed into urandom_read(). ]
--- drivers/char/random.c | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-)
drivers/char/random.c +14 -3
@@ -641,7 +641,7 @@ retry: }while (unlikely (entropy_count < pool_size-2 && pnfrac)); } -if (entropy_count <0 ) { +if (unlikely (entropy_count <0 )) {pr_warn ("random: negative entropy/overflow: pool %s count %d\n" , r->name, entropy_count);WARN_ON (1 );
@@ -980,7 +980,7 @@ static size_t account(struct entropy_sto int reserved) {int entropy_count, orig; -size_t ibytes; +size_t ibytes, nfrac;BUG_ON (r->entropy_count > r->poolinfo->poolfracbits);
@@ -998,7 +998,17 @@ retry: }if (ibytes < min) ibytes =0 ; -if ((entropy_count -= ibytes << (ENTROPY_SHIFT +3 )) <0 ) + +if (unlikely (entropy_count <0 )) { +pr_warn ("random: negative entropy count: pool %s count %d\n" , + r->name, entropy_count); +WARN_ON (1 ); + entropy_count =0 ; + } + nfrac = ibytes << (ENTROPY_SHIFT +3 ); +if ((size_t ) entropy_count > nfrac) + entropy_count -= nfrac; +else entropy_count =0 ;if (cmpxchg (&r->entropy_count, orig, entropy_count) != orig)
@@ -1375,6 +1385,7 @@ urandom_read(struct file *file, char __u"with %d bits of entropy available\n" , current->comm, nonblocking_pool.entropy_total); + nbytes =min_t (size_t, nbytes,INT_MAX >> (ENTROPY_SHIFT +3 )); ret =extract_entropy_user (&nonblocking_pool, buf, nbytes); trace_urandom_read(8 * nbytes, ENTROPY_BITS(&nonblocking_pool),
Greg Kroah-Hartman
maintainerPATCH 95/109 mtd: devices: elm: fix elm_context_save() and elm_context_restore() functions
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ted Juan <[email protected]>
commit 6938ad40cb97a52d88a763008935340729a4acc7 upstream.
These two function's switch case lack the 'break' that make them always return error.
--- drivers/mtd/devices/elm.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/mtd/devices/elm.c +2 -0
@@ -445,6 +445,7 @@ static int elm_context_save(struct elm_i ELM_SYNDROME_FRAGMENT_1 + offset); regs->elm_syndrome_fragment_0[i] =elm_read_reg (info,ELM_SYNDROME_FRAGMENT_0 + offset); +break ;default :return -EINVAL ; }
@@ -483,6 +484,7 @@ static int elm_context_restore(struct el regs->elm_syndrome_fragment_1[i]);elm_write_reg (info,ELM_SYNDROME_FRAGMENT_0 + offset, regs->elm_syndrome_fragment_0[i]); +break ;default :return -EINVAL ; }
Greg Kroah-Hartman
maintainerPATCH 96/109 dm thin metadata: do not allow the data block size to change
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mike Snitzer <[email protected]>
commit 9aec8629ec829fc9403788cd959e05dd87988bd1 upstream.
The block size for the thin-pool's data device must remained fixed for the life of the thin-pool. Disallow any attempt to change the thin-pool's data block size.
It should be noted that attempting to change the data block size via thin-pool table reload will be ignored as a side-effect of the thin-pool handover that the thin-pool target does during thin-pool table reload.
Here is an example outcome of attempting to load a thin-pool table that reduced the thin-pool's data block size from 1024K to 512K.
Before:
kernel: device-mapper: thin: 253:4: growing the data device from 204800 to 409600 blocks
After:
kernel: device-mapper: thin metadata: changing the data block size (from 2048 to 1024) is not supported
kernel: device-mapper: table: 253:4: thin-pool: Error creating metadata object
kernel: device-mapper: ioctl: error adding target to table
--- drivers/md/dm-thin-metadata.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/md/dm-thin-metadata.c +9 -0
@@ -613,6 +613,15 @@ static int __open_metadata(struct dm_poo disk_super =dm_block_data (sblock); +/* Verify the data block size hasn't changed */ +if (le32_to_cpu (disk_super->data_block_size) != pmd->data_block_size) { +DMERR ("changing the data block size (from %u to %llu) is not supported" , +le32_to_cpu (disk_super->data_block_size), + (unsigned long long )pmd->data_block_size); + r = -EINVAL ; + goto bad_unlock_sblock; + } + r =__check_incompat_features (disk_super, pmd);if (r <0 ) goto bad_unlock_sblock;
Greg Kroah-Hartman
maintainerPATCH 97/109 dm cache metadata: do not allow the data block size to change
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mike Snitzer <[email protected]>
commit 048e5a07f282c57815b3901d4a68a77fa131ce0a upstream.
The block size for the dm-cache's data device must remained fixed for the life of the cache. Disallow any attempt to change the cache's data block size.
--- drivers/md/dm-cache-metadata.c | 9 +++++++++ 1 file changed, 9 insertions(+)
drivers/md/dm-cache-metadata.c +9 -0
@@ -425,6 +425,15 @@ static int __open_metadata(struct dm_cac disk_super =dm_block_data (sblock); +/* Verify the data block size hasn't changed */ +if (le32_to_cpu (disk_super->data_block_size) != cmd->data_block_size) { +DMERR ("changing the data block size (from %u to %llu) is not supported" , +le32_to_cpu (disk_super->data_block_size), + (unsigned long long )cmd->data_block_size); + r = -EINVAL ; + goto bad; + } + r =__check_incompat_features (disk_super, cmd);if (r <0 ) goto bad;
Greg Kroah-Hartman
maintainerPATCH 98/109 RDMA/cxgb4: Initialize the device status page
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Steve Wise <[email protected]>
commit 6b54d54dea82ae214e4a45a503c4ef755a8ecee8 upstream.
The status page is mapped to user processes and allows sharing the device state between the kernel and user processes. This state isn't getting initialized and thus intermittently causes problems. Namely, the user process can mistakenly think the user doorbell writes are disabled which causes SQ work requests to never get fetched by HW.
--- drivers/infiniband/hw/cxgb4/device.c | 1 + 1 file changed, 1 insertion(+)
drivers/infiniband/hw/cxgb4/device.c +1 -0
@@ -654,6 +654,7 @@ static int c4iw_rdev_open(struct c4iw_rdpr_err (MOD "error allocating status page\n" ); goto err4; } + rdev->status_page->db_off =0 ;return 0 ; err4:c4iw_rqtpool_destroy (rdev);
Greg Kroah-Hartman
maintainerPATCH 99/109 PM / sleep: Fix request_firmware() error at resume
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Takashi Iwai <[email protected]>
commit 4320f6b1d9db4ca912c5eb6ecb328b2e090e1586 upstream.
The commit [247bc037: PM / Sleep: Mitigate race between the freezer and request_firmware()] introduced the finer state control, but it also leads to a new bug; for example, a bug report regarding the firmware loading of intel BT device at suspend/resume:
https://bugzilla.novell.com/show_bug.cgi?id=873790
The root cause seems to be a small window between the process resume and the clear of usermodehelper lock. The request_firmware() function checks the UMH lock and gives up when it's in UMH_DISABLE state. This is for avoiding the invalid f/w loading during suspend/resume phase. The problem is, however, that usermodehelper_enable() is called at the end of thaw_processes(). Thus, a thawed process in between can kick off the f/w loader code path (in this case, via btusb_setup_intel()) even before the call of usermodehelper_enable(). Then usermodehelper_read_trylock() returns an error and request_firmware() spews WARN_ON() in the end.
This oneliner patch fixes the issue just by setting to UMH_FREEZING state again before restarting tasks, so that the call of request_firmware() will be blocked until the end of this function instead of returning an error.
--- kernel/power/process.c | 1 + 1 file changed, 1 insertion(+)
kernel/power/process.c +1 -0
@@ -184,6 +184,7 @@ void thaw_processes(void)printk ("Restarting tasks ... " ); +__usermodehelper_set_disable_depth (UMH_FREEZING );thaw_workqueues ();read_lock (&tasklist_lock);
Greg Kroah-Hartman
maintainerPATCH 100/109 locking/mutex: Disable optimistic spinning on some architectures
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Zijlstra <[email protected]>
commit 4badad352a6bb202ec68afa7a574c0bb961e5ebc upstream.
The optimistic spin code assumes regular stores and cmpxchg() play nice; this is found to not be true for at least: parisc, sparc32, tile32, metag-lock1, arc-!llsc and hexagon.
There is further wreckage, but this in particular seemed easy to trigger, so blacklist this.
Opt in for known good archs.
--- arch/arm/Kconfig | 1 + arch/arm64/Kconfig | 1 + arch/powerpc/Kconfig | 1 + arch/sparc/Kconfig | 1 + arch/x86/Kconfig | 1 + kernel/Kconfig.locks | 5 ++++- 6 files changed, 9 insertions(+), 1 deletion(-)
arch/arm/Kconfig +1 -0
@@ -6,6 +6,7 @@ config ARM select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST select ARCH_HAVE_CUSTOM_GPIO_H select ARCH_MIGHT_HAVE_PC_PARPORT + select ARCH_SUPPORTS_ATOMIC_RMW select ARCH_USE_BUILTIN_BSWAP select ARCH_USE_CMPXCHG_LOCKREF select ARCH_WANT_IPC_PARSE_VERSION
arch/arm64/Kconfig +1 -0
@@ -2,6 +2,7 @@ config ARM64 def_bool y select ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select ARCH_USE_CMPXCHG_LOCKREF + select ARCH_SUPPORTS_ATOMIC_RMW select ARCH_HAS_TICK_BROADCAST if GENERIC_CLOCKEVENTS_BROADCAST select ARCH_WANT_OPTIONAL_GPIOLIB select ARCH_WANT_COMPAT_IPC_PARSE_VERSION
arch/powerpc/Kconfig +1 -0
@@ -145,6 +145,7 @@ config PPC select HAVE_IRQ_EXIT_ON_IRQ_STACK select ARCH_USE_CMPXCHG_LOCKREF if PPC64 select HAVE_ARCH_AUDITSYSCALL + select ARCH_SUPPORTS_ATOMIC_RMW config GENERIC_CSUM def_bool CPU_LITTLE_ENDIAN
arch/sparc/Kconfig +1 -0
@@ -78,6 +78,7 @@ config SPARC64 select HAVE_C_RECORDMCOUNT select NO_BOOTMEM select HAVE_ARCH_AUDITSYSCALL + select ARCH_SUPPORTS_ATOMIC_RMW config ARCH_DEFCONFIG string
arch/x86/Kconfig +1 -0
@@ -130,6 +130,7 @@ config X86 select HAVE_CC_STACKPROTECTOR select GENERIC_CPU_AUTOPROBE select HAVE_ARCH_AUDITSYSCALL + select ARCH_SUPPORTS_ATOMIC_RMW config INSTRUCTION_DECODER def_bool y
kernel/Kconfig.locks +4 -1
@@ -220,6 +220,9 @@ config INLINE_WRITE_UNLOCK_IRQRESTORE endif +config ARCH_SUPPORTS_ATOMIC_RMW + bool + config MUTEX_SPIN_ON_OWNER def_bool y - depends on SMP && !DEBUG_MUTEXES + depends on SMP && !DEBUG_MUTEXES && ARCH_SUPPORTS_ATOMIC_RMW
Greg Kroah-Hartman
maintainerPATCH 101/109 sched: Fix possible divide by zero in avg_atom() calculation
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Mateusz Guzik <[email protected]>
commit b0ab99e7736af88b8ac1b7ae50ea287fffa2badc upstream.
proc_sched_show_task() does:
if (nr_switches)
do_div(avg_atom, nr_switches);
nr_switches is unsigned long and do_div truncates it to 32 bits, which means it can test non-zero on e.g. x86-64 and be truncated to zero for division.
Fix the problem by using div64_ul() instead.
As a side effect calculations of avg_atom for big nr_switches are now correct.
--- kernel/sched/debug.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
kernel/sched/debug.c +1 -1
@@ -608,7 +608,7 @@ void proc_sched_show_task(struct task_st avg_atom = p->se.sum_exec_runtime;if (nr_switches) -do_div (avg_atom, nr_switches); + avg_atom =div64_ul (avg_atom, nr_switches);else avg_atom =-1LL ;
Greg Kroah-Hartman
maintainerPATCH 103/109 IB/mlx5: Enable "block multicast loopback" for kernel consumers
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Or Gerlitz <[email protected]>
commit 652c1a05171695d21b84dd3a723606b50eeb80fd upstream.
In commit f360d88a2efd, we advertise blocking multicast loopback to both kernel and userspace consumers, but don't allow kernel consumers (e.g IPoIB) to use it with their UD QPs. Fix that.
--- drivers/infiniband/hw/mlx5/qp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/infiniband/hw/mlx5/qp.c +1 -1
@@ -671,7 +671,7 @@ static int create_kernel_qp(struct mlx5_int err; uuari = &dev->mdev.priv.uuari; -if (init_attr->create_flags & ~IB_QP_CREATE_SIGNATURE_EN ) +if (init_attr->create_flags & ~(IB_QP_CREATE_SIGNATURE_EN |IB_QP_CREATE_BLOCK_MULTICAST_LOOPBACK ))return -EINVAL ;if (init_attr->qp_type ==MLX5_IB_QPT_REG_UMR )
Greg Kroah-Hartman
maintainerPATCH 104/109 aio: protect reqs_available updates from changes in interrupt handlers
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Benjamin LaHaise <[email protected]>
commit 263782c1c95bbddbb022dc092fd89a36bb8d5577 upstream.
As of commit f8567a3845ac05bb28f3c1b478ef752762bd39ef it is now possible to have put_reqs_available() called from irq context. While put_reqs_available() is per cpu, it did not protect itself from interrupts on the same CPU. This lead to aio_complete() corrupting the available io requests count when run under a heavy O_DIRECT workloads as reported by Robert Elliott. Fix this by disabling irq updates around the per cpu batch updates of reqs_available.
Many thanks to Robert and folks for testing and tracking this down.
--- fs/aio.c | 7 +++++++ 1 file changed, 7 insertions(+)
fs/aio.c +7 -0
@@ -830,16 +830,20 @@ void exit_aio(struct mm_struct *mm)static void put_reqs_available (struct kioctx *ctx,unsigned nr) {struct kioctx_cpu *kcpu; +unsigned long flags;preempt_disable (); kcpu =this_cpu_ptr (ctx->cpu); +local_irq_save (flags); kcpu->reqs_available += nr; +while (kcpu->reqs_available >= ctx->req_batch *2 ) { kcpu->reqs_available -= ctx->req_batch;atomic_add (ctx->req_batch, &ctx->reqs_available); } +local_irq_restore (flags);preempt_enable (); }
@@ -847,10 +851,12 @@ static bool get_reqs_available(struct ki {struct kioctx_cpu *kcpu;bool ret = false; +unsigned long flags;preempt_disable (); kcpu =this_cpu_ptr (ctx->cpu); +local_irq_save (flags);if (!kcpu->reqs_available) {int old, avail =atomic_read (&ctx->reqs_available);
@@ -869,6 +875,7 @@ static bool get_reqs_available(struct ki ret = true; kcpu->reqs_available--; out: +local_irq_restore (flags);preempt_enable ();return ret; }
Greg Kroah-Hartman
maintainerPATCH 105/109 gpio: dwapb: drop irq_setup_generic_chip()
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sebastian Andrzej Siewior <[email protected]>
commit 11d3d334af07408ce3a68860c40006ddcd343da5 upstream.
The driver calls irq_alloc_domain_generic_chips() which creates a gc and adds it to gc_list. The driver later then calls irq_setup_generic_chip() which also initializes the gc and adds it to the gc_list() and this corrupts the list. Enable LIST_DEBUG and you see the kernel complain. This isn't required, irq_alloc_domain_generic_chips() did the init.
--- drivers/gpio/gpio-dwapb.c | 3 --- 1 file changed, 3 deletions(-)
drivers/gpio/gpio-dwapb.c +0 -3
@@ -260,9 +260,6 @@ static void dwapb_configure_irqs(struct ct->regs.ack =GPIO_PORTA_EOI ; ct->regs.mask =GPIO_INTMASK ; -irq_setup_generic_chip (irq_gc,IRQ_MSK (port->bgc.gc.ngpio), -IRQ_GC_INIT_NESTED_LOCK ,IRQ_NOREQUEST ,0 ); -irq_set_chained_handler (irq, dwapb_irq_handler);irq_set_handler_data (irq, gpio);
Greg Kroah-Hartman
maintainerPATCH 106/109 ARM: dts: imx: Add alias for ethernet controller
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marek Vasut <[email protected]>
commit 22970070e027cbbb9b2878f8f7c31d0d7f29e94d upstream.
Add alias for FEC ethernet on i.MX to allow bootloaders (like U-Boot) patch-in the MAC address for FEC using this alias.
--- arch/arm/boot/dts/imx25.dtsi | 1 + arch/arm/boot/dts/imx27.dtsi | 1 + arch/arm/boot/dts/imx35.dtsi | 1 + arch/arm/boot/dts/imx50.dtsi | 1 + arch/arm/boot/dts/imx51.dtsi | 1 + arch/arm/boot/dts/imx53.dtsi | 1 + arch/arm/boot/dts/imx6qdl.dtsi | 1 + arch/arm/boot/dts/imx6sl.dtsi | 1 + 8 files changed, 8 insertions(+)
arch/arm/boot/dts/imx25.dtsi +1 -0
@@ -14,6 +14,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
arch/arm/boot/dts/imx27.dtsi +1 -0
@@ -16,6 +16,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
arch/arm/boot/dts/imx35.dtsi +1 -0
@@ -13,6 +13,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
arch/arm/boot/dts/imx50.dtsi +1 -0
@@ -17,6 +17,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
arch/arm/boot/dts/imx51.dtsi +1 -0
@@ -19,6 +19,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
arch/arm/boot/dts/imx53.dtsi +1 -0
@@ -18,6 +18,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
arch/arm/boot/dts/imx6qdl.dtsi +1 -0
@@ -16,6 +16,7 @@ / { aliases { + ethernet0 = &fec; can0 = &can1; can1 = &can2; gpio0 = &gpio1;
arch/arm/boot/dts/imx6sl.dtsi +1 -0
@@ -14,6 +14,7 @@ / { aliases { + ethernet0 = &fec; gpio0 = &gpio1; gpio1 = &gpio2; gpio2 = &gpio3;
Greg Kroah-Hartman
maintainerPATCH 107/109 iwlwifi: mvm: disable CTS to Self
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Emmanuel Grumbach <[email protected]>
commit dc271ee0d04d12d6bfabacbec803289a7072fbd9 upstream.
Firmware folks seem say that this flag can make trouble. Drop it. The advantage of CTS to self is that it slightly reduces the cost of the protection, but make the protection less reliable.
--- drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c +2 -6
@@ -667,13 +667,9 @@ static void iwl_mvm_mac_ctxt_cmd_common(if (vif->bss_conf.qos) cmd->qos_flags |=cpu_to_le32 (MAC_QOS_FLG_UPDATE_EDCA ); -/* Don't use cts to self as the fw doesn't support it currently. */ -if (vif->bss_conf.use_cts_prot) { +if (vif->bss_conf.use_cts_prot) cmd->protection_flags |=cpu_to_le32 (MAC_PROT_FLG_TGG_PROTECT ); -if (IWL_UCODE_API (mvm->fw->ucode_ver) >=8 ) - cmd->protection_flags |= -cpu_to_le32 (MAC_PROT_FLG_SELF_CTS_EN ); - } +IWL_DEBUG_RATE (mvm,"use_cts_prot %d, ht_operation_mode %d\n" , vif->bss_conf.use_cts_prot, vif->bss_conf.ht_operation_mode);
Greg Kroah-Hartman
maintainerPATCH 108/109 Dont trigger congestion wait on dirty-but-not-writeout pages
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Linus Torvalds <[email protected]>
commit b738d764652dc5aab1c8939f637112981fce9e0e upstream.
shrink_inactive_list() used to wait 0.1s to avoid congestion when all the pages that were isolated from the inactive list were dirty but not under active writeback. That makes no real sense, and apparently causes major interactivity issues under some loads since 3.11.
The ostensible reason for it was to wait for kswapd to start writing pages, but that seems questionable as well, since the congestion wait code seems to trigger for kswapd itself as well. Also, the logic behind delaying anything when we haven't actually started writeback is not clear - it only delays actually starting that writeback.
We'll still trigger the congestion waiting if
(a) the process is kswapd, and we hit pages flagged for immediate reclaim
(b) the process is not kswapd, and the zone backing dev writeback is actually congested.
This probably needs to be revisited, but as it is this fixes a reported regression.
--- mm/vmscan.c | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-)
mm/vmscan.c +5 -6
@@ -1554,19 +1554,18 @@ shrink_inactive_list(unsigned long nr_to* If dirty pages are scanned that are not queued for IO, it * implies that flushers are not keeping up. In this case, flag * the zone ZONE_TAIL_LRU_DIRTY and kswapd will start writing -* pages from reclaim context. It will forcibly stall in the -* next check. +* pages from reclaim context. */ if (nr_unqueued_dirty == nr_taken)zone_set_flag (zone,ZONE_TAIL_LRU_DIRTY );/* -* In addition, if kswapd scans pages marked marked for -* immediate reclaim and under writeback (nr_immediate), it -* implies that pages are cycling through the LRU faster than +* If kswapd scans pages marked marked for immediate +* reclaim and under writeback (nr_immediate), it implies +* that pages are cycling through the LRU faster than * they are written so also forcibly stall. */ -if (nr_unqueued_dirty == nr_taken || nr_immediate) +if (nr_immediate)congestion_wait (BLK_RW_ASYNC ,HZ /10 ); }
Greg Kroah-Hartman
maintainerPATCH 109/109 ARC: Implement ptrace(PTRACE_GET_THREAD_AREA)
In reply to Greg Kroah-Hartman3.15-stable review patch. If anyone has any objections, please let me know.
------------------
From: Anton Kolesov <[email protected]>
commit a4b6cb735b25aa84a462a1985e3e43bebaf5beb4 upstream.
This patch adds implementation of GET_THREAD_AREA ptrace request type. This is required by GDB to debug NPTL applications.
--- arch/arc/include/uapi/asm/ptrace.h | 1 + arch/arc/kernel/ptrace.c | 4 ++++ 2 files changed, 5 insertions(+)
arch/arc/include/uapi/asm/ptrace.h +1 -0
@@ -11,6 +11,7 @@#ifndef _UAPI__ASM_ARC_PTRACE_H#define _UAPI__ASM_ARC_PTRACE_H +#define PTRACE_GET_THREAD_AREA 25#ifndef __ASSEMBLY__/*
arch/arc/kernel/ptrace.c +4 -0
@@ -146,6 +146,10 @@ long arch_ptrace(struct task_struct *chipr_debug ("REQ=%ld: ADDR =0x%lx, DATA=0x%lx)\n" , request, addr, data);switch (request) { +case PTRACE_GET_THREAD_AREA : + ret =put_user (task_thread_info (child)->thr_ptr, + (unsigned long __user *)data); +break ;default : ret =ptrace_request (child, request, addr, data);break ;
At Sat, 26 Jul 2014 12:01:22 -0700,
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.15.7 release. There are 109 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 Mon Jul 28 19:02:07 UTC 2014. Anything received after that time might be too late.
All 3.15.7-rc1, 3.14.14-rc1, 3.10.50-rc1, and 3.4.100-rc1 passed my test.
- Test Cases:
- Build this kernel.
- Boot this kernel.
- Build the latest mainline kernel with this kernel.
- Test Tool:
https://github.com/satoru-takeuchi/test-linux-stable
- Test Result (kernel .config, ktest config and test log):
http://satoru-takeuchi.org/test-linux-stable/results/<version>-<test datetime>.tar.xz
- Build Environment:
- OS: Debian Jessy x86_64
- CPU: Intel(R) Core(TM) i5-2400 CPU @ 3.10GHz x 4
- memory: 8GB
- Test Target Environment:
- Debian Jessy x86_64 (KVM guest on the Build Environment)
- # of vCPU: 2
- memory: 2GB
Thanks,
Satoru
Quoted 472 lines
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.15.7-rc1.gzand the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:Greg Kroah-Hartman <[email protected]>
Linux 3.15.7-rc1Anton Kolesov <[email protected]>
ARC: Implementptrace(PTRACE_GET_THREAD_AREA)Linus Torvalds <[email protected]>
Don't trigger congestion wait on dirty-but-not-writeout pagesEmmanuel Grumbach <[email protected]>
iwlwifi: mvm: disable CTS to SelfMarek Vasut <[email protected]>
ARM: dts: imx: Add alias for ethernet controllerSebastian Andrzej Siewior <[email protected]>
gpio: dwapb: dropirq_setup_generic_chip()Benjamin LaHaise <[email protected]>
aio: protectreqs_availableupdates from changes in interrupt handlersOr Gerlitz <[email protected]>
IB/mlx5: Enable "block multicast loopback" for kernel consumersMichael Brown <[email protected]>
x86/efi: Include a .bss section within the PE/COFF headersMateusz Guzik <[email protected]>
sched: Fix possible divide by zero inavg_atom()calculationPeter Zijlstra <[email protected]>
locking/mutex: Disable optimistic spinning on some architecturesTakashi Iwai <[email protected]>
PM / sleep: Fixrequest_firmware()error at resumeSteve Wise <[email protected]>
RDMA/cxgb4: Initialize the device status pageMike Snitzer <[email protected]>
dm cache metadata: do not allow the data block size to changeMike Snitzer <[email protected]>
dm thin metadata: do not allow the data block size to changeTed Juan <[email protected]>
mtd: devices: elm: fixelm_context_save()andelm_context_restore()functionsHannes Frederic Sowa <[email protected]>
random: check for increase ofentropy_countbecause of signed conversionViresh Kumar <[email protected]>
cpufreq: move policy kobj to policy->cpu at resumePeter Zijlstra <[email protected]>
x86, tsc: Fix cpufreq lockupAmit Shah <[email protected]>
hwrng: fetch randomness only after device initJohn Stultz <[email protected]>
alarmtimer: Fix bug where relative alarm timers were treated as absoluteDave Airlie <[email protected]>
Revert "drm/i915: reverse dp link param selection, prefer fast over wide again"Alex Deucher <[email protected]>
drm/radeon: avoid leaking edid dataJason Wang <[email protected]>
drm/qxl: returnIRQ_NONEif it was not our irqAlex Deucher <[email protected]>
drm/radeon: set default bl level to something reasonableTomasz Figa <[email protected]>
irqchip: gic: Fix core ID calculation when topology is read from DTSuravee Suthikulpanit <[email protected]>
irqchip: gic: Add binding probe for ARM GIC400Matthias Brugger <[email protected]>
irqchip: gic: Add support for cortex a7 compatible stringMartin Lau <[email protected]>
ring-buffer: Fix polling ontrace_pipeAmitkumar Karwar <[email protected]>
mwifiex: fix Tx timeout issueHATAYAMA Daisuke <[email protected]>
perf/x86/intel: ignore CondChgd bit to avoid false NMI handlingJiri Olsa <[email protected]>
perf: Do not allow optimized switch for non-cloned eventsZoltan Kiss <[email protected]>
xen-netback: Fix pointer incrementation to avoid incorrect loggingZoltan Kiss <[email protected]>
xen-netback: Fix releasing header slot on error pathZoltan Kiss <[email protected]>
xen-netback: Fix releasingfrag_listskbs in error pathZoltan Kiss <[email protected]>
xen-netback: Fix handlingfrag_liston grant op error pathEric Dumazet <[email protected]>
ipv4: fix buffer overflow inip_options_compile()Ben Hutchings <[email protected]>
dns_resolver: Null-terminate the right stringManuel Sch�lling <[email protected]>
dns_resolver: assure thatdns_query()result is null-terminatedChristoph Schulz <[email protected]>
net: ppp: don't callsk_chk_filtertwiceBj�rn Mork <[email protected]>
net:huawei_cdc_ncm: add "subclass 3" devicesChristoph Schulz <[email protected]>
net: ppp: fix creating PPP pass and active filtersSowmini Varadhan <[email protected]>
sunvnet: clean up objects created invnet_new()onvnet_exit()Jerry Chu <[email protected]>
net-gre-gro: Fix a bug that breaks the forwarding pathNikolay Aleksandrov <[email protected]>
bonding: fixad_selectmodule param checkChristoph Schulz <[email protected]>
net: pppoe: use correct channel MTU when using Multilink PPPDaniel Borkmann <[email protected]>
net: sctp: fix information leaks in ulpevent layerJon Paul Maloy <[email protected]>
tipc: clear 'next'-pointer of message fragments before reassemblyhayeswang <[email protected]>
r8152: fix r8152_csum_workaround functionSuresh Reddy <[email protected]>
be2net: set EQ DB clear-intr bit inbe_open()Ben Pfaff <[email protected]>
netlink: Fix handling of error fromnetlink_dump().Thomas Fitzsimmons <[email protected]>
net: mvneta: Fix big endian issue inmvneta_txq_desc_csum()Thomas Petazzoni <[email protected]>
net: mvneta: fix operation in 10 Mbit/s modeAndrey Utkin <[email protected]>
appletalk: Fix socket referencing in skbYuchung Cheng <[email protected]>
tcp: fix false undo corner casesdingtianhong <[email protected]>
igmp: fix the problem when mc leave groupLoic Prylli <[email protected]>
net: FixNETDEV_CHANGEnotifier usage causing spurious arp flushBj�rn Mork <[email protected]>
net:qmi_wwan: add two Sierra Wireless/Netgear devicesBernd Wachter <[email protected]>
net:qmi_wwan: Add ID for Telewell TW-LTE 4G v2Edward Allcutt <[email protected]>
ipv4: icmp: Fix pMTU handling for rare caseChristoph Paasch <[email protected]>
tcp: Fix divide by zero when pushing during tcp-repairEric Dumazet <[email protected]>
bnx2x: fix possible panic under memory stressEric Dumazet <[email protected]>
vlan: free percpu stats in device destructorEric Dumazet <[email protected]>
net: fix sparse warning insk_dst_set()Eric Dumazet <[email protected]>
ipv4: irq safe sk_dst_[re]set() andipv4_sk_update_pmtu()fixEric Dumazet <[email protected]>
ipv4: fix dst race insk_dst_get()Wei-Chun Chao <[email protected]>
net: fix UDP tunnel GSO offrag_listGRO packetsBj�rn Mork <[email protected]>
net:huawei_cdc_ncm: increase command buffer sizeMugunthan V N <[email protected]>
drivers: net: cpsw: fix dual EMAC stall when connected to same switchLi RongQing <[email protected]>
8021q: fix a potential memory leakDaniel Borkmann <[email protected]>
net: sctp: checkproc_dointvecresult inproc_sctp_do_authNeal Cardwell <[email protected]>
tcp: fixtcp_match_skb_to_sack()for unaligned SACK at end of an skbKees Cook <[email protected]>
net: filter: fix upper BPF instruction limitDaniel Borkmann <[email protected]>
net: sctp: propagate sysctl errors from proc_do* properlyTyler Hall <[email protected]>
slcan: Portwrite_wakeupdeadlock fix from slipTyler Hall <[email protected]>
slip: Fix deadlock inwrite_wakeupDmitry Popov <[email protected]>
ip_tunnel: fixip_tunnel_lookupOr Gerlitz <[email protected]>
net/mlx4_en: Don't configure the HW vxlan parser when vxlan offloading isn't setOr Gerlitz <[email protected]>
net/mlx4_core: Fix the error flow when probing with invalid VF configurationHugh Dickins <[email protected]>
shmem: fix splicing from a hole while it's punchedHugh Dickins <[email protected]>
shmem: fix faulting into a hole, not takingi_mutexHugh Dickins <[email protected]>
shmem: fix faulting into a hole while it's punchedEmmanuel Grumbach <[email protected]>
iwlwifi: dvm: don't enable CTS to selfOren Givon <[email protected]>
iwlwifi: update the 7265 series HW IDsNiu Yawei <[email protected]>
quota: missing lock indqcache_shrink_scan()Stefan Assmann <[email protected]>
igb: do a reset on SR-IOV re-init if device is downTodd Fujinaka <[email protected]>
igb: Workaround for i210 Errata 25: Slow System ClockGuenter Roeck <[email protected]>
hwmon: (adt7470) Fix writes to temperature limit registersAxel Lin <[email protected]>
hwmon: (da9052) Don't use dash in the name attributeAxel Lin <[email protected]>
hwmon: (da9055) Don't use dash in the name attributeDavid Vrabel <[email protected]>
xen/manage: fix potential deadlock when resuming the consoleDavid Vrabel <[email protected]>
xen/balloon: set ballooned out pages as invalid in p2mzhangwei(Jovi) <[email protected]>
tracing: AddTRACE_ITER_PRINTKflag check in __trace_puts/__trace_bputszhangwei(Jovi) <[email protected]>
tracing: Addftrace_trace_stackinto __trace_puts/__trace_bputsSteven Rostedt (Red Hat) <[email protected]>
tracing: Fix graph tracer with stack tracer on other archsOleg Nesterov <[email protected]>
tracing: instance_rmdir() leaks ftrace_event_file->filterSrinivas Pandruvada <[email protected]>
iio:core: Handle error when mask type is not separateAnand Avati <[email protected]>
fuse: ignore entry-timeout onLOOKUP_REVALMiklos Szeredi <[email protected]>
fuse: handle large user and group IDMiklos Szeredi <[email protected]>
fuse: avoid scheduling while atomicMiklos Szeredi <[email protected]>
fuse: timeout comparison fixLoic Poulain <[email protected]>
Bluetooth: Ignore H5 non-link packets in non-active stateMarcel Holtmann <[email protected]>
Revert "Bluetooth: Add a new PID/VID 0cf3/e005 for AR3012."K. Y. Srinivasan <[email protected]>
Drivers: hv: util: Fix a bug in the KVP codeDexuan Cui <[email protected]>
Drivers: hv:hv_fcopy: fix a race condition for SMP guestTakashi Iwai <[email protected]>
ALSA: hda - Fix broken PM due to incomplete i915 initializationTakashi Iwai <[email protected]>
ALSA: hda - Revert stream assignment order for Intel controllersHans de Goede <[email protected]>
media:gspca_pac7302: Add new usb-id for Genius i-Look 317Abbas Raza <[email protected]>
usb: chipidea: udc: Disable auto ZLP generation on ep0Gavin Guo <[email protected]>
usb: Check if port status is equal to RxDetect-------------
Diffstat:
Makefile | 4 +- arch/arc/include/uapi/asm/ptrace.h | 1 + arch/arc/kernel/ptrace.c | 4 + arch/arm/Kconfig | 1 + arch/arm/boot/dts/imx25.dtsi | 1 + arch/arm/boot/dts/imx27.dtsi | 1 + arch/arm/boot/dts/imx35.dtsi | 1 + arch/arm/boot/dts/imx50.dtsi | 1 + arch/arm/boot/dts/imx51.dtsi | 1 + arch/arm/boot/dts/imx53.dtsi | 1 + arch/arm/boot/dts/imx6qdl.dtsi | 1 + arch/arm/boot/dts/imx6sl.dtsi | 1 + arch/arm64/Kconfig | 1 + arch/powerpc/Kconfig | 1 + arch/sparc/Kconfig | 1 + arch/x86/Kconfig | 1 + arch/x86/boot/header.S | 26 ++++- arch/x86/boot/tools/build.c | 38 ++++++-- arch/x86/kernel/cpu/perf_event_intel.c | 9 ++ arch/x86/kernel/tsc.c | 4 +- drivers/bluetooth/ath3k.c | 2 - drivers/bluetooth/btusb.c | 1 - drivers/bluetooth/hci_h5.c | 1 + drivers/char/hw_random/core.c | 41 ++++++-- drivers/char/random.c | 17 +++- drivers/cpufreq/cpufreq.c | 6 +- drivers/gpio/gpio-dwapb.c | 3 - drivers/gpu/drm/i915/intel_dp.c | 4 +- drivers/gpu/drm/qxl/qxl_irq.c | 3 + drivers/gpu/drm/radeon/atombios_encoders.c | 10 +- drivers/gpu/drm/radeon/radeon_display.c | 5 + drivers/hv/hv_fcopy.c | 2 +- drivers/hv/hv_kvp.c | 14 ++- drivers/hv/hv_util.c | 2 +- drivers/hwmon/adt7470.c | 6 +- drivers/hwmon/da9052-hwmon.c | 2 +- drivers/hwmon/da9055-hwmon.c | 2 +- drivers/iio/industrialio-event.c | 3 + drivers/infiniband/hw/cxgb4/device.c | 1 + drivers/infiniband/hw/mlx5/qp.c | 2 +- drivers/irqchip/irq-gic.c | 7 +- drivers/isdn/i4l/isdn_ppp.c | 28 +++--- drivers/md/dm-cache-metadata.c | 9 ++ drivers/md/dm-thin-metadata.c | 9 ++ drivers/media/usb/gspca/pac7302.c | 1 + drivers/mtd/devices/elm.c | 2 + drivers/net/bonding/bond_main.c | 2 +- drivers/net/can/slcan.c | 37 +++++-- drivers/net/ethernet/broadcom/bnx2x/bnx2x_cmn.c | 3 +- drivers/net/ethernet/emulex/benet/be_main.c | 2 +- drivers/net/ethernet/intel/igb/e1000_82575.c | 7 ++ drivers/net/ethernet/intel/igb/e1000_defines.h | 18 ++-- drivers/net/ethernet/intel/igb/e1000_hw.h | 3 + drivers/net/ethernet/intel/igb/e1000_i210.c | 66 +++++++++++++ drivers/net/ethernet/intel/igb/e1000_i210.h | 12 +++ drivers/net/ethernet/intel/igb/e1000_regs.h | 1 + drivers/net/ethernet/intel/igb/igb_main.c | 16 ++++ drivers/net/ethernet/marvell/mvneta.c | 4 +- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 2 +- drivers/net/ethernet/mellanox/mlx4/main.c | 3 +- drivers/net/ethernet/sun/sunvnet.c | 20 +++- drivers/net/ethernet/ti/cpsw.c | 7 +- drivers/net/ppp/ppp_generic.c | 30 +++--- drivers/net/ppp/pppoe.c | 2 +- drivers/net/slip/slip.c | 36 +++++-- drivers/net/slip/slip.h | 1 + drivers/net/usb/huawei_cdc_ncm.c | 10 +- drivers/net/usb/qmi_wwan.c | 3 + drivers/net/usb/r8152.c | 2 +- drivers/net/wireless/iwlwifi/dvm/rxon.c | 12 --- drivers/net/wireless/iwlwifi/mvm/mac-ctxt.c | 8 +- drivers/net/wireless/iwlwifi/pcie/drv.c | 3 +- drivers/net/wireless/mwifiex/main.c | 1 + drivers/net/xen-netback/netback.c | 86 ++++++++++++----- drivers/usb/chipidea/udc.c | 4 +- drivers/usb/core/hub.c | 19 ++++ drivers/xen/balloon.c | 12 +-- drivers/xen/manage.c | 5 +- fs/aio.c | 7 ++ fs/fuse/dev.c | 51 +++++----- fs/fuse/dir.c | 7 +- fs/fuse/inode.c | 20 +++- fs/quota/dquot.c | 2 + include/net/sock.h | 16 ++-- kernel/Kconfig.locks | 5 +- kernel/events/core.c | 2 +- kernel/power/process.c | 1 + kernel/sched/debug.c | 2 +- kernel/time/alarmtimer.c | 20 +++- kernel/trace/ftrace.c | 4 +- kernel/trace/ring_buffer.c | 4 - kernel/trace/trace.c | 18 +++- kernel/trace/trace_events.c | 1 + mm/shmem.c | 104 +++++++++++++++++--- mm/vmscan.c | 11 +-- net/8021q/vlan_core.c | 5 +- net/8021q/vlan_dev.c | 13 ++- net/appletalk/ddp.c | 3 - net/core/dev.c | 11 ++- net/core/dst.c | 16 +++- net/core/filter.c | 2 +- net/core/skbuff.c | 3 +- net/dns_resolver/dns_query.c | 4 +- net/ipv4/af_inet.c | 3 + net/ipv4/gre_offload.c | 3 + net/ipv4/icmp.c | 2 - net/ipv4/igmp.c | 10 +- net/ipv4/ip_options.c | 4 + net/ipv4/ip_tunnel.c | 26 ++--- net/ipv4/route.c | 15 +-- net/ipv4/tcp.c | 3 +- net/ipv4/tcp_input.c | 10 +- net/ipv4/tcp_offload.c | 2 +- net/ipv4/tcp_output.c | 6 +- net/ipv6/tcpv6_offload.c | 2 +- net/netlink/af_netlink.c | 4 +- net/sctp/sysctl.c | 46 ++++----- net/sctp/ulpevent.c | 122 +++--------------------- net/tipc/bcast.c | 1 + sound/pci/hda/hda_controller.c | 3 +- sound/pci/hda/hda_intel.c | 12 +-- sound/pci/hda/hda_priv.h | 1 + 122 files changed, 893 insertions(+), 433 deletions(-)
Greg Kroah-Hartman
maintainerQuoted 8 lines · Satoru Takeuchi
At Sat, 26 Jul 2014 12:01:22 -0700,
Quoted 6 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.15.7 release. There are 109 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.
Quoted 4 lines
Quoted 2 lines
Responses should be made by Mon Jul 28 19:02:07 UTC 2014. Anything received after that time might be too late.
All 3.15.7-rc1, 3.14.14-rc1, 3.10.50-rc1, and 3.4.100-rc1 passed my test.
Great, thanks for testing and letting me know.
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.15.7 release. There are 109 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 Mon Jul 28 19:02:07 UTC 2014. Anything received after that time might be too late.
Build results:
total: 139 pass: 139 fail: 0
Qemu tests all passed.
Details are available at http://server.roeck-us.net:8010/builders.
Guenter
Greg Kroah-Hartman
maintainerQuoted 10 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.15.7 release. There are 109 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 Mon Jul 28 19:02:07 UTC 2014. Anything received after that time might be too late.
Quoted 6 lines
Build results:
total: 139 pass: 139 fail: 0Qemu tests all passed.
Details are available at http://server.roeck-us.net:8010/builders.
Thanks for testing all of these and letting me know.
greg k-h