4.19.75-stable review
Subsystems (2)
Greg Kroah-Hartman
maintainercover 4.19.75-stable review
This is the start of the stable review cycle for the 4.19.75 release. There are 79 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 Sat 21 Sep 2019 09:44:25 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.75-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.19.75-rc1
Sean Young <[email protected]>
media: technisat-usb2: break out of loop at end of buffer
Will Deacon <[email protected]>
arm64: kpti: Whitelist Cortex-A CPUs that don't implement the CSV3 field
Kees Cook <[email protected]>
binfmt_elf: move brk out of mmap when doing direct loader exec
Jann Horn <[email protected]>
floppy: fix usercopy direction
Amir Goldstein <[email protected]>
ovl: fix regression caused by overlapping layers detection
Nathan Chancellor <[email protected]>
PCI: kirin: Fix section mismatch warning
Joerg Roedel <[email protected]>
iommu/amd: Fix race in increase_address_space()
Stuart Hayes <[email protected]>
iommu/amd: Flush old domains in kdump kernel
Hillf Danton <[email protected]>
keys: Fix missing null pointer check in request_key_auth_describe()
Tianyu Lan <[email protected]>
x86/hyper-v: Fix overflow bug in fill_gva_list()
Peter Zijlstra <[email protected]>
x86/uaccess: Don't leak the AC flags into __get_user() argument evaluation
Wenwen Wang <[email protected]>
dmaengine: ti: omap-dma: Add cleanup in omap_dma_probe()
Wenwen Wang <[email protected]>
dmaengine: ti: dma-crossbar: Fix a memory leak bug
Christophe JAILLET <[email protected]>
net: seeq: Fix the function used to release some memory in an error handling path
Dmitry Bogdanov <[email protected]>
net: aquantia: fix out of memory condition on rx side
Naoya Horiguchi <[email protected]>
tools/power turbostat: fix buffer overrun
Zephaniah E. Loss-Cutler-Hull <[email protected]>
tools/power x86_energy_perf_policy: Fix argument parsing
Ben Hutchings <[email protected]>
tools/power x86_energy_perf_policy: Fix "uninitialized variable" warnings at -O2
YueHaibing <[email protected]>
amd-xgbe: Fix error path in xgbe_mod_init()
Kim Phillips <[email protected]>
perf/x86/amd/ibs: Fix sample bias for dispatched micro-ops
Josh Hunt <[email protected]>
perf/x86/intel: Restrict period on Nehalem
Jarkko Nikula <[email protected]>
i2c: designware: Synchronize IRQs when unregistering slave client
Takashi Iwai <[email protected]>
sky2: Disable MSI on yet another ASUS boards (P6Xxxx)
Thomas Falcon <[email protected]>
ibmvnic: Do not process reset during or after device removal
zhaoyang <[email protected]>
ARM: 8901/1: add a criteria for pfn_valid of arm
Nagarjuna Kristam <[email protected]>
usb: host: xhci-tegra: Set DMA mask correctly
Dan Carpenter <[email protected]>
cifs: Use kzfree() to zero out the password
Ronnie Sahlberg <[email protected]>
cifs: set domainName when a domain-key is used in multiuser
Marc Zyngier <[email protected]>
kallsyms: Don't let kallsyms_lookup_size_offset() fail on retrieving the first symbol
Trond Myklebust <[email protected]>
NFSv2: Fix write regression
Trond Myklebust <[email protected]>
NFSv2: Fix eof handling
Thomas Jarosch <[email protected]>
netfilter: nf_conntrack_ftp: Fix debug output
Todd Seidelmann <[email protected]>
netfilter: xt_physdev: Fix spurious error message in physdev_mt_check
Thomas Gleixner <[email protected]>
x86/apic: Fix arch_dynirq_lower_bound() bug for DT enabled machines
Prashant Malani <[email protected]>
r8152: Set memory to all 0xFFs on failed reg reads
Ilya Leoshkevich <[email protected]>
bpf: allow narrow loads of some sk_reuseport_md fields with offset > 0
Sven Eckelmann <[email protected]>
batman-adv: Only read OGM2 tvlv_len after buffer len check
Doug Berger <[email protected]>
ARM: 8874/1: mm: only adjust sections of valid mm structures
Wenwen Wang <[email protected]>
qed: Add cleanup in qed_slowpath_start()
Ivan Khoronzhuk <[email protected]>
xdp: unpin xdp umem pages in error path
Christophe JAILLET <[email protected]>
Kconfig: Fix the reference to the IDT77105 Phy driver in the description of ATM_NICSTAR_USE_IDT77105
Trond Myklebust <[email protected]>
NFS: Fix initialisation of I/O result struct in nfs_pgio_rpcsetup
Trond Myklebust <[email protected]>
NFSv4: Fix return value in nfs_finish_open()
Trond Myklebust <[email protected]>
NFSv4: Fix return values for nfs4_file_open()
Juliana Rodrigueiro <[email protected]>
netfilter: xt_nfacct: Fix alignment mismatch in xt_nfacct_match_info
Pablo Neira Ayuso <[email protected]>
netfilter: nft_flow_offload: missing netlink attribute policy
Todd Seidelmann <[email protected]>
netfilter: ebtables: Fix argument order to ADD_COUNTER
Phil Reid <[email protected]>
fpga: altera-ps-spi: Fix getting of optional confd gpio
Quentin Monnet <[email protected]>
tools: bpftool: close prog FD before exit on showing a single program
Ilya Leoshkevich <[email protected]>
selftests/bpf: fix "bind{4, 6} deny specific IP & port" on s390
Ilya Leoshkevich <[email protected]>
s390/bpf: use 32-bit index for tail calls
Suman Anna <[email protected]>
bus: ti-sysc: Simplify cleanup upon failures in sysc_probe()
Janusz Krzysztofik <[email protected]>
ARM: OMAP1: ams-delta-fiq: Fix missing irq_ack
Faiz Abbas <[email protected]>
ARM: dts: dra74x: Fix iodelay configuration for mmc3
Tony Lindgren <[email protected]>
ARM: OMAP2+: Fix omap4 errata warning on other SoCs
Ilya Leoshkevich <[email protected]>
s390/bpf: fix lcgr instruction encoding
Tony Lindgren <[email protected]>
bus: ti-sysc: Fix using configured sysc mask value
Tony Lindgren <[email protected]>
ARM: OMAP2+: Fix missing SYSC_HAS_RESET_STATUS for dra7 epwmss
Faiz Abbas <[email protected]>
ARM: dts: am57xx: Disable voltage switching for SD card
YueHaibing <[email protected]>
ieee802154: hwsim: unregister hw while hwsim_subscribe_all_others fails
YueHaibing <[email protected]>
ieee802154: hwsim: Fix error handle path in hwsim_init_module
Masashi Honma <[email protected]>
nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds
Wen Huang <[email protected]>
mwifiex: Fix three heap overflow at parsing element in cfg80211_ap_settings
Razvan Stefanescu <[email protected]>
tty/serial: atmel: reschedule TX after RX was started
Chunyan Zhang <[email protected]>
serial: sprd: correct the wrong sequence of arguments
Hung-Te Lin <[email protected]>
firmware: google: check if size is valid when decoding VPD data
Matt Delco <[email protected]>
KVM: coalesced_mmio: add bounds checking
Cong Wang <[email protected]>
net_sched: let qdisc_put() accept NULL pointer
Dongli Zhang <[email protected]>
xen-netfront: do not assume sk_buff_head list is empty in error handling
Willem de Bruijn <[email protected]>
udp: correct reuseport selection with connected sockets
Xin Long <[email protected]>
ip6_gre: fix a dst leak in ip6erspan_tunnel_xmit
Yoshihiro Shimoda <[email protected]>
phy: renesas: rcar-gen3-usb2: Disable clearing VBUS in over-current
Sean Young <[email protected]>
media: tm6000: double free if usb disconnect while streaming
Alan Stern <[email protected]>
USB: usbcore: Fix slab-out-of-bounds bug during device reset
Aneesh Kumar K.V <[email protected]>
powerpc/mm/radix: Use the right page size for vmemmap mapping
Benjamin Tissoires <[email protected]>
Input: elan_i2c - remove Lenovo Legion Y7000 PnpID
Leon Romanovsky <[email protected]>
RDMA/restrack: Release task struct which was hold by CM_ID object
Aaron Armstrong Skomra <[email protected]>
HID: wacom: generic: read HID_DG_CONTACTMAX from any feature report
Pablo Neira Ayuso <[email protected]>
netfilter: nf_flow_table: set default timeout after successful insertion
-------------
Diffstat:
Documentation/filesystems/overlayfs.txt | 2 +- Makefile | 4 +- arch/arm/boot/dts/am571x-idk.dts | 7 +-- arch/arm/boot/dts/am572x-idk.dts | 7 +-- arch/arm/boot/dts/am574x-idk.dts | 7 +-- arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi | 1 + arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts | 7 +-- arch/arm/boot/dts/am57xx-beagle-x15-revc.dts | 7 +-- arch/arm/boot/dts/dra74x-mmc-iodelay.dtsi | 50 +++++++-------- arch/arm/mach-omap1/ams-delta-fiq-handler.S | 3 +- arch/arm/mach-omap1/ams-delta-fiq.c | 4 +- arch/arm/mach-omap2/omap4-common.c | 3 + arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 3 +- arch/arm/mm/init.c | 8 ++- arch/arm64/kernel/cpufeature.c | 6 ++ arch/powerpc/mm/pgtable-radix.c | 16 +++-- arch/s390/net/bpf_jit_comp.c | 12 ++-- arch/x86/events/amd/ibs.c | 13 +++- arch/x86/events/intel/core.c | 6 ++ arch/x86/hyperv/mmu.c | 8 ++- arch/x86/include/asm/perf_event.h | 12 ++-- arch/x86/include/asm/uaccess.h | 4 +- arch/x86/kernel/apic/io_apic.c | 8 ++- drivers/atm/Kconfig | 2 +- drivers/block/floppy.c | 4 +- drivers/bus/ti-sysc.c | 19 +++--- drivers/dma/ti/dma-crossbar.c | 4 +- drivers/dma/ti/omap-dma.c | 4 +- drivers/firmware/google/vpd.c | 4 +- drivers/firmware/google/vpd_decode.c | 55 +++++++++------- drivers/firmware/google/vpd_decode.h | 6 +- drivers/fpga/altera-ps-spi.c | 11 ++-- drivers/hid/wacom_sys.c | 10 +-- drivers/hid/wacom_wac.c | 4 ++ drivers/i2c/busses/i2c-designware-slave.c | 1 + drivers/infiniband/core/cma.c | 7 +-- drivers/infiniband/core/restrack.c | 6 +- drivers/input/mouse/elan_i2c_core.c | 2 +- drivers/iommu/amd_iommu.c | 40 ++++++++++-- drivers/media/usb/dvb-usb/technisat-usb2.c | 22 +++---- drivers/media/usb/tm6000/tm6000-dvb.c | 3 + drivers/net/ethernet/amd/xgbe/xgbe-main.c | 10 ++- drivers/net/ethernet/aquantia/atlantic/aq_vec.c | 3 +- drivers/net/ethernet/ibm/ibmvnic.c | 6 +- drivers/net/ethernet/marvell/sky2.c | 7 +++ drivers/net/ethernet/qlogic/qed/qed_main.c | 4 +- drivers/net/ethernet/seeq/sgiseeq.c | 7 ++- drivers/net/ieee802154/mac802154_hwsim.c | 8 ++- drivers/net/usb/r8152.c | 5 +- drivers/net/wireless/marvell/mwifiex/ie.c | 3 + drivers/net/wireless/marvell/mwifiex/uap_cmd.c | 9 ++- drivers/net/xen-netfront.c | 2 +- drivers/pci/controller/dwc/pcie-kirin.c | 4 +- drivers/phy/renesas/phy-rcar-gen3-usb2.c | 2 + drivers/tty/serial/atmel_serial.c | 1 - drivers/tty/serial/sprd_serial.c | 2 +- drivers/usb/core/config.c | 12 ++-- drivers/usb/host/xhci-tegra.c | 10 +++ fs/binfmt_elf.c | 11 ++++ fs/cifs/connect.c | 22 +++++++ fs/nfs/dir.c | 2 +- fs/nfs/nfs4file.c | 12 ++-- fs/nfs/pagelist.c | 2 +- fs/nfs/proc.c | 7 ++- fs/overlayfs/ovl_entry.h | 1 + fs/overlayfs/super.c | 73 ++++++++++++++-------- include/net/sock_reuseport.h | 21 ++++++- include/uapi/linux/netfilter/xt_nfacct.h | 5 ++ kernel/kallsyms.c | 6 +- net/batman-adv/bat_v_ogm.c | 18 ++++-- net/bridge/netfilter/ebtables.c | 8 +-- net/core/filter.c | 8 +-- net/core/sock_reuseport.c | 15 ++++- net/ipv4/datagram.c | 2 + net/ipv4/udp.c | 5 +- net/ipv6/datagram.c | 2 + net/ipv6/ip6_gre.c | 2 +- net/ipv6/udp.c | 5 +- net/netfilter/nf_conntrack_ftp.c | 2 +- net/netfilter/nf_flow_table_core.c | 2 +- net/netfilter/nft_flow_offload.c | 6 ++ net/netfilter/xt_nfacct.c | 36 +++++++---- net/netfilter/xt_physdev.c | 6 +- net/sched/sch_generic.c | 3 + net/wireless/nl80211.c | 4 +- net/xdp/xdp_umem.c | 4 +- security/keys/request_key_auth.c | 6 ++ tools/bpf/bpftool/prog.c | 4 +- tools/power/x86/turbostat/turbostat.c | 2 +- .../x86_energy_perf_policy.c | 28 +++++---- tools/testing/selftests/bpf/test_sock.c | 7 ++- virt/kvm/coalesced_mmio.c | 17 ++--- 92 files changed, 561 insertions(+), 290 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/79 netfilter: nf_flow_table: set default timeout after successful insertion
From: Pablo Neira Ayuso <[email protected]>
commit 110e48725db6262f260f10727d0fb2d3d25895e4 upstream.
Set up the default timeout for this new entry otherwise the garbage collector might quickly remove it right after the flowtable insertion.
--- net/netfilter/nf_flow_table_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/netfilter/nf_flow_table_core.c +1 -1
@@ -203,7 +203,7 @@ int flow_offload_add(struct nf_flowtablereturn err; } - flow->timeout = (u32 )jiffies; + flow->timeout = (u32 )jiffies +NF_FLOW_TIMEOUT ;return 0 ; }EXPORT_SYMBOL_GPL (flow_offload_add);
Greg Kroah-Hartman
maintainerPATCH 2/79 HID: wacom: generic: read HID_DG_CONTACTMAX from any feature report
In reply to Greg Kroah-HartmanFrom: Aaron Armstrong Skomra <[email protected]>
commit 184eccd40389df29abefab88092c4ff33191fd0c upstream.
In the generic code path, HID_DG_CONTACTMAX was previously only read from the second byte of report 0x23.
Another report (0x82) has the HID_DG_CONTACTMAX in the higher nibble of the third byte. We should support reading the value of HID_DG_CONTACTMAX no matter what report we are reading or which position that value is in.
To do this we submit the feature report as a event report using hid_report_raw_event(). Our modified finger event path records the value of HID_DG_CONTACTMAX when it sees that usage.
--- drivers/hid/wacom_sys.c | 10 ++++++---- drivers/hid/wacom_wac.c | 4 ++++ 2 files changed, 10 insertions(+), 4 deletions(-)
drivers/hid/wacom_sys.c +6 -4
@@ -282,14 +282,16 @@ static void wacom_feature_mapping(struct/* leave touch_max as is if predefined */ if (!features->touch_max) {/* read manually */ - data =kzalloc (2 ,GFP_KERNEL ); + n =hid_report_len (field->report); + data =hid_alloc_report_buf (field->report,GFP_KERNEL );if (!data)break ; data[0 ] = field->report->id; ret =wacom_get_report (hdev,HID_FEATURE_REPORT , - data,2 ,WAC_CMD_RETRIES ); -if (ret ==2 ) { - features->touch_max = data[1 ]; + data, n,WAC_CMD_RETRIES ); +if (ret == n) { + ret =hid_report_raw_event (hdev, +HID_FEATURE_REPORT , data, n,0 ); }else { features->touch_max =16 ; hid_warn(hdev, "wacom_feature_mapping: "
drivers/hid/wacom_wac.c +4 -0
@@ -2533,6 +2533,7 @@ static void wacom_wac_finger_event(strucstruct wacom *wacom =hid_get_drvdata (hdev);struct wacom_wac *wacom_wac = &wacom->wacom_wac;unsigned equivalent_usage =wacom_equivalent_usage (usage->hid); +struct wacom_features *features = &wacom->wacom_wac.features;switch (equivalent_usage) {case HID_GD_X :
@@ -2553,6 +2554,9 @@ static void wacom_wac_finger_event(struccase HID_DG_TIPSWITCH : wacom_wac->hid_data.tipswitch = value;break ; +case HID_DG_CONTACTMAX : + features->touch_max = value; +return ; }
Greg Kroah-Hartman
maintainerPATCH 3/79 RDMA/restrack: Release task struct which was hold by CM_ID object
In reply to Greg Kroah-HartmanFrom: Leon Romanovsky <[email protected]>
commit ed7a01fd3fd77f40b4ef2562b966a5decd8928d2 upstream.
Tracking CM_ID resource is performed in two stages: creation of cm_id and connecting it to the cma_dev. It is needed because rdma-cm protocol exports two separate user-visible calls rdma_create_id and rdma_accept.
At the time of CM_ID creation, the real owner of that object is unknown yet and we need to grab task_struct. This task_struct is released or reassigned in attach phase later on. but call to rdma_destroy_id left this task_struct unreleased.
Such separation is unique to CM_ID and other restrack objects initialize in one shot. It means that it is safe to use "res->valid" check to catch unfinished CM_ID flow and release task_struct for that object.
--- drivers/infiniband/core/cma.c | 7 +++---- drivers/infiniband/core/restrack.c | 6 ++++-- 2 files changed, 7 insertions(+), 6 deletions(-)
drivers/infiniband/core/cma.c +3 -4
@@ -1723,8 +1723,8 @@ void rdma_destroy_id(struct rdma_cm_id *mutex_lock (&id_priv->handler_mutex);mutex_unlock (&id_priv->handler_mutex); +rdma_restrack_del (&id_priv->res);if (id_priv->cma_dev) { -rdma_restrack_del (&id_priv->res);if (rdma_cap_ib_cm (id_priv->id.device,1 )) {if (id_priv->cm_id.ib)ib_destroy_cm_id (id_priv->cm_id.ib);
@@ -3463,10 +3463,9 @@ int rdma_bind_addr(struct rdma_cm_id *idreturn 0 ; err2: -if (id_priv->cma_dev) { -rdma_restrack_del (&id_priv->res); +rdma_restrack_del (&id_priv->res); +if (id_priv->cma_dev)cma_release_dev (id_priv); - } err1:cma_comp_exch (id_priv,RDMA_CM_ADDR_BOUND ,RDMA_CM_IDLE );return ret;
drivers/infiniband/core/restrack.c +4 -2
@@ -209,7 +209,7 @@ void rdma_restrack_del(struct rdma_restrstruct ib_device *dev;if (!res->valid) -return ; + goto out; dev =res_to_dev (res);if (!dev)
@@ -222,8 +222,10 @@ void rdma_restrack_del(struct rdma_restrdown_write (&dev->res.rwsem);hash_del (&res->node); res->valid = false; +up_write (&dev->res.rwsem); + +out:if (res->task)put_task_struct (res->task); -up_write (&dev->res.rwsem); }EXPORT_SYMBOL (rdma_restrack_del);
Re: [PATCH 4.19 03/79] RDMA/restrack: Release task struct which was hold by CM_ID object
Hi!
Quoted 6 lines
commit
ed7a01fd3fd77f40b4ef2562b966a5decd8928d2upstream.Tracking
CM_IDresource is performed in two stages: creation ofcm_idand connecting it to thecma_dev. It is needed because rdma-cm protocol exports two separate user-visible callsrdma_create_idandrdma_accept.
...
Mainline says this needs additional fix, fe9bc1644918aa1d, see below.
drivers/infiniband/core/restrack.c void rdma_restrack_del(struct rdma_restr · line 215
Quoted 11 lines
drivers/infiniband/core/restrack.c +1
-1@@ -209,7 +209,7 @@ void rdma_restrack_del(struct rdma_restrstruct ib_device *dev;if (!res->valid) -return ; + goto out; dev =res_to_dev (res);if (!dev)
# return;
This test does return, does it need to go through 'goto out', too? (I see it should not happen, but...)
drivers/infiniband/core/restrack.c void rdma_restrack_del(struct rdma_restr · line 230
Quoted 11 lines
drivers/infiniband/core/restrack.c +3
-1@@ -222,8 +222,10 @@ void rdma_restrack_del(struct rdma_restrdown_write (&dev->res.rwsem);hash_del (&res->node); res->valid = false; +up_write (&dev->res.rwsem); + +out:if (res->task)put_task_struct (res->task); -up_write (&dev->res.rwsem); }
Mainline says res->task = NULL is needed there, see fe9bc1644918aa1d.
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Greg Kroah-Hartman
maintainerRe: [PATCH 4.19 03/79] RDMA/restrack: Release task struct which was hold by CM_ID object
Quoted 28 lines · Pavel Machek
Hi!
Quoted 6 lines
commit
ed7a01fd3fd77f40b4ef2562b966a5decd8928d2upstream.Tracking
CM_IDresource is performed in two stages: creation ofcm_idand connecting it to thecma_dev. It is needed because rdma-cm protocol exports two separate user-visible callsrdma_create_idandrdma_accept....
Mainline says this needs additional fix,
fe9bc1644918aa1d, see below.drivers/infiniband/core/restrack.c void rdma_restrack_del(struct rdma_restr · line 215
Quoted 11 lines
drivers/infiniband/core/restrack.c +1
-1@@ -209,7 +209,7 @@ void rdma_restrack_del(struct rdma_restrstruct ib_device *dev;if (!res->valid) -return ; + goto out; dev =res_to_dev (res);if (!dev)# return;
This test does return, does it need to go through 'goto out', too? (I see it should not happen, but...)
Quoted 13 lines
drivers/infiniband/core/restrack.c void rdma_restrack_del(struct rdma_restr · line 230
Quoted 11 lines
drivers/infiniband/core/restrack.c +3
-1@@ -222,8 +222,10 @@ void rdma_restrack_del(struct rdma_restrdown_write (&dev->res.rwsem);hash_del (&res->node); res->valid = false; +up_write (&dev->res.rwsem); + +out:if (res->task)put_task_struct (res->task); -up_write (&dev->res.rwsem); }Mainline says
res->task= NULL is needed there, seefe9bc1644918aa1d.
Good catch, now queued up, thanks!
greg k-h
Greg Kroah-Hartman
maintainerPATCH 4/79 Input: elan_i2c - remove Lenovo Legion Y7000 PnpID
In reply to Greg Kroah-HartmanFrom: Benjamin Tissoires <[email protected]>
commit 0c043d70d04711fe6c380df9065fdc44192c49bf upstream.
Looks like the Bios of the Lenovo Legion Y7000 is using ELAN061B when the actual device is supposed to be used with hid-multitouch.
Remove it from the list of the supported device, hoping that no one will complain about the loss in functionality.
--- drivers/input/mouse/elan_i2c_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/input/mouse/elan_i2c_core.c +1 -1
@@ -1358,7 +1358,7 @@ static const struct acpi_device_id elan_ { "ELAN0618", 0 }, { "ELAN0619", 0 }, { "ELAN061A", 0 }, - { "ELAN061B", 0 }, +/* { "ELAN061B", 0 }, not working on the Lenovo Legion Y7000 */ { "ELAN061C", 0 }, { "ELAN061D", 0 }, { "ELAN061E", 0 },
Greg Kroah-Hartman
maintainerPATCH 5/79 powerpc/mm/radix: Use the right page size for vmemmap mapping
In reply to Greg Kroah-HartmanFrom: Aneesh Kumar K.V <[email protected]>
commit 89a3496e0664577043666791ec07fb731d57c950 upstream.
We use mmu_vmemmap_psize to find the page size for mapping the vmmemap area. With radix translation, we are suboptimally setting this value to PAGE_SIZE.
We do check for 2M page size support and update mmu_vmemap_psize to use hugepage size but we suboptimally reset the value to PAGE_SIZE in radix__early_init_mmu(). This resulted in always mapping vmemmap area with 64K page size.
--- arch/powerpc/mm/pgtable-radix.c | 16 +++++++--------- 1 file changed, 7 insertions(+), 9 deletions(-)
arch/powerpc/mm/pgtable-radix.c +7 -9
@@ -521,14 +521,6 @@ void __init radix__early_init_devtree(vo mmu_psize_defs[MMU_PAGE_64K ].shift =16 ; mmu_psize_defs[MMU_PAGE_64K ].ap =0x5 ; found: -#ifdef CONFIG_SPARSEMEM_VMEMMAP -if (mmu_psize_defs[MMU_PAGE_2M ].shift) { -/* -* map vmemmap using 2M if available -*/ - mmu_vmemmap_psize =MMU_PAGE_2M ; - } -#endif /* CONFIG_SPARSEMEM_VMEMMAP */ return ; }
@@ -567,7 +559,13 @@ void __init radix__early_init_mmu(void)#ifdef CONFIG_SPARSEMEM_VMEMMAP /* vmemmap mapping */ - mmu_vmemmap_psize = mmu_virtual_psize; +if (mmu_psize_defs[MMU_PAGE_2M ].shift) { +/* +* map vmemmap using 2M if available +*/ + mmu_vmemmap_psize =MMU_PAGE_2M ; + }else + mmu_vmemmap_psize = mmu_virtual_psize;#endif /* * initialize page table size
Greg Kroah-Hartman
maintainerPATCH 6/79 USB: usbcore: Fix slab-out-of-bounds bug during device reset
In reply to Greg Kroah-HartmanFrom: Alan Stern <[email protected]>
commit 3dd550a2d36596a1b0ee7955da3b611c031d3873 upstream.
The syzbot fuzzer provoked a slab-out-of-bounds error in the USB core:
BUG: KASAN: slab-out-of-bounds in memcmp+0xa6/0xb0 lib/string.c:904 Read of size 1 at addr ffff8881d175bed6 by task kworker/0:3/2746 CPU: 0 PID: 2746 Comm: kworker/0:3 Not tainted 5.3.0-rc5+ #28 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: usb_hub_wq hub_event Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0xca/0x13e lib/dump_stack.c:113 print_address_description+0x6a/0x32c mm/kasan/report.c:351 __kasan_report.cold+0x1a/0x33 mm/kasan/report.c:482 kasan_report+0xe/0x12 mm/kasan/common.c:612 memcmp+0xa6/0xb0 lib/string.c:904 memcmp include/linux/string.h:400 [inline] descriptors_changed drivers/usb/core/hub.c:5579 [inline] usb_reset_and_verify_device+0x564/0x1300 drivers/usb/core/hub.c:5729 usb_reset_device+0x4c1/0x920 drivers/usb/core/hub.c:5898 rt2x00usb_probe+0x53/0x7af
drivers/net/wireless/ralink/rt2x00/rt2x00usb.c:806
The error occurs when the descriptors_changed() routine (called during a device reset) attempts to compare the old and new BOS and capability descriptors. The length it uses for the comparison is the wTotalLength value stored in BOS descriptor, but this value is not necessarily the same as the length actually allocated for the descriptors. If it is larger the routine will call memcmp() with a length that is too big, thus reading beyond the end of the allocated region and leading to this fault.
The kernel reads the BOS descriptor twice: first to get the total length of all the capability descriptors, and second to read it along with all those other descriptors. A malicious (or very faulty) device may send different values for the BOS descriptor fields each time. The memory area will be allocated using the wTotalLength value read the first time, but stored within it will be the value read the second time.
To prevent this possibility from causing any errors, this patch modifies the BOS descriptor after it has been read the second time:
It sets the wTotalLength field to the actual length of the descriptors that were read in and validated. Then the memcpy() call, or any other code using these descriptors, will be able to rely on wTotalLength being valid.
--- drivers/usb/core/config.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-)
drivers/usb/core/config.c +8 -4
@@ -925,7 +925,7 @@ int usb_get_bos_descriptor(struct usb_destruct usb_bos_descriptor *bos;struct usb_dev_cap_header *cap;struct usb_ssp_cap_descriptor *ssp_cap; -unsigned char *buffer; +unsigned char *buffer, *buffer0;int length, total_len, num, i, ssac;__u8 cap_type;int ret;
@@ -970,10 +970,12 @@ int usb_get_bos_descriptor(struct usb_de ret = -ENOMSG ; goto err; } + + buffer0 = buffer; total_len -= length; + buffer += length;for (i =0 ; i < num; i++) { - buffer += length; cap = (struct usb_dev_cap_header *)buffer;if (total_len <sizeof (*cap) || total_len < cap->bLength) {
@@ -987,8 +989,6 @@ int usb_get_bos_descriptor(struct usb_debreak ; } - total_len -= length; -if (cap->bDescriptorType !=USB_DT_DEVICE_CAPABILITY ) {dev_warn (ddev,"descriptor type invalid, skip\n" );continue ;
@@ -1023,7 +1023,11 @@ int usb_get_bos_descriptor(struct usb_dedefault :break ; } + + total_len -= length; + buffer += length; } + dev->bos->desc->wTotalLength =cpu_to_le16 (buffer - buffer0);return 0 ;
Greg Kroah-Hartman
maintainerPATCH 7/79 media: tm6000: double free if usb disconnect while streaming
In reply to Greg Kroah-HartmanFrom: Sean Young <[email protected]>
commit 699bf94114151aae4dceb2d9dbf1a6312839dcae upstream.
The usb_bulk_urb will kfree'd on disconnect, so ensure the pointer is set to NULL after each free.
stop stream
urb killing
urb buffer free
tm6000: got start feed request tm6000_start_feed
tm6000: got start stream request tm6000_start_stream
tm6000: pipe reset
tm6000: got start feed request tm6000_start_feed
tm6000: got start feed request tm6000_start_feed
tm6000: got start feed request tm6000_start_feed
tm6000: got start feed request tm6000_start_feed
tm6000: IR URB failure: status: -71, length 0 xhci_hcd 0000:00:14.0: ERROR unknown event type 37 xhci_hcd 0000:00:14.0: ERROR unknown event type 37
tm6000: error tm6000_urb_received
usb 1-2: USB disconnect, device number 5
tm6000: disconnecting tm6000 #0
==================================================================
BUG: KASAN: use-after-free in dvb_fini+0x75/0x140 [tm6000_dvb] Read of size 8 at addr ffff888241044060 by task kworker/2:0/22 CPU: 2 PID: 22 Comm: kworker/2:0 Tainted: G W 5.3.0-rc4+ #1 Hardware name: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET65W (1.40 ) 07/02/2019 Workqueue: usb_hub_wq hub_event Call Trace: dump_stack+0x9a/0xf0 print_address_description.cold+0xae/0x34f __kasan_report.cold+0x75/0x93 ? tm6000_fillbuf+0x390/0x3c0 [tm6000_alsa] ? dvb_fini+0x75/0x140 [tm6000_dvb] kasan_report+0xe/0x12 dvb_fini+0x75/0x140 [tm6000_dvb] tm6000_close_extension+0x51/0x80 [tm6000] tm6000_usb_disconnect.cold+0xd4/0x105 [tm6000] usb_unbind_interface+0xe4/0x390 device_release_driver_internal+0x121/0x250 bus_remove_device+0x197/0x260 device_del+0x268/0x550 ? __device_links_no_driver+0xd0/0xd0 ? usb_remove_ep_devs+0x30/0x3b usb_disable_device+0x122/0x400 usb_disconnect+0x153/0x430 hub_event+0x800/0x1e40 ? trace_hardirqs_on_thunk+0x1a/0x20 ? hub_port_debounce+0x1f0/0x1f0 ? retint_kernel+0x10/0x10 ? lock_is_held_type+0xf1/0x130 ? hub_port_debounce+0x1f0/0x1f0 ? process_one_work+0x4ae/0xa00 process_one_work+0x4ba/0xa00 ? pwq_dec_nr_in_flight+0x160/0x160 ? do_raw_spin_lock+0x10a/0x1d0 worker_thread+0x7a/0x5c0 ? process_one_work+0xa00/0xa00 kthread+0x1d5/0x200 ? kthread_create_worker_on_cpu+0xd0/0xd0 ret_from_fork+0x3a/0x50 Allocated by task 2682: save_stack+0x1b/0x80 __kasan_kmalloc.constprop.0+0xc2/0xd0 usb_alloc_urb+0x28/0x60 tm6000_start_feed+0x10a/0x300 [tm6000_dvb] dmx_ts_feed_start_filtering+0x86/0x120 [dvb_core] dvb_dmxdev_start_feed+0x121/0x180 [dvb_core] dvb_dmxdev_filter_start+0xcb/0x540 [dvb_core] dvb_demux_do_ioctl+0x7ed/0x890 [dvb_core] dvb_usercopy+0x97/0x1f0 [dvb_core] dvb_demux_ioctl+0x11/0x20 [dvb_core] do_vfs_ioctl+0x5d8/0x9d0 ksys_ioctl+0x5e/0x90 __x64_sys_ioctl+0x3d/0x50 do_syscall_64+0x74/0xe0 entry_SYSCALL_64_after_hwframe+0x49/0xbe Freed by task 22: save_stack+0x1b/0x80 __kasan_slab_free+0x12c/0x170 kfree+0xfd/0x3a0 xhci_giveback_urb_in_irq+0xfe/0x230 xhci_td_cleanup+0x276/0x340 xhci_irq+0x1129/0x3720 __handle_irq_event_percpu+0x6e/0x420 handle_irq_event_percpu+0x6f/0x100 handle_irq_event+0x55/0x84 handle_edge_irq+0x108/0x3b0 handle_irq+0x2e/0x40 do_IRQ+0x83/0x1a0
--- drivers/media/usb/tm6000/tm6000-dvb.c | 3 +++ 1 file changed, 3 insertions(+)
drivers/media/usb/tm6000/tm6000-dvb.c +3 -0
@@ -105,6 +105,7 @@ static void tm6000_urb_received(struct uprintk (KERN_ERR "tm6000: error %s\n" , __func__);kfree (urb->transfer_buffer);usb_free_urb (urb); + dev->dvb->bulk_urb =NULL ; } } }
@@ -135,6 +136,7 @@ static int tm6000_start_stream(struct tm dvb->bulk_urb->transfer_buffer =kzalloc (size,GFP_KERNEL );if (!dvb->bulk_urb->transfer_buffer) {usb_free_urb (dvb->bulk_urb); + dvb->bulk_urb =NULL ;return -ENOMEM ; }
@@ -161,6 +163,7 @@ static int tm6000_start_stream(struct tmkfree (dvb->bulk_urb->transfer_buffer);usb_free_urb (dvb->bulk_urb); + dvb->bulk_urb =NULL ;return ret; }
Greg Kroah-Hartman
maintainerPATCH 8/79 phy: renesas: rcar-gen3-usb2: Disable clearing VBUS in over-current
In reply to Greg Kroah-HartmanFrom: Yoshihiro Shimoda <[email protected]>
commit e6839c31a608e79f2057fab987dd814f5d3477e6 upstream.
The hardware manual should be revised, but the initial value of VBCTRL.OCCLREN is set to 1 actually. If the bit is set, the hardware clears VBCTRL.VBOUT and ADPCTRL.DRVVBUS registers automatically when the hardware detects over-current signal from a USB power switch. However, since the hardware doesn't have any registers which indicates over-current, the driver cannot handle it at all. So, if "is_otg_channel" hardware detects over-current, since ADPCTRL.DRVVBUS register is cleared automatically, the channel cannot be used after that.
To resolve this behavior, this patch sets the VBCTRL.OCCLREN to 0 to keep ADPCTRL.DRVVBUS even if the "is_otg_channel" hardware detects over-current. (We assume a USB power switch itself protects over-current and turns the VBUS off.)
This patch is inspired by a BSP patch from Kazuya Mizuguchi.
--- drivers/phy/renesas/phy-rcar-gen3-usb2.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/phy/renesas/phy-rcar-gen3-usb2.c +2 -0
@@ -66,6 +66,7 @@ USB2_OBINT_IDDIGCHG)/* VBCTRL */ +#define USB2_VBCTRL_OCCLREN BIT(16)#define USB2_VBCTRL_DRVVBUSSEL BIT(8)/* LINECTRL1 */
@@ -289,6 +290,7 @@ static void rcar_gen3_init_otg(struct rcu32 val; val =readl (usb2_base +USB2_VBCTRL ); + val &= ~USB2_VBCTRL_OCCLREN ;writel (val |USB2_VBCTRL_DRVVBUSSEL , usb2_base +USB2_VBCTRL );writel (USB2_OBINT_BITS , usb2_base +USB2_OBINTSTA ); val =readl (usb2_base +USB2_OBINTEN );
Greg Kroah-Hartman
maintainerPATCH 9/79 ip6_gre: fix a dst leak in ip6erspan_tunnel_xmit
In reply to Greg Kroah-HartmanFrom: Xin Long <[email protected]>
[ Upstream commit 28e486037747c2180470b77c290d4090ad42f259 ]
In ip6erspan_tunnel_xmit(), if the skb will not be sent out, it has to be freed on the tx_err path. Otherwise when deleting a netns, it would cause dst/dev to leak, and dmesg shows:
unregister_netdevice: waiting for lo to become free. Usage count = 1
--- net/ipv6/ip6_gre.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/ipv6/ip6_gre.c +1 -1
@@ -988,7 +988,7 @@ static netdev_tx_t ip6erspan_tunnel_xmitif (unlikely (!tun_info || !(tun_info->mode &IP_TUNNEL_INFO_TX ) ||ip_tunnel_info_af (tun_info) !=AF_INET6 )) -return -EINVAL ; + goto tx_err; key = &tun_info->key;memset (&fl6,0 ,sizeof (fl6));
Greg Kroah-Hartman
maintainerPATCH 10/79 udp: correct reuseport selection with connected sockets
In reply to Greg Kroah-HartmanFrom: Willem de Bruijn <[email protected]>
[ Upstream commit acdcecc61285faed359f1a3568c32089cc3a8329 ]
UDP reuseport groups can hold a mix unconnected and connected sockets. Ensure that connections only receive all traffic to their 4-tuple.
Fast reuseport returns on the first reuseport match on the assumption that all matches are equal. Only if connections are present, return to the previous behavior of scoring all sockets.
Record if connections are present and if so (1) treat such connected sockets as an independent match from the group, (2) only return 2-tuple matches from reuseport and (3) do not return on the first 2-tuple reuseport match to allow for a higher scoring match later.
New field has_conns is set without locks. No other fields in the bitmap are modified at runtime and the field is only ever set unconditionally, so an RMW cannot miss a change.
--- include/net/sock_reuseport.h | 21 ++++++++++++++++++++- net/core/sock_reuseport.c | 15 +++++++++++++-- net/ipv4/datagram.c | 2 ++ net/ipv4/udp.c | 5 +++-- net/ipv6/datagram.c | 2 ++ net/ipv6/udp.c | 5 +++-- 6 files changed, 43 insertions(+), 7 deletions(-)
include/net/sock_reuseport.h +20 -1
@@ -21,7 +21,8 @@ struct sock_reuseport {unsigned int synq_overflow_ts;/* ID stays the same even after the size of socks[] grows. */ unsigned int reuseport_id; -bool bind_inany; + unsigned int bind_inany:1; + unsigned int has_conns:1;struct bpf_prog __rcu *prog;/* optional BPF sock selector */ struct sock *socks[0 ];/* array of sock pointers */ };
@@ -35,6 +36,24 @@ extern struct sock *reuseport_select_socstruct sk_buff *skb, int hdr_len);extern int reuseport_attach_prog (struct sock *sk,struct bpf_prog *prog); + +static inline bool reuseport_has_conns (struct sock *sk,bool set) +{ +struct sock_reuseport *reuse; +bool ret = false; + +rcu_read_lock (); + reuse =rcu_dereference (sk->sk_reuseport_cb); +if (reuse) { +if (set) + reuse->has_conns =1 ; + ret = reuse->has_conns; + } +rcu_read_unlock (); + +return ret; +} +int reuseport_get_id (struct sock_reuseport *reuse);#endif /* _SOCK_REUSEPORT_H */
net/core/sock_reuseport.c +13 -2
@@ -292,8 +292,19 @@ struct sock *reuseport_select_sock(struc select_by_hash:/* no bpf or invalid bpf result: fall back to hash usage */ -if (!sk2) - sk2 = reuse->socks[reciprocal_scale (hash, socks)]; +if (!sk2) { +int i, j; + + i = j =reciprocal_scale (hash, socks); +while (reuse->socks[i]->sk_state ==TCP_ESTABLISHED ) { + i++; +if (i >= reuse->num_socks) + i =0 ; +if (i == j) + goto out; + } + sk2 = reuse->socks[i]; + } } out:
net/ipv4/datagram.c +2 -0
@@ -19,6 +19,7 @@#include <net/sock.h> #include <net/route.h> #include <net/tcp_states.h> +#include <net/sock_reuseport.h> int __ip4_datagram_connect (struct sock *sk,struct sockaddr *uaddr,int addr_len) {
@@ -73,6 +74,7 @@ int __ip4_datagram_connect(struct sock * } inet->inet_daddr = fl4->daddr; inet->inet_dport = usin->sin_port; +reuseport_has_conns (sk, true); sk->sk_state =TCP_ESTABLISHED ;sk_set_txhash (sk); inet->inet_id = jiffies;
net/ipv4/udp.c +3 -2
@@ -443,12 +443,13 @@ static struct sock *udp4_lib_lookup2(str score =compute_score (sk, net, saddr, sport, daddr, hnum, dif, sdif, exact_dif);if (score > badness) { -if (sk->sk_reuseport) { +if (sk->sk_reuseport && + sk->sk_state !=TCP_ESTABLISHED ) { hash =udp_ehashfn (net, daddr, hnum, saddr, sport); result =reuseport_select_sock (sk, hash, skb,sizeof (struct udphdr )); -if (result) +if (result && !reuseport_has_conns (sk, false))return result; } badness = score;
net/ipv6/datagram.c +2 -0
@@ -31,6 +31,7 @@#include <net/ip6_route.h> #include <net/tcp_states.h> #include <net/dsfield.h> +#include <net/sock_reuseport.h> #include <linux/errqueue.h> #include <linux/uaccess.h>
@@ -258,6 +259,7 @@ ipv4_connected: goto out; } +reuseport_has_conns (sk, true); sk->sk_state =TCP_ESTABLISHED ;sk_set_txhash (sk); out:
net/ipv6/udp.c +3 -2
@@ -177,13 +177,14 @@ static struct sock *udp6_lib_lookup2(str score =compute_score (sk, net, saddr, sport, daddr, hnum, dif, sdif, exact_dif);if (score > badness) { -if (sk->sk_reuseport) { +if (sk->sk_reuseport && + sk->sk_state !=TCP_ESTABLISHED ) { hash =udp6_ehashfn (net, daddr, hnum, saddr, sport); result =reuseport_select_sock (sk, hash, skb,sizeof (struct udphdr )); -if (result) +if (result && !reuseport_has_conns (sk, false))return result; } result = sk;
Re: [PATCH 4.19 10/79] udp: correct reuseport selection with connected sockets
Quoted 11 lines · Greg Kroah-Hartman
From: Willem de Bruijn <[email protected]>
[ Upstream commit
acdcecc61285faed359f1a3568c32089cc3a8329]UDP reuseport groups can hold a mix unconnected and connected sockets. Ensure that connections only receive all traffic to their 4-tuple.
Fast reuseport returns on the first reuseport match on the assumption that all matches are equal. Only if connections are present, return to the previous behavior of scoring all sockets.
Quoted 8 lines
Record if connections are present and if so (1) treat such connected sockets as an independent match from the group, (2) only return 2-tuple matches from reuseport and (3) do not return on the first 2-tuple reuseport match to allow for a higher scoring match later.
New field
has_connsis set without locks. No other fields in the bitmap are modified at runtime and the field is only ever set unconditionally, so an RMW cannot miss a change.
That's an ... extremely tricky game with concurrent access. I'm pretty sure it is not valid C, but maybe it is acceptable for kernel.
include/net/sock_reuseport.h struct sock_reuseport { · line 25
Quoted 9 lines
include/net/sock_reuseport.h +2
-1@@ -21,7 +21,8 @@ struct sock_reuseport {unsigned int synq_overflow_ts;/* ID stays the same even after the size of socks[] grows. */ unsigned int reuseport_id; -bool bind_inany; + unsigned int bind_inany:1; + unsigned int has_conns:1;
But should it at least be commented here? If someone adds another int :1, he may get a surprise...
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Greg Kroah-Hartman
maintainerPATCH 11/79 xen-netfront: do not assume sk_buff_head list is empty in error handling
In reply to Greg Kroah-HartmanFrom: Dongli Zhang <[email protected]>
[ Upstream commit 00b368502d18f790ab715e055869fd4bb7484a9b ]
When skb_shinfo(skb) is not able to cache extra fragment (that is, skb_shinfo(skb)->nr_frags >= MAX_SKB_FRAGS), xennet_fill_frags() assumes the sk_buff_head list is already empty. As a result, cons is increased only by 1 and returns to error handling path in xennet_poll().
However, if the sk_buff_head list is not empty, queue->rx.rsp_cons may be set incorrectly. That is, queue->rx.rsp_cons would point to the rx ring buffer entries whose queue->rx_skbs[i] and queue->grant_rx_ref[i] are already cleared to NULL. This leads to NULL pointer access in the next iteration to process rx ring buffer entries.
Below is how xennet_poll() does error handling. All remaining entries in tmpq are accounted to queue->rx.rsp_cons without assuming how many outstanding skbs are remained in the list.
985 static int xennet_poll(struct napi_struct *napi, int budget)
... ...
1032 if (unlikely(xennet_set_skb_gso(skb, gso))) {
1033 __skb_queue_head(&tmpq, skb); 1034 queue->rx.rsp_cons += skb_queue_len(&tmpq); 1035 goto err;
1036 }
It is better to always have the error handling in the same way.
--- drivers/net/xen-netfront.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/xen-netfront.c +1 -1
@@ -909,7 +909,7 @@ static RING_IDX xennet_fill_frags(struct__pskb_pull_tail (skb, pull_to -skb_headlen (skb)); }if (unlikely (skb_shinfo (skb)->nr_frags >=MAX_SKB_FRAGS )) { - queue->rx.rsp_cons = ++cons; + queue->rx.rsp_cons = ++cons +skb_queue_len (list);kfree_skb (nskb);return ~0U ; }
Greg Kroah-Hartman
maintainerPATCH 12/79 net_sched: let qdisc_put() accept NULL pointer
In reply to Greg Kroah-HartmanFrom: Cong Wang <[email protected]>
[ Upstream commit 6efb971ba8edfbd80b666f29de12882852f095ae ]
When tcf_block_get() fails in sfb_init(), q->qdisc is still a NULL pointer which leads to a crash in sfb_destroy(). Similar for sch_dsmark.
Instead of fixing each separately, Linus suggested to just accept NULL pointer in qdisc_put(), which would make callers easier.
(For sch_dsmark, the bug probably exists long before commit 6529eaba33f0.)
--- net/sched/sch_generic.c | 3 +++ 1 file changed, 3 insertions(+)
net/sched/sch_generic.c +3 -0
@@ -950,6 +950,9 @@ void qdisc_destroy(struct Qdisc *qdisc)const struct Qdisc_ops *ops = qdisc->ops;struct sk_buff *skb, *tmp; +if (!qdisc) +return ; +if (qdisc->flags &TCQ_F_BUILTIN || !refcount_dec_and_test (&qdisc->refcnt))return ;
Greg Kroah-Hartman
maintainerPATCH 13/79 KVM: coalesced_mmio: add bounds checking
In reply to Greg Kroah-HartmanFrom: Matt Delco <[email protected]>
commit b60fe990c6b07ef6d4df67bc0530c7c90a62623a upstream.
The first/last indexes are typically shared with a user app. The app can change the 'last' index that the kernel uses to store the next result. This change sanity checks the index before using it for writing to a potentially arbitrary address.
This fixes CVE-2019-14821.
--- virt/kvm/coalesced_mmio.c | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-)
virt/kvm/coalesced_mmio.c +10 -7
@@ -40,7 +40,7 @@ static int coalesced_mmio_in_range(strucreturn 1 ; } -static int coalesced_mmio_has_room (struct kvm_coalesced_mmio_dev *dev) +static int coalesced_mmio_has_room (struct kvm_coalesced_mmio_dev *dev,u32 last) {struct kvm_coalesced_mmio_ring *ring;unsigned avail;
@@ -52,7 +52,7 @@ static int coalesced_mmio_has_room(struc* there is always one unused entry in the buffer */ ring = dev->kvm->coalesced_mmio_ring; - avail = (ring->first - ring->last -1 ) %KVM_COALESCED_MMIO_MAX ; + avail = (ring->first - last -1 ) %KVM_COALESCED_MMIO_MAX ;if (avail ==0 ) {/* full */ return 0 ;
@@ -67,24 +67,27 @@ static int coalesced_mmio_write(struct k {struct kvm_coalesced_mmio_dev *dev =to_mmio (this);struct kvm_coalesced_mmio_ring *ring = dev->kvm->coalesced_mmio_ring; +__u32 insert;if (!coalesced_mmio_in_range (dev, addr, len))return -EOPNOTSUPP ;spin_lock (&dev->kvm->ring_lock); -if (!coalesced_mmio_has_room (dev)) { + insert =READ_ONCE (ring->last); +if (!coalesced_mmio_has_room (dev, insert) || + insert >=KVM_COALESCED_MMIO_MAX ) {spin_unlock (&dev->kvm->ring_lock);return -EOPNOTSUPP ; }/* copy data in first free entry of the ring */ - ring->coalesced_mmio[ring->last].phys_addr = addr; - ring->coalesced_mmio[ring->last].len = len; -memcpy (ring->coalesced_mmio[ring->last].data, val, len); + ring->coalesced_mmio[insert].phys_addr = addr; + ring->coalesced_mmio[insert].len = len; +memcpy (ring->coalesced_mmio[insert].data, val, len);smp_wmb (); - ring->last = (ring->last +1 ) %KVM_COALESCED_MMIO_MAX ; + ring->last = (insert +1 ) %KVM_COALESCED_MMIO_MAX ;spin_unlock (&dev->kvm->ring_lock);return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 14/79 firmware: google: check if size is valid when decoding VPD data
In reply to Greg Kroah-HartmanFrom: Hung-Te Lin <[email protected]>
commit 4b708b7b1a2c09fbdfff6b942ebe3a160213aacd upstream.
The VPD implementation from Chromium Vital Product Data project used to parse data from untrusted input without checking if the meta data is invalid or corrupted. For example, the size from decoded content may be negative value, or larger than whole input buffer. Such invalid data may cause buffer overflow.
To fix that, the size parameters passed to vpd_decode functions should be changed to unsigned integer (u32) type, and the parsing of entry header should be refactored so every size field is correctly verified before starting to decode.
--- drivers/firmware/google/vpd.c | 4 +- drivers/firmware/google/vpd_decode.c | 55 ++++++++++++++++++++--------------- drivers/firmware/google/vpd_decode.h | 6 +-- 3 files changed, 37 insertions(+), 28 deletions(-)
drivers/firmware/google/vpd.c +2 -2
@@ -100,8 +100,8 @@ static int vpd_section_check_key_name(coreturn VPD_OK ; } -static int vpd_section_attrib_add (const u8 *key,s32 key_len, -const u8 *value,s32 value_len, +static int vpd_section_attrib_add (const u8 *key,u32 key_len, +const u8 *value,u32 value_len,void *arg) {int ret;
drivers/firmware/google/vpd_decode.c +32 -23
84 lines not on this page · raw message
drivers/firmware/google/vpd_decode.h +3 -3
@@ -33,8 +33,8 @@ enum { };/* Callback for vpd_decode_string to invoke. */ -typedef int vpd_decode_callback (const u8 *key,s32 key_len, -const u8 *value,s32 value_len, +typedef int vpd_decode_callback (const u8 *key,u32 key_len, +const u8 *value,u32 value_len,void *arg);/*
@@ -52,7 +52,7 @@ typedef int vpd_decode_callback(const u8* If one entry is successfully decoded, sends it to callback and returns the * result. */ -int vpd_decode_string (const s32 max_len,const u8 *input_buf,s32 *consumed, +int vpd_decode_string (const u32 max_len,const u8 *input_buf,u32 *consumed,vpd_decode_callback callback,void *callback_arg);#endif /* __VPD_DECODE_H */
Greg Kroah-Hartman
maintainerPATCH 15/79 serial: sprd: correct the wrong sequence of arguments
In reply to Greg Kroah-HartmanFrom: Chunyan Zhang <[email protected]>
commit 9c801e313195addaf11c16e155f50789d6ebfd19 upstream.
The sequence of arguments which was passed to handle_lsr_errors() didn't match the parameters defined in that function, &lsr was passed to flag and &flag was passed to lsr, this patch fixed that.
--- drivers/tty/serial/sprd_serial.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/tty/serial/sprd_serial.c +1 -1
@@ -232,7 +232,7 @@ static inline void sprd_rx(struct uart_pif (lsr & (SPRD_LSR_BI |SPRD_LSR_PE |SPRD_LSR_FE |SPRD_LSR_OE )) -if (handle_lsr_errors (port, &lsr, &flag)) +if (handle_lsr_errors (port, &flag, &lsr))continue ;if (uart_handle_sysrq_char (port, ch))continue ;
Greg Kroah-Hartman
maintainerPATCH 16/79 tty/serial: atmel: reschedule TX after RX was started
In reply to Greg Kroah-HartmanFrom: Razvan Stefanescu <[email protected]>
commit d2ace81bf902a9f11d52e59e5d232d2255a0e353 upstream.
When half-duplex RS485 communication is used, after RX is started, TX tasklet still needs to be scheduled tasklet. This avoids console freezing when more data is to be transmitted, if the serial communication is not closed.
--- drivers/tty/serial/atmel_serial.c | 1 - 1 file changed, 1 deletion(-)
drivers/tty/serial/atmel_serial.c +0 -1
@@ -1270,7 +1270,6 @@ atmel_handle_transmit(struct uart_port * atmel_port->hd_start_rx = false;atmel_start_rx (port); -return ; }atmel_tasklet_schedule (atmel_port, &atmel_port->tasklet_tx);
Greg Kroah-Hartman
maintainerPATCH 17/79 mwifiex: Fix three heap overflow at parsing element in cfg80211_ap_settings
In reply to Greg Kroah-HartmanFrom: Wen Huang <[email protected]>
commit 7caac62ed598a196d6ddf8d9c121e12e082cac3a upstream.
mwifiex_update_vs_ie(),mwifiex_set_uap_rates() and mwifiex_set_wmm_params() call memcpy() without checking the destination size.Since the source is given from user-space, this may trigger a heap buffer overflow.
Fix them by putting the length check before performing memcpy().
This fix addresses CVE-2019-14814,CVE-2019-14815,CVE-2019-14816.
--- drivers/net/wireless/marvell/mwifiex/ie.c | 3 +++ drivers/net/wireless/marvell/mwifiex/uap_cmd.c | 9 ++++++++- 2 files changed, 11 insertions(+), 1 deletion(-)
drivers/net/wireless/marvell/mwifiex/ie.c +3 -0
@@ -241,6 +241,9 @@ static int mwifiex_update_vs_ie(const u8 } vs_ie = (struct ieee_types_header *)vendor_ie; +if (le16_to_cpu (ie->ie_length) + vs_ie->len +2 > +IEEE_MAX_IE_SIZE ) +return -EINVAL ;memcpy (ie->ie_buffer +le16_to_cpu (ie->ie_length), vs_ie, vs_ie->len +2 );le16_unaligned_add_cpu (&ie->ie_length, vs_ie->len +2 );
drivers/net/wireless/marvell/mwifiex/uap_cmd.c +8 -1
@@ -265,6 +265,8 @@ mwifiex_set_uap_rates(struct mwifiex_uap rate_ie = (void *)cfg80211_find_ie (WLAN_EID_SUPP_RATES , var_pos, len);if (rate_ie) { +if (rate_ie->len >MWIFIEX_SUPPORTED_RATES ) +return ;memcpy (bss_cfg->rates, rate_ie +1 , rate_ie->len); rate_len = rate_ie->len; }
@@ -272,8 +274,11 @@ mwifiex_set_uap_rates(struct mwifiex_uap rate_ie = (void *)cfg80211_find_ie (WLAN_EID_EXT_SUPP_RATES , params->beacon.tail, params->beacon.tail_len); -if (rate_ie) +if (rate_ie) { +if (rate_ie->len >MWIFIEX_SUPPORTED_RATES - rate_len) +return ;memcpy (bss_cfg->rates + rate_len, rate_ie +1 , rate_ie->len); + }return ; }
@@ -391,6 +396,8 @@ mwifiex_set_wmm_params(struct mwifiex_pr params->beacon.tail_len);if (vendor_ie) { wmm_ie = vendor_ie; +if (*(wmm_ie +1 ) >sizeof (struct mwifiex_types_wmm_info )) +return ;memcpy (&bss_cfg->wmm_info, wmm_ie +sizeof (struct ieee_types_header ), *(wmm_ie +1 )); priv->wmm_enabled =1 ;
Greg Kroah-Hartman
maintainerPATCH 18/79 nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds
In reply to Greg Kroah-HartmanFrom: Masashi Honma <[email protected]>
commit 4b2c5a14cd8005a900075f7dfec87473c6ee66fb upstream.
commit 1222a1601488 ("nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds") was incomplete and requires one more fix to prevent accessing to rssi_thresholds[n] because user can control rssi_thresholds[i] values to make i reach to n. For example, rssi_thresholds = {-400, -300, -200, -100} when last is -34.
--- net/wireless/nl80211.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/wireless/nl80211.c +3 -1
@@ -10270,9 +10270,11 @@ static int cfg80211_cqm_rssi_update(stru hyst = wdev->cqm_config->rssi_hyst; n = wdev->cqm_config->n_rssi_thresholds; -for (i =0 ; i < n; i++) +for (i =0 ; i < n; i++) { + i =array_index_nospec (i, n);if (last < wdev->cqm_config->rssi_thresholds[i])break ; + } low_index = i -1 ;if (low_index >=0 ) {
Re: [PATCH 4.19 18/79] nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds
Hi!
Quoted 9 lines
commit
4b2c5a14cd8005a900075f7dfec87473c6ee66fbupstream.commit
1222a1601488("nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds") was incomplete and requires one more fix to prevent accessing to rssi_thresholds[n] because user can control rssi_thresholds[i] values to make i reach to n. For example,rssi_thresholds= {-400, -300, -200, -100} when last is -34.
net/wireless/nl80211.c static int cfg80211_cqm_rssi_update(stru · line 10278
Quoted 10 lines
net/wireless/nl80211.c +3
-1@@ -10270,9 +10270,11 @@ static int cfg80211_cqm_rssi_update(stru hyst = wdev->cqm_config->rssi_hyst; n = wdev->cqm_config->n_rssi_thresholds; -for (i =0 ; i < n; i++) +for (i =0 ; i < n; i++) { + i =array_index_nospec (i, n);if (last < wdev->cqm_config->rssi_thresholds[i])break ; + }
Variable "i" is not controlled by userspace: it is initialized by kernel and runs from 0 to n.
I don't see a spectre vulnerability here.
[In fact, other array_index_nospec() uses in this function seem also unneccessary.]
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Greg Kroah-Hartman
maintainerPATCH 19/79 ieee802154: hwsim: Fix error handle path in hwsim_init_module
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
[ Upstream commit 1cbbbf39efab05fae67f59e6ed01bb85061c69e2 ]
KASAN report this:
BUG: unable to handle kernel paging request at fffffbfff834f001 PGD 237fe8067 P4D 237fe8067 PUD 237e64067 PMD 1c968d067 PTE 0 Oops: 0000 [#1] SMP KASAN PTI CPU: 1 PID: 8871 Comm: syz-executor.0 Tainted: G C 5.0.0+ #5 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.10.2-1ubuntu1 04/01/2014 RIP: 0010:strcmp+0x31/0xa0 lib/string.c:328 Code: 00 00 00 00 fc ff df 55 53 48 83 ec 08 eb 0a 84 db 48 89 ef 74 5a 4c 89 e6 48 89 f8 48 89 fa 48 8d 6f 01 48 c1 e8 03 83 e2 07 <42> 0f b6 04 28 38 d0 7f 04 84 c0 75 50 48 89 f0 48 89 f2 0f b6 5d RSP: 0018:ffff8881e0c57800 EFLAGS: 00010246 RAX: 1ffffffff834f001 RBX: ffffffffc1a78000 RCX: ffffffff827b9503 RDX: 0000000000000000 RSI: ffffffffc1a40008 RDI: ffffffffc1a78008 RBP: ffffffffc1a78009 R08: fffffbfff6a92195 R09: fffffbfff6a92195 R10: ffff8881e0c578b8 R11: fffffbfff6a92194 R12: ffffffffc1a40008 R13: dffffc0000000000 R14: ffffffffc1a3e470 R15: ffffffffc1a40000 FS: 00007fdcc02ff700(0000) GS:ffff8881f7300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff834f001 CR3: 00000001b3134003 CR4: 00000000007606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: genl_family_find_byname+0x7f/0xf0 net/netlink/genetlink.c:104 genl_register_family+0x1e1/0x1070 net/netlink/genetlink.c:333 ? 0xffffffffc1978000 hwsim_init_module+0x6a/0x1000 [mac802154_hwsim] ? 0xffffffffc1978000 ? 0xffffffffc1978000 ? 0xffffffffc1978000 do_one_initcall+0xbc/0x47d init/main.c:887 do_init_module+0x1b5/0x547 kernel/module.c:3456 load_module+0x6405/0x8c10 kernel/module.c:3804 __do_sys_finit_module+0x162/0x190 kernel/module.c:3898 do_syscall_64+0x9f/0x450 arch/x86/entry/common.c:290 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x462e99 Code: f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007fdcc02fec58 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 000000000073bf00 RCX: 0000000000462e99 RDX: 0000000000000000 RSI: 0000000020000200 RDI: 0000000000000003 RBP: 00007fdcc02fec70 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fdcc02ff6bc R13: 00000000004bcefa R14: 00000000006f6fb0 R15: 0000000000000004 Modules linked in: mac802154_hwsim(+) mac802154 ieee802154 speakup(C) rc_proteus_2309 rtc_rk808 streebog_generic rds vboxguest madera_spi madera da9052_wdt mISDN_core ueagle_atm usbatm atm ir_imon_decoder scsi_transport_sas rc_dntv_live_dvb_t panel_samsung_s6d16d0 drm drm_panel_orientation_quirks lib80211 fb_agm1264k_fl(C) gspca_pac7302 gspca_main videobuf2_v4l2 soundwire_intel_init i2c_dln2 dln2 usbcore hid_gaff 88pm8607 nfnetlink axp20x_i2c axp20x uio pata_marvell pmbus_core snd_sonicvibes gameport snd_pcm snd_opl3_lib snd_timer snd_hwdep snd_mpu401_uart snd_rawmidi snd_seq_device snd soundcore rtc_ds1511 rtc_ds1742 vsock dwc_xlgmac rtc_rx8010 libphy twofish_x86_64_3way twofish_x86_64 twofish_common ad5696_i2c ad5686 lp8788_charger cxd2880_spi dvb_core videobuf2_common videodev media videobuf2_vmalloc videobuf2_memops fbtft(C) sysimgblt sysfillrect syscopyarea fb_sys_fops janz_ican3 firewire_net firewire_core crc_itu_t spi_slave_system_control i2c_matroxfb i2c_algo_bit matroxfb_base fb fbdev matroxfb_DAC1064 matroxfb_accel cfbcopyarea cfbimgblt cfbfillrect matroxfb_Ti3026 matroxfb_g450 g450_pll matroxfb_misc leds_blinkm ti_dac7311 intel_spi_pci intel_spi spi_nor hid_elan hid async_tx rc_cinergy_1400 rc_core intel_ishtp kxcjk_1013 industrialio_triggered_buffer kfifo_buf can_dev intel_th spi_pxa2xx_platform pata_artop vme_ca91cx42 gb_gbphy(C) greybus(C) industrialio mptbase st_drv cmac ttpci_eeprom via_wdt gpio_xra1403 mtd iptable_security iptable_raw iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter ip6_vti ip_vti ip_gre ipip sit tunnel4 ip_tunnel hsr veth netdevsim vxcan batman_adv cfg80211 rfkill chnl_net caif nlmon dummy team bonding vcan bridge stp llc ip6_gre gre ip6_tunnel tunnel6 tun joydev mousedev ppdev kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 input_leds crypto_simd cryptd glue_helper ide_pci_generic piix psmouse ide_core serio_raw ata_generic i2c_piix4 pata_acpi parport_pc parport floppy rtc_cmos intel_agp intel_gtt agpgart sch_fq_codel ip_tables x_tables sha1_ssse3 sha1_generic ipv6 [last unloaded: speakup] Dumping ftrace buffer: (ftrace buffer empty) CR2: fffffbfff834f001 ---[ end trace 5aa772c793e0e971 ]--- RIP: 0010:strcmp+0x31/0xa0 lib/string.c:328 Code: 00 00 00 00 fc ff df 55 53 48 83 ec 08 eb 0a 84 db 48 89 ef 74 5a 4c 89 e6 48 89 f8 48 89 fa 48 8d 6f 01 48 c1 e8 03 83 e2 07 <42> 0f b6 04 28 38 d0 7f 04 84 c0 75 50 48 89 f0 48 89 f2 0f b6 5d RSP: 0018:ffff8881e0c57800 EFLAGS: 00010246 RAX: 1ffffffff834f001 RBX: ffffffffc1a78000 RCX: ffffffff827b9503 RDX: 0000000000000000 RSI: ffffffffc1a40008 RDI: ffffffffc1a78008 RBP: ffffffffc1a78009 R08: fffffbfff6a92195 R09: fffffbfff6a92195 R10: ffff8881e0c578b8 R11: fffffbfff6a92194 R12: ffffffffc1a40008 R13: dffffc0000000000 R14: ffffffffc1a3e470 R15: ffffffffc1a40000 FS: 00007fdcc02ff700(0000) GS:ffff8881f7300000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: fffffbfff834f001 CR3: 00000001b3134003 CR4: 00000000007606e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
PKRU: 55555554
The error handing path misplace the cleanup in hwsim_init_module, switch the two cleanup functions to fix above issues.
--- drivers/net/ieee802154/mac802154_hwsim.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/net/ieee802154/mac802154_hwsim.c +2 -2
@@ -920,9 +920,9 @@ static __init int hwsim_init_module(void)return 0 ; platform_drv: -genl_unregister_family (&hwsim_genl_family); -platform_dev:platform_device_unregister (mac802154hwsim_dev); +platform_dev: +genl_unregister_family (&hwsim_genl_family);return rc; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 20/79 ieee802154: hwsim: unregister hw while hwsim_subscribe_all_others fails
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
[ Upstream commit de166bbe861738c8bc3e5dad5b03f45d7d6ef914 ]
KASAN report this:
kernel BUG at net/mac802154/main.c:130!
invalid opcode: 0000 [#1] PREEMPT SMP
CPU: 0 PID: 19932 Comm: modprobe Not tainted 5.1.0-rc6+ #22 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014 RIP: 0010:ieee802154_free_hw+0x2a/0x30 [mac802154] Code: 55 48 8d 57 38 48 89 e5 53 48 89 fb 48 8b 47 38 48 39 c2 75 15 48 8d 7f 48 e8 82 85 16 e1 48 8b 7b 28 e8 f9 ef 83 e2 5b 5d c3 <0f> 0b 0f 1f 40 00 55 48 89 e5 53 48 89 fb 0f b6 86 80 00 00 00 88 RSP: 0018:ffffc90001c7b9f0 EFLAGS: 00010206 RAX: ffff88822df3aa80 RBX: ffff88823143d5c0 RCX: 0000000000000002 RDX: ffff88823143d5f8 RSI: ffff88822b1fabc0 RDI: ffff88823143d5c0 RBP: ffffc90001c7b9f8 R08: 0000000000000000 R09: 0000000000000001 R10: 0000000000000000 R11: 0000000000000000 R12: 00000000fffffff4 R13: ffff88822dea4f50 R14: ffff88823143d7c0 R15: 00000000fffffff4 FS: 00007ff52e999540(0000) GS:ffff888237a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fdc06dba768 CR3: 000000023160a000 CR4: 00000000000006f0 Call Trace: hwsim_add_one+0x2dd/0x540 [mac802154_hwsim] hwsim_probe+0x2f/0xb0 [mac802154_hwsim] platform_drv_probe+0x3a/0x90 ? driver_sysfs_add+0x79/0xb0 really_probe+0x1d4/0x2d0 driver_probe_device+0x50/0xf0 device_driver_attach+0x54/0x60 __driver_attach+0x7e/0xd0 ? device_driver_attach+0x60/0x60 bus_for_each_dev+0x68/0xc0 driver_attach+0x19/0x20 bus_add_driver+0x15e/0x200 driver_register+0x5b/0xf0 __platform_driver_register+0x31/0x40 hwsim_init_module+0x74/0x1000 [mac802154_hwsim] ? 0xffffffffa00e9000 do_one_initcall+0x6c/0x3cc ? kmem_cache_alloc_trace+0x248/0x3b0 do_init_module+0x5b/0x1f1 load_module+0x1db1/0x2690 ? m_show+0x1d0/0x1d0 __do_sys_finit_module+0xc5/0xd0 __x64_sys_finit_module+0x15/0x20 do_syscall_64+0x6b/0x1d0 entry_SYSCALL_64_after_hwframe+0x49/0xbe RIP: 0033:0x7ff52e4a2839 Code: 00 f3 c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 1f f6 2c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffffa7b3c08 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 00005647560a2a00 RCX: 00007ff52e4a2839 RDX: 0000000000000000 RSI: 00005647547f3c2e RDI: 0000000000000003 RBP: 00005647547f3c2e R08: 0000000000000000 R09: 00005647560a2a00 R10: 0000000000000003 R11: 0000000000000246 R12: 0000000000000000 R13: 00005647560a2c10 R14: 0000000000040000 R15: 00005647560a2a00 Modules linked in: mac802154_hwsim(+) mac802154 [last unloaded: mac802154_hwsim]
In hwsim_add_one, if hwsim_subscribe_all_others fails, we should call ieee802154_unregister_hw to free resources.
--- drivers/net/ieee802154/mac802154_hwsim.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/net/ieee802154/mac802154_hwsim.c +3 -1
@@ -821,7 +821,7 @@ static int hwsim_add_one(struct genl_info *info, struct device *dev, err =hwsim_subscribe_all_others (phy);if (err <0 ) {mutex_unlock (&hwsim_phys_lock); - goto err_reg; + goto err_subscribe; } }list_add_tail (&phy->list, &hwsim_phys);
@@ -831,6 +831,8 @@ static int hwsim_add_one(struct genl_info *info, struct device *dev,return idx; +err_subscribe: +ieee802154_unregister_hw (phy->hw); err_reg:kfree (pib); err_pib:
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 21/79 ARM: dts: am57xx: Disable voltage switching for SD card
In reply to Greg Kroah-HartmanFrom: Faiz Abbas <[email protected]>
[ Upstream commit fb59ee37cfe20d10d19568899d1458a58361246c ]
If UHS speed modes are enabled, a compatible SD card switches down to 1.8V during enumeration. If after this a software reboot/crash takes place and on-chip ROM tries to enumerate the SD card, the difference in IO voltages (host @ 3.3V and card @ 1.8V) may end up damaging the card.
The fix for this is to have support for power cycling the card in hardware (with a PORz/soft-reset line causing a power cycle of the card). Because the beaglebone X15 (rev A,B and C), am57xx-idks and am57xx-evms don't have this capability, disable voltage switching for these boards.
The major effect of this is that the maximum supported speed mode is now high speed(50 MHz) down from SDR104(200 MHz).
commit 88a748419b84 ("ARM: dts: am57xx-idk: Remove support for voltage switching for SD card") did this only for idk boards. Do it for all affected boards.
--- arch/arm/boot/dts/am571x-idk.dts | 7 +------ arch/arm/boot/dts/am572x-idk.dts | 7 +------ arch/arm/boot/dts/am574x-idk.dts | 7 +------ arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi | 1 + arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts | 7 +------ arch/arm/boot/dts/am57xx-beagle-x15-revc.dts | 7 +------ 6 files changed, 6 insertions(+), 30 deletions(-)
arch/arm/boot/dts/am571x-idk.dts +1 -6
@@ -98,14 +98,9 @@ }; &mmc1 { - pinctrl-names = "default", "hs", "sdr12", "sdr25", "sdr50", "ddr50", "sdr104"; + pinctrl-names = "default", "hs"; pinctrl-0 = <&mmc1_pins_default_no_clk_pu>; pinctrl-1 = <&mmc1_pins_hs>; - pinctrl-2 = <&mmc1_pins_sdr12>; - pinctrl-3 = <&mmc1_pins_sdr25>; - pinctrl-4 = <&mmc1_pins_sdr50>; - pinctrl-5 = <&mmc1_pins_ddr50_rev20 &mmc1_iodelay_ddr50_conf>; - pinctrl-6 = <&mmc1_pins_sdr104 &mmc1_iodelay_sdr104_rev20_conf>; }; &mmc2 {
arch/arm/boot/dts/am572x-idk.dts +1 -6
@@ -20,14 +20,9 @@ }; &mmc1 { - pinctrl-names = "default", "hs", "sdr12", "sdr25", "sdr50", "ddr50", "sdr104"; + pinctrl-names = "default", "hs"; pinctrl-0 = <&mmc1_pins_default_no_clk_pu>; pinctrl-1 = <&mmc1_pins_hs>; - pinctrl-2 = <&mmc1_pins_sdr12>; - pinctrl-3 = <&mmc1_pins_sdr25>; - pinctrl-4 = <&mmc1_pins_sdr50>; - pinctrl-5 = <&mmc1_pins_ddr50 &mmc1_iodelay_ddr_rev20_conf>; - pinctrl-6 = <&mmc1_pins_sdr104 &mmc1_iodelay_sdr104_rev20_conf>; }; &mmc2 {
arch/arm/boot/dts/am574x-idk.dts +1 -6
@@ -24,14 +24,9 @@ }; &mmc1 { - pinctrl-names = "default", "hs", "sdr12", "sdr25", "sdr50", "ddr50", "sdr104"; + pinctrl-names = "default", "hs"; pinctrl-0 = <&mmc1_pins_default_no_clk_pu>; pinctrl-1 = <&mmc1_pins_hs>; - pinctrl-2 = <&mmc1_pins_default>; - pinctrl-3 = <&mmc1_pins_hs>; - pinctrl-4 = <&mmc1_pins_sdr50>; - pinctrl-5 = <&mmc1_pins_ddr50 &mmc1_iodelay_ddr_conf>; - pinctrl-6 = <&mmc1_pins_ddr50 &mmc1_iodelay_sdr104_conf>; }; &mmc2 {
arch/arm/boot/dts/am57xx-beagle-x15-common.dtsi +1 -0
@@ -433,6 +433,7 @@ bus-width = <4>; cd-gpios = <&gpio6 27 GPIO_ACTIVE_LOW>; /* gpio 219 */ + no-1-8-v; }; &mmc2 {
arch/arm/boot/dts/am57xx-beagle-x15-revb1.dts +1 -6
@@ -19,14 +19,9 @@ }; &mmc1 { - pinctrl-names = "default", "hs", "sdr12", "sdr25", "sdr50", "ddr50", "sdr104"; + pinctrl-names = "default", "hs"; pinctrl-0 = <&mmc1_pins_default>; pinctrl-1 = <&mmc1_pins_hs>; - pinctrl-2 = <&mmc1_pins_sdr12>; - pinctrl-3 = <&mmc1_pins_sdr25>; - pinctrl-4 = <&mmc1_pins_sdr50>; - pinctrl-5 = <&mmc1_pins_ddr50 &mmc1_iodelay_ddr_rev11_conf>; - pinctrl-6 = <&mmc1_pins_sdr104 &mmc1_iodelay_sdr104_rev11_conf>; vmmc-supply = <&vdd_3v3>; vqmmc-supply = <&ldo1_reg>; };
arch/arm/boot/dts/am57xx-beagle-x15-revc.dts +1 -6
@@ -19,14 +19,9 @@ }; &mmc1 { - pinctrl-names = "default", "hs", "sdr12", "sdr25", "sdr50", "ddr50", "sdr104"; + pinctrl-names = "default", "hs"; pinctrl-0 = <&mmc1_pins_default>; pinctrl-1 = <&mmc1_pins_hs>; - pinctrl-2 = <&mmc1_pins_sdr12>; - pinctrl-3 = <&mmc1_pins_sdr25>; - pinctrl-4 = <&mmc1_pins_sdr50>; - pinctrl-5 = <&mmc1_pins_ddr50 &mmc1_iodelay_ddr_rev20_conf>; - pinctrl-6 = <&mmc1_pins_sdr104 &mmc1_iodelay_sdr104_rev20_conf>; vmmc-supply = <&vdd_3v3>; vqmmc-supply = <&ldo1_reg>; };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 22/79 ARM: OMAP2+: Fix missing SYSC_HAS_RESET_STATUS for dra7 epwmss
In reply to Greg Kroah-HartmanFrom: Tony Lindgren <[email protected]>
[ Upstream commit afd58b162e48076e3fe66d08a69eefbd6fe71643 ]
TRM says PWMSS_SYSCONFIG bit for SOFTRESET changes to zero when reset is completed. Let's configure it as otherwise we get warnings on boot when we check the data against dts provided data. Eventually the legacy platform data will be just dropped, but let's fix the warning first.
--- arch/arm/mach-omap2/omap_hwmod_7xx_data.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/arm/mach-omap2/omap_hwmod_7xx_data.c +2 -1
@@ -385,7 +385,8 @@ static struct omap_hwmod dra7xx_dcan2_hwmod = {static struct omap_hwmod_class_sysconfig dra7xx_epwmss_sysc = { .rev_offs =0x0 , .sysc_offs =0x4 , - .sysc_flags =SYSC_HAS_SIDLEMODE |SYSC_HAS_SOFTRESET , + .sysc_flags =SYSC_HAS_SIDLEMODE |SYSC_HAS_SOFTRESET | +SYSC_HAS_RESET_STATUS , .idlemodes = (SIDLE_FORCE |SIDLE_NO |SIDLE_SMART ), .sysc_fields = &omap_hwmod_sysc_type2, };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 23/79 bus: ti-sysc: Fix using configured sysc mask value
In reply to Greg Kroah-HartmanFrom: Tony Lindgren <[email protected]>
[ Upstream commit e212abd452a4af3174fcd469d46656f83e135a19 ]
We have cases where there are no softreset bits like with am335x lcdc. In that case ti,sysc-mask = <0> needs to be handled properly.
--- drivers/bus/ti-sysc.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-)
drivers/bus/ti-sysc.c +1 -4
@@ -1022,10 +1022,7 @@ static int sysc_init_sysc_mask(struct sysc *ddata)if (error)return 0 ; -if (val) - ddata->cfg.sysc_val = val & ddata->cap->sysc_mask; -else - ddata->cfg.sysc_val = ddata->cap->sysc_mask; + ddata->cfg.sysc_val = val & ddata->cap->sysc_mask;return 0 ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 24/79 s390/bpf: fix lcgr instruction encoding
In reply to Greg Kroah-HartmanFrom: Ilya Leoshkevich <[email protected]>
[ Upstream commit bb2d267c448f4bc3a3389d97c56391cb779178ae ]
"masking, test in bounds 3" fails on s390, because BPF_ALU64_IMM(BPF_NEG, BPF_REG_2, 0) ignores the top 32 bits of BPF_REG_2. The reason is that JIT emits lcgfr instead of lcgr. The associated comment indicates that the code was intended to emit lcgr in the first place, it's just that the wrong opcode was used.
Fix by using the correct opcode.
--- arch/s390/net/bpf_jit_comp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/s390/net/bpf_jit_comp.c +1 -1
@@ -841,7 +841,7 @@ static noinline int bpf_jit_insn(struct bpf_jit *jit, struct bpf_prog *fp, int ibreak ;case BPF_ALU64 |BPF_NEG :/* dst = -dst */ /* lcgr %dst,%dst */ -EMIT4 (0xb9130000 , dst_reg, dst_reg); +EMIT4 (0xb9030000 , dst_reg, dst_reg);break ;/* * BPF_FROM_BE/LE
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 25/79 ARM: OMAP2+: Fix omap4 errata warning on other SoCs
In reply to Greg Kroah-HartmanFrom: Tony Lindgren <[email protected]>
[ Upstream commit 45da5e09dd32fa98c32eaafe2513db6bd75e2f4f ]
We have errata i688 workaround produce warnings on SoCs other than omap4 and omap5:
omap4_sram_init:Unable to allocate sram needed to handle errata I688 omap4_sram_init:Unable to get sram pool needed to handle errata I688
This is happening because there is no ti,omap4-mpu node, or no SRAM to configure for the other SoCs, so let's remove the warning based on the SoC revision checks.
As nobody has complained it seems that the other SoC variants do not need this workaround.
--- arch/arm/mach-omap2/omap4-common.c | 3 +++ 1 file changed, 3 insertions(+)
arch/arm/mach-omap2/omap4-common.c +3 -0
@@ -131,6 +131,9 @@ static int __init omap4_sram_init(void)struct device_node *np;struct gen_pool *sram_pool; +if (!soc_is_omap44xx () && !soc_is_omap54xx ()) +return 0 ; + np =of_find_compatible_node (NULL ,NULL ,"ti,omap4-mpu" );if (!np) pr_warn("%s:Unable to allocate sram needed to handle errata I688\n",
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 26/79 ARM: dts: dra74x: Fix iodelay configuration for mmc3
In reply to Greg Kroah-HartmanFrom: Faiz Abbas <[email protected]>
[ Upstream commit 07f9a8be66a9bd86f9eaedf8f8aeb416195adab8 ]
According to the latest am572x[1] and dra74x[2] data manuals, mmc3 default, hs, sdr12 and sdr25 modes use iodelay values given in MMC3_MANUAL1. Set the MODE_SELECT bit for these so that manual mode is selected and correct iodelay values can be configured.
[1] http://www.ti.com/lit/ds/symlink/am5728.pdf
[2] http://www.ti.com/lit/ds/symlink/dra746.pdf
--- arch/arm/boot/dts/dra74x-mmc-iodelay.dtsi | 50 +++++++++++------------ 1 file changed, 25 insertions(+), 25 deletions(-)
arch/arm/boot/dts/dra74x-mmc-iodelay.dtsi +25 -25
@@ -32,7 +32,7 @@ * * Datamanual Revisions: * - * AM572x Silicon Revision 2.0: SPRS953B, Revised November 2016 + * AM572x Silicon Revision 2.0: SPRS953F, Revised May 2019 * AM572x Silicon Revision 1.1: SPRS915R, Revised November 2016 * */
@@ -229,45 +229,45 @@ mmc3_pins_default: mmc3_pins_default { pinctrl-single,pins = < - DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ - DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ - DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ - DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ - DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ - DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ + DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ + DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ + DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ + DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ + DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ + DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ >; }; mmc3_pins_hs: mmc3_pins_hs { pinctrl-single,pins = < - DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ - DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ - DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ - DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ - DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ - DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ + DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ + DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ + DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ + DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ + DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ + DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ >; }; mmc3_pins_sdr12: mmc3_pins_sdr12 { pinctrl-single,pins = < - DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ - DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ - DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ - DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ - DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ - DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ + DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ + DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ + DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ + DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ + DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ + DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ >; }; mmc3_pins_sdr25: mmc3_pins_sdr25 { pinctrl-single,pins = < - DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ - DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ - DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ - DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ - DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ - DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ + DRA7XX_CORE_IOPAD(0x377c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_clk.mmc3_clk */ + DRA7XX_CORE_IOPAD(0x3780, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_cmd.mmc3_cmd */ + DRA7XX_CORE_IOPAD(0x3784, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat0.mmc3_dat0 */ + DRA7XX_CORE_IOPAD(0x3788, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat1.mmc3_dat1 */ + DRA7XX_CORE_IOPAD(0x378c, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat2.mmc3_dat2 */ + DRA7XX_CORE_IOPAD(0x3790, (PIN_INPUT_PULLUP | MODE_SELECT | MUX_MODE0)) /* mmc3_dat3.mmc3_dat3 */ >; };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 27/79 ARM: OMAP1: ams-delta-fiq: Fix missing irq_ack
In reply to Greg Kroah-HartmanFrom: Janusz Krzysztofik <[email protected]>
[ Upstream commit fa8397e45c64e60c80373bc19ee56e42a6bed9b6 ]
Non-serio path of Amstrad Delta FIQ deferred handler depended on irq_ack() method provided by OMAP GPIO driver. That method has been removed by commit 693de831c6e5 ("gpio: omap: remove irq_ack method"). Remove useless code from the deferred handler and reimplement the missing operation inside the base FIQ handler.
Should another dependency - irq_unmask() - be ever removed from the OMAP GPIO driver, WARN once if missing.
--- arch/arm/mach-omap1/ams-delta-fiq-handler.S | 3 ++- arch/arm/mach-omap1/ams-delta-fiq.c | 4 +--- 2 files changed, 3 insertions(+), 4 deletions(-)
arch/arm/mach-omap1/ams-delta-fiq-handler.S +2 -1
@@ -135,6 +135,8 @@ restart: orr r11, r11, r13 @ mask all requested interrupts str r11, [r12, #OMAP1510_GPIO_INT_MASK] + str r13, [r12, #OMAP1510_GPIO_INT_STATUS] @ ack all requested interrupts + ands r10, r13, #KEYBRD_CLK_MASK @ extract keyboard status - set? beq hksw @ no - try next source
@@ -142,7 +144,6 @@ restart: @@@@@@@@@@@@@@@@@@@@@@ @ Keyboard clock FIQ mode interrupt handler @ r10 now contains KEYBRD_CLK_MASK, use it - str r10, [r12, #OMAP1510_GPIO_INT_STATUS] @ ack the interrupt bic r11, r11, r10 @ unmask it str r11, [r12, #OMAP1510_GPIO_INT_MASK]
arch/arm/mach-omap1/ams-delta-fiq.c +1 -3
@@ -73,9 +73,7 @@ static irqreturn_t deferred_fiq(int irq, void *dev_id)* interrupts default to since commit 80ac93c27441 * requires interrupt already acked and unmasked. */ -if (irq_chip->irq_ack) - irq_chip->irq_ack (d); -if (irq_chip->irq_unmask) +if (!WARN_ON_ONCE (!irq_chip->irq_unmask)) irq_chip->irq_unmask (d); }for (; irq_counter[gpio] < fiq_count; irq_counter[gpio]++)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 28/79 bus: ti-sysc: Simplify cleanup upon failures in sysc_probe()
In reply to Greg Kroah-HartmanFrom: Suman Anna <[email protected]>
[ Upstream commit a304f483b6b00d42bde41c45ca52c670945348e2 ]
The clocks are not yet parsed and prepared until after a successful sysc_get_clocks(), so there is no need to unprepare the clocks upon any failure of any of the prior functions in sysc_probe(). The current code path would have been a no-op because of the clock validity checks within sysc_unprepare(), but let's just simplify the cleanup path by returning the error directly.
While at this, also fix the cleanup path for a sysc_init_resets() failure which is executed after the clocks are prepared.
--- drivers/bus/ti-sysc.c | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-)
drivers/bus/ti-sysc.c +7 -7
@@ -1685,7 +1685,7 @@ static int sysc_probe(struct platform_device *pdev) error =sysc_init_dts_quirks (ddata);if (error) - goto unprepare; +return error; error =sysc_get_clocks (ddata);if (error)
@@ -1693,27 +1693,27 @@ static int sysc_probe(struct platform_device *pdev) error =sysc_map_and_check_registers (ddata);if (error) - goto unprepare; +return error; error =sysc_init_sysc_mask (ddata);if (error) - goto unprepare; +return error; error =sysc_init_idlemodes (ddata);if (error) - goto unprepare; +return error; error =sysc_init_syss_mask (ddata);if (error) - goto unprepare; +return error; error =sysc_init_pdata (ddata);if (error) - goto unprepare; +return error; error =sysc_init_resets (ddata);if (error) -return error; + goto unprepare;pm_runtime_enable (ddata->dev); error =sysc_init_module (ddata);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 29/79 s390/bpf: use 32-bit index for tail calls
In reply to Greg Kroah-HartmanFrom: Ilya Leoshkevich <[email protected]>
[ Upstream commit 91b4db5313a2c793aabc2143efb8ed0cf0fdd097 ]
"p runtime/jit: pass > 32bit index to tail_call" fails when bpf_jit_enable=1, because the tail call is not executed.
This in turn is because the generated code assumes index is 64-bit, while it must be 32-bit, and as a result prog array bounds check fails, while it should pass. Even if bounds check would have passed, the code that follows uses 64-bit index to compute prog array offset.
Fix by using clrj instead of clgrj for comparing index with array size, and also by using llgfr for truncating index to 32 bits before using it to compute prog array offset.
--- arch/s390/net/bpf_jit_comp.c | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-)
arch/s390/net/bpf_jit_comp.c +6 -4
@@ -1015,8 +1015,8 @@ static noinline int bpf_jit_insn(struct bpf_jit *jit, struct bpf_prog *fp, int i/* llgf %w1,map.max_entries(%b2) */ EMIT6_DISP_LH (0xe3000000 ,0x0016 ,REG_W1 ,REG_0 ,BPF_REG_2 , offsetof(struct bpf_array, map.max_entries)); -/* clgrj %b3,%w1,0xa,label0: if %b3 >= %w1 goto out */ -EMIT6_PCREL_LABEL (0xec000000 ,0x0065 ,BPF_REG_3 , +/* clrj %b3,%w1,0xa,label0: if (u32)%b3 >= (u32)%w1 goto out */ +EMIT6_PCREL_LABEL (0xec000000 ,0x0077 ,BPF_REG_3 ,REG_W1 ,0 ,0xa );/*
@@ -1042,8 +1042,10 @@ static noinline int bpf_jit_insn(struct bpf_jit *jit, struct bpf_prog *fp, int i* goto out; */ -/* sllg %r1,%b3,3: %r1 = index * 8 */ -EMIT6_DISP_LH (0xeb000000 ,0x000d ,REG_1 ,BPF_REG_3 ,REG_0 ,3 ); +/* llgfr %r1,%b3: %r1 = (u32) index */ +EMIT4 (0xb9160000 ,REG_1 ,BPF_REG_3 ); +/* sllg %r1,%r1,3: %r1 *= 8 */ +EMIT6_DISP_LH (0xeb000000 ,0x000d ,REG_1 ,REG_1 ,REG_0 ,3 );/* lg %r1,prog(%b2,%r1) */ EMIT6_DISP_LH (0xe3000000 ,0x0004 ,REG_1 ,BPF_REG_2 ,REG_1 , offsetof(struct bpf_array , ptrs));
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 30/79 selftests/bpf: fix "bind{4, 6} deny specific IP & port" on s390
In reply to Greg Kroah-HartmanFrom: Ilya Leoshkevich <[email protected]>
[ Upstream commit 27df5c7068bf23cab282dc64b1c9894429b3b8a0 ]
"bind4 allow specific IP & port" and "bind6 deny specific IP & port" fail on s390 because of endianness issue: the 4 IP address bytes are loaded as a word and compared with a constant, but the value of this constant should be different on big- and little- endian machines, which is not the case right now.
Use __bpf_constant_ntohl to generate proper value based on machine endianness.
--- tools/testing/selftests/bpf/test_sock.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
tools/testing/selftests/bpf/test_sock.c +5 -2
@@ -13,6 +13,7 @@#include <bpf/bpf.h> #include "cgroup_helpers.h" +#include "bpf_endian.h" #include "bpf_rlimit.h" #include "bpf_util.h"
@@ -231,7 +232,8 @@ static struct sock_test tests[] = {/* if (ip == expected && port == expected) */ BPF_LDX_MEM (BPF_W ,BPF_REG_7 ,BPF_REG_6 , offsetof(struct bpf_sock, src_ip6[3])), -BPF_JMP_IMM (BPF_JNE ,BPF_REG_7 ,0x01000000 ,4 ), +BPF_JMP_IMM (BPF_JNE ,BPF_REG_7 , +__bpf_constant_ntohl (0x00000001 ),4 ),BPF_LDX_MEM (BPF_W ,BPF_REG_7 ,BPF_REG_6 , offsetof(struct bpf_sock , src_port)), BPF_JMP_IMM(BPF_JNE, BPF_REG_7, 0x2001, 2),
@@ -260,7 +262,8 @@ static struct sock_test tests[] = {/* if (ip == expected && port == expected) */ BPF_LDX_MEM (BPF_W ,BPF_REG_7 ,BPF_REG_6 , offsetof(struct bpf_sock , src_ip4)), -BPF_JMP_IMM (BPF_JNE ,BPF_REG_7 ,0x0100007F ,4 ), +BPF_JMP_IMM (BPF_JNE ,BPF_REG_7 , +__bpf_constant_ntohl (0x7F000001 ),4 ),BPF_LDX_MEM (BPF_W ,BPF_REG_7 ,BPF_REG_6 , offsetof(struct bpf_sock , src_port)), BPF_JMP_IMM(BPF_JNE, BPF_REG_7, 0x1002, 2),
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 31/79 tools: bpftool: close prog FD before exit on showing a single program
In reply to Greg Kroah-HartmanFrom: Quentin Monnet <[email protected]>
[ Upstream commit d34b044038bfb0e19caa8b019910efc465f41d5f ]
When showing metadata about a single program by invoking "bpftool prog show PROG", the file descriptor referring to the program is not closed before returning from the function. Let's close it.
--- tools/bpf/bpftool/prog.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
tools/bpf/bpftool/prog.c +3 -1
@@ -381,7 +381,9 @@ static int do_show(int argc, char **argv)if (fd <0 )return -1 ; -return show_prog (fd); + err =show_prog (fd); +close (fd); +return err; }if (argc)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 32/79 fpga: altera-ps-spi: Fix getting of optional confd gpio
In reply to Greg Kroah-HartmanFrom: Phil Reid <[email protected]>
[ Upstream commit dec43da46f63eb71f519d963ba6832838e4262a3 ]
Currently the driver does not handle EPROBE_DEFER for the confd gpio. Use devm_gpiod_get_optional() instead of devm_gpiod_get() and return error codes from altera_ps_probe().
--- drivers/fpga/altera-ps-spi.c | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-)
drivers/fpga/altera-ps-spi.c +7 -4
@@ -207,7 +207,7 @@ static int altera_ps_write_complete(struct fpga_manager *mgr,return -EIO ; } -if (!IS_ERR (conf->confd)) { +if (conf->confd) {if (!gpiod_get_raw_value_cansleep (conf->confd)) {dev_err (&mgr->dev,"CONF_DONE is inactive!\n" );return -EIO ;
@@ -265,10 +265,13 @@ static int altera_ps_probe(struct spi_device *spi)return PTR_ERR (conf->status); } - conf->confd =devm_gpiod_get (&spi->dev,"confd" ,GPIOD_IN ); + conf->confd =devm_gpiod_get_optional (&spi->dev,"confd" ,GPIOD_IN );if (IS_ERR (conf->confd)) { -dev_warn (&spi->dev,"Not using confd gpio: %ld\n" , -PTR_ERR (conf->confd)); +dev_err (&spi->dev,"Failed to get confd gpio: %ld\n" , +PTR_ERR (conf->confd)); +return PTR_ERR (conf->confd); + }else if (!conf->confd) { +dev_warn (&spi->dev,"Not using confd gpio" ); }/* Register manager with unique name */
Signature · 1 line
2.20.1
Re: [PATCH 4.19 32/79] fpga: altera-ps-spi: Fix getting of optional confd gpio
Hi!
Quoted 6 lines
Currently the driver does not handle
EPROBE_DEFERfor the confd gpio. Usedevm_gpiod_get_optional()instead ofdevm_gpiod_get()and return error codes fromaltera_ps_probe().drivers/fpga/altera-ps-spi.c +0
-0@@ -265,10 +265,13 @@ static int altera_ps_probe(struct spi_device *spi)return PTR_ERR (conf->status);
drivers/fpga/altera-ps-spi.c static int altera_ps_probe(struct spi_device *spi) · line 272
Quoted 10 lines
drivers/fpga/altera-ps-spi.c +4
-3} - conf->confd =devm_gpiod_get (&spi->dev,"confd" ,GPIOD_IN ); + conf->confd =devm_gpiod_get_optional (&spi->dev,"confd" ,GPIOD_IN );if (IS_ERR (conf->confd)) { -dev_warn (&spi->dev,"Not using confd gpio: %ld\n" , -PTR_ERR (conf->confd)); +dev_err (&spi->dev,"Failed to get confd gpio: %ld\n" , +PTR_ERR (conf->confd)); +return PTR_ERR (conf->confd);
Will this result in repeated errors in dmesg in case of EPROBE_DEFER? We often avoid printing such messages in EPROBE_DEFER case.
drivers/fpga/altera-ps-spi.c static int altera_ps_probe(struct spi_device *spi) · line 277
Quoted 5 lines
drivers/fpga/altera-ps-spi.c +2
-0+ }else if (!conf->confd) { +dev_warn (&spi->dev,"Not using confd gpio" ); }/* Register manager with unique name */
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Re: [PATCH 4.19 32/79] fpga: altera-ps-spi: Fix getting of optional confd gpio
Quoted 10 lines · Pavel Machek
Hi!
Quoted 8 lines
Currently the driver does not handle
EPROBE_DEFERfor the confd gpio. Usedevm_gpiod_get_optional()instead ofdevm_gpiod_get()and return error codes fromaltera_ps_probe().drivers/fpga/altera-ps-spi.c +0
-0@@ -265,10 +265,13 @@ static int altera_ps_probe(struct spi_device *spi)return PTR_ERR (conf->status); }
Quoted 11 lines
drivers/fpga/altera-ps-spi.c static int altera_ps_probe(struct spi_device *spi) · line 272
Quoted 8 lines
drivers/fpga/altera-ps-spi.c +4
-3- conf->confd =devm_gpiod_get (&spi->dev,"confd" ,GPIOD_IN ); + conf->confd =devm_gpiod_get_optional (&spi->dev,"confd" ,GPIOD_IN );if (IS_ERR (conf->confd)) { -dev_warn (&spi->dev,"Not using confd gpio: %ld\n" , -PTR_ERR (conf->confd)); +dev_err (&spi->dev,"Failed to get confd gpio: %ld\n" , +PTR_ERR (conf->confd)); +return PTR_ERR (conf->confd);Will this result in repeated errors in dmesg in case of
EPROBE_DEFER? We often avoid printing such messages inEPROBE_DEFERcase.
Yes it will. I can submit a patch for that if required.
Quoted 10 lines
drivers/fpga/altera-ps-spi.c static int altera_ps_probe(struct spi_device *spi) · line 277
Quoted 6 lines
drivers/fpga/altera-ps-spi.c +2
-0+ }else if (!conf->confd) { +dev_warn (&spi->dev,"Not using confd gpio" ); }/* Register manager with unique name */ Best regards,
Pavel
Signature · 2 lines
Regards Phil Reid
Greg Kroah-Hartman
maintainerPATCH 33/79 netfilter: ebtables: Fix argument order to ADD_COUNTER
In reply to Greg Kroah-HartmanFrom: Todd Seidelmann <[email protected]>
[ Upstream commit f20faa06d83de440bec8e200870784c3458793c4 ]
The ordering of arguments to the x_tables ADD_COUNTER macro appears to be wrong in ebtables (cf. ip_tables.c, ip6_tables.c, and arp_tables.c).
This causes data corruption in the ebtables userspace tools because they get incorrect packet & byte counts from the kernel.
--- net/bridge/netfilter/ebtables.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
net/bridge/netfilter/ebtables.c +4 -4
@@ -225,7 +225,7 @@ unsigned int ebt_do_table(struct sk_buff *skb,return NF_DROP ; } -ADD_COUNTER (*(counter_base + i),1 , skb->len); +ADD_COUNTER (*(counter_base + i), skb->len,1 );/* these should only watch: not modify, nor tell us * what to do with the packet
@@ -963,8 +963,8 @@ static void get_counters(const struct ebt_counter *oldcounters,continue ; counter_base =COUNTER_BASE (oldcounters, nentries, cpu);for (i =0 ; i < nentries; i++) -ADD_COUNTER (counters[i], counter_base[i].pcnt, - counter_base[i].bcnt); +ADD_COUNTER (counters[i], counter_base[i].bcnt, + counter_base[i].pcnt); } }
@@ -1289,7 +1289,7 @@ static int do_update_counters(struct net *net, const char *name,/* we add to the counters of the first cpu */ for (i =0 ; i < num_counters; i++) -ADD_COUNTER (t->private->counters[i], tmp[i].pcnt, tmp[i].bcnt); +ADD_COUNTER (t->private->counters[i], tmp[i].bcnt, tmp[i].pcnt);write_unlock_bh (&t->lock); ret =0 ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 34/79 netfilter: nft_flow_offload: missing netlink attribute policy
In reply to Greg Kroah-HartmanFrom: Pablo Neira Ayuso <[email protected]>
[ Upstream commit 14c415862c0630e01712a4eeaf6159a2b1b6d2a4 ]
The netlink attribute policy for NFTA_FLOW_TABLE_NAME is missing.
--- net/netfilter/nft_flow_offload.c | 6 ++++++ 1 file changed, 6 insertions(+)
net/netfilter/nft_flow_offload.c +6 -0
@@ -149,6 +149,11 @@ static int nft_flow_offload_validate(const struct nft_ctx *ctx,return nft_chain_validate_hooks (ctx->chain, hook_mask); } +static const struct nla_policy nft_flow_offload_policy[NFTA_FLOW_MAX +1 ] = { + [NFTA_FLOW_TABLE_NAME ] = { .type =NLA_STRING , + .len =NFT_NAME_MAXLEN -1 }, +}; +static int nft_flow_offload_init (const struct nft_ctx *ctx,const struct nft_expr *expr,const struct nlattr *const tb[])
@@ -207,6 +212,7 @@ static const struct nft_expr_ops nft_flow_offload_ops = {static struct nft_expr_type nft_flow_offload_type__read_mostly = { .name ="flow_offload" , .ops = &nft_flow_offload_ops, + .policy = nft_flow_offload_policy, .maxattr =NFTA_FLOW_MAX , .owner =THIS_MODULE , };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 35/79 netfilter: xt_nfacct: Fix alignment mismatch in xt_nfacct_match_info
In reply to Greg Kroah-HartmanFrom: Juliana Rodrigueiro <[email protected]>
[ Upstream commit 89a26cd4b501e9511d3cd3d22327fc76a75a38b3 ]
When running a 64-bit kernel with a 32-bit iptables binary, the size of the xt_nfacct_match_info struct diverges.
kernel: sizeof(struct xt_nfacct_match_info) : 40
iptables: sizeof(struct xt_nfacct_match_info)) : 36
Trying to append nfacct related rules results in an unhelpful message. Although it is suggested to look for more information in dmesg, nothing can be found there.
# iptables -A <chain> -m nfacct --nfacct-name <acct-object>
iptables: Invalid argument. Run `dmesg' for more information.This patch fixes the memory misalignment by enforcing 8-byte alignment within the struct's first revision. This solution is often used in many other uapi netfilter headers.
--- include/uapi/linux/netfilter/xt_nfacct.h | 5 ++++ net/netfilter/xt_nfacct.c | 36 ++++++++++++++++-------- 2 files changed, 30 insertions(+), 11 deletions(-)
include/uapi/linux/netfilter/xt_nfacct.h +5 -0
@@ -11,4 +11,9 @@ struct xt_nfacct_match_info { struct nf_acct *nfacct; }; +struct xt_nfacct_match_info_v1 { +char name[NFACCT_NAME_MAX ]; +struct nf_acct *nfacct __attribute__((aligned (8 ))); +}; +#endif /* _XT_NFACCT_MATCH_H */
net/netfilter/xt_nfacct.c +25 -11
@@ -57,25 +57,39 @@ nfacct_mt_destroy(const struct xt_mtdtor_param *par)nfnl_acct_put (info->nfacct); } -static struct xt_match nfacct_mt_reg__read_mostly = { - .name ="nfacct" , - .family =NFPROTO_UNSPEC , - .checkentry = nfacct_mt_checkentry, - .match = nfacct_mt, - .destroy = nfacct_mt_destroy, - .matchsize =sizeof (struct xt_nfacct_match_info ), - .usersize = offsetof(struct xt_nfacct_match_info , nfacct), - .me =THIS_MODULE , +static struct xt_match nfacct_mt_reg[]__read_mostly = { + { + .name ="nfacct" , + .revision =0 , + .family =NFPROTO_UNSPEC , + .checkentry = nfacct_mt_checkentry, + .match = nfacct_mt, + .destroy = nfacct_mt_destroy, + .matchsize =sizeof (struct xt_nfacct_match_info ), + .usersize = offsetof(struct xt_nfacct_match_info , nfacct), + .me =THIS_MODULE , + }, + { + .name ="nfacct" , + .revision =1 , + .family =NFPROTO_UNSPEC , + .checkentry = nfacct_mt_checkentry, + .match = nfacct_mt, + .destroy = nfacct_mt_destroy, + .matchsize =sizeof (struct xt_nfacct_match_info_v1 ), + .usersize = offsetof(struct xt_nfacct_match_info_v1 , nfacct), + .me =THIS_MODULE , + }, };static int __init nfacct_mt_init (void ) { -return xt_register_match (&nfacct_mt_reg); +return xt_register_matches (nfacct_mt_reg,ARRAY_SIZE (nfacct_mt_reg)); } static void __exit nfacct_mt_exit(void) { -xt_unregister_match (&nfacct_mt_reg); +xt_unregister_matches (nfacct_mt_reg,ARRAY_SIZE (nfacct_mt_reg)); }module_init (nfacct_mt_init);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 36/79 NFSv4: Fix return values for nfs4_file_open()
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
[ Upstream commit 90cf500e338ab3f3c0f126ba37e36fb6a9058441 ]
Currently, we are translating RPC level errors such as timeouts, as well as interrupts etc into EOPENSTALE, which forces a single replay of the open attempt. What we actually want to do is force the replay only in the cases where the returned error indicates that the file may have changed on the server.
So the fix is to spell out the exact set of errors where we want to return EOPENSTALE.
--- fs/nfs/nfs4file.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
fs/nfs/nfs4file.c +6 -6
@@ -73,13 +73,13 @@ nfs4_file_open(struct inode *inode, struct file *filp)if (IS_ERR (inode)) { err =PTR_ERR (inode);switch (err) { -case -EPERM : -case -EACCES : -case -EDQUOT : -case -ENOSPC : -case -EROFS : - goto out_put_ctx;default : + goto out_put_ctx; +case -ENOENT : +case -ESTALE : +case -EISDIR : +case -ENOTDIR : +case -ELOOP : goto out_drop; } }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 37/79 NFSv4: Fix return value in nfs_finish_open()
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
[ Upstream commit 9821421a291b548ef4369c6998745baa36ddecd5 ]
If the file turns out to be of the wrong type after opening, we want to revalidate the path and retry, so return EOPENSTALE rather than ESTALE.
--- fs/nfs/dir.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/nfs/dir.c +1 -1
@@ -1486,7 +1486,7 @@ static int nfs_finish_open(struct nfs_open_context *ctx,if (S_ISREG (file->f_path.dentry->d_inode->i_mode))nfs_file_set_open_context (file, ctx);else - err = -ESTALE ; + err = -EOPENSTALE ; out:return err; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 38/79 NFS: Fix initialisation of I/O result struct in nfs_pgio_rpcsetup
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
[ Upstream commit 17d8c5d145000070c581f2a8aa01edc7998582ab ]
Initialise the result count to 0 rather than initialising it to the argument count. The reason is that we want to ensure we record the I/O stats correctly in the case where an error is returned (for instance in the layoutstats).
--- fs/nfs/pagelist.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/nfs/pagelist.c +1 -1
@@ -567,7 +567,7 @@ static void nfs_pgio_rpcsetup(struct nfs_pgio_header *hdr, } hdr->res.fattr = &hdr->fattr; - hdr->res.count = count; + hdr->res.count =0 ; hdr->res.eof =0 ; hdr->res.verf = &hdr->verf;nfs_fattr_init (&hdr->fattr);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 39/79 Kconfig: Fix the reference to the IDT77105 Phy driver in the description of ATM_NICSTAR_USE_IDT77105
In reply to Greg Kroah-HartmanFrom: Christophe JAILLET <[email protected]>
[ Upstream commit cd9d4ff9b78fcd0fc4708900ba3e52e71e1a7690 ]
This should be IDT77105, not IDT77015.
--- drivers/atm/Kconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/atm/Kconfig +1 -1
@@ -200,7 +200,7 @@ config ATM_NICSTAR_USE_SUNI make the card work). config ATM_NICSTAR_USE_IDT77105 - bool "Use IDT77015 PHY driver (25Mbps)" + bool "Use IDT77105 PHY driver (25Mbps)" depends on ATM_NICSTAR help Support for the PHYsical layer chip in ForeRunner LE25 cards. In
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 40/79 xdp: unpin xdp umem pages in error path
In reply to Greg Kroah-HartmanFrom: Ivan Khoronzhuk <[email protected]>
[ Upstream commit fb89c39455e4b49881c5a42761bd71f03d3ef888 ]
Fix mem leak caused by missed unpin routine for umem pages.
--- net/xdp/xdp_umem.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
net/xdp/xdp_umem.c +3 -1
@@ -322,7 +322,7 @@ static int xdp_umem_reg(struct xdp_umem *umem, struct xdp_umem_reg *mr) umem->pages =kcalloc (umem->npgs,sizeof (*umem->pages),GFP_KERNEL );if (!umem->pages) { err = -ENOMEM ; - goto out_account; + goto out_pin; }for (i =0 ; i < umem->npgs; i++)
@@ -330,6 +330,8 @@ static int xdp_umem_reg(struct xdp_umem *umem, struct xdp_umem_reg *mr)return 0 ; +out_pin: +xdp_umem_unpin_pages (umem); out_account:xdp_umem_unaccount_pages (umem);return err;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 41/79 qed: Add cleanup in qed_slowpath_start()
In reply to Greg Kroah-HartmanFrom: Wenwen Wang <[email protected]>
[ Upstream commit de0e4fd2f07ce3bbdb69dfb8d9426b7227451b69 ]
If qed_mcp_send_drv_version() fails, no cleanup is executed, leading to memory leaks. To fix this issue, introduce the label 'err4' to perform the cleanup work before returning the error.
--- drivers/net/ethernet/qlogic/qed/qed_main.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/net/ethernet/qlogic/qed/qed_main.c +3 -1
@@ -1150,7 +1150,7 @@ static int qed_slowpath_start(struct qed_dev *cdev, &drv_version);if (rc) {DP_NOTICE (cdev,"Failed sending drv version command\n" ); -return rc; + goto err4; } }
@@ -1158,6 +1158,8 @@ static int qed_slowpath_start(struct qed_dev *cdev,return 0 ; +err4: +qed_ll2_dealloc_if (cdev); err3:qed_hw_stop (cdev); err2:
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 42/79 ARM: 8874/1: mm: only adjust sections of valid mm structures
In reply to Greg Kroah-HartmanFrom: Doug Berger <[email protected]>
[ Upstream commit c51bc12d06b3a5494fbfcbd788a8e307932a06e9 ]
A timing hazard exists when an early fork/exec thread begins exiting and sets its mm pointer to NULL while a separate core tries to update the section information.
This commit ensures that the mm pointer is not NULL before setting its section parameters. The arguments provided by commit 11ce4b33aedc ("ARM: 8672/1: mm: remove tasklist locking from update_sections_early()") are equally valid for not requiring grabbing the task_lock around this check.
--- arch/arm/mm/init.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/arm/mm/init.c +2 -1
@@ -713,7 +713,8 @@ static void update_sections_early(struct section_perm perms[], int n)if (t->flags &PF_KTHREAD )continue ;for_each_thread (t, s) -set_section_perms (perms, n, true, s->mm); +if (s->mm) +set_section_perms (perms, n, true, s->mm); }set_section_perms (perms, n, true, current->active_mm);set_section_perms (perms, n, true, &init_mm);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 43/79 batman-adv: Only read OGM2 tvlv_len after buffer len check
In reply to Greg Kroah-HartmanFrom: Sven Eckelmann <[email protected]>
[ Upstream commit 0ff0f15a32c093381ad1abc06abe85afb561ab28 ]
Multiple batadv_ogm2_packet can be stored in an skbuff. The functions batadv_v_ogm_send_to_if() uses batadv_v_ogm_aggr_packet() to check if there is another additional batadv_ogm2_packet in the skb or not before they continue processing the packet.
The length for such an OGM2 is BATADV_OGM2_HLEN + batadv_ogm2_packet->tvlv_len. The check must first check that at least BATADV_OGM2_HLEN bytes are available before it accesses tvlv_len (which is part of the header. Otherwise it might try read outside of the currently available skbuff to get the content of tvlv_len.
--- net/batman-adv/bat_v_ogm.c | 18 ++++++++++++------ 1 file changed, 12 insertions(+), 6 deletions(-)
net/batman-adv/bat_v_ogm.c +12 -6
@@ -643,17 +643,23 @@ batadv_v_ogm_process_per_outif(struct batadv_priv *bat_priv,* batadv_v_ogm_aggr_packet() - checks if there is another OGM aggregated * @buff_pos: current position in the skb * @packet_len: total length of the skb -* @tvlv_len: tvlv length of the previously considered OGM +* @ogm2_packet: potential OGM2 in buffer * * Return: true if there is enough space for another OGM, false otherwise. */ -static bool batadv_v_ogm_aggr_packet (int buff_pos,int packet_len, -__be16 tvlv_len) +static bool +batadv_v_ogm_aggr_packet (int buff_pos,int packet_len, +const struct batadv_ogm2_packet *ogm2_packet) {int next_buff_pos =0 ; - next_buff_pos += buff_pos +BATADV_OGM2_HLEN ; - next_buff_pos +=ntohs (tvlv_len); +/* check if there is enough space for the header */ + next_buff_pos += buff_pos +sizeof (*ogm2_packet); +if (next_buff_pos > packet_len) +return false; + +/* check if there is enough space for the optional TVLV */ + next_buff_pos +=ntohs (ogm2_packet->tvlv_len);return (next_buff_pos <= packet_len) && (next_buff_pos <=BATADV_MAX_AGGREGATION_BYTES );
@@ -830,7 +836,7 @@ int batadv_v_ogm_packet_recv(struct sk_buff *skb, ogm_packet = (struct batadv_ogm2_packet *)skb->data;while (batadv_v_ogm_aggr_packet (ogm_offset,skb_headlen (skb), - ogm_packet->tvlv_len)) { + ogm_packet)) {batadv_v_ogm_process (skb, ogm_offset, if_incoming); ogm_offset +=BATADV_OGM2_HLEN ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 44/79 bpf: allow narrow loads of some sk_reuseport_md fields with offset > 0
In reply to Greg Kroah-HartmanFrom: Ilya Leoshkevich <[email protected]>
[ Upstream commit 2c238177bd7f4b14bdf7447cc1cd9bb791f147e6 ]
test_select_reuseport fails on s390 due to verifier rejecting test_select_reuseport_kern.o with the following message:
; data_check.eth_protocol = reuse_md->eth_protocol; 18: (69) r1 = *(u16 *)(r6 +22) invalid bpf_context access off=22 size=2
This is because on big-endian machines casts from __u32 to __u16 are generated by referencing the respective variable as __u16 with an offset of 2 (as opposed to 0 on little-endian machines).
The verifier already has all the infrastructure in place to allow such accesses, it's just that they are not explicitly enabled for eth_protocol field. Enable them for eth_protocol field by using bpf_ctx_range instead of offsetof.
Ditto for ip_protocol, bind_inany and len, since they already allow narrowing, and the same problem can arise when working with them.
--- net/core/filter.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
net/core/filter.c +4 -4
@@ -7234,13 +7234,13 @@ sk_reuseport_is_valid_access(int off, int size,return size == size_default;/* Fields that allow narrowing */ -case offsetof(struct sk_reuseport_md , eth_protocol): + case bpf_ctx_range(struct sk_reuseport_md, eth_protocol): if (size < FIELD_SIZEOF(struct sk_buff, protocol))return false;/* fall through */ -case offsetof(struct sk_reuseport_md , ip_protocol): -case offsetof(struct sk_reuseport_md , bind_inany): -case offsetof(struct sk_reuseport_md , len): + case bpf_ctx_range(struct sk_reuseport_md, ip_protocol): + case bpf_ctx_range(struct sk_reuseport_md, bind_inany): + case bpf_ctx_range(struct sk_reuseport_md, len):bpf_ctx_record_field_size (info, size_default);return bpf_ctx_narrow_access_ok (off, size, size_default);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 45/79 r8152: Set memory to all 0xFFs on failed reg reads
In reply to Greg Kroah-HartmanFrom: Prashant Malani <[email protected]>
[ Upstream commit f53a7ad189594a112167efaf17ea8d0242b5ac00 ]
get_registers() blindly copies the memory written to by the usb_control_msg() call even if the underlying urb failed.
This could lead to junk register values being read by the driver, since some indirect callers of get_registers() ignore the return values. One example is:
ocp_read_dword() ignores the return value of generic_ocp_read(), which calls get_registers().
So, emulate PCI "Master Abort" behavior by setting the buffer to all 0xFFs when usb_control_msg() fails.
This patch is copied from the r8152 driver (v2.12.0) published by Realtek (www.realtek.com).
--- drivers/net/usb/r8152.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/net/usb/r8152.c +4 -1
@@ -788,8 +788,11 @@ int get_registers(struct r8152 *tp, u16 value, u16 index, u16 size, void *data) ret =usb_control_msg (tp->udev,usb_rcvctrlpipe (tp->udev,0 ),RTL8152_REQ_GET_REGS ,RTL8152_REQT_READ , value, index, tmp, size,500 ); +if (ret <0 ) +memset (data,0xff , size); +else +memcpy (data, tmp, size); -memcpy (data, tmp, size);kfree (tmp);return ret;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 46/79 x86/apic: Fix arch_dynirq_lower_bound() bug for DT enabled machines
In reply to Greg Kroah-HartmanFrom: Thomas Gleixner <[email protected]>
[ Upstream commit 3e5bedc2c258341702ddffbd7688c5e6eb01eafa ]
Rahul Tanwar reported the following bug on DT systems:
Quoted 11 lines
'
ioapic_dynirq_base' contains the virtual IRQ base number. Presently, it is updated to the end of hardware IRQ numbers but this is done only when IOAPIC configuration type isIOAPIC_DOMAIN_LEGACYorIOAPIC_DOMAIN_STRICT. There is a third typeIOAPIC_DOMAIN_DYNAMICwhich applies when IOAPIC configuration comes from devicetree.See
dtb_add_ioapic()inarch/x86/kernel/devicetree.cIn case of
IOAPIC_DOMAIN_DYNAMIC(DT/OF based system), 'ioapic_dynirq_base' remains to zero initialized value. This means that for OF based systems, virtual IRQ base will get set to zero.
Such systems will very likely not even boot.
For DT enabled machines ioapic_dynirq_base is irrelevant and not updated, so simply map the IRQ base 1:1 instead.
--- arch/x86/kernel/apic/io_apic.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
arch/x86/kernel/apic/io_apic.c +7 -1
@@ -2432,7 +2432,13 @@ unsigned int arch_dynirq_lower_bound(unsigned int from)* dmar_alloc_hwirq() may be called before setup_IO_APIC(), so use * gsi_top if ioapic_dynirq_base hasn't been initialized yet. */ -return ioapic_initialized ? ioapic_dynirq_base : gsi_top; +if (!ioapic_initialized) +return gsi_top; +/* +* For DT enabled machines ioapic_dynirq_base is irrelevant and not +* updated. So simply return @from if ioapic_dynirq_base == 0. +*/ +return ioapic_dynirq_base ? : from; }#ifdef CONFIG_X86_32
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 47/79 netfilter: xt_physdev: Fix spurious error message in physdev_mt_check
In reply to Greg Kroah-HartmanFrom: Todd Seidelmann <[email protected]>
[ Upstream commit 3cf2f450fff304be9cf4868bf0df17f253bc5b1c ]
Simplify the check in physdev_mt_check() to emit an error message only when passed an invalid chain (ie, NF_INET_LOCAL_OUT). This avoids cluttering up the log with errors against valid rules.
For large/heavily modified rulesets, current behavior can quickly overwhelm the ring buffer, because this function gets called on every change, regardless of the rule that was changed.
--- net/netfilter/xt_physdev.c | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-)
net/netfilter/xt_physdev.c +2 -4
@@ -104,11 +104,9 @@ static int physdev_mt_check(const struct xt_mtchk_param *par)if (info->bitmask & (XT_PHYSDEV_OP_OUT |XT_PHYSDEV_OP_ISOUT ) && (!(info->bitmask &XT_PHYSDEV_OP_BRIDGED ) || info->invert &XT_PHYSDEV_OP_BRIDGED ) && - par->hook_mask & ((1 <<NF_INET_LOCAL_OUT ) | - (1 <<NF_INET_FORWARD ) | (1 <<NF_INET_POST_ROUTING ))) { + par->hook_mask & (1 <<NF_INET_LOCAL_OUT )) {pr_info_ratelimited ("--physdev-out and --physdev-is-out only supported in the FORWARD and POSTROUTING chains with bridged traffic\n" ); -if (par->hook_mask & (1 <<NF_INET_LOCAL_OUT )) -return -EINVAL ; +return -EINVAL ; }if (!brnf_probed) {
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 48/79 netfilter: nf_conntrack_ftp: Fix debug output
In reply to Greg Kroah-HartmanFrom: Thomas Jarosch <[email protected]>
[ Upstream commit 3a069024d371125227de3ac8fa74223fcf473520 ]
The find_pattern() debug output was printing the 'skip' character. This can be a NULL-byte and messes up further pr_debug() output.
Output without the fix:
kernel: nf_conntrack_ftp: Pattern matches!
kernel: nf_conntrack_ftp: Skipped up to <7>nf_conntrack_ftp: find_pattern PORT': dlen = 8
kernel: nf_conntrack_ftp: find_pattern `EPRT': dlen = 8
Output with the fix:
kernel: nf_conntrack_ftp: Pattern matches!
kernel: nf_conntrack_ftp: Skipped up to 0x0 delimiter!
kernel: nf_conntrack_ftp: Match succeeded!
kernel: nf_conntrack_ftp: conntrack_ftp: match `172,17,0,100,200,207' (20 bytes at 4150681645)
kernel: nf_conntrack_ftp: find_pattern `PORT': dlen = 8
--- net/netfilter/nf_conntrack_ftp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/netfilter/nf_conntrack_ftp.c +1 -1
@@ -323,7 +323,7 @@ static int find_pattern(const char *data, size_t dlen, i++; } -pr_debug ("Skipped up to `%c'!\n" , skip); +pr_debug ("Skipped up to 0x%hhx delimiter!\n" , skip); *numoff = i; *numlen =getnum (data + i, dlen - i, cmd, term, numoff);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 49/79 NFSv2: Fix eof handling
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
[ Upstream commit 71affe9be45a5c60b9772e1b2701710712637274 ]
If we received a reply from the server with a zero length read and no error, then that implies we are at eof.
--- fs/nfs/proc.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
fs/nfs/proc.c +2 -1
@@ -594,7 +594,8 @@ static int nfs_read_done(struct rpc_task *task, struct nfs_pgio_header *hdr)/* Emulate the eof flag, which isn't normally needed in NFSv2 * as it is guaranteed to always return the file attributes */ -if (hdr->args.offset + hdr->res.count >= hdr->res.fattr->size) +if ((hdr->res.count ==0 && hdr->args.count >0 ) || + hdr->args.offset + hdr->res.count >= hdr->res.fattr->size) hdr->res.eof =1 ; }return 0 ;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 50/79 NFSv2: Fix write regression
In reply to Greg Kroah-HartmanFrom: Trond Myklebust <[email protected]>
[ Upstream commit d33d4beb522987d1c305c12500796f9be3687dee ]
Ensure we update the write result count on success, since the RPC call itself does not do so.
--- fs/nfs/proc.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
fs/nfs/proc.c +3 -1
@@ -616,8 +616,10 @@ static int nfs_proc_pgio_rpc_prepare(struct rpc_task *task,static int nfs_write_done (struct rpc_task *task,struct nfs_pgio_header *hdr) { -if (task->tk_status >=0 ) +if (task->tk_status >=0 ) { + hdr->res.count = hdr->args.count;nfs_writeback_update_inode (hdr); + }return 0 ; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 51/79 kallsyms: Dont let kallsyms_lookup_size_offset() fail on retrieving the first symbol
In reply to Greg Kroah-HartmanFrom: Marc Zyngier <[email protected]>
[ Upstream commit 2a1a3fa0f29270583f0e6e3100d609e09697add1 ]
An arm64 kernel configured with
CONFIG_KPROBES=y
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
CONFIG_KALLSYMS_BASE_RELATIVE=y
reports the following kprobe failure:
[ 0.032677] kprobes: failed to populate blacklist: -22 [ 0.033376] Please take care of using kprobes.
It appears that kprobe fails to retrieve the symbol at address 0xffff000010081000, despite this symbol being in System.map:
ffff000010081000 T __exception_text_start
This symbol is part of the first group of aliases in the kallsyms_offsets array (symbol names generated using ugly hacks in scripts/kallsyms.c):
kallsyms_offsets:
.long 0x1000 // do_undefinstr
.long 0x1000 // efi_header_end
.long 0x1000 // _stext
.long 0x1000 // __exception_text_start
.long 0x12b0 // do_cp15instrLooking at the implementation of get_symbol_pos(), it returns the lowest index for aliasing symbols. In this case, it return 0.
But kallsyms_lookup_size_offset() considers 0 as a failure, which is obviously wrong (there is definitely a valid symbol living there). In turn, the kprobe blacklisting stops abruptly, hence the original error.
A CONFIG_KALLSYMS_ALL kernel wouldn't fail as there is always some random symbols at the beginning of this array, which are never looked up via kallsyms_lookup_size_offset.
Fix it by considering that get_symbol_pos() is always successful (which is consistent with the other uses of this function).
--- kernel/kallsyms.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
kernel/kallsyms.c +4 -2
@@ -262,8 +262,10 @@ int kallsyms_lookup_size_offset(unsigned long addr, unsigned long *symbolsize, {char namebuf[KSYM_NAME_LEN ]; -if (is_ksym_addr (addr)) -return !!get_symbol_pos (addr, symbolsize, offset); +if (is_ksym_addr (addr)) { +get_symbol_pos (addr, symbolsize, offset); +return 1 ; + }return !!module_address_lookup (addr, symbolsize, offset,NULL , namebuf) || !!__bpf_address_lookup (addr, symbolsize, offset, namebuf); }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 52/79 cifs: set domainName when a domain-key is used in multiuser
In reply to Greg Kroah-HartmanFrom: Ronnie Sahlberg <[email protected]>
[ Upstream commit f2aee329a68f5a907bcff11a109dfe17c0b41aeb ]
RHBZ: 1710429
When we use a domain-key to authenticate using multiuser we must also set the domainnmame for the new volume as it will be used and passed to the server in the NTLMSSP Domain-name.
--- fs/cifs/connect.c | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+)
fs/cifs/connect.c +22 -0
@@ -2756,6 +2756,7 @@ static int cifs_set_cifscreds(struct smb_vol *vol, struct cifs_ses *ses) { int rc = 0; +int is_domain =0 ;const char *delim, *payload;char *desc;ssize_t len;
@@ -2803,6 +2804,7 @@ cifs_set_cifscreds(struct smb_vol *vol, struct cifs_ses *ses) rc =PTR_ERR (key); goto out_err; } + is_domain =1 ; }down_read (&key->sem);
@@ -2860,6 +2862,26 @@ cifs_set_cifscreds(struct smb_vol *vol, struct cifs_ses *ses) goto out_key_put; } +/* +* If we have a domain key then we must set the domainName in the +* for the request. +*/ +if (is_domain && ses->domainName) { + vol->domainname =kstrndup (ses->domainName, +strlen (ses->domainName), +GFP_KERNEL ); +if (!vol->domainname) { +cifs_dbg (FYI ,"Unable to allocate %zd bytes for " +"domain\n" , len); + rc = -ENOMEM ; +kfree (vol->username); + vol->username =NULL ; +kfree (vol->password); + vol->password =NULL ; + goto out_key_put; + } + } + out_key_put:up_read (&key->sem);key_put (key);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 53/79 cifs: Use kzfree() to zero out the password
In reply to Greg Kroah-HartmanFrom: Dan Carpenter <[email protected]>
[ Upstream commit 478228e57f81f6cb60798d54fc02a74ea7dd267e ]
It's safer to zero out the password so that it can never be disclosed.
--- fs/cifs/connect.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
fs/cifs/connect.c +1 -1
@@ -2876,7 +2876,7 @@ cifs_set_cifscreds(struct smb_vol *vol, struct cifs_ses *ses) rc = -ENOMEM ;kfree (vol->username); vol->username =NULL ; -kfree (vol->password); +kzfree (vol->password); vol->password =NULL ; goto out_key_put; }
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 54/79 usb: host: xhci-tegra: Set DMA mask correctly
In reply to Greg Kroah-HartmanFrom: Nagarjuna Kristam <[email protected]>
[ Upstream commit 993cc8753453fccfe060a535bbe21fcf1001b626 ]
The Falcon microcontroller that runs the XUSB firmware and which is responsible for exposing the XHCI interface can address only 40 bits of memory. Typically that's not a problem because Tegra devices don't have enough system memory to exceed those 40 bits.
However, if the ARM SMMU is enable on Tegra186 and later, the addresses passed to the XUSB controller can be anywhere in the 48-bit IOV address space of the ARM SMMU. Since the DMA/IOMMU API starts allocating from the top of the IOVA space, the Falcon microcontroller is not able to load the firmware successfully.
Fix this by setting the DMA mask to 40 bits, which will force the DMA API to map the buffer for the firmware to an IOVA that is addressable by the Falcon.
--- drivers/usb/host/xhci-tegra.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
drivers/usb/host/xhci-tegra.c +10 -0
@@ -1148,6 +1148,16 @@ static int tegra_xusb_probe(struct platform_device *pdev)tegra_xusb_ipfs_config (tegra, regs); +/* +* The XUSB Falcon microcontroller can only address 40 bits, so set +* the DMA mask accordingly. +*/ + err =dma_set_mask_and_coherent (tegra->dev,DMA_BIT_MASK (40 )); +if (err <0 ) { +dev_err (&pdev->dev,"failed to set DMA mask: %d\n" , err); + goto put_rpm; + } + err =tegra_xusb_load_firmware (tegra);if (err <0 ) {dev_err (&pdev->dev,"failed to load firmware: %d\n" , err);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 55/79 ARM: 8901/1: add a criteria for pfn_valid of arm
In reply to Greg Kroah-HartmanFrom: zhaoyang <[email protected]>
[ Upstream commit 5b3efa4f1479c91cb8361acef55f9c6662feba57 ]
pfn_valid can be wrong when parsing a invalid pfn whose phys address exceeds BITS_PER_LONG as the MSB will be trimed when shifted.
The issue originally arise from bellowing call stack, which corresponding to an access of the /proc/kpageflags from userspace with a invalid pfn parameter and leads to kernel panic.
[46886.723249] c7 [<c031ff98>] (stable_page_flags) from [<c03203f8>] [46886.723264] c7 [<c0320368>] (kpageflags_read) from [<c0312030>] [46886.723280] c7 [<c0311fb0>] (proc_reg_read) from [<c02a6e6c>] [46886.723290] c7 [<c02a6e24>] (__vfs_read) from [<c02a7018>] [46886.723301] c7 [<c02a6f74>] (vfs_read) from [<c02a778c>] [46886.723315] c7 [<c02a770c>] (SyS_pread64) from [<c0108620>]
(ret_fast_syscall+0x0/0x28)
--- arch/arm/mm/init.c | 5 +++++ 1 file changed, 5 insertions(+)
arch/arm/mm/init.c +5 -0
@@ -196,6 +196,11 @@ static void __init zone_sizes_init(unsigned long min, unsigned long max_low,#ifdef CONFIG_HAVE_ARCH_PFN_VALID int pfn_valid (unsigned long pfn) { +phys_addr_t addr =__pfn_to_phys (pfn); + +if (__phys_to_pfn (addr) != pfn) +return 0 ; +return memblock_is_map_memory (__pfn_to_phys (pfn)); }EXPORT_SYMBOL (pfn_valid);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 56/79 ibmvnic: Do not process reset during or after device removal
In reply to Greg Kroah-HartmanFrom: Thomas Falcon <[email protected]>
[ Upstream commit 36f1031c51a2538e5558fb44c6d6b88f98d3c0f2 ]
Currently, the ibmvnic driver will not schedule device resets if the device is being removed, but does not check the device state before the reset is actually processed. This leads to a race where a reset is scheduled with a valid device state but is processed after the driver has been removed, resulting in an oops.
Fix this by checking the device state before processing a queued reset event.
--- drivers/net/ethernet/ibm/ibmvnic.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
drivers/net/ethernet/ibm/ibmvnic.c +5 -1
@@ -1998,6 +1998,10 @@ static void __ibmvnic_reset(struct work_struct *work) rwi =get_next_rwi (adapter);while (rwi) { +if (adapter->state ==VNIC_REMOVING || + adapter->state ==VNIC_REMOVED ) + goto out; +if (adapter->force_reset_recovery) { adapter->force_reset_recovery = false; rc =do_hard_reset (adapter, rwi, reset_state);
@@ -2022,7 +2026,7 @@ static void __ibmvnic_reset(struct work_struct *work)netdev_dbg (adapter->netdev,"Reset failed\n" );free_all_rwi (adapter); } - +out: adapter->resetting = false;if (we_lock_rtnl)rtnl_unlock ();
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 57/79 sky2: Disable MSI on yet another ASUS boards (P6Xxxx)
In reply to Greg Kroah-HartmanFrom: Takashi Iwai <[email protected]>
[ Upstream commit 189308d5823a089b56e2299cd96589507dac7319 ]
A similar workaround for the suspend/resume problem is needed for yet another ASUS machines, P6X models. Like the previous fix, the BIOS doesn't provide the standard DMI_SYS_* entry, so again DMI_BOARD_* entries are used instead.
--- drivers/net/ethernet/marvell/sky2.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/net/ethernet/marvell/sky2.c +7 -0
@@ -4954,6 +4954,13 @@ static const struct dmi_system_id msi_blacklist[] = { DMI_MATCH(DMI_BOARD_NAME, "P6T"), }, }, + { + .ident = "ASUS P6X", + .matches = { + DMI_MATCH(DMI_BOARD_VENDOR, "ASUSTeK Computer INC."), + DMI_MATCH(DMI_BOARD_NAME, "P6X"), + }, + }, {} };
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 58/79 i2c: designware: Synchronize IRQs when unregistering slave client
In reply to Greg Kroah-HartmanFrom: Jarkko Nikula <[email protected]>
[ Upstream commit c486dcd2f1bbdd524a1e0149734b79e4ae329650 ]
Make sure interrupt handler i2c_dw_irq_handler_slave() has finished before clearing the the dev->slave pointer in i2c_dw_unreg_slave().
There is possibility for a race if i2c_dw_irq_handler_slave() is running on another CPU while clearing the dev->slave pointer.
--- drivers/i2c/busses/i2c-designware-slave.c | 1 + 1 file changed, 1 insertion(+)
drivers/i2c/busses/i2c-designware-slave.c +1 -0
@@ -94,6 +94,7 @@ static int i2c_dw_unreg_slave(struct i2c_client *slave) dev->disable_int (dev); dev->disable (dev); +synchronize_irq (dev->irq); dev->slave =NULL ;pm_runtime_put (dev->dev);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 59/79 perf/x86/intel: Restrict period on Nehalem
In reply to Greg Kroah-HartmanFrom: Josh Hunt <[email protected]>
[ Upstream commit 44d3bbb6f5e501b873218142fe08cdf62a4ac1f3 ]
We see our Nehalem machines reporting 'perfevents: irq loop stuck!' in some cases when using perf:
perfevents: irq loop stuck!
WARNING: CPU: 0 PID: 3485 at arch/x86/events/intel/core.c:2282 intel_pmu_handle_irq+0x37b/0x530 ... RIP: 0010:intel_pmu_handle_irq+0x37b/0x530 ... Call Trace: <NMI> ? perf_event_nmi_handler+0x2e/0x50 ? intel_pmu_save_and_restart+0x50/0x50 perf_event_nmi_handler+0x2e/0x50 nmi_handle+0x6e/0x120 default_do_nmi+0x3e/0x100 do_nmi+0x102/0x160 end_repeat_nmi+0x16/0x50 ... ? native_write_msr+0x6/0x20 ? native_write_msr+0x6/0x20 </NMI> intel_pmu_enable_event+0x1ce/0x1f0 x86_pmu_start+0x78/0xa0 x86_pmu_enable+0x252/0x310 __perf_event_task_sched_in+0x181/0x190 ? __switch_to_asm+0x41/0x70 ? __switch_to_asm+0x35/0x70 ? __switch_to_asm+0x41/0x70 ? __switch_to_asm+0x35/0x70 finish_task_switch+0x158/0x260 __schedule+0x2f6/0x840 ? hrtimer_start_range_ns+0x153/0x210 schedule+0x32/0x80 schedule_hrtimeout_range_clock+0x8a/0x100 ? hrtimer_init+0x120/0x120 ep_poll+0x2f7/0x3a0 ? wake_up_q+0x60/0x60 do_epoll_wait+0xa9/0xc0 __x64_sys_epoll_wait+0x1a/0x20 do_syscall_64+0x4e/0x110 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdeb1e96c03
...
--- arch/x86/events/intel/core.c | 6 ++++++ 1 file changed, 6 insertions(+)
arch/x86/events/intel/core.c +6 -0
@@ -3319,6 +3319,11 @@ static u64 bdw_limit_period(struct perf_event *event, u64 left)return left; } +static u64 nhm_limit_period (struct perf_event *event,u64 left) +{ +return max (left,32ULL ); +} +PMU_FORMAT_ATTR (event,"config:0-7" );PMU_FORMAT_ATTR (umask,"config:8-15" );PMU_FORMAT_ATTR (edge,"config:18" );
@@ -4115,6 +4120,7 @@ __init int intel_pmu_init(void) x86_pmu.pebs_constraints = intel_nehalem_pebs_event_constraints; x86_pmu.enable_all = intel_pmu_nhm_enable_all; x86_pmu.extra_regs = intel_nehalem_extra_regs; + x86_pmu.limit_period = nhm_limit_period; x86_pmu.cpu_events = nhm_events_attrs;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 60/79 perf/x86/amd/ibs: Fix sample bias for dispatched micro-ops
In reply to Greg Kroah-HartmanFrom: Kim Phillips <[email protected]>
[ Upstream commit 0f4cd769c410e2285a4e9873a684d90423f03090 ]
When counting dispatched micro-ops with cnt_ctl=1, in order to prevent sample bias, IBS hardware preloads the least significant 7 bits of current count (IbsOpCurCnt) with random values, such that, after the interrupt is handled and counting resumes, the next sample taken will be slightly perturbed.
The current count bitfield is in the IBS execution control h/w register, alongside the maximum count field.
Currently, the IBS driver writes that register with the maximum count, leaving zeroes to fill the current count field, thereby overwriting the random bits the hardware preloaded for itself.
Fix the driver to actually retain and carry those random bits from the read of the IBS control register, through to its write, instead of overwriting the lower current count bits with zeroes.
Tested with:
perf record -c 100001 -e ibs_op/cnt_ctl=1/pp -a -C 0 taskset -c 0 <workload>
'perf annotate' output before:
15.70 65: addsd %xmm0,%xmm1
17.30 add $0x1,%rax
15.88 cmp %rdx,%rax
je 82
17.32 72: test $0x1,%al
jne 7c
7.52 movapd %xmm1,%xmm0
5.90 jmp 65
8.23 7c: sqrtsd %xmm1,%xmm0
12.15 jmp 65'perf annotate' output after:
16.63 65: addsd %xmm0,%xmm1
16.82 add $0x1,%rax
16.81 cmp %rdx,%rax
je 82
16.69 72: test $0x1,%al
jne 7c
8.30 movapd %xmm1,%xmm0
8.13 jmp 65
8.24 7c: sqrtsd %xmm1,%xmm0
8.39 jmp 65Tested on Family 15h and 17h machines.
Machines prior to family 10h Rev. C don't have the RDWROPCNT capability, and have the IbsOpCurCnt bitfield reserved, so this patch shouldn't affect their operation.
It is unknown why commit db98c5faf8cb ("perf/x86: Implement 64-bit counter support for IBS") ignored the lower 4 bits of the IbsOpCurCnt field; the number of preloaded random bits has always been 7, AFAICT.
--- arch/x86/events/amd/ibs.c | 13 ++++++++++--- arch/x86/include/asm/perf_event.h | 12 ++++++++---- 2 files changed, 18 insertions(+), 7 deletions(-)
arch/x86/events/amd/ibs.c +10 -3
@@ -672,10 +672,17 @@ fail: throttle =perf_event_overflow (event, &data, ®s); out: -if (throttle) +if (throttle) {perf_ibs_stop (event,0 ); -else -perf_ibs_enable_event (perf_ibs, hwc, period >>4 ); + }else { + period >>=4 ; + +if ((ibs_caps &IBS_CAPS_RDWROPCNT ) && + (*config &IBS_OP_CNT_CTL )) + period |= *config &IBS_OP_CUR_CNT_RAND ; + +perf_ibs_enable_event (perf_ibs, hwc, period); + }perf_event_update_userpage (event);
arch/x86/include/asm/perf_event.h +8 -4
@@ -209,16 +209,20 @@ struct x86_pmu_capability {#define IBSCTL_LVT_OFFSET_VALID (1ULL<<8)#define IBSCTL_LVT_OFFSET_MASK 0x0F -/* ibs fetch bits/masks */ +/* IBS fetch bits/masks */ #define IBS_FETCH_RAND_EN (1ULL<<57)#define IBS_FETCH_VAL (1ULL<<49)#define IBS_FETCH_ENABLE (1ULL<<48)#define IBS_FETCH_CNT 0xFFFF0000ULL#define IBS_FETCH_MAX_CNT 0x0000FFFFULL -/* ibs op bits/masks */ -/* lower 4 bits of the current count are ignored: */ -#define IBS_OP_CUR_CNT (0xFFFF0ULL<<32) +/* +* IBS op bits/masks +* The lower 7 bits of the current count are random bits +* preloaded by hardware and ignored in software +*/ +#define IBS_OP_CUR_CNT (0xFFF80ULL<<32) +#define IBS_OP_CUR_CNT_RAND (0x0007FULL<<32)#define IBS_OP_CNT_CTL (1ULL<<19)#define IBS_OP_VAL (1ULL<<18)#define IBS_OP_ENABLE (1ULL<<17)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 61/79 amd-xgbe: Fix error path in xgbe_mod_init()
In reply to Greg Kroah-HartmanFrom: YueHaibing <[email protected]>
[ Upstream commit b6b4dc4c1fa7f1c99398e7dc85758049645e9588 ]
In xgbe_mod_init(), we should do cleanup if some error occurs
--- drivers/net/ethernet/amd/xgbe/xgbe-main.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/net/ethernet/amd/xgbe/xgbe-main.c +8 -2
@@ -469,13 +469,19 @@ static int __init xgbe_mod_init(void) ret =xgbe_platform_init ();if (ret) -return ret; + goto err_platform_init; ret =xgbe_pci_init ();if (ret) -return ret; + goto err_pci_init;return 0 ; + +err_pci_init: +xgbe_platform_exit (); +err_platform_init: +unregister_netdevice_notifier (&xgbe_netdev_notifier); +return ret; } static void __exit xgbe_mod_exit(void)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 62/79 tools/power x86_energy_perf_policy: Fix "uninitialized variable" warnings at -O2
In reply to Greg Kroah-HartmanFrom: Ben Hutchings <[email protected]>
[ Upstream commit adb8049097a9ec4acd09fbd3aa8636199a78df8a ]
x86_energy_perf_policy first uses __get_cpuid() to check the maximum CPUID level and exits if it is too low. It then assumes that later calls will succeed (which I think is architecturally guaranteed). It also assumes that CPUID works at all (which is not guaranteed on x86_32).
If optimisations are enabled, gcc warns about potentially uninitialized variables. Fix this by adding an exit-on-error after every call to __get_cpuid() instead of just checking the maximum level.
--- .../x86_energy_perf_policy.c | 26 +++++++++++-------- 1 file changed, 15 insertions(+), 11 deletions(-)
tools/power/x86/x86_energy_perf_policy/x86_energy_perf_policy.c +15 -11
@@ -1260,6 +1260,15 @@ void probe_dev_msr(void)if (system ("/sbin/modprobe msr > /dev/null 2>&1" ))err (-5 ,"no /dev/cpu/0/msr, Try \"# modprobe msr\" " ); } + +static void get_cpuid_or_exit (unsigned int leaf, +unsigned int *eax,unsigned int *ebx, +unsigned int *ecx,unsigned int *edx) +{ +if (!__get_cpuid (leaf, eax, ebx, ecx, edx)) +errx (1 ,"Processor not supported\n" ); +} +/* * early_cpuid() * initialize turbo_is_enabled, has_hwp, has_epb
@@ -1267,15 +1276,10 @@ void probe_dev_msr(void)*/ void early_cpuid (void ) { -unsigned int eax, ebx, ecx, edx, max_level; +unsigned int eax, ebx, ecx, edx;unsigned int fms, family, model; -__get_cpuid (0 , &max_level, &ebx, &ecx, &edx); - -if (max_level <6 ) -errx (1 ,"Processor not supported\n" ); - -__get_cpuid (1 , &fms, &ebx, &ecx, &edx); +get_cpuid_or_exit (1 , &fms, &ebx, &ecx, &edx); family = (fms >>8 ) &0xf ; model = (fms >>4 ) &0xf ;if (family ==6 || family ==0xf )
@@ -1289,7 +1293,7 @@ void early_cpuid(void) bdx_highest_ratio = msr &0xFF ; } -__get_cpuid (0x6 , &eax, &ebx, &ecx, &edx); +get_cpuid_or_exit (0x6 , &eax, &ebx, &ecx, &edx); turbo_is_enabled = (eax >>1 ) &1 ; has_hwp = (eax >>7 ) &1 ; has_epb = (ecx >>3 ) &1 ;
@@ -1307,7 +1311,7 @@ void parse_cpuid(void) eax = ebx = ecx = edx =0 ; -__get_cpuid (0 , &max_level, &ebx, &ecx, &edx); +get_cpuid_or_exit (0 , &max_level, &ebx, &ecx, &edx);if (ebx ==0x756e6547 && edx ==0x49656e69 && ecx ==0x6c65746e ) genuine_intel =1 ;
@@ -1316,7 +1320,7 @@ void parse_cpuid(void)fprintf (stderr,"CPUID(0): %.4s%.4s%.4s " , (char *)&ebx, (char *)&edx, (char *)&ecx); -__get_cpuid (1 , &fms, &ebx, &ecx, &edx); +get_cpuid_or_exit (1 , &fms, &ebx, &ecx, &edx); family = (fms >>8 ) &0xf ; model = (fms >>4 ) &0xf ; stepping = fms &0xf ;
@@ -1341,7 +1345,7 @@ void parse_cpuid(void)errx (1 ,"CPUID: no MSR" ); -__get_cpuid (0x6 , &eax, &ebx, &ecx, &edx); +get_cpuid_or_exit (0x6 , &eax, &ebx, &ecx, &edx);/* turbo_is_enabled already set */ /* has_hwp already set */ has_hwp_notify = eax & (1 <<8 );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 63/79 tools/power x86_energy_perf_policy: Fix argument parsing
In reply to Greg Kroah-HartmanFrom: Zephaniah E. Loss-Cutler-Hull <[email protected]>
[ Upstream commit 03531482402a2bc4ab93cf6dde46833775e035e9 ]
The -w argument in x86_energy_perf_policy currently triggers an unconditional segfault.
This is because the argument string reads: "+a:c:dD:E:e:f:m:M:rt:u:vw" and yet the argument handler expects an argument.
When parse_optarg_string is called with a null argument, we then proceed to crash in strncmp, not horribly friendly.
The man page describes -w as taking an argument, the long form (--hwp-window) is correctly marked as taking a required argument, and the code expects it.
As such, this patch simply marks the short form (-w) as requiring an argument.
--- tools/power/x86/x86_energy_perf_policy/x86_energy_perf_policy.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/power/x86/x86_energy_perf_policy/x86_energy_perf_policy.c +1 -1
@@ -546,7 +546,7 @@ void cmdline(int argc, char **argv) progname = argv[0 ]; -while ((opt =getopt_long_only (argc, argv,"+a:c:dD:E:e:f:m:M:rt:u:vw" , +while ((opt =getopt_long_only (argc, argv,"+a:c:dD:E:e:f:m:M:rt:u:vw:" , long_options, &option_index)) !=-1 ) {switch (opt) {case 'a' :
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 64/79 tools/power turbostat: fix buffer overrun
In reply to Greg Kroah-HartmanFrom: Naoya Horiguchi <[email protected]>
[ Upstream commit eeb71c950bc6eee460f2070643ce137e067b234c ]
turbostat could be terminated by general protection fault on some latest hardwares which (for example) support 9 levels of C-states and show 18 "tADDED" lines. That bloats the total output and finally causes buffer overrun. So let's extend the buffer to avoid this.
--- tools/power/x86/turbostat/turbostat.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/power/x86/turbostat/turbostat.c +1 -1
@@ -4953,7 +4953,7 @@ int initialize_counters(int cpu_id)void allocate_output_buffer () { - output_buffer =calloc (1 , (1 + topo.num_cpus) *1024 ); + output_buffer =calloc (1 , (1 + topo.num_cpus) *2048 ); outp = output_buffer;if (outp ==NULL )err (-1 ,"calloc output buffer" );
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 65/79 net: aquantia: fix out of memory condition on rx side
In reply to Greg Kroah-HartmanFrom: Dmitry Bogdanov <[email protected]>
[ Upstream commit be6cef69ba570ebb327eba1ef6438f7af49aaf86 ]
On embedded environments with hard memory limits it is a normal although rare case when skb can't be allocated on rx part under high traffic.
In such OOM cases napi_complete_done() was not called.
So the napi object became in an invalid state like it is "scheduled". Kernel do not re-schedules the poll of that napi object.
Consequently, kernel can not remove that object the system hangs on ifconfig down waiting for a poll.
We are fixing this by gracefully closing napi poll routine with correct invocation of napi_complete_done.
This was reproduced with artificially failing the allocation of skb to simulate an "out of memory" error case and check that traffic does not get stuck.
--- drivers/net/ethernet/aquantia/atlantic/aq_vec.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/aquantia/atlantic/aq_vec.c +2 -1
@@ -89,6 +89,7 @@ static int aq_vec_poll(struct napi_struct *napi, int budget) } } +err_exit:if (!was_tx_cleaned) work_done = budget;
@@ -98,7 +99,7 @@ static int aq_vec_poll(struct napi_struct *napi, int budget) 1U << self->aq_ring_param.vec_idx); } } -err_exit: +return work_done; }
Signature · 1 line
2.20.1
Re: [PATCH 4.19 65/79] net: aquantia: fix out of memory condition on rx side
Hi!
Quoted 23 lines
[ Upstream commit
be6cef69ba570ebb327eba1ef6438f7af49aaf86]On embedded environments with hard memory limits it is a normal although rare case when skb can't be allocated on rx part under high traffic.
In such OOM cases
napi_complete_done()was not called.
So the napi object became in an invalid state like it is "scheduled". Kernel do not re-schedules the poll of that napi object.Consequently, kernel can not remove that object the system hangs on
ifconfig downwaiting for a poll.We are fixing this by gracefully closing napi poll routine with correct invocation of
napi_complete_done.This was reproduced with artificially failing the allocation of skb to simulate an "out of memory" error case and check that traffic does not get stuck.
drivers/net/ethernet/aquantia/atlantic/aq_vec.c static int aq_vec_poll(struct napi_struct *napi, int budget) · line 95
Quoted 7 lines
drivers/net/ethernet/aquantia/atlantic/aq_vec.c +1
-0@@ -89,6 +89,7 @@ static int aq_vec_poll(struct napi_struct *napi, int budget) } } +err_exit:if (!was_tx_cleaned) work_done = budget;
This results in some... really "interesting" code that could use some refactoring.
First, "goto err_exit" is now same as break.
Second, if (!self) now sets variable that is never used. "if (!self) return 0;" would be more readable and would allow for less confusing indentation.
Best regards,
Pavel
Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Greg Kroah-Hartman
maintainerPATCH 66/79 net: seeq: Fix the function used to release some memory in an error handling path
In reply to Greg Kroah-HartmanFrom: Christophe JAILLET <[email protected]>
[ Upstream commit e1e54ec7fb55501c33b117c111cb0a045b8eded2 ]
In commit 99cd149efe82 ("sgiseeq: replace use of dma_cache_wback_inv"), a call to 'get_zeroed_page()' has been turned into a call to 'dma_alloc_coherent()'. Only the remove function has been updated to turn the corresponding 'free_page()' into 'dma_free_attrs()'.
The error hndling path of the probe function has not been updated.
Fix it now.
Rename the corresponding label to something more in line.
--- drivers/net/ethernet/seeq/sgiseeq.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/net/ethernet/seeq/sgiseeq.c +4 -3
@@ -793,15 +793,16 @@ static int sgiseeq_probe(struct platform_device *pdev)printk (KERN_ERR "Sgiseeq: Cannot register net device, " "aborting.\n" ); err = -ENODEV ; - goto err_out_free_page; + goto err_out_free_attrs; }printk (KERN_INFO "%s: %s %pM\n" , dev->name, sgiseeqstr, dev->dev_addr);return 0 ; -err_out_free_page: -free_page ((unsigned long ) sp->srings); +err_out_free_attrs: +dma_free_attrs (&pdev->dev,sizeof (*sp->srings), sp->srings, + sp->srings_dma,DMA_ATTR_NON_CONSISTENT ); err_out_free_dev:free_netdev (dev);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 67/79 dmaengine: ti: dma-crossbar: Fix a memory leak bug
In reply to Greg Kroah-HartmanFrom: Wenwen Wang <[email protected]>
[ Upstream commit 2c231c0c1dec42192aca0f87f2dc68b8f0cbc7d2 ]
In ti_dra7_xbar_probe(), 'rsv_events' is allocated through kcalloc(). Then of_property_read_u32_array() is invoked to search for the property. However, if this process fails, 'rsv_events' is not deallocated, leading to a memory leak bug. To fix this issue, free 'rsv_events' before returning the error.
--- drivers/dma/ti/dma-crossbar.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/dma/ti/dma-crossbar.c +3 -1
@@ -395,8 +395,10 @@ static int ti_dra7_xbar_probe(struct platform_device *pdev) ret =of_property_read_u32_array (node, pname, (u32 *)rsv_events, nelm *2 ); -if (ret) +if (ret) { +kfree (rsv_events);return ret; + }for (i =0 ; i < nelm; i++) { ti_dra7_xbar_reserve(rsv_events[i][0], rsv_events[i][1],
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 68/79 dmaengine: ti: omap-dma: Add cleanup in omap_dma_probe()
In reply to Greg Kroah-HartmanFrom: Wenwen Wang <[email protected]>
[ Upstream commit 962411b05a6d3342aa649e39cda1704c1fc042c6 ]
If devm_request_irq() fails to disable all interrupts, no cleanup is performed before retuning the error. To fix this issue, invoke omap_dma_free() to do the cleanup.
--- drivers/dma/ti/omap-dma.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/dma/ti/omap-dma.c +3 -1
@@ -1543,8 +1543,10 @@ static int omap_dma_probe(struct platform_device *pdev) rc =devm_request_irq (&pdev->dev, irq, omap_dma_irq,IRQF_SHARED ,"omap-dma-engine" , od); -if (rc) +if (rc) { +omap_dma_free (od);return rc; + } }if (omap_dma_glbl_read (od,CAPS_0 ) &CAPS_0_SUPPORT_LL123 )
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 69/79 x86/uaccess: Dont leak the AC flags into __get_user() argument evaluation
In reply to Greg Kroah-HartmanFrom: Peter Zijlstra <[email protected]>
[ Upstream commit 9b8bd476e78e89c9ea26c3b435ad0201c3d7dbf5 ]
Identical to __put_user(); the __get_user() argument evalution will too leak UBSAN crud into the __uaccess_begin() / __uaccess_end() region. While uncommon this was observed to happen for:
drivers/xen/gntdev.c: if (__get_user(old_status, batch->status[i]))
where UBSAN added array bound checking.
This complements commit:
6ae865615fc4 ("x86/uaccess: Dont leak the AC flag into __put_user() argument evaluation")
Tested-by Sedat Dilek <[email protected]>
--- arch/x86/include/asm/uaccess.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
arch/x86/include/asm/uaccess.h +3 -1
@@ -451,8 +451,10 @@ do { \ ({ \ int __gu_err; \ __inttype(*(ptr)) __gu_val; \ + __typeof__(ptr) __gu_ptr = (ptr); \ + __typeof__(size) __gu_size = (size); \ __uaccess_begin_nospec(); \ - __get_user_size(__gu_val, (ptr), (size), __gu_err, -EFAULT); \ + __get_user_size(__gu_val, __gu_ptr, __gu_size, __gu_err, -EFAULT); \ __uaccess_end(); \ (x) = (__force __typeof__(*(ptr)))__gu_val; \ __builtin_expect(__gu_err, 0); \
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 70/79 x86/hyper-v: Fix overflow bug in fill_gva_list()
In reply to Greg Kroah-HartmanFrom: Tianyu Lan <[email protected]>
[ Upstream commit 4030b4c585c41eeefec7bd20ce3d0e100a0f2e4d ]
When the 'start' parameter is >= 0xFF000000 on 32-bit systems, or >= 0xFFFFFFFF'FF000000 on 64-bit systems, fill_gva_list() gets into an infinite loop.
With such inputs, 'cur' overflows after adding HV_TLB_FLUSH_UNIT and always compares as less than end. Memory is filled with guest virtual addresses until the system crashes.
Fix this by never incrementing 'cur' to be larger than 'end'.
--- arch/x86/hyperv/mmu.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
arch/x86/hyperv/mmu.c +5 -3
@@ -37,12 +37,14 @@ static inline int fill_gva_list(u64 gva_list[], int offset,* Lower 12 bits encode the number of additional * pages to flush (in addition to the 'cur' page). */ -if (diff >=HV_TLB_FLUSH_UNIT ) +if (diff >=HV_TLB_FLUSH_UNIT ) { gva_list[gva_n] |= ~PAGE_MASK ; -else if (diff) + cur +=HV_TLB_FLUSH_UNIT ; + }else if (diff) { gva_list[gva_n] |= (diff -1 ) >>PAGE_SHIFT ; + cur = end; + } - cur +=HV_TLB_FLUSH_UNIT ; gva_n++; }while (cur < end);
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 71/79 keys: Fix missing null pointer check in request_key_auth_describe()
In reply to Greg Kroah-HartmanFrom: Hillf Danton <[email protected]>
[ Upstream commit d41a3effbb53b1bcea41e328d16a4d046a508381 ]
If a request_key authentication token key gets revoked, there's a window in which request_key_auth_describe() can see it with a NULL payload - but it makes no check for this and something like the following oops may occur:
BUG: Kernel NULL pointer dereference at 0x00000038 Faulting instruction address: 0xc0000000004ddf30 Oops: Kernel access of bad area, sig: 11 [#1] ... NIP [...] request_key_auth_describe+0x90/0xd0 LR [...] request_key_auth_describe+0x54/0xd0 Call Trace: [...] request_key_auth_describe+0x54/0xd0 (unreliable) [...] proc_keys_show+0x308/0x4c0 [...] seq_read+0x3d0/0x540 [...] proc_reg_read+0x90/0x110 [...] __vfs_read+0x3c/0x70 [...] vfs_read+0xb4/0x1b0 [...] ksys_read+0x7c/0x130 [...] system_call+0x5c/0x70
Fix this by checking for a NULL pointer when describing such a key.
Also make the read routine check for a NULL pointer to be on the safe side.
[DH: Modified to not take already-held rcu lock and modified to also check
in the read routine]
--- security/keys/request_key_auth.c | 6 ++++++ 1 file changed, 6 insertions(+)
security/keys/request_key_auth.c +6 -0
@@ -71,6 +71,9 @@ static void request_key_auth_describe(const struct key *key, {struct request_key_auth *rka =get_request_key_auth (key); +if (!rka) +return ; +seq_puts (m,"key:" );seq_puts (m, key->description);if (key_is_positive (key))
@@ -88,6 +91,9 @@ static long request_key_auth_read(const struct key *key,size_t datalen;long ret; +if (!rka) +return -EKEYREVOKED ; + datalen = rka->callout_len; ret = datalen;
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 72/79 iommu/amd: Flush old domains in kdump kernel
In reply to Greg Kroah-HartmanFrom: Stuart Hayes <[email protected]>
[ Upstream commit 36b7200f67dfe75b416b5281ed4ace9927b513bc ]
When devices are attached to the amd_iommu in a kdump kernel, the old device table entries (DTEs), which were copied from the crashed kernel, will be overwritten with a new domain number. When the new DTE is written, the IOMMU is told to flush the DTE from its internal cache--but it is not told to flush the translation cache entries for the old domain number.
Without this patch, AMD systems using the tg3 network driver fail when kdump tries to save the vmcore to a network system, showing network timeouts and (sometimes) IOMMU errors in the kernel log.
This patch will flush IOMMU translation cache entries for the old domain when a DTE gets overwritten with a new domain number.
--- drivers/iommu/amd_iommu.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
drivers/iommu/amd_iommu.c +24 -0
@@ -1153,6 +1153,17 @@ static void amd_iommu_flush_tlb_all(struct amd_iommu *iommu)iommu_completion_wait (iommu); } +static void amd_iommu_flush_tlb_domid (struct amd_iommu *iommu,u32 dom_id) +{ +struct iommu_cmd cmd; + +build_inv_iommu_pages (&cmd,0 ,CMD_INV_IOMMU_ALL_PAGES_ADDRESS , + dom_id,1 ); +iommu_queue_command (iommu, &cmd); + +iommu_completion_wait (iommu); +} +static void amd_iommu_flush_all (struct amd_iommu *iommu) {struct iommu_cmd cmd;
@@ -1838,6 +1849,7 @@ static void set_dte_entry(u16 devid, struct protection_domain *domain, {u64 pte_root =0 ;u64 flags =0 ; +u32 old_domid;if (domain->mode !=PAGE_MODE_NONE ) pte_root =iommu_virt_to_phys (domain->pt_root);
@@ -1887,8 +1899,20 @@ static void set_dte_entry(u16 devid, struct protection_domain *domain, flags &= ~DEV_DOMID_MASK ; flags |= domain->id; + old_domid = amd_iommu_dev_table[devid].data[1 ] &DEV_DOMID_MASK ; amd_iommu_dev_table[devid].data[1 ] = flags; amd_iommu_dev_table[devid].data[0 ] = pte_root; + +/* +* A kdump kernel might be replacing a domain ID that was copied from +* the previous kernel--if so, it needs to flush the translation cache +* entries for the old domain ID that is being overwritten +*/ +if (old_domid) { +struct amd_iommu *iommu = amd_iommu_rlookup_table[devid]; + +amd_iommu_flush_tlb_domid (iommu, old_domid); + } }static void clear_dte_entry (u16 devid)
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 73/79 iommu/amd: Fix race in increase_address_space()
In reply to Greg Kroah-HartmanFrom: Joerg Roedel <[email protected]>
[ Upstream commit 754265bcab78a9014f0f99cd35e0d610fcd7dfa7 ]
After the conversion to lock-less dma-api call the increase_address_space() function can be called without any locking. Multiple CPUs could potentially race for increasing the address space, leading to invalid domain->mode settings and invalid page-tables. This has been happening in the wild under high IO load and memory pressure.
Fix the race by locking this operation. The function is called infrequently so that this does not introduce a performance regression in the dma-api path again.
--- drivers/iommu/amd_iommu.c | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-)
drivers/iommu/amd_iommu.c +11 -5
@@ -1340,18 +1340,21 @@ static void domain_flush_devices(struct protection_domain *domain)* another level increases the size of the address space by 9 bits to a size up * to 64 bits. */ -static bool increase_address_space (struct protection_domain *domain, +static void increase_address_space (struct protection_domain *domain,gfp_t gfp) { +unsigned long flags;u64 *pte; -if (domain->mode ==PAGE_MODE_6_LEVEL ) +spin_lock_irqsave (&domain->lock, flags); + +if (WARN_ON_ONCE (domain->mode ==PAGE_MODE_6_LEVEL ))/* address space already 64 bit large */ -return false; + goto out; pte = (void *)get_zeroed_page (gfp);if (!pte) -return false; + goto out; *pte =PM_LEVEL_PDE (domain->mode,iommu_virt_to_phys (domain->pt_root));
@@ -1359,7 +1362,10 @@ static bool increase_address_space(struct protection_domain *domain, domain->mode +=1 ; domain->updated = true; -return true; +out: +spin_unlock_irqrestore (&domain->lock, flags); + +return ; } static u64 *alloc_pte(struct protection_domain *domain,
Signature · 1 line
2.20.1
Greg Kroah-Hartman
maintainerPATCH 74/79 PCI: kirin: Fix section mismatch warning
In reply to Greg Kroah-HartmanFrom: Nathan Chancellor <[email protected]>
commit 6870b673509779195cab300aedc844b352d9cfbc upstream.
The PCI kirin driver compilation produces the following section mismatch warning:
WARNING: vmlinux.o(.text+0x4758cc): Section mismatch in reference from the function kirin_pcie_probe() to the function .init.text:kirin_add_pcie_port()
The function kirin_pcie_probe() references
the function __init kirin_add_pcie_port().
This is often because kirin_pcie_probe lacks a __init annotation or the annotation of kirin_add_pcie_port is wrong.
Remove '__init' from kirin_add_pcie_port() to fix it.
--- drivers/pci/controller/dwc/pcie-kirin.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/pci/controller/dwc/pcie-kirin.c +2 -2
@@ -467,8 +467,8 @@ static int kirin_pcie_add_msi(struct dw_return 0 ; } -static int __init kirin_add_pcie_port (struct dw_pcie *pci, -struct platform_device *pdev) +static int kirin_add_pcie_port (struct dw_pcie *pci, +struct platform_device *pdev) {int ret;
Greg Kroah-Hartman
maintainerPATCH 75/79 ovl: fix regression caused by overlapping layers detection
In reply to Greg Kroah-HartmanFrom: Amir Goldstein <[email protected]>
commit 0be0bfd2de9dfdd2098a9c5b14bdd8f739c9165d upstream.
Once upon a time, commit 2cac0c00a6cd ("ovl: get exclusive ownership on upper/work dirs") in v4.13 added some sanity checks on overlayfs layers. This change caused a docker regression. The root cause was mount leaks by docker, which as far as I know, still exist.
To mitigate the regression, commit 85fdee1eef1a ("ovl: fix regression caused by exclusive upper/work dir protection") in v4.14 turned the mount errors into warnings for the default index=off configuration.
Recently, commit 146d62e5a586 ("ovl: detect overlapping layers") in v5.2, re-introduced exclusive upper/work dir checks regardless of index=off configuration.
This changes the status quo and mount leak related bug reports have started to re-surface. Restore the status quo to fix the regressions. To clarify, index=off does NOT relax overlapping layers check for this ovelayfs mount. index=off only relaxes exclusive upper/work dir checks with another overlayfs mount.
To cover the part of overlapping layers detection that used the exclusive upper/work dir checks to detect overlap with self upper/work dir, add a trap also on the work base dir.
--- Documentation/filesystems/overlayfs.txt | 2 fs/overlayfs/ovl_entry.h | 1 fs/overlayfs/super.c | 73 ++++++++++++++++++++------------ 3 files changed, 49 insertions(+), 27 deletions(-)
Documentation/filesystems/overlayfs.txt +1 -1
@@ -302,7 +302,7 @@ beneath or above the path of another ove Using an upper layer path and/or a workdir path that are already used by another overlay mount is not allowed and may fail with EBUSY. Using -partially overlapping paths is not allowed but will not fail with EBUSY. +partially overlapping paths is not allowed and may fail with EBUSY. If files are accessed from two overlayfs mounts which share or overlap the upper layer and/or workdir path the behavior of the overlay is undefined, though it will not result in a crash or deadlock.
fs/overlayfs/ovl_entry.h +1 -0
@@ -69,6 +69,7 @@ struct ovl_fs {bool workdir_locked;/* Traps in ovl inode cache */ struct inode *upperdir_trap; +struct inode *workbasedir_trap;struct inode *workdir_trap;struct inode *indexdir_trap;/* Inode numbers in all layers do not use the high xino_bits */
fs/overlayfs/super.c +47 -26
146 lines not on this page · raw message
Greg Kroah-Hartman
maintainerPATCH 76/79 floppy: fix usercopy direction
In reply to Greg Kroah-HartmanFrom: Jann Horn <[email protected]>
commit 52f6f9d74f31078964ca1574f7bb612da7877ac8 upstream.
As sparse points out, these two copy_from_user() should actually be copy_to_user().
--- drivers/block/floppy.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/block/floppy.c +2 -2
@@ -3791,7 +3791,7 @@ static int compat_getdrvprm(int drive, v.native_format =UDP ->native_format;mutex_unlock (&floppy_mutex); -if (copy_from_user (arg, &v,sizeof (struct compat_floppy_drive_params ))) +if (copy_to_user (arg, &v,sizeof (struct compat_floppy_drive_params )))return -EFAULT ;return 0 ; }
@@ -3827,7 +3827,7 @@ static int compat_getdrvstat(int drive, v.bufblocks =UDRS ->bufblocks;mutex_unlock (&floppy_mutex); -if (copy_from_user (arg, &v,sizeof (struct compat_floppy_drive_struct ))) +if (copy_to_user (arg, &v,sizeof (struct compat_floppy_drive_struct )))return -EFAULT ;return 0 ; Eintr:
Greg Kroah-Hartman
maintainerPATCH 77/79 binfmt_elf: move brk out of mmap when doing direct loader exec
In reply to Greg Kroah-HartmanFrom: Kees Cook <[email protected]>
commit bbdc6076d2e5d07db44e74c11b01a3e27ab90b32 upstream.
Commmit eab09532d400 ("binfmt_elf: use ELF_ET_DYN_BASE only for PIE"), made changes in the rare case when the ELF loader was directly invoked (e.g to set a non-inheritable LD_LIBRARY_PATH, testing new versions of the loader), by moving into the mmap region to avoid both ET_EXEC and PIE binaries. This had the effect of also moving the brk region into mmap, which could lead to the stack and brk being arbitrarily close to each other. An unlucky process wouldn't get its requested stack size and stack allocations could end up scribbling on the heap.
This is illustrated here. In the case of using the loader directly, brk (so helpfully identified as "[heap]") is allocated with the _loader_ not the binary. For example, with ASLR entirely disabled, you can see this more clearly:
$ /bin/cat /proc/self/maps 555555554000-55555555c000 r-xp 00000000 ... /bin/cat 55555575b000-55555575c000 r--p 00007000 ... /bin/cat 55555575c000-55555575d000 rw-p 00008000 ... /bin/cat 55555575d000-55555577e000 rw-p 00000000 ... [heap] ... 7ffff7ff7000-7ffff7ffa000 r--p 00000000 ... [vvar] 7ffff7ffa000-7ffff7ffc000 r-xp 00000000 ... [vdso] 7ffff7ffc000-7ffff7ffd000 r--p 00027000 ... /lib/x86_64-linux-gnu/ld-2.27.so 7ffff7ffd000-7ffff7ffe000 rw-p 00028000 ... /lib/x86_64-linux-gnu/ld-2.27.so 7ffff7ffe000-7ffff7fff000 rw-p 00000000 ... 7ffffffde000-7ffffffff000 rw-p 00000000 ... [stack]
$ /lib/x86_64-linux-gnu/ld-2.27.so /bin/cat /proc/self/maps ... 7ffff7bcc000-7ffff7bd4000 r-xp 00000000 ... /bin/cat 7ffff7bd4000-7ffff7dd3000 ---p 00008000 ... /bin/cat 7ffff7dd3000-7ffff7dd4000 r--p 00007000 ... /bin/cat 7ffff7dd4000-7ffff7dd5000 rw-p 00008000 ... /bin/cat 7ffff7dd5000-7ffff7dfc000 r-xp 00000000 ... /lib/x86_64-linux-gnu/ld-2.27.so 7ffff7fb2000-7ffff7fd6000 rw-p 00000000 ... 7ffff7ff7000-7ffff7ffa000 r--p 00000000 ... [vvar] 7ffff7ffa000-7ffff7ffc000 r-xp 00000000 ... [vdso] 7ffff7ffc000-7ffff7ffd000 r--p 00027000 ... /lib/x86_64-linux-gnu/ld-2.27.so 7ffff7ffd000-7ffff7ffe000 rw-p 00028000 ... /lib/x86_64-linux-gnu/ld-2.27.so 7ffff7ffe000-7ffff8020000 rw-p 00000000 ... [heap] 7ffffffde000-7ffffffff000 rw-p 00000000 ... [stack]
The solution is to move brk out of mmap and into ELF_ET_DYN_BASE since nothing is there in the direct loader case (and ET_EXEC is still far away at 0x400000). Anything that ran before should still work (i.e. the ultimately-launched binary already had the brk very far from its text, so this should be no different from a COMPAT_BRK standpoint). The only risk I see here is that if someone started to suddenly depend on the entire memory space lower than the mmap region being available when launching binaries via a direct loader execs which seems highly unlikely, I'd hope: this would mean a binary would _not_ work when exec()ed normally.
(Note that this is only done under CONFIG_ARCH_HAS_ELF_RANDOMIZATION when randomization is turned on.)
--- fs/binfmt_elf.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
fs/binfmt_elf.c +11 -0
@@ -1137,6 +1137,17 @@ static int load_elf_binary(struct linux_ current->mm->start_stack = bprm->p;if ((current->flags &PF_RANDOMIZE ) && (randomize_va_space >1 )) { +/* +* For architectures with ELF randomization, when executing +* a loader directly (i.e. no interpreter listed in ELF +* headers), move the brk area out of the mmap region +* (since it grows up, and may collide early with the stack +* growing down), and into the unused ELF_ET_DYN_BASE region. +*/ +if (IS_ENABLED (CONFIG_ARCH_HAS_ELF_RANDOMIZE ) && !interpreter) + current->mm->brk = current->mm->start_brk = +ELF_ET_DYN_BASE ; + current->mm->brk = current->mm->start_brk =arch_randomize_brk (current->mm);#ifdef compat_brk_randomized
Greg Kroah-Hartman
maintainerPATCH 78/79 arm64: kpti: Whitelist Cortex-A CPUs that dont implement the CSV3 field
In reply to Greg Kroah-HartmanFrom: Will Deacon <[email protected]>
commit 2a355ec25729053bb9a1a89b6c1d1cdd6c3b3fb1 upstream.
While the CSV3 field of the ID_AA64_PFR0 CPU ID register can be checked to see if a CPU is susceptible to Meltdown and therefore requires kpti to be enabled, existing CPUs do not implement this field.
We therefore whitelist all unaffected Cortex-A CPUs that do not implement the CSV3 field.
--- arch/arm64/kernel/cpufeature.c | 6 ++++++ 1 file changed, 6 insertions(+)
arch/arm64/kernel/cpufeature.c +6 -0
@@ -895,6 +895,12 @@ static bool unmap_kernel_at_el0(const ststatic const struct midr_range kpti_safe_list[] = {MIDR_ALL_VERSIONS (MIDR_CAVIUM_THUNDERX2 ),MIDR_ALL_VERSIONS (MIDR_BRCM_VULCAN ), +MIDR_ALL_VERSIONS (MIDR_CORTEX_A35 ), +MIDR_ALL_VERSIONS (MIDR_CORTEX_A53 ), +MIDR_ALL_VERSIONS (MIDR_CORTEX_A55 ), +MIDR_ALL_VERSIONS (MIDR_CORTEX_A57 ), +MIDR_ALL_VERSIONS (MIDR_CORTEX_A72 ), +MIDR_ALL_VERSIONS (MIDR_CORTEX_A73 ), {/* sentinel */ } };char const *str ="command line option" ;
Greg Kroah-Hartman
maintainerPATCH 79/79 media: technisat-usb2: break out of loop at end of buffer
In reply to Greg Kroah-HartmanFrom: Sean Young <[email protected]>
commit 0c4df39e504bf925ab666132ac3c98d6cbbe380b upstream.
Ensure we do not access the buffer beyond the end if no 0xff byte is encountered.
--- drivers/media/usb/dvb-usb/technisat-usb2.c | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-)
drivers/media/usb/dvb-usb/technisat-usb2.c +10 -12
@@ -607,10 +607,9 @@ static int technisat_usb2_frontend_attacstatic int technisat_usb2_get_ir (struct dvb_usb_device *d) {struct technisat_usb2_state *state = d->priv; -u8 *buf = state->buf; -u8 *b; -int ret;struct ir_raw_event ev; +u8 *buf = state->buf; +int i, ret; buf[0 ] =GET_IR_DATA_VENDOR_REQUEST ; buf[1 ] =0x08 ;
@@ -646,26 +645,25 @@ unlock:return 0 ;/* no key pressed */ /* decoding */ - b = buf+1 ;#if 0 deb_rc ("RC: %d " , ret); -debug_dump (b, ret, deb_rc); +debug_dump (buf +1 , ret, deb_rc);#endif ev.pulse =0 ; -while (1 ) { - ev.pulse = !ev.pulse; - ev.duration = (*b *FIRMWARE_CLOCK_DIVISOR *FIRMWARE_CLOCK_TICK ) /1000 ; -ir_raw_event_store (d->rc_dev, &ev); - - b++; -if (*b ==0xff ) { +for (i =1 ; i <ARRAY_SIZE (state->buf); i++) { +if (buf[i] ==0xff ) { ev.pulse =0 ; ev.duration =888888 *2 ;ir_raw_event_store (d->rc_dev, &ev);break ; } + + ev.pulse = !ev.pulse; + ev.duration = (buf[i] *FIRMWARE_CLOCK_DIVISOR * +FIRMWARE_CLOCK_TICK ) /1000 ; +ir_raw_event_store (d->rc_dev, &ev); }ir_raw_event_handle (d->rc_dev);
stable-rc/linux-4.19.y boot: 68 boots: 0 failed, 68 passed (v4.19.74-80-g42a609acc1b2)
stable-rc/linux-4.19.y boot: 68 boots: 0 failed, 68 passed (v4.19.74-80-g42a609acc1b2)
Full Boot Summary: https://kernelci.org/boot/all/job/stable-rc/branch/linux-4.19.y/kernel/v4.19.74-80-g42a609acc1b2/
Full Build Summary: https://kernelci.org/build/stable-rc/branch/linux-4.19.y/kernel/v4.19.74-80-g42a609acc1b2/
Tree: stable-rc
Branch: linux-4.19.y
Git Describe: v4.19.74-80-g42a609acc1b2
Git Commit: 42a609acc1b2b5a744dd9ad3d3eb6a71906e4bcc
Git URL: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Tested: 38 unique boards, 16 SoC families, 12 builds out of 206
---
For more info write to <[email protected]>
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.75 release. There are 79 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 Sat 21 Sep 2019 09:44:25 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.75-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.thanks,
greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Summary
------------------------------------------------------------------------
kernel: 4.19.75-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-4.19.y
git commit: 42a609acc1b2b5a744dd9ad3d3eb6a71906e4bcc
git describe: v4.19.74-80-g42a609acc1b2
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-4.19-oe/build/v4.19.74-80-g42a609acc1b2
No regressions (compared to build v4.19.74)
No fixes (compared to build v4.19.74)
Ran 21908 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c - arm64
- hi6220-hikey - arm64
- i386
- juno-r2 - arm64
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15 - arm
- x86_64
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* kselftest
* libhugetlbfs
* libgpiod
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-cpuhotplug-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-timers-tests
* network-basic-tests
* perf
* spectre-meltdown-checker-test
* v4l2-compliance
* ltp-open-posix-tests
* kvm-unit-tests
* ssuite
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Jon Hunter
maintainerQuoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.75 release. There are 79 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 Sat 21 Sep 2019 09:44:25 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 8 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.75-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v4.19:
12 builds: 12 pass, 0 fail
22 boots: 22 pass, 0 fail
32 tests: 32 pass, 0 failLinux version: 4.19.75-rc1-g42a609acc1b2
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra30-cardhu-a04Cheers
Jon
Signature · 1 line
nvpublic
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.75 release. There are 79 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 Sat 21 Sep 2019 09:44:25 PM UTC. Anything received after that time might be too late.
Build results:
total: 156 pass: 156 fail: 0 Qemu test results: total: 390 pass: 390 fail: 0
Guenter
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.75 release. There are 79 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 Sat 21 Sep 2019 09:44:25 PM UTC. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
Quoted 9 lines
https://www.kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.19.75-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-4.19.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah