5.8.13-rc1 review
Subsystems (3)
Greg Kroah-Hartman
maintainercover 5.8.13-rc1 review
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-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-5.8.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 5.8.13-rc1
Tony Lindgren <[email protected]>
clocksource/drivers/timer-ti-dm: Do reset before enable
Mike Snitzer <[email protected]>
dm: fix bio splitting and its bio completion order for regular IO
Marc Zyngier <[email protected]>
KVM: arm64: Assume write fault on S1PTW permission fault on instruction fetch
Jens Axboe <[email protected]>
io_uring: ensure open/openat2 name is cleaned on cancelation
Christian Borntraeger <[email protected]>
s390/zcrypt: Fix ZCRYPT_PERDEV_REQCNT ioctl
Laurent Dufour <[email protected]>
mm: don't rely on system state to detect hot-plug operations
Laurent Dufour <[email protected]>
mm: replace memmap_context by meminit_context
Vasily Gorbik <[email protected]>
mm/gup: fix gup_fast with dynamic page table folding
Gao Xiang <[email protected]>
mm, THP, swap: fix allocating cluster for swapfile by mistake
Charan Teja Reddy <[email protected]>
dmabuf: fix NULL pointer dereference in dma_buf_release()
Jiaxun Yang <[email protected]>
MIPS: Loongson2ef: Disable Loongson MMI instructions
Hans Verkuil <[email protected]>
media: cec-adap.c: don't use flush_scheduled_work()
Johannes Thumshirn <[email protected]>
btrfs: fix overflow when copying corrupt csums for a message
Anand Jain <[email protected]>
btrfs: fix put of uninitialized kobject after seed device delete
Masami Hiramatsu <[email protected]>
kprobes: tracing/kprobes: Fix to kill kprobes on initmem after boot
Masami Hiramatsu <[email protected]>
kprobes: Fix to check probe enabled before disarm_kprobe_ftrace()
Masami Hiramatsu <[email protected]>
lib/bootconfig: Fix to remove tailing spaces after value
Masami Hiramatsu <[email protected]>
lib/bootconfig: Fix a bug of breaking existing tree nodes
Felix Fietkau <[email protected]>
mt76: mt7615: use v1 MCU API on MT7615 to fix issues with adding/removing stations
Jan Höppner <[email protected]>
s390/dasd: Fix zero write for FBA devices
Tom Rix <[email protected]>
tracing: fix double free
Nick Desaulniers <[email protected]>
lib/string.c: implement stpcpy
Kai-Heng Feng <[email protected]>
ALSA: hda/realtek: Enable front panel headset LED on Lenovo ThinkStation P520
Hui Wang <[email protected]>
ALSA: hda/realtek - Couldn't detect Mic if booting with headset plugged
Joakim Tjernlund <[email protected]>
ALSA: usb-audio: Add delay quirk for H570e USB headsets
James Smart <[email protected]>
scsi: lpfc: Fix initial FLOGI failure due to BBSCN not supported
Thomas Gleixner <[email protected]>
x86/ioapic: Unbreak check_timer()
Thomas Gleixner <[email protected]>
x86/irq: Make run_on_irqstack_cond() typesafe
Mikulas Patocka <[email protected]>
arch/x86/lib/usercopy_64.c: fix __copy_user_flushcache() cache writeback
Minchan Kim <[email protected]>
mm: validate pmd after splitting
Tom Lendacky <[email protected]>
KVM: SVM: Add a dedicated INVD intercept routine
Sean Christopherson <[email protected]>
KVM: x86: Reset MMU context if guest toggles CR4.SMAP or CR4.PKE
Ray Jui <[email protected]>
spi: bcm-qspi: Fix probe regression on iProc platforms
Icenowy Zheng <[email protected]>
regulator: axp20x: fix LDO2/4 description
Wei Li <[email protected]>
MIPS: Add the missing 'CPU_1074K' into __get_cpu_type()
Dan Carpenter <[email protected]>
PM / devfreq: tegra30: Disable clock on error in probe
Huacai Chen <[email protected]>
MIPS: Loongson-3: Fix fp register access if MSA enabled
Saeed Mahameed <[email protected]>
net/mlx5e: mlx5e_fec_in_caps() returns a boolean
Dmitry Baryshkov <[email protected]>
regmap: fix page selection for noinc writes
Dmitry Baryshkov <[email protected]>
regmap: fix page selection for noinc reads
Chuck Lever <[email protected]>
SUNRPC: Fix svc_flush_dcache()
Jens Axboe <[email protected]>
io_uring: fix openat/openat2 unified prep handling
Tom Rix <[email protected]>
ALSA: asihpi: fix iounmap in error handler
John Crispin <[email protected]>
mac80211: fix 80 MHz association to 160/80+80 AP on 6 GHz
Johannes Berg <[email protected]>
cfg80211: fix 6 GHz channel conversion
Wen Gong <[email protected]>
mac80211: do not disable HE if HT is missing on 2.4 GHz
Necip Fazil Yildiran <[email protected]>
lib80211: fix unmet direct dependendices config warning when !CRYPTO
Yonghong Song <[email protected]>
bpf: Fix a rcu warning for bpffs map pretty-print
Linus Lüssing <[email protected]>
batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh
Linus Lüssing <[email protected]>
batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh
Linus Lüssing <[email protected]>
batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN
Necip Fazil Yildiran <[email protected]>
nvme-tcp: fix kconfig dependency warning when !CRYPTO
Björn Töpel <[email protected]>
xsk: Fix number of pinned pages/umem size discrepancy
Sven Eckelmann <[email protected]>
batman-adv: Add missing include for in_interrupt()
Jason Gunthorpe <[email protected]>
RDMA/core: Fix ordering of CQ pool destruction
Vladimir Oltean <[email protected]>
spi: spi-fsl-dspi: use XSPI mode instead of DMA for DPAA2 SoCs
Dexuan Cui <[email protected]>
hv_netvsc: Switch the data path at the right time during hibernation
Martin Cerveny <[email protected]>
drm/sun4i: sun8i-csc: Secondary CSC register correction
Vinicius Costa Gomes <[email protected]>
igc: Fix not considering the TX delay for timestamps
Vinicius Costa Gomes <[email protected]>
igc: Fix wrong timestamp latency numbers
Dmitry Bogdanov <[email protected]>
net: qed: RDMA personality shouldn't fail VF load
Dmitry Bogdanov <[email protected]>
net: qede: Disable aRFS for NPAR and 100G
Dmitry Bogdanov <[email protected]>
net: qed: Disable aRFS for NPAR and 100G
Marek Szyprowski <[email protected]>
drm/vc4/vc4_hdmi: fill ASoC card owner
Tony Ambardar <[email protected]>
tools/libbpf: Avoid counting local symbols in ABI check
Daniel Borkmann <[email protected]>
bpf: Fix clobbering of r2 in bpf_gen_ld_abs
Eric Dumazet <[email protected]>
mac802154: tx: fix use-after-free
Pablo Neira Ayuso <[email protected]>
netfilter: nft_meta: use socket user_ns to retrieve skuid and skgid
Eelco Chaudron <[email protected]>
netfilter: conntrack: nf_conncount_init is failing with IPv6 disabled
Martin Willi <[email protected]>
netfilter: ctnetlink: fix mark based dump filtering regression
Will McVicker <[email protected]>
netfilter: ctnetlink: add a range check for l3/l4 protonum
Linus Lüssing <[email protected]>
batman-adv: mcast/TT: fix wrongly dropped or rerouted packets
Jing Xiangfeng <[email protected]>
atm: eni: fix the missed pci_disable_device() for eni_init_one()
Tony Ambardar <[email protected]>
libbpf: Fix build failure from uninitialized variable warning
Linus Lüssing <[email protected]>
batman-adv: bla: fix type misuse for backbone_gw hash indexing
Maximilian Luz <[email protected]>
mwifiex: Increase AES key storage size to 256 bits
Tianjia Zhang <[email protected]>
clocksource/drivers/h8300_timer8: Fix wrong return value in h8300_8timer_init()
Tom Rix <[email protected]>
ieee802154/adf7242: check status of adf7242_read_reg
Liu Jian <[email protected]>
ieee802154: fix one possible memleak in ca8210_dev_com_init
Damien Le Moal <[email protected]>
riscv: Fix Kendryte K210 device tree
Qii Wang <[email protected]>
i2c: mediatek: Send i2c master code at more than 1MHz
Josh Poimboeuf <[email protected]>
objtool: Fix noreturn detection for ignored functions
Hans de Goede <[email protected]>
i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices()
Bhawanpreet Lakha <[email protected]>
drm/amd/display: Don't log hdcp module warnings in dmesg
Michel Dänzer <[email protected]>
drm/amdgpu/dc: Require primary plane to be enabled whenever the CRTC is
Jun Lei <[email protected]>
drm/amd/display: update nv1x stutter latencies
Bhawanpreet Lakha <[email protected]>
drm/amd/display: Don't use DRM_ERROR() for DTM add topology
Dennis Li <[email protected]>
drm/amdkfd: fix a memory leak issue
Borislav Petkov <[email protected]>
EDAC/ghes: Check whether the driver is on the safe list correctly
Sven Schnelle <[email protected]>
lockdep: fix order in trace_hardirqs_off_caller()
Ilya Leoshkevich <[email protected]>
s390/init: add missing __init annotations
Eddie James <[email protected]>
i2c: aspeed: Mask IRQ status to relevant bits
Palmer Dabbelt <[email protected]>
RISC-V: Take text_mutex in ftrace_init_nop()
Sumera Priyadarsini <[email protected]>
clk: versatile: Add of_node_put() before return statement
Hans de Goede <[email protected]>
ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN Converter9 2-in-1
Sylwester Nawrocki <[email protected]>
ASoC: wm8994: Ensure the device is resumed in wm89xx_mic_detect functions
Sylwester Nawrocki <[email protected]>
ASoC: wm8994: Skip setting of the WM8994_MICBIAS register for WM1811
Kuninori Morimoto <[email protected]>
ASoC: pcm3168a: ignore 0 Hz settings
Amol Grover <[email protected]>
device_cgroup: Fix RCU list debugging warning
-------------
Diffstat:
Makefile | 4 +- arch/arm64/include/asm/kvm_emulate.h | 12 +- arch/arm64/kvm/hyp/switch.c | 2 +- arch/arm64/kvm/mmio.c | 2 +- arch/arm64/kvm/mmu.c | 2 +- arch/ia64/mm/init.c | 6 +- arch/mips/include/asm/cpu-type.h | 1 + arch/mips/loongson2ef/Platform | 4 + arch/mips/loongson64/cop2-ex.c | 24 ++-- arch/riscv/boot/dts/kendryte/k210.dtsi | 6 +- arch/riscv/include/asm/ftrace.h | 7 + arch/riscv/kernel/ftrace.c | 19 +++ arch/s390/include/asm/pgtable.h | 42 ++++-- arch/s390/kernel/setup.c | 6 +- arch/x86/entry/common.c | 2 +- arch/x86/entry/entry_64.S | 2 + arch/x86/include/asm/idtentry.h | 2 +- arch/x86/include/asm/irq_stack.h | 70 ++++++++-- arch/x86/kernel/apic/io_apic.c | 1 + arch/x86/kernel/irq.c | 2 +- arch/x86/kernel/irq_64.c | 2 +- arch/x86/kvm/svm/svm.c | 8 +- arch/x86/kvm/x86.c | 3 +- arch/x86/lib/usercopy_64.c | 2 +- drivers/atm/eni.c | 2 +- drivers/base/node.c | 85 +++++++----- drivers/base/regmap/internal.h | 2 +- drivers/base/regmap/regcache.c | 2 +- drivers/base/regmap/regmap.c | 33 ++--- drivers/clk/versatile/clk-impd1.c | 4 +- drivers/clocksource/h8300_timer8.c | 2 +- drivers/clocksource/timer-ti-dm-systimer.c | 44 ++++--- drivers/devfreq/tegra30-devfreq.c | 4 +- drivers/dma-buf/dma-buf.c | 2 + drivers/edac/ghes_edac.c | 4 + .../gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 2 + drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 32 ++--- .../gpu/drm/amd/display/dc/dcn20/dcn20_resource.c | 4 +- .../gpu/drm/amd/display/modules/hdcp/hdcp_log.h | 2 +- .../gpu/drm/amd/display/modules/hdcp/hdcp_psp.c | 2 +- drivers/gpu/drm/sun4i/sun8i_csc.h | 2 +- drivers/gpu/drm/vc4/vc4_hdmi.c | 1 + drivers/i2c/busses/i2c-aspeed.c | 2 + drivers/i2c/busses/i2c-mt65xx.c | 2 +- drivers/i2c/i2c-core-base.c | 2 +- drivers/infiniband/core/device.c | 6 +- drivers/md/dm.c | 23 +--- drivers/media/cec/core/cec-adap.c | 2 +- drivers/net/ethernet/intel/igc/igc.h | 20 ++- drivers/net/ethernet/intel/igc/igc_ptp.c | 19 +++ drivers/net/ethernet/mellanox/mlx5/core/en/port.c | 7 +- drivers/net/ethernet/qlogic/qed/qed_dev.c | 11 +- drivers/net/ethernet/qlogic/qed/qed_l2.c | 3 + drivers/net/ethernet/qlogic/qed/qed_main.c | 2 + drivers/net/ethernet/qlogic/qed/qed_sriov.c | 1 + drivers/net/ethernet/qlogic/qede/qede_filter.c | 3 + drivers/net/ethernet/qlogic/qede/qede_main.c | 11 +- drivers/net/hyperv/netvsc_drv.c | 11 +- drivers/net/ieee802154/adf7242.c | 4 +- drivers/net/ieee802154/ca8210.c | 1 + drivers/net/wireless/marvell/mwifiex/fw.h | 2 +- drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c | 4 +- drivers/net/wireless/mediatek/mt76/mt7615/mcu.c | 3 +- drivers/nvme/host/Kconfig | 1 + drivers/regulator/axp20x-regulator.c | 7 +- drivers/s390/block/dasd_fba.c | 9 +- drivers/s390/crypto/zcrypt_api.c | 3 +- drivers/scsi/lpfc/lpfc_hbadisc.c | 76 +++++++---- drivers/spi/spi-bcm-qspi.c | 2 +- drivers/spi/spi-fsl-dspi.c | 6 +- fs/btrfs/disk-io.c | 11 +- fs/btrfs/sysfs.c | 16 ++- fs/io_uring.c | 8 +- include/linux/kprobes.h | 5 + include/linux/mm.h | 2 +- include/linux/mmzone.h | 11 +- include/linux/node.h | 11 +- include/linux/pgtable.h | 10 ++ include/linux/qed/qed_if.h | 1 + init/main.c | 2 + kernel/bpf/inode.c | 4 +- kernel/kprobes.c | 27 +++- kernel/trace/trace_events_hist.c | 1 - kernel/trace/trace_preemptirq.c | 4 +- lib/bootconfig.c | 38 ++++-- lib/string.c | 24 ++++ mm/gup.c | 18 +-- mm/madvise.c | 2 +- mm/memory_hotplug.c | 5 +- mm/page_alloc.c | 10 +- mm/swapfile.c | 2 +- net/batman-adv/bridge_loop_avoidance.c | 145 +++++++++++++++++---- net/batman-adv/bridge_loop_avoidance.h | 4 +- net/batman-adv/multicast.c | 46 +++++-- net/batman-adv/multicast.h | 15 +++ net/batman-adv/routing.c | 4 + net/batman-adv/soft-interface.c | 11 +- net/core/filter.c | 4 +- net/mac80211/mlme.c | 3 +- net/mac80211/util.c | 7 +- net/mac802154/tx.c | 8 +- net/netfilter/nf_conntrack_netlink.c | 22 +--- net/netfilter/nf_conntrack_proto.c | 2 + net/netfilter/nft_meta.c | 4 +- net/sunrpc/svcsock.c | 2 +- net/wireless/Kconfig | 1 + net/wireless/util.c | 2 +- net/xdp/xdp_umem.c | 17 ++- security/device_cgroup.c | 3 +- sound/pci/asihpi/hpioctl.c | 4 +- sound/pci/hda/patch_realtek.c | 13 +- sound/soc/codecs/pcm3168a.c | 7 + sound/soc/codecs/wm8994.c | 10 ++ sound/soc/codecs/wm_hubs.c | 3 + sound/soc/codecs/wm_hubs.h | 1 + sound/soc/intel/boards/bytcr_rt5640.c | 10 ++ sound/usb/quirks.c | 7 +- tools/lib/bpf/Makefile | 2 + tools/lib/bpf/libbpf.c | 2 +- tools/objtool/check.c | 2 +- 120 files changed, 866 insertions(+), 410 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/99 device_cgroup: Fix RCU list debugging warning
From: Amol Grover <[email protected]>
[ Upstream commit bc62d68e2a0a69fcdcf28aca8edb01abf306b698 ]
exceptions may be traversed using list_for_each_entry_rcu() outside of an RCU read side critical section BUT under the protection of decgroup_mutex. Hence add the corresponding lockdep expression to fix the following false-positive warning:
[ 2.304417] ============================= [ 2.304418] WARNING: suspicious RCU usage [ 2.304420] 5.5.4-stable #17 Tainted: G E [ 2.304422] ----------------------------- [ 2.304424] security/device_cgroup.c:355 RCU-list traversed in non-reader section!!
--- security/device_cgroup.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
security/device_cgroup.c +2 -1
@@ -354,7 +354,8 @@ static bool match_exception_partial(struct list_head *exceptions, short type, {struct dev_exception_item *ex; -list_for_each_entry_rcu (ex, exceptions, list) { +list_for_each_entry_rcu (ex, exceptions, list, +lockdep_is_held (&devcgroup_mutex)) {if ((type &DEVCG_DEV_BLOCK ) && !(ex->type &DEVCG_DEV_BLOCK ))continue ;if ((type &DEVCG_DEV_CHAR ) && !(ex->type &DEVCG_DEV_CHAR ))
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 2/99 ASoC: pcm3168a: ignore 0 Hz settings
In reply to Greg Kroah-HartmanFrom: Kuninori Morimoto <[email protected]>
[ Upstream commit 7ad26d6671db758c959d7e1d100b138a38483612 ]
Some sound card try to set 0 Hz as reset, but it is impossible. This patch ignores it to avoid error return.
--- sound/soc/codecs/pcm3168a.c | 7 +++++++ 1 file changed, 7 insertions(+)
sound/soc/codecs/pcm3168a.c +7 -0
@@ -306,6 +306,13 @@ static int pcm3168a_set_dai_sysclk(struct snd_soc_dai *dai,struct pcm3168a_priv *pcm3168a =snd_soc_component_get_drvdata (dai->component);int ret; +/* +* Some sound card sets 0 Hz as reset, +* but it is impossible to set. Ignore it here +*/ +if (freq ==0 ) +return 0 ; +if (freq >PCM3168A_MAX_SYSCLK )return -EINVAL ;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 3/99 ASoC: wm8994: Skip setting of the WM8994_MICBIAS register for WM1811
In reply to Greg Kroah-HartmanFrom: Sylwester Nawrocki <[email protected]>
[ Upstream commit 811c5494436789e7149487c06e0602b507ce274b ]
The WM8994_MICBIAS register is not available in the WM1811 CODEC so skip initialization of that register for that device.
This suppresses an error during boot:
"wm8994-codec: ASoC: error at snd_soc_component_update_bits on wm8994-codec"
--- sound/soc/codecs/wm8994.c | 2 ++ sound/soc/codecs/wm_hubs.c | 3 +++ sound/soc/codecs/wm_hubs.h | 1 + 3 files changed, 6 insertions(+)
sound/soc/codecs/wm8994.c +2 -0
@@ -4166,11 +4166,13 @@ static int wm8994_component_probe(struct snd_soc_component *component) wm8994->hubs.dcs_readback_mode =2 ;break ; } + wm8994->hubs.micd_scthr = true;break ;case WM8958 : wm8994->hubs.dcs_readback_mode =1 ; wm8994->hubs.hp_startup_mode =1 ; + wm8994->hubs.micd_scthr = true;switch (control->revision) {case 0 :
sound/soc/codecs/wm_hubs.c +3 -0
@@ -1223,6 +1223,9 @@ int wm_hubs_handle_analogue_pdata(struct snd_soc_component *component,snd_soc_component_update_bits (component,WM8993_ADDITIONAL_CONTROL ,WM8993_LINEOUT2_FB ,WM8993_LINEOUT2_FB ); +if (!hubs->micd_scthr) +return 0 ; + snd_soc_component_update_bits(component, WM8993_MICBIAS, WM8993_JD_SCTHR_MASK | WM8993_JD_THR_MASK | WM8993_MICB1_LVL | WM8993_MICB2_LVL,
sound/soc/codecs/wm_hubs.h +1 -0
@@ -27,6 +27,7 @@ struct wm_hubs_data {int hp_startup_mode;int series_startup;int no_series_update; +bool micd_scthr;bool no_cache_dac_hp_direct;struct list_head dcs_cache;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 4/99 ASoC: wm8994: Ensure the device is resumed in wm89xx_mic_detect functions
In reply to Greg Kroah-HartmanFrom: Sylwester Nawrocki <[email protected]>
[ Upstream commit f5a2cda4f1db89776b64c4f0f2c2ac609527ac70 ]
When the wm8958_mic_detect, wm8994_mic_detect functions get called from the machine driver, e.g. from the card's late_probe() callback, the CODEC device may be PM runtime suspended and any regmap writes have no effect. Add PM runtime calls to these functions to ensure the device registers are updated as expected.
This suppresses an error during boot
"wm8994-codec: ASoC: error at snd_soc_component_update_bits on wm8994-codec" caused by the regmap access error due to the cache_only flag being set.
--- sound/soc/codecs/wm8994.c | 8 ++++++++ 1 file changed, 8 insertions(+)
sound/soc/codecs/wm8994.c +8 -0
@@ -3491,6 +3491,8 @@ int wm8994_mic_detect(struct snd_soc_component *component, struct snd_soc_jack *return -EINVAL ; } +pm_runtime_get_sync (component->dev); +switch (micbias) {case 1 : micdet = &wm8994->micdet[0 ];
@@ -3538,6 +3540,8 @@ int wm8994_mic_detect(struct snd_soc_component *component, struct snd_soc_jack *snd_soc_dapm_sync (dapm); +pm_runtime_put (component->dev); +return 0 ; }EXPORT_SYMBOL_GPL (wm8994_mic_detect);
@@ -3905,6 +3909,8 @@ int wm8958_mic_detect(struct snd_soc_component *component, struct snd_soc_jack *return -EINVAL ; } +pm_runtime_get_sync (component->dev); +if (jack) {snd_soc_dapm_force_enable_pin (dapm,"CLK_SYS" );snd_soc_dapm_sync (dapm);
@@ -3973,6 +3979,8 @@ int wm8958_mic_detect(struct snd_soc_component *component, struct snd_soc_jack *snd_soc_dapm_sync (dapm); } +pm_runtime_put (component->dev); +return 0 ; }EXPORT_SYMBOL_GPL (wm8958_mic_detect);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 5/99 ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN Converter9 2-in-1
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
[ Upstream commit 6a0137101f47301fff2da6ba4b9048383d569909 ]
The MPMAN Converter9 2-in-1 almost fully works with out default settings. The only problem is that it has only 1 speaker so any sounds only playing on the right channel get lost.
Add a quirk for this model using the default settings + MONO_SPEAKER.
--- sound/soc/intel/boards/bytcr_rt5640.c | 10 ++++++++++ 1 file changed, 10 insertions(+)
sound/soc/intel/boards/bytcr_rt5640.c +10 -0
@@ -591,6 +591,16 @@ static const struct dmi_system_id byt_rt5640_quirk_table[] = {BYT_RT5640_SSP0_AIF1 | BYT_RT5640_MCLK_EN), }, + { /* MPMAN Converter 9, similar hw as the I.T.Works TW891 2-in-1 */ + .matches = { +DMI_MATCH (DMI_SYS_VENDOR ,"MPMAN" ), + DMI_MATCH(DMI_PRODUCT_NAME, "Converter9"), + }, + .driver_data = (void *)(BYTCR_INPUT_DEFAULTS | +BYT_RT5640_MONO_SPEAKER | +BYT_RT5640_SSP0_AIF1 | + BYT_RT5640_MCLK_EN), + }, {/* MPMAN MPWIN895CL */ .matches = {
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 6/99 clk: versatile: Add of_node_put() before return statement
In reply to Greg Kroah-HartmanFrom: Sumera Priyadarsini <[email protected]>
[ Upstream commit da9c43dc0e2ec5c42a3d414e389feb30467000e2 ]
Every iteration of for_each_available_child_of_node() decrements the reference count of the previous node, however when control is transferred from the middle of the loop, as in the case of a return or break or goto, there is no decrement thus ultimately resulting in a memory leak.
Fix a potential memory leak in clk-impd1.c by inserting of_node_put() before a return statement.
Issue found with Coccinelle.
--- drivers/clk/versatile/clk-impd1.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/clk/versatile/clk-impd1.c +3 -1
@@ -109,8 +109,10 @@ static int integrator_impd1_clk_probe(struct platform_device *pdev)for_each_available_child_of_node (np, child) { ret =integrator_impd1_clk_spawn (dev, np, child); -if (ret) +if (ret) { +of_node_put (child);break ; + } }return ret;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 7/99 RISC-V: Take text_mutex in ftrace_init_nop()
In reply to Greg Kroah-HartmanFrom: Palmer Dabbelt <[email protected]>
[ Upstream commit 66d18dbda8469a944dfec6c49d26d5946efba218 ]
Without this we get lockdep failures. They're spurious failures as SMP isn't up when ftrace_init_nop() is called. As far as I can tell the easiest fix is to just take the lock, which also seems like the safest fix.
--- arch/riscv/include/asm/ftrace.h | 7 +++++++ arch/riscv/kernel/ftrace.c | 19 +++++++++++++++++++ 2 files changed, 26 insertions(+)
arch/riscv/include/asm/ftrace.h +7 -0
@@ -66,6 +66,13 @@ do { \* Let auipc+jalr be the basic *mcount unit*, so we make it 8 bytes here. */ #define MCOUNT_INSN_SIZE 8 + +#ifndef __ASSEMBLY__ +struct dyn_ftrace ; +int ftrace_init_nop (struct module *mod,struct dyn_ftrace *rec); +#define ftrace_init_nop ftrace_init_nop +#endif +#endif #endif /* _ASM_RISCV_FTRACE_H */
arch/riscv/kernel/ftrace.c +19 -0
@@ -97,6 +97,25 @@ int ftrace_make_nop(struct module *mod, struct dyn_ftrace *rec,return __ftrace_modify_call (rec->ip, addr, false); } + +/* +* This is called early on, and isn't wrapped by +* ftrace_arch_code_modify_{prepare,post_process}() and therefor doesn't hold +* text_mutex, which triggers a lockdep failure. SMP isn't running so we could +* just directly poke the text, but it's simpler to just take the lock +* ourselves. +*/ +int ftrace_init_nop (struct module *mod,struct dyn_ftrace *rec) +{ +int out; + +ftrace_arch_code_modify_prepare (); + out =ftrace_make_nop (mod, rec,MCOUNT_ADDR ); +ftrace_arch_code_modify_post_process (); + +return out; +} +int ftrace_update_ftrace_func (ftrace_func_t func) { int ret = __ftrace_modify_call((unsigned long)&ftrace_call,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 8/99 i2c: aspeed: Mask IRQ status to relevant bits
In reply to Greg Kroah-HartmanFrom: Eddie James <[email protected]>
[ Upstream commit 1a1d6db23ddacde0b15ea589e9103373e05af8de ]
Mask the IRQ status to only the bits that the driver checks. This prevents excessive driver warnings when operating in slave mode when additional bits are set that the driver doesn't handle.
--- drivers/i2c/busses/i2c-aspeed.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/i2c/busses/i2c-aspeed.c +2 -0
@@ -69,6 +69,7 @@* These share bit definitions, so use the same values for the enable & * status bits. */ +#define ASPEED_I2CD_INTR_RECV_MASK 0xf000ffff#define ASPEED_I2CD_INTR_SDA_DL_TIMEOUT BIT(14)#define ASPEED_I2CD_INTR_BUS_RECOVER_DONE BIT(13)#define ASPEED_I2CD_INTR_SLAVE_MATCH BIT(7)
@@ -604,6 +605,7 @@ static irqreturn_t aspeed_i2c_bus_irq(int irq, void *dev_id)writel (irq_received & ~ASPEED_I2CD_INTR_RX_DONE , bus->base +ASPEED_I2C_INTR_STS_REG );readl (bus->base +ASPEED_I2C_INTR_STS_REG ); + irq_received &=ASPEED_I2CD_INTR_RECV_MASK ; irq_remaining = irq_received;#if IS_ENABLED (CONFIG_I2C_SLAVE )
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 9/99 s390/init: add missing __init annotations
In reply to Greg Kroah-HartmanFrom: Ilya Leoshkevich <[email protected]>
[ Upstream commit fcb2b70cdb194157678fb1a75f9ff499aeba3d2a ]
Add __init to reserve_memory_end, reserve_oldmem and remove_oldmem. Sometimes these functions are not inlined, and then the build complains about section mismatch.
--- arch/s390/kernel/setup.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
arch/s390/kernel/setup.c +3 -3
@@ -619,7 +619,7 @@ static struct notifier_block kdump_mem_nb = {/* * Make sure that the area behind memory_end is protected */ -static void reserve_memory_end (void ) +static void __init reserve_memory_end (void ) {if (memory_end_set)memblock_reserve (memory_end,ULONG_MAX );
@@ -628,7 +628,7 @@ static void reserve_memory_end(void)/* * Make sure that oldmem, where the dump is stored, is protected */ -static void reserve_oldmem (void ) +static void __init reserve_oldmem (void ) {#ifdef CONFIG_CRASH_DUMP if (OLDMEM_BASE )
@@ -640,7 +640,7 @@ static void reserve_oldmem(void)/* * Make sure that oldmem, where the dump is stored, is protected */ -static void remove_oldmem (void ) +static void __init remove_oldmem (void ) {#ifdef CONFIG_CRASH_DUMP if (OLDMEM_BASE )
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 10/99 lockdep: fix order in trace_hardirqs_off_caller()
In reply to Greg Kroah-HartmanFrom: Sven Schnelle <[email protected]>
[ Upstream commit 73ac74c7d489756d2313219a108809921dbfaea1 ]
Switch order so that locking state is consistent even if the IRQ tracer calls into lockdep again.
--- kernel/trace/trace_preemptirq.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
kernel/trace/trace_preemptirq.c +2 -2
@@ -102,14 +102,14 @@ NOKPROBE_SYMBOL(trace_hardirqs_on_caller); __visible void trace_hardirqs_off_caller(unsigned long caller_addr) { +lockdep_hardirqs_off (CALLER_ADDR0 ); +if (!this_cpu_read (tracing_irq_cpu)) {this_cpu_write (tracing_irq_cpu,1 );tracer_hardirqs_off (CALLER_ADDR0 , caller_addr);if (!in_nmi ())trace_irq_disable_rcuidle (CALLER_ADDR0 , caller_addr); } - -lockdep_hardirqs_off (CALLER_ADDR0 ); }EXPORT_SYMBOL (trace_hardirqs_off_caller);NOKPROBE_SYMBOL (trace_hardirqs_off_caller);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 11/99 EDAC/ghes: Check whether the driver is on the safe list correctly
In reply to Greg Kroah-HartmanFrom: Borislav Petkov <[email protected]>
[ Upstream commit 251c54ea26fa6029b01a76161a37a12fde5124e4 ]
With CONFIG_DEBUG_TEST_DRIVER_REMOVE=y, a system would try to probe, unregister and probe again a driver.
When ghes_edac is attempted to be loaded on a system which is not on the safe platforms list, ghes_edac_register() would return early. The unregister counterpart ghes_edac_unregister() would still attempt to unregister and exit early at the refcount test, leading to the refcount underflow below.
In order to not do *anything* on the unregister path too, reuse the force_load parameter and check it on that path too, before fumbling with the refcount.
ghes_edac: ghes_edac_register: entry
ghes_edac: ghes_edac_register: return -ENODEV
------------[ cut here ]------------ refcount_t: underflow; use-after-free. WARNING: CPU: 10 PID: 1 at lib/refcount.c:28 refcount_warn_saturate+0xb9/0x100 Modules linked in: CPU: 10 PID: 1 Comm: swapper/0 Not tainted 5.9.0-rc4+ #12 Hardware name: GIGABYTE MZ01-CE1-00/MZ01-CE1-00, BIOS F02 08/29/2018 RIP: 0010:refcount_warn_saturate+0xb9/0x100 Code: 82 e8 fb 8f 4d 00 90 0f 0b 90 90 c3 80 3d 55 4c f5 00 00 75 88 c6 05 4c 4c f5 00 01 90 48 c7 c7 d0 8a 10 82 e8 d8 8f 4d 00 90 <0f> 0b 90 90 c3 80 3d 30 4c f5 00 00 0f 85 61 ff ff ff c6 05 23 4c RSP: 0018:ffffc90000037d58 EFLAGS: 00010292 RAX: 0000000000000026 RBX: ffff88840b8da000 RCX: 0000000000000000 RDX: 0000000000000001 RSI: ffffffff8216b24f RDI: 00000000ffffffff RBP: ffff88840c662e00 R08: 0000000000000001 R09: 0000000000000001 R10: 0000000000000001 R11: 0000000000000046 R12: 0000000000000000 R13: 0000000000000001 R14: 0000000000000000 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88840ee80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000000000000000 CR3: 0000800002211000 CR4: 00000000003506e0 Call Trace: ghes_edac_unregister ghes_remove platform_drv_remove really_probe driver_probe_device device_driver_attach __driver_attach ? device_driver_attach ? device_driver_attach bus_for_each_dev bus_add_driver driver_register ? bert_init ghes_init do_one_initcall ? rcu_read_lock_sched_held kernel_init_freeable ? rest_init kernel_init ret_from_fork ... ghes_edac: ghes_edac_unregister: FALSE, refcount: -1073741824
--- drivers/edac/ghes_edac.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/edac/ghes_edac.c +4 -0
@@ -469,6 +469,7 @@ int ghes_edac_register(struct ghes *ghes, struct device *dev)if (!force_load && idx <0 )return -ENODEV ; }else { + force_load = true; idx =0 ; }
@@ -566,6 +567,9 @@ void ghes_edac_unregister(struct ghes *ghes)struct mem_ctl_info *mci;unsigned long flags; +if (!force_load) +return ; +mutex_lock (&ghes_reg_mutex);if (!refcount_dec_and_test (&ghes_refcount))
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 12/99 drm/amdkfd: fix a memory leak issue
In reply to Greg Kroah-HartmanFrom: Dennis Li <[email protected]>
[ Upstream commit 087d764159996ae378b08c0fdd557537adfd6899 ]
In the resume stage of GPU recovery, start_cpsch will call pm_init which set pm->allocated as false, cause the next pm_release_ib has no chance to release ib memory.
Add pm_release_ib in stop_cpsch which will be called in the suspend stage of GPU recovery.
--- drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/gpu/drm/amd/amdkfd/kfd_device_queue_manager.c +2 -0
@@ -1177,6 +1177,8 @@ static int stop_cpsch(struct device_queue_manager *dqm) dqm->sched_running = false;dqm_unlock (dqm); +pm_release_ib (&dqm->packets); +kfd_gtt_sa_free (dqm->dev, dqm->fence_mem);pm_uninit (&dqm->packets, hanging);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 13/99 drm/amd/display: Dont use DRM_ERROR() for DTM add topology
In reply to Greg Kroah-HartmanFrom: Bhawanpreet Lakha <[email protected]>
[ Upstream commit 4cdd7b332ed139b1e37faeb82409a14490adb644 ]
[Why]
Previously we were only calling add_topology when hdcp was being enabled. Now we call add_topology by default so the ERROR messages are printed if the firmware is not loaded.
This error message is not relevant for normal display functionality so no need to print a ERROR message.
[How]
Change DRM_ERROR to DRM_INFO
--- drivers/gpu/drm/amd/display/modules/hdcp/hdcp_psp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/display/modules/hdcp/hdcp_psp.c +1 -1
@@ -88,7 +88,7 @@ enum mod_hdcp_status mod_hdcp_add_display_to_topology(struct mod_hdcp *hdcp,enum mod_hdcp_status status =MOD_HDCP_STATUS_SUCCESS ;if (!psp->dtm_context.dtm_initialized) { -DRM_ERROR ("Failed to add display topology, DTM TA is not initialized." ); +DRM_INFO ("Failed to add display topology, DTM TA is not initialized." ); display->state =MOD_HDCP_DISPLAY_INACTIVE ;return MOD_HDCP_STATUS_FAILURE ; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 14/99 drm/amd/display: update nv1x stutter latencies
In reply to Greg Kroah-HartmanFrom: Jun Lei <[email protected]>
[ Upstream commit c4790a8894232f39c25c7c546c06efe074e63384 ]
[why]
Recent characterization shows increased stutter latencies on some SKUs, leading to underflow.
[how]
Update SOC params to account for this worst case latency.
--- drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/gpu/drm/amd/display/dc/dcn20/dcn20_resource.c +2 -2
@@ -409,8 +409,8 @@ struct _vcs_dpi_soc_bounding_box_st dcn2_0_nv14_soc = { }, }, .num_states = 5, - .sr_exit_time_us = 8.6, - .sr_enter_plus_exit_time_us = 10.9, + .sr_exit_time_us = 11.6, + .sr_enter_plus_exit_time_us = 13.9, .urgent_latency_us = 4.0, .urgent_latency_pixel_data_only_us = 4.0, .urgent_latency_pixel_mixed_with_vm_data_us = 4.0,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 15/99 drm/amdgpu/dc: Require primary plane to be enabled whenever the CRTC is
In reply to Greg Kroah-HartmanFrom: Michel Dänzer <[email protected]>
[ Upstream commit 2f228aab21bbc74e90e267a721215ec8be51daf7 ]
Don't check drm_crtc_state::active for this either, per its documentation in include/drm/drm_crtc.h:
* Hence drivers must not consult @active in their various
* &drm_mode_config_funcs.atomic_check callback to reject an atomic
* commit.
atomic_remove_fb disables the CRTC as needed for disabling the primary plane.
This prevents at least the following problems if the primary plane gets disabled (e.g. due to destroying the FB assigned to the primary plane, as happens e.g. with mutter in Wayland mode):
* The legacy cursor ioctl returned EINVAL for a non-0 cursor FB ID (which enables the cursor plane).
* If the cursor plane was enabled, changing the legacy DPMS property value from off to on returned EINVAL.
v2:
* Minor changes to code comment and commit log, per review feedback.
GitLab: https://gitlab.gnome.org/GNOME/mutter/-/issues/1108
GitLab: https://gitlab.gnome.org/GNOME/mutter/-/issues/1165
GitLab: https://gitlab.gnome.org/GNOME/mutter/-/issues/1344
--- .../gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 32 ++++++------------- 1 file changed, 10 insertions(+), 22 deletions(-)
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c +10 -22
@@ -5257,19 +5257,6 @@ static void dm_crtc_helper_disable(struct drm_crtc *crtc) { } -static bool does_crtc_have_active_cursor (struct drm_crtc_state *new_crtc_state) -{ -struct drm_device *dev = new_crtc_state->crtc->dev; -struct drm_plane *plane; - -drm_for_each_plane_mask (plane, dev, new_crtc_state->plane_mask) { -if (plane->type ==DRM_PLANE_TYPE_CURSOR ) -return true; - } - -return false; -} -static int count_crtc_active_planes (struct drm_crtc_state *new_crtc_state) {struct drm_atomic_state *state = new_crtc_state->state;
@@ -5349,19 +5336,20 @@ static int dm_crtc_helper_atomic_check(struct drm_crtc *crtc,return ret; } -/* In some use cases, like reset, no stream is attached */ -if (!dm_crtc_state->stream) -return 0 ; -/* -* We want at least one hardware plane enabled to use -* the stream with a cursor enabled. +* We require the primary plane to be enabled whenever the CRTC is, otherwise +* drm_mode_cursor_universal may end up trying to enable the cursor plane while all other +* planes are disabled, which is not supported by the hardware. And there is legacy +* userspace which stops using the HW cursor altogether in response to the resulting EINVAL. */ -if (state->enable && state->active && -does_crtc_have_active_cursor (state) && - dm_crtc_state->active_planes ==0 ) +if (state->enable && + !(state->plane_mask &drm_plane_mask (crtc->primary)))return -EINVAL ; +/* In some use cases, like reset, no stream is attached */ +if (!dm_crtc_state->stream) +return 0 ; +if (dc_validate_stream (dc, dm_crtc_state->stream) ==DC_OK )return 0 ;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 16/99 drm/amd/display: Dont log hdcp module warnings in dmesg
In reply to Greg Kroah-HartmanFrom: Bhawanpreet Lakha <[email protected]>
[ Upstream commit 875d369d8f75275d30e59421602d9366426abff7 ]
[Why]
DTM topology updates happens by default now. This results in DTM warnings when hdcp is not even being enabled. This spams the dmesg and doesn't effect normal display functionality so it is better to log it using DRM_DEBUG_KMS()
[How]
Change the DRM_WARN() to DRM_DEBUG_KMS()
--- drivers/gpu/drm/amd/display/modules/hdcp/hdcp_log.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/amd/display/modules/hdcp/hdcp_log.h +1 -1
@@ -27,7 +27,7 @@#define MOD_HDCP_LOG_H_ #ifdef CONFIG_DRM_AMD_DC_HDCP -#define HDCP_LOG_ERR (hdcp, ...) DRM_WARN(__VA_ARGS__) +#define HDCP_LOG_ERR (hdcp, ...) DRM_DEBUG_KMS(__VA_ARGS__)#define HDCP_LOG_VER (hdcp, ...) DRM_DEBUG_KMS(__VA_ARGS__)#define HDCP_LOG_FSM (hdcp, ...) DRM_DEBUG_KMS(__VA_ARGS__)#define HDCP_LOG_TOP (hdcp, ...) pr_debug("[HDCP_TOP]:"__VA_ARGS__)
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 17/99 i2c: core: Call i2c_acpi_install_space_handler() before i2c_acpi_register_devices()
In reply to Greg Kroah-HartmanFrom: Hans de Goede <[email protected]>
[ Upstream commit 21653a4181ff292480599dad996a2b759ccf050f ]
Some ACPI i2c-devices _STA method (which is used to detect if the device is present) use autodetection code which probes which device is present over i2c. This requires the I2C ACPI OpRegion handler to be registered before we enumerate i2c-clients under the i2c-adapter.
This fixes the i2c touchpad on the Lenovo ThinkBook 14-IIL and ThinkBook 15 IIL not getting an i2c-client instantiated and thus not working.
--- drivers/i2c/i2c-core-base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/i2c-core-base.c +1 -1
@@ -1336,8 +1336,8 @@ static int i2c_register_adapter(struct i2c_adapter *adap)/* create pre-declared device nodes */ of_i2c_register_devices (adap); -i2c_acpi_register_devices (adap);i2c_acpi_install_space_handler (adap); +i2c_acpi_register_devices (adap);if (adap->nr < __i2c_first_dynamic_bus_num)i2c_scan_static_board_info (adap);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 18/99 objtool: Fix noreturn detection for ignored functions
In reply to Greg Kroah-HartmanFrom: Josh Poimboeuf <[email protected]>
[ Upstream commit db6c6a0df840e3f52c84cc302cc1a08ba11a4416 ]
When a function is annotated with STACK_FRAME_NON_STANDARD, objtool doesn't validate its code paths. It also skips sibling call detection within the function.
But sibling call detection is actually needed for the case where the ignored function doesn't have any return instructions. Otherwise objtool naively marks the function as implicit static noreturn, which affects the reachability of its callers, resulting in "unreachable instruction" warnings.
Fix it by just enabling sibling call detection for ignored functions. The 'insn->ignore' check in add_jump_destinations() is no longer needed after
e6da9567959e ("objtool: Don't use ignore flag for fake jumps").
Fixes the following warning:
arch/x86/kvm/vmx/vmx.o: warning: objtool: vmx_handle_exit_irqoff()+0x142: unreachable instruction
which triggers on an allmodconfig with CONFIG_GCOV_KERNEL unset.
--- tools/objtool/check.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/objtool/check.c +1 -1
@@ -619,7 +619,7 @@ static int add_jump_destinations(struct objtool_file *file)if (!is_static_jump (insn))continue ; -if (insn->ignore || insn->offset ==FAKE_JUMP_OFFSET ) +if (insn->offset ==FAKE_JUMP_OFFSET )continue ; rela = find_rela_by_dest_range(file->elf, insn->sec,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 19/99 i2c: mediatek: Send i2c master code at more than 1MHz
In reply to Greg Kroah-HartmanFrom: Qii Wang <[email protected]>
[ Upstream commit b44658e755b5a733e9df04449facbc738df09170 ]
The master code needs to being sent when the speed is more than I2C_MAX_FAST_MODE_PLUS_FREQ, not I2C_MAX_FAST_MODE_FREQ in the latest I2C-bus specification and user manual.
--- drivers/i2c/busses/i2c-mt65xx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/i2c/busses/i2c-mt65xx.c +1 -1
@@ -736,7 +736,7 @@ static int mtk_i2c_set_speed(struct mtk_i2c *i2c, unsigned int parent_clk)for (clk_div =1 ; clk_div <= max_clk_div; clk_div++) { clk_src = parent_clk / clk_div; -if (target_speed >I2C_MAX_FAST_MODE_FREQ ) { +if (target_speed >I2C_MAX_FAST_MODE_PLUS_FREQ ) {/* Set master code speed register */ ret = mtk_i2c_calculate_speed(i2c, clk_src, I2C_MAX_FAST_MODE_FREQ,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 20/99 riscv: Fix Kendryte K210 device tree
In reply to Greg Kroah-HartmanFrom: Damien Le Moal <[email protected]>
[ Upstream commit f025d9d9934b84cd03b7796072d10686029c408e ]
The Kendryte K210 SoC CLINT is compatible with Sifive clint v0 (sifive,clint0). Fix the Kendryte K210 device tree clint entry to be inline with the sifive timer definition documented in Documentation/devicetree/bindings/timer/sifive,clint.yaml. The device tree clint entry is renamed similarly to u-boot device tree definition to improve compatibility with u-boot defined device tree. To ensure correct initialization, the interrup-cells attribute is added and the interrupt-extended attribute definition fixed.
This fixes boot failures with Kendryte K210 SoC boards.
Note that the clock referenced is kept as K210_CLK_ACLK, which does not necessarilly match the clint MTIME increment rate. This however does not seem to cause any problem for now.
--- arch/riscv/boot/dts/kendryte/k210.dtsi | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
arch/riscv/boot/dts/kendryte/k210.dtsi +4 -2
@@ -95,10 +95,12 @@ #clock-cells = <1>; }; - clint0: interrupt-controller@2000000 { + clint0: clint@2000000 { + #interrupt-cells = <1>; compatible = "riscv,clint0"; reg = <0x2000000 0xC000>; - interrupts-extended = <&cpu0_intc 3>, <&cpu1_intc 3>; + interrupts-extended = <&cpu0_intc 3 &cpu0_intc 7 + &cpu1_intc 3 &cpu1_intc 7>; clocks = <&sysctl K210_CLK_ACLK>; };
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 21/99 ieee802154: fix one possible memleak in ca8210_dev_com_init
In reply to Greg Kroah-HartmanFrom: Liu Jian <[email protected]>
[ Upstream commit 88f46b3fe2ac41c381770ebad9f2ee49346b57a2 ]
We should call destroy_workqueue to destroy mlme_workqueue in error branch.
--- drivers/net/ieee802154/ca8210.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/ieee802154/ca8210.c +1 -0
@@ -2925,6 +2925,7 @@ static int ca8210_dev_com_init(struct ca8210_priv *priv) );if (!priv->irq_workqueue) {dev_crit (&priv->spi->dev,"alloc of irq_workqueue failed!\n" ); +destroy_workqueue (priv->mlme_workqueue);return -ENOMEM ; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 22/99 ieee802154/adf7242: check status of adf7242_read_reg
In reply to Greg Kroah-HartmanFrom: Tom Rix <[email protected]>
[ Upstream commit e3914ed6cf44bfe1f169e26241f8314556fd1ac1 ]
Clang static analysis reports this error
adf7242.c:887:6: warning: Assigned value is garbage or undefined
len = len_u8;
^ ~~~~~~len_u8 is set in
adf7242_read_reg(lp, 0, &len_u8);
When this call fails, len_u8 is not set.
So check the return code.
--- drivers/net/ieee802154/adf7242.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/net/ieee802154/adf7242.c +3 -1
@@ -882,7 +882,9 @@ static int adf7242_rx(struct adf7242_local *lp)int ret;u8 lqi, len_u8, *data; -adf7242_read_reg (lp,0 , &len_u8); + ret =adf7242_read_reg (lp,0 , &len_u8); +if (ret) +return ret; len = len_u8;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 23/99 clocksource/drivers/h8300_timer8: Fix wrong return value in h8300_8timer_init()
In reply to Greg Kroah-HartmanFrom: Tianjia Zhang <[email protected]>
[ Upstream commit 400d033f5a599120089b5f0c54d14d198499af5a ]
In the init function, if the call to of_iomap() fails, the return value is ENXIO instead of -ENXIO.
Change to the right negative errno.
--- drivers/clocksource/h8300_timer8.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/clocksource/h8300_timer8.c +1 -1
@@ -169,7 +169,7 @@ static int __init h8300_8timer_init(struct device_node *node)return PTR_ERR (clk); } - ret =ENXIO ; + ret = -ENXIO ; base =of_iomap (node,0 );if (!base) {pr_err ("failed to map registers for clockevent\n" );
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 24/99 mwifiex: Increase AES key storage size to 256 bits
In reply to Greg Kroah-HartmanFrom: Maximilian Luz <[email protected]>
[ Upstream commit 4afc850e2e9e781976fb2c7852ce7bac374af938 ]
Following commit e18696786548 ("mwifiex: Prevent memory corruption handling keys") the mwifiex driver fails to authenticate with certain networks, specifically networks with 256 bit keys, and repeatedly asks for the password. The kernel log repeats the following lines (id and bssid redacted):
mwifiex_pcie 0000:01:00.0: info: trying to associate to '<id>' bssid <bssid> mwifiex_pcie 0000:01:00.0: info: associated to bssid <bssid> successfully mwifiex_pcie 0000:01:00.0: crypto keys added
mwifiex_pcie 0000:01:00.0: info: successfully disconnected from <bssid>: reason code 3
Tracking down this problem lead to the overflow check introduced by the aforementioned commit into mwifiex_ret_802_11_key_material_v2(). This check fails on networks with 256 bit keys due to the current storage size for AES keys in struct mwifiex_aes_param being only 128 bit.
To fix this issue, increase the storage size for AES keys to 256 bit.
--- drivers/net/wireless/marvell/mwifiex/fw.h | 2 +- drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
drivers/net/wireless/marvell/mwifiex/fw.h +1 -1
@@ -954,7 +954,7 @@ struct mwifiex_tkip_param {struct mwifiex_aes_param {u8 pn[WPA_PN_SIZE ];__le16 key_len; -u8 key[WLAN_KEY_LEN_CCMP ]; +u8 key[WLAN_KEY_LEN_CCMP_256 ]; } __packed;struct mwifiex_wapi_param {
drivers/net/wireless/marvell/mwifiex/sta_cmdresp.c +2 -2
@@ -619,7 +619,7 @@ static int mwifiex_ret_802_11_key_material_v2(struct mwifiex_private *priv, key_v2 = &resp->params.key_material_v2; len =le16_to_cpu (key_v2->key_param_set.key_params.aes.key_len); -if (len >WLAN_KEY_LEN_CCMP ) +if (len >sizeof (key_v2->key_param_set.key_params.aes.key))return -EINVAL ;if (le16_to_cpu (key_v2->action) == HostCmd_ACT_GEN_SET) {
@@ -635,7 +635,7 @@ static int mwifiex_ret_802_11_key_material_v2(struct mwifiex_private *priv,return 0 ;memset (priv->aes_key_v2.key_param_set.key_params.aes.key,0 , -WLAN_KEY_LEN_CCMP ); +sizeof (key_v2->key_param_set.key_params.aes.key)); priv->aes_key_v2.key_param_set.key_params.aes.key_len =cpu_to_le16 (len); memcpy(priv->aes_key_v2.key_param_set.key_params.aes.key,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 25/99 batman-adv: bla: fix type misuse for backbone_gw hash indexing
In reply to Greg Kroah-HartmanFrom: Linus Lüssing <[email protected]>
[ Upstream commit 097930e85f90f252c44dc0d084598265dd44ca48 ]
It seems that due to a copy & paste error the void pointer in batadv_choose_backbone_gw() is cast to the wrong type.
Fixing this by using "struct batadv_bla_backbone_gw" instead of "struct batadv_bla_claim" which better matches the caller's side.
For now it seems that we were lucky because the two structs both have their orig/vid and addr/vid in the beginning. However I stumbled over this issue when I was trying to add some debug variables in front of "orig" in batadv_backbone_gw, which caused hash lookups to fail.
--- net/batman-adv/bridge_loop_avoidance.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
net/batman-adv/bridge_loop_avoidance.c +4 -3
@@ -83,11 +83,12 @@ static inline u32 batadv_choose_claim(const void *data, u32 size)*/ static inline u32 batadv_choose_backbone_gw (const void *data,u32 size) { -const struct batadv_bla_claim *claim = (struct batadv_bla_claim *)data; +const struct batadv_bla_backbone_gw *gw;u32 hash =0 ; - hash =jhash (&claim->addr,sizeof (claim->addr), hash); - hash =jhash (&claim->vid,sizeof (claim->vid), hash); + gw = (struct batadv_bla_backbone_gw *)data; + hash =jhash (&gw->orig,sizeof (gw->orig), hash); + hash =jhash (&gw->vid,sizeof (gw->vid), hash);return hash % size; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 26/99 libbpf: Fix build failure from uninitialized variable warning
In reply to Greg Kroah-HartmanFrom: Tony Ambardar <[email protected]>
[ Upstream commit 3168c158ad3535af1cd7423c9f8cd5ac549f2f9c ]
While compiling libbpf, some GCC versions (at least 8.4.0) have difficulty determining control flow and a emit warning for potentially uninitialized usage of 'map', which results in a build error if using "-Werror":
In file included from libbpf.c:56:libbpf.c: In function '__bpf_object__open':
libbpf_internal.h:59:2: warning: 'map' may be used uninitialized in this function [-Wmaybe-uninitialized]
libbpf_print(level, "libbpf: " fmt, ##__VA_ARGS__); \
^~~~~~~~~~~~
libbpf.c:5032:18: note: 'map' was declared here
struct bpf_map *map, *targ_map;
^~~The warning/error is false based on code inspection, so silence it with a NULL initialization.
Reference: 063e68813391 ("libbpf: Fix false uninitialized variable warning")
--- tools/lib/bpf/libbpf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
tools/lib/bpf/libbpf.c +1 -1
@@ -5030,8 +5030,8 @@ static int bpf_object__collect_map_relos(struct bpf_object *obj,int i, j, nrels, new_sz;const struct btf_var_secinfo *vi =NULL ;const struct btf_type *sec, *var, *def; +struct bpf_map *map =NULL , *targ_map;const struct btf_member *member; -struct bpf_map *map, *targ_map;const char *name, *mname;Elf_Data *symbols;unsigned int moff;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 27/99 atm: eni: fix the missed pci_disable_device() for eni_init_one()
In reply to Greg Kroah-HartmanFrom: Jing Xiangfeng <[email protected]>
[ Upstream commit c2b947879ca320ac5505c6c29a731ff17da5e805 ]
eni_init_one() misses to call pci_disable_device() in an error path. Jump to err_disable to fix it.
--- drivers/atm/eni.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/atm/eni.c +1 -1
@@ -2239,7 +2239,7 @@ static int eni_init_one(struct pci_dev *pci_dev, rc =dma_set_mask_and_coherent (&pci_dev->dev,DMA_BIT_MASK (32 ));if (rc <0 ) - goto out; + goto err_disable; rc = -ENOMEM ; eni_dev =kmalloc (sizeof (struct eni_dev ),GFP_KERNEL );
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 28/99 batman-adv: mcast/TT: fix wrongly dropped or rerouted packets
In reply to Greg Kroah-HartmanFrom: Linus Lüssing <[email protected]>
[ Upstream commit 7dda5b3384121181c4e79f6eaeac2b94c0622c8d ]
The unicast packet rerouting code makes several assumptions. For instance it assumes that there is always exactly one destination in the TT. This breaks for multicast frames in a unicast packets in several ways:
For one thing if there is actually no TT entry and the destination node was selected due to the multicast tvlv flags it announced. Then an intermediate node will wrongly drop the packet.
For another thing if there is a TT entry but the TTVN of this entry is newer than the originally addressed destination node: Then the intermediate node will wrongly redirect the packet, leading to duplicated multicast packets at a multicast listener and missing packets at other multicast listeners or multicast routers.
Fixing this by not applying the unicast packet rerouting to batman-adv unicast packets with a multicast payload. We are not able to detect a roaming multicast listener at the moment and will just continue to send the multicast frame to both the new and old destination for a while in case of such a roaming multicast listener.
--- net/batman-adv/routing.c | 4 ++++ 1 file changed, 4 insertions(+)
net/batman-adv/routing.c +4 -0
@@ -826,6 +826,10 @@ static bool batadv_check_unicast_ttvn(struct batadv_priv *bat_priv, vid =batadv_get_vid (skb, hdr_len); ethhdr = (struct ethhdr *)(skb->data + hdr_len); +/* do not reroute multicast frames in a unicast header */ +if (is_multicast_ether_addr (ethhdr->h_dest)) +return true; +/* check if the destination client was served by this node and it is now * roaming. In this case, it means that the node has got a ROAM_ADV * message and that it knows the new destination in the mesh to re-route
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 29/99 netfilter: ctnetlink: add a range check for l3/l4 protonum
In reply to Greg Kroah-HartmanFrom: Will McVicker <[email protected]>
[ Upstream commit 1cc5ef91d2ff94d2bf2de3b3585423e8a1051cb6 ]
The indexes to the nf_nat_l[34]protos arrays come from userspace. So check the tuple's family, e.g. l3num, when creating the conntrack in order to prevent an OOB memory access during setup. Here is an example kernel panic on 4.14.180 when userspace passes in an index greater than NFPROTO_NUMPROTO.
Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Modules linked in:... Process poc (pid: 5614, stack limit = 0x00000000a3933121) CPU: 4 PID: 5614 Comm: poc Tainted: G S W O 4.14.180-g051355490483 Hardware name: Qualcomm Technologies, Inc. SM8150 V2 PM8150 Google Inc. MSM task: 000000002a3dfffe task.stack: 00000000a3933121 pc : __cfi_check_fail+0x1c/0x24 lr : __cfi_check_fail+0x1c/0x24 ... Call trace: __cfi_check_fail+0x1c/0x24 name_to_dev_t+0x0/0x468 nfnetlink_parse_nat_setup+0x234/0x258 ctnetlink_parse_nat_setup+0x4c/0x228 ctnetlink_new_conntrack+0x590/0xc40 nfnetlink_rcv_msg+0x31c/0x4d4 netlink_rcv_skb+0x100/0x184 nfnetlink_rcv+0xf4/0x180 netlink_unicast+0x360/0x770 netlink_sendmsg+0x5a0/0x6a4 ___sys_sendmsg+0x314/0x46c SyS_sendmsg+0xb4/0x108 el0_svc_naked+0x34/0x38
This crash is not happening since 5.4+, however, ctnetlink still allows for creating entries with unsupported layer 3 protocol number.
--- net/netfilter/nf_conntrack_netlink.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/netfilter/nf_conntrack_netlink.c +2 -1
@@ -1404,7 +1404,8 @@ ctnetlink_parse_tuple_filter(const struct nlattr * const cda[],if (err <0 )return err; - +if (l3num !=NFPROTO_IPV4 && l3num !=NFPROTO_IPV6 ) +return -EOPNOTSUPP ; tuple->src.l3num = l3num; if (flags & CTA_FILTER_FLAG(CTA_IP_DST) ||
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 30/99 netfilter: ctnetlink: fix mark based dump filtering regression
In reply to Greg Kroah-HartmanFrom: Martin Willi <[email protected]>
[ Upstream commit 6c0d95d1238d944fe54f0bbfc7ec017d78435daa ]
conntrack mark based dump filtering may falsely skip entries if a mask is given: If the mask-based check does not filter out the entry, the else-if check is always true and compares the mark without considering the mask. The if/else-if logic seems wrong.
Given that the mask during filter setup is implicitly set to 0xffffffff if not specified explicitly, the mark filtering flags seem to just complicate things. Restore the previously used approach by always matching against a zero mask is no filter mark is given.
--- net/netfilter/nf_conntrack_netlink.c | 19 +++---------------- 1 file changed, 3 insertions(+), 16 deletions(-)
net/netfilter/nf_conntrack_netlink.c +3 -16
@@ -851,7 +851,6 @@ static int ctnetlink_done(struct netlink_callback *cb) }struct ctnetlink_filter { -u_int32_t cta_flags;u8 family;u_int32_t orig_flags;
@@ -906,10 +905,6 @@ static int ctnetlink_parse_tuple_filter(const struct nlattr * const cda[],struct nf_conntrack_zone *zone, u_int32_t flags); -/* applied on filters */ -#define CTA_FILTER_F_CTA_MARK (1 << 0) -#define CTA_FILTER_F_CTA_MARK_MASK (1 << 1) -static struct ctnetlink_filter *ctnetlink_alloc_filter (const struct nlattr *const cda[],u8 family) {
@@ -930,14 +925,10 @@ ctnetlink_alloc_filter(const struct nlattr * const cda[], u8 family)#ifdef CONFIG_NF_CONNTRACK_MARK if (cda[CTA_MARK ]) { filter->mark.val =ntohl (nla_get_be32 (cda[CTA_MARK ])); - filter->cta_flags |=CTA_FILTER_FLAG (CTA_MARK ); - -if (cda[CTA_MARK_MASK ]) { +if (cda[CTA_MARK_MASK ]) filter->mark.mask =ntohl (nla_get_be32 (cda[CTA_MARK_MASK ])); - filter->cta_flags |=CTA_FILTER_FLAG (CTA_MARK_MASK ); - }else { +else filter->mark.mask =0xffffffff ; - } }else if (cda[CTA_MARK_MASK ]) { err = -EINVAL ; goto err_filter;
@@ -1117,11 +1108,7 @@ static int ctnetlink_filter_match(struct nf_conn *ct, void *data) }#ifdef CONFIG_NF_CONNTRACK_MARK -if ((filter->cta_flags &CTA_FILTER_FLAG (CTA_MARK_MASK )) && - (ct->mark & filter->mark.mask) != filter->mark.val) - goto ignore_entry; -else if ((filter->cta_flags &CTA_FILTER_FLAG (CTA_MARK )) && - ct->mark != filter->mark.val) +if ((ct->mark & filter->mark.mask) != filter->mark.val) goto ignore_entry;#endif
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 31/99 netfilter: conntrack: nf_conncount_init is failing with IPv6 disabled
In reply to Greg Kroah-HartmanFrom: Eelco Chaudron <[email protected]>
[ Upstream commit 526e81b990e53e31ba40ba304a2285ffd098721f ]
The openvswitch module fails initialization when used in a kernel without IPv6 enabled. nf_conncount_init() fails because the ct code unconditionally tries to initialize the netns IPv6 related bit, regardless of the build option. The change below ignores the IPv6 part if not enabled.
Note that the corresponding _put() function already has this IPv6 configuration check.
--- net/netfilter/nf_conntrack_proto.c | 2 ++ 1 file changed, 2 insertions(+)
net/netfilter/nf_conntrack_proto.c +2 -0
@@ -565,6 +565,7 @@ static int nf_ct_netns_inet_get(struct net *net)int err; err =nf_ct_netns_do_get (net,NFPROTO_IPV4 ); +#if IS_ENABLED (CONFIG_IPV6 )if (err <0 ) goto err1; err =nf_ct_netns_do_get (net,NFPROTO_IPV6 );
@@ -575,6 +576,7 @@ static int nf_ct_netns_inet_get(struct net *net) err2:nf_ct_netns_put (net,NFPROTO_IPV4 ); err1: +#endif return err; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 32/99 netfilter: nft_meta: use socket user_ns to retrieve skuid and skgid
In reply to Greg Kroah-HartmanFrom: Pablo Neira Ayuso <[email protected]>
[ Upstream commit 0c92411bb81de9bc516d6924f50289d8d5f880e5 ]
... instead of using init_user_ns.
--- net/netfilter/nft_meta.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/netfilter/nft_meta.c +2 -2
@@ -147,11 +147,11 @@ nft_meta_get_eval_skugid(enum nft_meta_keys key,switch (key) {case NFT_META_SKUID : - *dest =from_kuid_munged (&init_user_ns, + *dest =from_kuid_munged (sock_net (sk)->user_ns, sock->file->f_cred->fsuid);break ;case NFT_META_SKGID : - *dest =from_kgid_munged (&init_user_ns, + *dest =from_kgid_munged (sock_net (sk)->user_ns, sock->file->f_cred->fsgid);break ;default :
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 33/99 mac802154: tx: fix use-after-free
In reply to Greg Kroah-HartmanFrom: Eric Dumazet <[email protected]>
[ Upstream commit 0ff4628f4c6c1ab87eef9f16b25355cadc426d64 ]
syzbot reported a bug in ieee802154_tx() [1]
A similar issue in ieee802154_xmit_worker() is also fixed in this patch.
[1]
BUG: KASAN: use-after-free in ieee802154_tx+0x3d2/0x480 net/mac802154/tx.c:88
Read of size 4 at addr ffff8880251a8c70 by task syz-executor.3/928
CPU: 0 PID: 928 Comm: syz-executor.3 Not tainted 5.9.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x198/0x1fd lib/dump_stack.c:118
print_address_description.constprop.0.cold+0xae/0x497 mm/kasan/report.c:383
__kasan_report mm/kasan/report.c:513 [inline]
kasan_report.cold+0x1f/0x37 mm/kasan/report.c:530
ieee802154_tx+0x3d2/0x480 net/mac802154/tx.c:88
ieee802154_subif_start_xmit+0xbe/0xe4 net/mac802154/tx.c:130
__netdev_start_xmit include/linux/netdevice.h:4634 [inline]
netdev_start_xmit include/linux/netdevice.h:4648 [inline]
dev_direct_xmit+0x4e9/0x6e0 net/core/dev.c:4203
packet_snd net/packet/af_packet.c:2989 [inline]
packet_sendmsg+0x2413/0x5290 net/packet/af_packet.c:3014
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:671
____sys_sendmsg+0x6e8/0x810 net/socket.c:2353
___sys_sendmsg+0xf3/0x170 net/socket.c:2407
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2440
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x45d5b9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 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 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007fc98e749c78 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 000000000002ccc0 RCX: 000000000045d5b9
RDX: 0000000000000000 RSI: 0000000020007780 RDI: 000000000000000b
RBP: 000000000118d020 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cfec
R13: 00007fff690c720f R14: 00007fc98e74a9c0 R15: 000000000118cfec
Allocated by task 928:
kasan_save_stack+0x1b/0x40 mm/kasan/common.c:48
kasan_set_track mm/kasan/common.c:56 [inline]
__kasan_kmalloc.constprop.0+0xbf/0xd0 mm/kasan/common.c:461
slab_post_alloc_hook mm/slab.h:518 [inline]
slab_alloc_node mm/slab.c:3254 [inline]
kmem_cache_alloc_node+0x136/0x3e0 mm/slab.c:3574
__alloc_skb+0x71/0x550 net/core/skbuff.c:198
alloc_skb include/linux/skbuff.h:1094 [inline]
alloc_skb_with_frags+0x92/0x570 net/core/skbuff.c:5771
sock_alloc_send_pskb+0x72a/0x880 net/core/sock.c:2348
packet_alloc_skb net/packet/af_packet.c:2837 [inline]
packet_snd net/packet/af_packet.c:2932 [inline]
packet_sendmsg+0x19fb/0x5290 net/packet/af_packet.c:3014
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:671
____sys_sendmsg+0x6e8/0x810 net/socket.c:2353
___sys_sendmsg+0xf3/0x170 net/socket.c:2407
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2440
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
Freed by task 928:
kasan_save_stack+0x1b/0x40 mm/kasan/common.c:48
kasan_set_track+0x1c/0x30 mm/kasan/common.c:56
kasan_set_free_info+0x1b/0x30 mm/kasan/generic.c:355
__kasan_slab_free+0xd8/0x120 mm/kasan/common.c:422
__cache_free mm/slab.c:3418 [inline]
kmem_cache_free.part.0+0x74/0x1e0 mm/slab.c:3693
kfree_skbmem+0xef/0x1b0 net/core/skbuff.c:622
__kfree_skb net/core/skbuff.c:679 [inline]
consume_skb net/core/skbuff.c:838 [inline]
consume_skb+0xcf/0x160 net/core/skbuff.c:832
__dev_kfree_skb_any+0x9c/0xc0 net/core/dev.c:3107
fakelb_hw_xmit+0x20e/0x2a0 drivers/net/ieee802154/fakelb.c:81
drv_xmit_async net/mac802154/driver-ops.h:16 [inline]
ieee802154_tx+0x282/0x480 net/mac802154/tx.c:81
ieee802154_subif_start_xmit+0xbe/0xe4 net/mac802154/tx.c:130
__netdev_start_xmit include/linux/netdevice.h:4634 [inline]
netdev_start_xmit include/linux/netdevice.h:4648 [inline]
dev_direct_xmit+0x4e9/0x6e0 net/core/dev.c:4203
packet_snd net/packet/af_packet.c:2989 [inline]
packet_sendmsg+0x2413/0x5290 net/packet/af_packet.c:3014
sock_sendmsg_nosec net/socket.c:651 [inline]
sock_sendmsg+0xcf/0x120 net/socket.c:671
____sys_sendmsg+0x6e8/0x810 net/socket.c:2353
___sys_sendmsg+0xf3/0x170 net/socket.c:2407
__sys_sendmsg+0xe5/0x1b0 net/socket.c:2440
do_syscall_64+0x2d/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9
The buggy address belongs to the object at ffff8880251a8c00
which belongs to the cache skbuff_head_cache of size 224
The buggy address is located 112 bytes inside of
224-byte region [ffff8880251a8c00, ffff8880251a8ce0)
The buggy address belongs to the page:
page:0000000062b6a4f1 refcount:1 mapcount:0 mapping:0000000000000000 index:0x0 pfn:0x251a8
flags: 0xfffe0000000200(slab)
raw: 00fffe0000000200 ffffea0000435c88 ffffea00028b6c08 ffff8880a9055d00
raw: 0000000000000000 ffff8880251a80c0 000000010000000c 0000000000000000
page dumped because: kasan: bad access detected
Memory state around the buggy address:
ffff8880251a8b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
ffff8880251a8b80: fb fb fb fb fc fc fc fc fc fc fc fc fc fc fc fc
>ffff8880251a8c00: fa fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb
^
ffff8880251a8c80: fb fb fb fb fb fb fb fb fb fb fb fb fc fc fc fc
ffff8880251a8d00: fc fc fc fc fc fc fc fc fa fb fb fb fb fb fb fb--- net/mac802154/tx.c | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-)
net/mac802154/tx.c +5 -3
@@ -34,11 +34,11 @@ void ieee802154_xmit_worker(struct work_struct *work)if (res) goto err_tx; -ieee802154_xmit_complete (&local->hw, skb, false); - dev->stats.tx_packets++; dev->stats.tx_bytes += skb->len; +ieee802154_xmit_complete (&local->hw, skb, false); +return ; err_tx:
@@ -78,6 +78,8 @@ ieee802154_tx(struct ieee802154_local *local, struct sk_buff *skb)/* async is priority, otherwise sync is fallback */ if (local->ops->xmit_async) { +unsigned int len = skb->len; + ret =drv_xmit_async (local, skb);if (ret) {ieee802154_wake_queue (&local->hw);
@@ -85,7 +87,7 @@ ieee802154_tx(struct ieee802154_local *local, struct sk_buff *skb) } dev->stats.tx_packets++; - dev->stats.tx_bytes += skb->len; + dev->stats.tx_bytes += len; }else { local->tx_skb = skb;queue_work (local->workqueue, &local->tx_work);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 34/99 bpf: Fix clobbering of r2 in bpf_gen_ld_abs
In reply to Greg Kroah-HartmanFrom: Daniel Borkmann <[email protected]>
[ Upstream commit e6a18d36118bea3bf497c9df4d9988b6df120689 ]
Bryce reported that he saw the following with:
0: r6 = r1 1: r1 = 12 2: r0 = *(u16 *)skb[r1]
The xlated sequence was incorrectly clobbering r2 with pointer value of r6 ...
0: (bf) r6 = r1
1: (b7) r1 = 12
2: (bf) r1 = r6
3: (bf) r2 = r1
4: (85) call bpf_skb_load_helper_16_no_cache#7692160
... and hence call to the load helper never succeeded given the offset was too high. Fix it by reordering the load of r6 to r1.
Other than that the insn has similar calling convention than BPF helpers, that is, r0 - r5 are scratch regs, so nothing else affected after the insn.
--- net/core/filter.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
net/core/filter.c +2 -2
@@ -6998,8 +6998,6 @@ static int bpf_gen_ld_abs(const struct bpf_insn *orig,bool indirect =BPF_MODE (orig->code) ==BPF_IND ;struct bpf_insn *insn = insn_buf; -/* We're guaranteed here that CTX is in R6. */ - *insn++ =BPF_MOV64_REG (BPF_REG_1 ,BPF_REG_CTX );if (!indirect) { *insn++ =BPF_MOV64_IMM (BPF_REG_2 , orig->imm); }else {
@@ -7007,6 +7005,8 @@ static int bpf_gen_ld_abs(const struct bpf_insn *orig,if (orig->imm) *insn++ =BPF_ALU64_IMM (BPF_ADD ,BPF_REG_2 , orig->imm); } +/* We're guaranteed here that CTX is in R6. */ + *insn++ =BPF_MOV64_REG (BPF_REG_1 ,BPF_REG_CTX );switch (BPF_SIZE (orig->code)) {case BPF_B :
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 35/99 tools/libbpf: Avoid counting local symbols in ABI check
In reply to Greg Kroah-HartmanFrom: Tony Ambardar <[email protected]>
[ Upstream commit 746f534a4809e07f427f7d13d10f3a6a9641e5c3 ]
Encountered the following failure building libbpf from kernel 5.8.5 sources with GCC 8.4.0 and binutils 2.34: (long paths shortened)
Warning: Num of global symbols in sharedobjs/libbpf-in.o (234) does NOT match with num of versioned symbols in libbpf.so (236). Please make sure all LIBBPF_API symbols are versioned in libbpf.map.
# --- libbpf_global_syms.tmp 2020-09-02 07:30:58.920084380 +0000
# +++ libbpf_versioned_syms.tmp 2020-09-02 07:30:58.924084388 +0000
@@ -1,3 +1,5 @@
+_fini
+_init
bpf_btf_get_fd_by_id
bpf_btf_get_next_id
bpf_create_map
make[4]: *** [Makefile:210: check_abi] Error 1
Investigation shows _fini and _init are actually local symbols counted amongst global ones:
$ readelf --dyn-syms --wide libbpf.so|head -10
Symbol table '.dynsym' contains 343 entries:
Num: Value Size Type Bind Vis Ndx Name
0: 00000000 0 NOTYPE LOCAL DEFAULT UND
1: 00004098 0 SECTION LOCAL DEFAULT 11
2: 00004098 8 FUNC LOCAL DEFAULT 11 _init@@LIBBPF_0.0.1
3: 00023040 8 FUNC LOCAL DEFAULT 14 _fini@@LIBBPF_0.0.1
4: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.4
5: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.1
6: 0000ffa4 8 FUNC GLOBAL DEFAULT 12 bpf_object__find_map_by_offset@@LIBBPF_0.0.1A previous commit filtered global symbols in sharedobjs/libbpf-in.o. Do the same with the libbpf.so DSO for consistent comparison.
--- tools/lib/bpf/Makefile | 2 ++ 1 file changed, 2 insertions(+)
tools/lib/bpf/Makefile +2 -0
@@ -152,6 +152,7 @@ GLOBAL_SYM_COUNT = $(shell readelf -s -- awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ sort -u | wc -l) VERSIONED_SYM_COUNT = $(shell readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | sort -u | wc -l) CMD_TARGETS = $(LIB_TARGET) $(PC_FILE)
@@ -219,6 +220,7 @@ check_abi: $(OUTPUT)libbpf.so awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ sort -u > $(OUTPUT)libbpf_global_syms.tmp; \ readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | \ sort -u > $(OUTPUT)libbpf_versioned_syms.tmp; \ diff -u $(OUTPUT)libbpf_global_syms.tmp \
Re: [PATCH 5.8 35/99] tools/libbpf: Avoid counting local symbols in ABI check
Quoted 39 lines · Greg Kroah-Hartman
From: Tony Ambardar <[email protected]>
[ Upstream commit
746f534a4809e07f427f7d13d10f3a6a9641e5c3]Encountered the following failure building libbpf from kernel 5.8.5 sources with GCC 8.4.0 and binutils 2.34: (long paths shortened)
Warning: Num of global symbols in
sharedobjs/libbpf-in.o(234) does NOT match with num of versioned symbols in libbpf.so (236). Please make sure allLIBBPF_APIsymbols are versioned in libbpf.map.
# --- libbpf_global_syms.tmp 2020-09-02 07:30:58.920084380 +0000
# +++ libbpf_versioned_syms.tmp 2020-09-02 07:30:58.924084388 +0000
@@ -1,3 +1,5 @@
+_fini
+_init
bpf_btf_get_fd_by_id
bpf_btf_get_next_id
bpf_create_map
make[4]: *** [Makefile:210:check_abi] Error 1Investigation shows
_finiand_initare actually local symbols counted amongst global ones:$ readelf --dyn-syms --wide libbpf.so|head -10Symbol table '.dynsym' contains 343 entries:
Num: Value Size Type Bind Vis Ndx Name 0: 00000000 0 NOTYPE LOCAL DEFAULT UND 1: 00004098 0 SECTION LOCAL DEFAULT 11 2: 00004098 8 FUNC LOCAL DEFAULT 11 _init@@LIBBPF_0.0.1 3: 00023040 8 FUNC LOCAL DEFAULT 14 _fini@@LIBBPF_0.0.1 4: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.4 5: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.1 6: 0000ffa4 8 FUNC GLOBAL DEFAULT 12 bpf_object__find_map_by_offset@@LIBBPF_0.0.1A previous commit filtered global symbols in
sharedobjs/libbpf-in.o. Do the same with the libbpf.so DSO for consistent comparison.
Quoted 6 lines
Fixes 306b267cb3c4 ("libbpf: Verify versioned symbols")Signed-off-by Tony Ambardar <[email protected]>Signed-off-by Alexei Starovoitov <[email protected]>Acked-by Andrii Nakryiko <[email protected]>Signed-off-by Sasha Levin <[email protected]>
This seems to work everywhere else, but breaks PPC64LE.
Justin
Quoted 24 lines
--- tools/lib/bpf/Makefile | 2 ++ 1 file changed, 2 insertions(+)tools/lib/bpf/Makefile +2
-0@@ -152,6 +152,7 @@ GLOBAL_SYM_COUNT = $(shell readelf -s -- awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ sort -u | wc -l) VERSIONED_SYM_COUNT = $(shell readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | sort -u | wc -l) CMD_TARGETS = $(LIB_TARGET) $(PC_FILE)@@ -219,6 +220,7 @@ check_abi: $(OUTPUT)libbpf.so awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ sort -u > $(OUTPUT)libbpf_global_syms.tmp; \ readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | \ sort -u > $(OUTPUT)libbpf_versioned_syms.tmp; \ diff -u $(OUTPUT)libbpf_global_syms.tmp \
Re: [PATCH 5.8 35/99] tools/libbpf: Avoid counting local symbols in ABI check
[adding Michael Ellerman, linux-ppc maintainer]
Hello Justin,
Quoted 42 lines · Justin Forbes
Quoted 39 lines · Greg Kroah-Hartman
From: Tony Ambardar <[email protected]>
[ Upstream commit
746f534a4809e07f427f7d13d10f3a6a9641e5c3]Encountered the following failure building libbpf from kernel 5.8.5 sources with GCC 8.4.0 and binutils 2.34: (long paths shortened)
Warning: Num of global symbols in
sharedobjs/libbpf-in.o(234) does NOT match with num of versioned symbols in libbpf.so (236). Please make sure allLIBBPF_APIsymbols are versioned in libbpf.map.
# --- libbpf_global_syms.tmp 2020-09-02 07:30:58.920084380 +0000
# +++ libbpf_versioned_syms.tmp 2020-09-02 07:30:58.924084388 +0000
@@ -1,3 +1,5 @@
+_fini
+_init
bpf_btf_get_fd_by_id
bpf_btf_get_next_id
bpf_create_map
make[4]: *** [Makefile:210:check_abi] Error 1Investigation shows
_finiand_initare actually local symbols counted amongst global ones:$ readelf --dyn-syms --wide libbpf.so|head -10Symbol table '.dynsym' contains 343 entries:
Num: Value Size Type Bind Vis Ndx Name 0: 00000000 0 NOTYPE LOCAL DEFAULT UND 1: 00004098 0 SECTION LOCAL DEFAULT 11 2: 00004098 8 FUNC LOCAL DEFAULT 11 _init@@LIBBPF_0.0.1 3: 00023040 8 FUNC LOCAL DEFAULT 14 _fini@@LIBBPF_0.0.1 4: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.4 5: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.1 6: 0000ffa4 8 FUNC GLOBAL DEFAULT 12 bpf_object__find_map_by_offset@@LIBBPF_0.0.1A previous commit filtered global symbols in
sharedobjs/libbpf-in.o. Do the same with the libbpf.so DSO for consistent comparison.
Quoted 9 lines
Quoted 6 lines
Fixes 306b267cb3c4 ("libbpf: Verify versioned symbols")Signed-off-by Tony Ambardar <[email protected]>Signed-off-by Alexei Starovoitov <[email protected]>Acked-by Andrii Nakryiko <[email protected]>Signed-off-by Sasha Levin <[email protected]>This seems to work everywhere else, but breaks PPC64LE.
I also ran into a PPC build error while working on some bpf problems, but it seemed
like a pre-existing PPC issue. I did submit an upstream fix, which is marked for stable
and being reviewed by Michael. See here for discussion and the patch:
https://lkml.org/lkml/2020/9/17/668.
Is that the same problem you encountered? Does that patch address your issue?
Thanks,
Tony
Quoted 26 lines
Justin
Quoted 24 lines
--- tools/lib/bpf/Makefile | 2 ++ 1 file changed, 2 insertions(+)tools/lib/bpf/Makefile +2
-0@@ -152,6 +152,7 @@ GLOBAL_SYM_COUNT = $(shell readelf -s -- awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ sort -u | wc -l) VERSIONED_SYM_COUNT = $(shell readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | sort -u | wc -l) CMD_TARGETS = $(LIB_TARGET) $(PC_FILE)@@ -219,6 +220,7 @@ check_abi: $(OUTPUT)libbpf.so awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ sort -u > $(OUTPUT)libbpf_global_syms.tmp; \ readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | \ sort -u > $(OUTPUT)libbpf_versioned_syms.tmp; \ diff -u $(OUTPUT)libbpf_global_syms.tmp \
Re: [PATCH 5.8 35/99] tools/libbpf: Avoid counting local symbols in ABI check
Quoted 58 lines · Tony Ambardar
[adding Michael Ellerman, linux-ppc maintainer]
Hello Justin,
Quoted 42 lines · Justin Forbes
Quoted 39 lines · Greg Kroah-Hartman
From: Tony Ambardar <[email protected]>
[ Upstream commit
746f534a4809e07f427f7d13d10f3a6a9641e5c3]Encountered the following failure building libbpf from kernel 5.8.5 sources with GCC 8.4.0 and binutils 2.34: (long paths shortened)
Warning: Num of global symbols in
sharedobjs/libbpf-in.o(234) does NOT match with num of versioned symbols in libbpf.so (236). Please make sure allLIBBPF_APIsymbols are versioned in libbpf.map.
# --- libbpf_global_syms.tmp 2020-09-02 07:30:58.920084380 +0000
# +++ libbpf_versioned_syms.tmp 2020-09-02 07:30:58.924084388 +0000
@@ -1,3 +1,5 @@
+_fini
+_init
bpf_btf_get_fd_by_id
bpf_btf_get_next_id
bpf_create_map
make[4]: *** [Makefile:210:check_abi] Error 1Investigation shows
_finiand_initare actually local symbols counted amongst global ones:$ readelf --dyn-syms --wide libbpf.so|head -10Symbol table '.dynsym' contains 343 entries:
Num: Value Size Type Bind Vis Ndx Name 0: 00000000 0 NOTYPE LOCAL DEFAULT UND 1: 00004098 0 SECTION LOCAL DEFAULT 11 2: 00004098 8 FUNC LOCAL DEFAULT 11 _init@@LIBBPF_0.0.1 3: 00023040 8 FUNC LOCAL DEFAULT 14 _fini@@LIBBPF_0.0.1 4: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.4 5: 00000000 0 OBJECT GLOBAL DEFAULT ABS LIBBPF_0.0.1 6: 0000ffa4 8 FUNC GLOBAL DEFAULT 12 bpf_object__find_map_by_offset@@LIBBPF_0.0.1A previous commit filtered global symbols in
sharedobjs/libbpf-in.o. Do the same with the libbpf.so DSO for consistent comparison.Quoted 9 lines
Quoted 6 lines
Fixes 306b267cb3c4 ("libbpf: Verify versioned symbols")Signed-off-by Tony Ambardar <[email protected]>Signed-off-by Alexei Starovoitov <[email protected]>Acked-by Andrii Nakryiko <[email protected]>Signed-off-by Sasha Levin <[email protected]>This seems to work everywhere else, but breaks PPC64LE.
Quoted 8 lines
I also ran into a PPC build error while working on some bpf problems, but it seemed
like a pre-existing PPC issue. I did submit an upstream fix, which is marked for stable
and being reviewed by Michael. See here for discussion and the patch:
https://lkml.org/lkml/2020/9/17/668.Is that the same problem you encountered? Does that patch address your issue?
It is not, the issue I see is:
Warning: Num of global symbols in sharedobjs/libbpf-in.o (259) does NOT match with num of versioned symbols in libbpf.so (50). Please make sure all LIBBPF_API symbols are versioned in libbpf.map.
I only see it on ppc64le with this patch, all other arch that Fedora builds are fine (x86_64, i686, aarch64, armv7, s390). If I revert this patch, all builds succeed. We are using gcc 10.2.1 though.
Justin
Quoted 30 lines
Thanks,
TonyQuoted 26 lines
Justin
Quoted 24 lines
--- tools/lib/bpf/Makefile | 2 ++ 1 file changed, 2 insertions(+)tools/lib/bpf/Makefile +2
-0@@ -152,6 +152,7 @@ GLOBAL_SYM_COUNT = $(shell readelf -s -- awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ sort -u | wc -l) VERSIONED_SYM_COUNT = $(shell readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}' | \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | sort -u | wc -l) CMD_TARGETS = $(LIB_TARGET) $(PC_FILE)@@ -219,6 +220,7 @@ check_abi: $(OUTPUT)libbpf.so awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ sort -u > $(OUTPUT)libbpf_global_syms.tmp; \ readelf --dyn-syms --wide $(OUTPUT)libbpf.so | \ + awk '/GLOBAL/ && /DEFAULT/ && !/UND/ {print $$NF}'| \ grep -Eo '[^ ]+@LIBBPF_' | cut -d@ -f1 | \ sort -u > $(OUTPUT)libbpf_versioned_syms.tmp; \ diff -u $(OUTPUT)libbpf_global_syms.tmp \
Greg Kroah-Hartman
maintainerPATCH 36/99 drm/vc4/vc4_hdmi: fill ASoC card owner
In reply to Greg Kroah-HartmanFrom: Marek Szyprowski <[email protected]>
[ Upstream commit ec653df2a0cbc306a4bfcb0e3484d318fa779002 ]
card->owner is a required property and since commit 81033c6b584b ("ALSA:
core: Warn on empty module") a warning is issued if it is empty. Fix lack of it. This fixes following warning observed on RaspberryPi 3B board with ARM 32bit kernel and multi_v7_defconfig:
------------[ cut here ]------------ WARNING: CPU: 1 PID: 210 at sound/core/init.c:207 snd_card_new+0x378/0x398 [snd] Modules linked in: vc4(+) snd_soc_core ac97_bus snd_pcm_dmaengine bluetooth snd_pcm snd_timer crc32_arm_ce raspberrypi_hwmon snd soundcore ecdh_generic ecc bcm2835_thermal phy_generic CPU: 1 PID: 210 Comm: systemd-udevd Not tainted 5.8.0-rc1-00027-g81033c6b584b #1087 Hardware name: BCM2835 [<c03113c0>] (unwind_backtrace) from [<c030bcb4>] (show_stack+0x10/0x14) [<c030bcb4>] (show_stack) from [<c071cef8>] (dump_stack+0xd4/0xe8) [<c071cef8>] (dump_stack) from [<c0345bfc>] (__warn+0xdc/0xf4) [<c0345bfc>] (__warn) from [<c0345cc4>] (warn_slowpath_fmt+0xb0/0xb8) [<c0345cc4>] (warn_slowpath_fmt) from [<bf02ff74>] (snd_card_new+0x378/0x398 [snd]) [<bf02ff74>] (snd_card_new [snd]) from [<bf11f0b4>] (snd_soc_bind_card+0x280/0x99c [snd_soc_core]) [<bf11f0b4>] (snd_soc_bind_card [snd_soc_core]) from [<bf12f000>] (devm_snd_soc_register_card+0x34/0x6c [snd_soc_core]) [<bf12f000>] (devm_snd_soc_register_card [snd_soc_core]) from [<bf165654>] (vc4_hdmi_bind+0x43c/0x5f4 [vc4]) [<bf165654>] (vc4_hdmi_bind [vc4]) from [<c09d660c>] (component_bind_all+0xec/0x24c) [<c09d660c>] (component_bind_all) from [<bf15c44c>] (vc4_drm_bind+0xd4/0x174 [vc4]) [<bf15c44c>] (vc4_drm_bind [vc4]) from [<c09d6ac0>] (try_to_bring_up_master+0x160/0x1b0) [<c09d6ac0>] (try_to_bring_up_master) from [<c09d6f38>] (component_master_add_with_match+0xd0/0x104) [<c09d6f38>] (component_master_add_with_match) from [<bf15c588>] (vc4_platform_drm_probe+0x9c/0xbc [vc4]) [<bf15c588>] (vc4_platform_drm_probe [vc4]) from [<c09df740>] (platform_drv_probe+0x6c/0xa4) [<c09df740>] (platform_drv_probe) from [<c09dd6f0>] (really_probe+0x210/0x350) [<c09dd6f0>] (really_probe) from [<c09dd940>] (driver_probe_device+0x5c/0xb4) [<c09dd940>] (driver_probe_device) from [<c09ddb38>] (device_driver_attach+0x58/0x60) [<c09ddb38>] (device_driver_attach) from [<c09ddbc0>] (__driver_attach+0x80/0xbc) [<c09ddbc0>] (__driver_attach) from [<c09db820>] (bus_for_each_dev+0x68/0xb4) [<c09db820>] (bus_for_each_dev) from [<c09dc9f8>] (bus_add_driver+0x130/0x1e8) [<c09dc9f8>] (bus_add_driver) from [<c09de648>] (driver_register+0x78/0x110) [<c09de648>] (driver_register) from [<c0302038>] (do_one_initcall+0x50/0x220) [<c0302038>] (do_one_initcall) from [<c03db544>] (do_init_module+0x60/0x210) [<c03db544>] (do_init_module) from [<c03da4f8>] (load_module+0x1e34/0x2338) [<c03da4f8>] (load_module) from [<c03dac00>] (sys_finit_module+0xac/0xbc) [<c03dac00>] (sys_finit_module) from [<c03000c0>] (ret_fast_syscall+0x0/0x54) Exception stack(0xeded9fa8 to 0xeded9ff0) ... ---[ end trace 6414689569c2bc08 ]---
--- drivers/gpu/drm/vc4/vc4_hdmi.c | 1 + 1 file changed, 1 insertion(+)
drivers/gpu/drm/vc4/vc4_hdmi.c +1 -0
@@ -1117,6 +1117,7 @@ static int vc4_hdmi_audio_init(struct vc4_hdmi *hdmi) card->num_links =1 ; card->name ="vc4-hdmi" ; card->dev = dev; + card->owner =THIS_MODULE ;/* * Be careful, snd_soc_register_card() calls dev_set_drvdata() and
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 37/99 net: qed: Disable aRFS for NPAR and 100G
In reply to Greg Kroah-HartmanFrom: Dmitry Bogdanov <[email protected]>
[ Upstream commit 2d2fe8433796603091ac8ea235b9165ac5a85f9a ]
In CMT and NPAR the PF is unknown when the GFS block processes the packet. Therefore cannot use searcher as it has a per PF database, and thus ARFS must be disabled.
--- drivers/net/ethernet/qlogic/qed/qed_dev.c | 11 ++++++++++- drivers/net/ethernet/qlogic/qed/qed_l2.c | 3 +++ drivers/net/ethernet/qlogic/qed/qed_main.c | 2 ++ include/linux/qed/qed_if.h | 1 + 4 files changed, 16 insertions(+), 1 deletion(-)
drivers/net/ethernet/qlogic/qed/qed_dev.c +10 -1
@@ -4191,7 +4191,8 @@ static int qed_hw_get_nvm_info(struct qed_hwfn *p_hwfn, struct qed_ptt *p_ptt) cdev->mf_bits =BIT (QED_MF_LLH_MAC_CLSS ) |BIT (QED_MF_LLH_PROTO_CLSS ) |BIT (QED_MF_LL2_NON_UNICAST ) | -BIT (QED_MF_INTER_PF_SWITCH ); +BIT (QED_MF_INTER_PF_SWITCH ) | +BIT (QED_MF_DISABLE_ARFS );break ;case NVM_CFG1_GLOB_MF_MODE_DEFAULT : cdev->mf_bits = BIT(QED_MF_LLH_MAC_CLSS) |
@@ -4204,6 +4205,14 @@ static int qed_hw_get_nvm_info(struct qed_hwfn *p_hwfn, struct qed_ptt *p_ptt)DP_INFO (p_hwfn,"Multi function mode is 0x%lx\n" , cdev->mf_bits); + +/* In CMT the PF is unknown when the GFS block processes the +* packet. Therefore cannot use searcher as it has a per PF +* database, and thus ARFS must be disabled. +* +*/ +if (QED_IS_CMT (cdev)) + cdev->mf_bits |=BIT (QED_MF_DISABLE_ARFS ); } DP_INFO(p_hwfn, "Multi function mode is 0x%lx\n",
drivers/net/ethernet/qlogic/qed/qed_l2.c +3 -0
@@ -2001,6 +2001,9 @@ void qed_arfs_mode_configure(struct qed_hwfn *p_hwfn, struct qed_ptt *p_ptt, struct qed_arfs_config_params *p_cfg_params) { + if (test_bit(QED_MF_DISABLE_ARFS, &p_hwfn->cdev->mf_bits)) + return; +if (p_cfg_params->mode !=QED_FILTER_CONFIG_MODE_DISABLE ) { qed_gft_config(p_hwfn, p_ptt, p_hwfn->rel_pf_id, p_cfg_params->tcp,
drivers/net/ethernet/qlogic/qed/qed_main.c +2 -0
@@ -289,6 +289,8 @@ int qed_fill_dev_info(struct qed_dev *cdev, dev_info->fw_eng =FW_ENGINEERING_VERSION ; dev_info->b_inter_pf_switch =test_bit (QED_MF_INTER_PF_SWITCH , &cdev->mf_bits); +if (!test_bit (QED_MF_DISABLE_ARFS , &cdev->mf_bits)) + dev_info->b_arfs_capable = true; dev_info->tx_switching = true;if (hw_info->b_wol_support ==QED_WOL_SUPPORT_PME )
include/linux/qed/qed_if.h +1 -0
@@ -648,6 +648,7 @@ struct qed_dev_info {#define QED_MFW_VERSION_3_OFFSET 24u32 flash_size; +bool b_arfs_capable;bool b_inter_pf_switch;bool tx_switching;bool rdma_supported;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 38/99 net: qede: Disable aRFS for NPAR and 100G
In reply to Greg Kroah-HartmanFrom: Dmitry Bogdanov <[email protected]>
[ Upstream commit 0367f05885b9f21d062447bd2ba1302ba3cc7392 ]
In some configurations ARFS cannot be used, so disable it if device is not capable.
--- drivers/net/ethernet/qlogic/qede/qede_filter.c | 3 +++ drivers/net/ethernet/qlogic/qede/qede_main.c | 11 +++++------ 2 files changed, 8 insertions(+), 6 deletions(-)
drivers/net/ethernet/qlogic/qede/qede_filter.c +3 -0
@@ -336,6 +336,9 @@ int qede_alloc_arfs(struct qede_dev *edev) {int i; +if (!edev->dev_info.common.b_arfs_capable) +return -EINVAL ; + edev->arfs =vzalloc (sizeof (*edev->arfs));if (!edev->arfs)return -ENOMEM ;
drivers/net/ethernet/qlogic/qede/qede_main.c +5 -6
@@ -827,7 +827,7 @@ static void qede_init_ndev(struct qede_dev *edev)NETIF_F_IP_CSUM |NETIF_F_IPV6_CSUM |NETIF_F_TSO |NETIF_F_TSO6 |NETIF_F_HW_TC ; -if (!IS_VF (edev) && edev->dev_info.common.num_hwfns ==1 ) +if (edev->dev_info.common.b_arfs_capable) hw_features |=NETIF_F_NTUPLE ; if (edev->dev_info.common.vxlan_enable ||
@@ -2278,7 +2278,7 @@ static void qede_unload(struct qede_dev *edev, enum qede_unload_mode mode,qede_vlan_mark_nonconfigured (edev); edev->ops->fastpath_stop (edev->cdev); -if (!IS_VF (edev) && edev->dev_info.common.num_hwfns ==1 ) { +if (edev->dev_info.common.b_arfs_capable) {qede_poll_for_freeing_arfs_filters (edev);qede_free_arfs (edev); }
@@ -2345,10 +2345,9 @@ static int qede_load(struct qede_dev *edev, enum qede_load_mode mode,if (rc) goto err2; -if (!IS_VF (edev) && edev->dev_info.common.num_hwfns ==1 ) { - rc =qede_alloc_arfs (edev); -if (rc) -DP_NOTICE (edev,"aRFS memory allocation failed\n" ); +if (qede_alloc_arfs (edev)) { + edev->ndev->features &= ~NETIF_F_NTUPLE ; + edev->dev_info.common.b_arfs_capable = false; }qede_napi_add_enable (edev);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 39/99 net: qed: RDMA personality shouldnt fail VF load
In reply to Greg Kroah-HartmanFrom: Dmitry Bogdanov <[email protected]>
[ Upstream commit ce1cf9e5025f4e2d2198728391f1847b3e168bc6 ]
Fix the assert during VF driver installation when the personality is iWARP
--- drivers/net/ethernet/qlogic/qed/qed_sriov.c | 1 + 1 file changed, 1 insertion(+)
drivers/net/ethernet/qlogic/qed/qed_sriov.c +1 -0
@@ -97,6 +97,7 @@ static int qed_sp_vf_start(struct qed_hwfn *p_hwfn, struct qed_vf_info *p_vf) p_ramrod->personality =PERSONALITY_ETH ;break ;case QED_PCI_ETH_ROCE : +case QED_PCI_ETH_IWARP : p_ramrod->personality =PERSONALITY_RDMA_AND_ETH ;break ;default :
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 40/99 igc: Fix wrong timestamp latency numbers
In reply to Greg Kroah-HartmanFrom: Vinicius Costa Gomes <[email protected]>
[ Upstream commit f03369b9bfab8e23ac28ca7ab7e6631c374b7cbe ]
The previous timestamping latency numbers were obtained by interpolating the i210 numbers with the i225 crystal clock value. That calculation was wrong.
Use the correct values from real measurements.
--- drivers/net/ethernet/intel/igc/igc.h | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-)
drivers/net/ethernet/intel/igc/igc.h +8 -12
@@ -298,18 +298,14 @@ extern char igc_driver_version[];#define IGC_RX_HDR_LEN IGC_RXBUFFER_256/* Transmit and receive latency (for PTP timestamps) */ -/* FIXME: These values were estimated using the ones that i225 has as -* basis, they seem to provide good numbers with ptp4l/phc2sys, but we -* need to confirm them. -*/ -#define IGC_I225_TX_LATENCY_10 9542 -#define IGC_I225_TX_LATENCY_100 1024 -#define IGC_I225_TX_LATENCY_1000 178 -#define IGC_I225_TX_LATENCY_2500 64 -#define IGC_I225_RX_LATENCY_10 20662 -#define IGC_I225_RX_LATENCY_100 2213 -#define IGC_I225_RX_LATENCY_1000 448 -#define IGC_I225_RX_LATENCY_2500 160 +#define IGC_I225_TX_LATENCY_10 240 +#define IGC_I225_TX_LATENCY_100 58 +#define IGC_I225_TX_LATENCY_1000 80 +#define IGC_I225_TX_LATENCY_2500 1325 +#define IGC_I225_RX_LATENCY_10 6450 +#define IGC_I225_RX_LATENCY_100 185 +#define IGC_I225_RX_LATENCY_1000 300 +#define IGC_I225_RX_LATENCY_2500 1485/* RX and TX descriptor control thresholds. * PTHRESH - MAC will consider prefetch if it has fewer than this number of
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 41/99 igc: Fix not considering the TX delay for timestamps
In reply to Greg Kroah-HartmanFrom: Vinicius Costa Gomes <[email protected]>
[ Upstream commit 4406e977a4a1e997818b6d77c3218ef8d15b2abf ]
When timestamping a packet there's a delay between the start of the packet and the point where the hardware actually captures the timestamp. This difference needs to be considered if we want accurate timestamps.
This was done on the RX side, but not on the TX side.
--- drivers/net/ethernet/intel/igc/igc_ptp.c | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+)
drivers/net/ethernet/intel/igc/igc_ptp.c +19 -0
@@ -471,12 +471,31 @@ static void igc_ptp_tx_hwtstamp(struct igc_adapter *adapter)struct sk_buff *skb = adapter->ptp_tx_skb;struct skb_shared_hwtstamps shhwtstamps;struct igc_hw *hw = &adapter->hw; +int adjust =0 ;u64 regval; regval =rd32 (IGC_TXSTMPL ); regval |= (u64 )rd32 (IGC_TXSTMPH ) <<32 ;igc_ptp_systim_to_hwtstamp (adapter, &shhwtstamps, regval); +switch (adapter->link_speed) { +case SPEED_10 : + adjust =IGC_I225_TX_LATENCY_10 ; +break ; +case SPEED_100 : + adjust =IGC_I225_TX_LATENCY_100 ; +break ; +case SPEED_1000 : + adjust =IGC_I225_TX_LATENCY_1000 ; +break ; +case SPEED_2500 : + adjust =IGC_I225_TX_LATENCY_2500 ; +break ; + } + + shhwtstamps.hwtstamp = +ktime_add_ns (shhwtstamps.hwtstamp, adjust); +/* Clear the lock early before calling skb_tstamp_tx so that * applications are not woken up before the lock bit is clear. We use * a copy of the skb pointer to ensure other threads can't change it
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 42/99 drm/sun4i: sun8i-csc: Secondary CSC register correction
In reply to Greg Kroah-HartmanFrom: Martin Cerveny <[email protected]>
[ Upstream commit cab4c03b4ba54c8d9378298cacb8bc0fd74ceece ]
"Allwinner V3s" has secondary video layer (VI). Decoded video is displayed in wrong colors until secondary CSC registers are programmed correctly.
--- drivers/gpu/drm/sun4i/sun8i_csc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/sun4i/sun8i_csc.h +1 -1
@@ -12,7 +12,7 @@ struct sun8i_mixer;/* VI channel CSC units offsets */ #define CCSC00_OFFSET 0xAA050 -#define CCSC01_OFFSET 0xFA000 +#define CCSC01_OFFSET 0xFA050#define CCSC10_OFFSET 0xA0000#define CCSC11_OFFSET 0xF0000
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 43/99 hv_netvsc: Switch the data path at the right time during hibernation
In reply to Greg Kroah-HartmanFrom: Dexuan Cui <[email protected]>
[ Upstream commit de214e52de1bba5392b5b7054924a08dbd57c2f6 ]
When netvsc_resume() is called, the mlx5 VF NIC has not been resumed yet, so in the future the host might sliently fail the call netvsc_vf_changed() -> netvsc_switch_datapath() there, even if the call works now.
Call netvsc_vf_changed() in the NETDEV_CHANGE event handler: at that time the mlx5 VF NIC has been resumed.
--- drivers/net/hyperv/netvsc_drv.c | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-)
drivers/net/hyperv/netvsc_drv.c +1 -10
@@ -2576,7 +2576,6 @@ static int netvsc_resume(struct hv_device *dev)struct net_device *net =hv_get_drvdata (dev);struct net_device_context *net_device_ctx;struct netvsc_device_info *device_info; -struct net_device *vf_netdev;int ret;rtnl_lock ();
@@ -2589,15 +2588,6 @@ static int netvsc_resume(struct hv_device *dev)netvsc_devinfo_put (device_info); net_device_ctx->saved_netvsc_dev_info =NULL ; -/* A NIC driver (e.g. mlx5) may keep the VF network interface across -* hibernation, but here the data path is implicitly switched to the -* netvsc NIC since the vmbus channel is closed and re-opened, so -* netvsc_vf_changed() must be used to switch the data path to the VF. -*/ - vf_netdev =rtnl_dereference (net_device_ctx->vf_netdev); -if (vf_netdev &&netvsc_vf_changed (vf_netdev) !=NOTIFY_OK ) - ret = -EINVAL ; -rtnl_unlock ();return ret;
@@ -2658,6 +2648,7 @@ static int netvsc_netdev_event(struct notifier_block *this,return netvsc_unregister_vf (event_dev);case NETDEV_UP :case NETDEV_DOWN : +case NETDEV_CHANGE :return netvsc_vf_changed (event_dev);default :return NOTIFY_DONE ;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 44/99 spi: spi-fsl-dspi: use XSPI mode instead of DMA for DPAA2 SoCs
In reply to Greg Kroah-HartmanFrom: Vladimir Oltean <[email protected]>
[ Upstream commit 505623a2be48b36de533951ced130876a76a2d55 ]
The arch/arm64/boot/dts/freescale/fsl-ls208xa.dtsi device tree lacks DMA channels for DSPI, so naturally, the driver fails to probe:
[ 2.945302] fsl-dspi 2100000.spi: rx dma channel not available [ 2.951134] fsl-dspi 2100000.spi: can't get dma channels
In retrospect, this should have been obvious, because LS2080A, LS2085A LS2088A and LX2160A don't appear to have an eDMA module at all. Looking again at their datasheets, the CTARE register (which is specific to XSPI functionality) seems to be documented, so switch them to XSPI mode instead.
--- drivers/spi/spi-fsl-dspi.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
drivers/spi/spi-fsl-dspi.c +3 -3
@@ -174,17 +174,17 @@ static const struct fsl_dspi_devtype_data devtype_data[] = { .fifo_size = 16, }, [LS2080A] = { - .trans_mode = DSPI_DMA_MODE, + .trans_mode = DSPI_XSPI_MODE, .max_clock_factor = 8, .fifo_size = 4, }, [LS2085A] = { - .trans_mode = DSPI_DMA_MODE, + .trans_mode = DSPI_XSPI_MODE, .max_clock_factor = 8, .fifo_size = 4, }, [LX2160A] = { - .trans_mode = DSPI_DMA_MODE, + .trans_mode = DSPI_XSPI_MODE, .max_clock_factor = 8, .fifo_size = 4, },
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 45/99 RDMA/core: Fix ordering of CQ pool destruction
In reply to Greg Kroah-HartmanFrom: Jason Gunthorpe <[email protected]>
[ Upstream commit 4aa1615268a8ac2b20096211d3f9ac53874067d7 ]
rxe will hold a refcount on the IB device as long as CQ objects exist, this causes destruction of a rxe device to hang if the CQ pool has any cached CQs since they are being destroyed after the refcount must go to zero.
Treat the CQ pool like a client and create/destroy it before/after all other clients. No users of CQ pool can exist past a client remove call.
--- drivers/infiniband/core/device.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
drivers/infiniband/core/device.c +4 -2
@@ -1282,6 +1282,8 @@ static void disable_device(struct ib_device *device)remove_client_context (device, cid); } +ib_cq_pool_destroy (device); +/* Pairs with refcount_set in enable_device */ ib_device_put (device);wait_for_completion (&device->unreg_completion);
@@ -1325,6 +1327,8 @@ static int enable_device_and_get(struct ib_device *device) goto out; } +ib_cq_pool_init (device); +down_read (&clients_rwsem); xa_for_each_marked (&clients, index, client, CLIENT_REGISTERED) { ret =add_client_context (device, client);
@@ -1397,7 +1401,6 @@ int ib_register_device(struct ib_device *device, const char *name) goto dev_cleanup; } -ib_cq_pool_init (device); ret =enable_device_and_get (device);dev_set_uevent_suppress (&device->dev, false);/* Mark for userspace that device is ready */
@@ -1452,7 +1455,6 @@ static void __ib_unregister_device(struct ib_device *ib_dev) goto out;disable_device (ib_dev); -ib_cq_pool_destroy (ib_dev);/* Expedite removing unregistered pointers from the hash table */ free_netdevs (ib_dev);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 46/99 batman-adv: Add missing include for in_interrupt()
In reply to Greg Kroah-HartmanFrom: Sven Eckelmann <[email protected]>
[ Upstream commit 4bba9dab86b6ac15ca560ef1f2b5aa4529cbf784 ]
The fix for receiving (internally generated) bla packets outside the interrupt context introduced the usage of in_interrupt(). But this functionality is only defined in linux/preempt.h which was not included with the same patch.
--- net/batman-adv/bridge_loop_avoidance.c | 1 + 1 file changed, 1 insertion(+)
net/batman-adv/bridge_loop_avoidance.c +1 -0
@@ -25,6 +25,7 @@#include <linux/lockdep.h> #include <linux/netdevice.h> #include <linux/netlink.h> +#include <linux/preempt.h> #include <linux/rculist.h> #include <linux/rcupdate.h> #include <linux/seq_file.h>
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 47/99 xsk: Fix number of pinned pages/umem size discrepancy
In reply to Greg Kroah-HartmanFrom: Björn Töpel <[email protected]>
[ Upstream commit 2b1667e54caf95e1e4249d9068eea7a3089a5229 ]
For AF_XDP sockets, there was a discrepancy between the number of of pinned pages and the size of the umem region.
The size of the umem region is used to validate the AF_XDP descriptor addresses. The logic that pinned the pages covered by the region only took whole pages into consideration, creating a mismatch between the size and pinned pages. A user could then pass AF_XDP addresses outside the range of pinned pages, but still within the size of the region, crashing the kernel.
This change correctly calculates the number of pages to be pinned. Further, the size check for the aligned mode is simplified. Now the code simply checks if the size is divisible by the chunk size.
--- net/xdp/xdp_umem.c | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-)
net/xdp/xdp_umem.c +8 -9
@@ -303,10 +303,10 @@ static int xdp_umem_account_pages(struct xdp_umem *umem)static int xdp_umem_reg (struct xdp_umem *umem,struct xdp_umem_reg *mr) { +u32 npgs_rem, chunk_size = mr->chunk_size, headroom = mr->headroom;bool unaligned_chunks = mr->flags &XDP_UMEM_UNALIGNED_CHUNK_FLAG ; -u32 chunk_size = mr->chunk_size, headroom = mr->headroom;u64 npgs, addr = mr->addr, size = mr->len; -unsigned int chunks, chunks_per_page; +unsigned int chunks, chunks_rem;int err;if (chunk_size <XDP_UMEM_MIN_CHUNK_SIZE || chunk_size >PAGE_SIZE ) {
@@ -336,19 +336,18 @@ static int xdp_umem_reg(struct xdp_umem *umem, struct xdp_umem_reg *mr)if ((addr + size) < addr)return -EINVAL ; - npgs = size >>PAGE_SHIFT ; + npgs =div_u64_rem (size,PAGE_SIZE , &npgs_rem); +if (npgs_rem) + npgs++;if (npgs >U32_MAX )return -EINVAL ; - chunks = (unsigned int )div_u64 (size, chunk_size); + chunks = (unsigned int )div_u64_rem (size, chunk_size, &chunks_rem);if (chunks ==0 )return -EINVAL ; -if (!unaligned_chunks) { - chunks_per_page =PAGE_SIZE / chunk_size; -if (chunks < chunks_per_page || chunks % chunks_per_page) -return -EINVAL ; - } +if (!unaligned_chunks && chunks_rem) +return -EINVAL ;if (headroom >= chunk_size -XDP_PACKET_HEADROOM )return -EINVAL ;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 48/99 nvme-tcp: fix kconfig dependency warning when !CRYPTO
In reply to Greg Kroah-HartmanFrom: Necip Fazil Yildiran <[email protected]>
[ Upstream commit af5ad17854f96a6d3c9775e776bd01ab262672a1 ]
When NVME_TCP is enabled and CRYPTO is disabled, it results in the following Kbuild warning:
WARNING: unmet direct dependencies detected for CRYPTO_CRC32C
Depends on [n]: CRYPTO [=n]
Selected by [y]:
- NVME_TCP [=y] && INET [=y] && BLK_DEV_NVME [=y]
The reason is that NVME_TCP selects CRYPTO_CRC32C without depending on or selecting CRYPTO while CRYPTO_CRC32C is subordinate to CRYPTO.
Honor the kconfig menu hierarchy to remove kconfig dependency warnings.
--- drivers/nvme/host/Kconfig | 1 + 1 file changed, 1 insertion(+)
drivers/nvme/host/Kconfig +1 -0
@@ -73,6 +73,7 @@ config NVME_TCP depends on INET depends on BLK_DEV_NVME select NVME_FABRICS + select CRYPTO select CRYPTO_CRC32C help This provides support for the NVMe over Fabrics protocol using
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 49/99 batman-adv: mcast: fix duplicate mcast packets in BLA backbone from LAN
In reply to Greg Kroah-HartmanFrom: Linus Lüssing <[email protected]>
[ Upstream commit 3236d215ad38a3f5372e65cd1e0a52cf93d3c6a2 ]
Scenario:
* Multicast frame send from a BLA backbone (multiple nodes with their bat0 bridged together, with BLA enabled)
Issue:
* BLA backbone nodes receive the frame multiple times on bat0
For multicast frames received via batman-adv broadcast packets the originator of the broadcast packet is checked before decapsulating and forwarding the frame to bat0 (batadv_bla_is_backbone_gw()-> batadv_recv_bcast_packet()). If it came from a node which shares the same BLA backbone with us then it is not forwarded to bat0 to avoid a loop.
When sending a multicast frame in a non-4-address batman-adv unicast packet we are currently missing this check - and cannot do so because the batman-adv unicast packet has no originator address field.
However, we can simply fix this on the sender side by only sending the multicast frame via unicasts to interested nodes which do not share the same BLA backbone with us. This also nicely avoids some unnecessary transmissions on mesh side.
Note that no infinite loop was observed, probably because of dropping via batadv_interface_tx()->batadv_bla_tx(). However the duplicates still utterly confuse switches/bridges, ICMPv6 duplicate address detection and neighbor discovery and therefore leads to long delays before being able to establish TCP connections, for instance. And it also leads to the Linux bridge printing messages like:
"br-lan: received packet on eth1 with own address as source address ..."
--- net/batman-adv/multicast.c | 46 ++++++++++++++++++++++++++------- net/batman-adv/multicast.h | 15 +++++++++++ net/batman-adv/soft-interface.c | 5 ++-- 3 files changed, 53 insertions(+), 13 deletions(-)
net/batman-adv/multicast.c +36 -10
@@ -51,6 +51,7 @@#include <uapi/linux/batadv_packet.h> #include <uapi/linux/batman_adv.h> +#include "bridge_loop_avoidance.h" #include "hard-interface.h" #include "hash.h" #include "log.h"
@@ -1434,6 +1435,35 @@ batadv_mcast_forw_mode(struct batadv_priv *bat_priv, struct sk_buff *skb,return BATADV_FORW_ALL ; } +/** +* batadv_mcast_forw_send_orig() - send a multicast packet to an originator +* @bat_priv: the bat priv with all the soft interface information +* @skb: the multicast packet to send +* @vid: the vlan identifier +* @orig_node: the originator to send the packet to +* +* Return: NET_XMIT_DROP in case of error or NET_XMIT_SUCCESS otherwise. +*/ +int batadv_mcast_forw_send_orig (struct batadv_priv *bat_priv, +struct sk_buff *skb, +unsigned short vid, +struct batadv_orig_node *orig_node) +{ +/* Avoid sending multicast-in-unicast packets to other BLA +* gateways - they already got the frame from the LAN side +* we share with them. +* TODO: Refactor to take BLA into account earlier, to avoid +* reducing the mcast_fanout count. +*/ +if (batadv_bla_is_backbone_gw_orig (bat_priv, orig_node->orig, vid)) { +dev_kfree_skb (skb); +return NET_XMIT_SUCCESS ; + } + +return batadv_send_skb_unicast (bat_priv, skb,BATADV_UNICAST ,0 , + orig_node, vid); +} +/** * batadv_mcast_forw_tt() - forwards a packet to multicast listeners * @bat_priv: the bat priv with all the soft interface information
@@ -1471,8 +1501,8 @@ batadv_mcast_forw_tt(struct batadv_priv *bat_priv, struct sk_buff *skb,break ; } -batadv_send_skb_unicast (bat_priv, newskb,BATADV_UNICAST ,0 , - orig_entry->orig_node, vid); +batadv_mcast_forw_send_orig (bat_priv, newskb, vid, + orig_entry->orig_node); }rcu_read_unlock ();
@@ -1513,8 +1543,7 @@ batadv_mcast_forw_want_all_ipv4(struct batadv_priv *bat_priv,break ; } -batadv_send_skb_unicast (bat_priv, newskb,BATADV_UNICAST ,0 , - orig_node, vid); +batadv_mcast_forw_send_orig (bat_priv, newskb, vid, orig_node); }rcu_read_unlock ();return ret;
@@ -1551,8 +1580,7 @@ batadv_mcast_forw_want_all_ipv6(struct batadv_priv *bat_priv,break ; } -batadv_send_skb_unicast (bat_priv, newskb,BATADV_UNICAST ,0 , - orig_node, vid); +batadv_mcast_forw_send_orig (bat_priv, newskb, vid, orig_node); }rcu_read_unlock ();return ret;
@@ -1618,8 +1646,7 @@ batadv_mcast_forw_want_all_rtr4(struct batadv_priv *bat_priv,break ; } -batadv_send_skb_unicast (bat_priv, newskb,BATADV_UNICAST ,0 , - orig_node, vid); +batadv_mcast_forw_send_orig (bat_priv, newskb, vid, orig_node); }rcu_read_unlock ();return ret;
@@ -1656,8 +1683,7 @@ batadv_mcast_forw_want_all_rtr6(struct batadv_priv *bat_priv,break ; } -batadv_send_skb_unicast (bat_priv, newskb,BATADV_UNICAST ,0 , - orig_node, vid); +batadv_mcast_forw_send_orig (bat_priv, newskb, vid, orig_node); }rcu_read_unlock ();return ret;
net/batman-adv/multicast.h +15 -0
@@ -46,6 +46,11 @@ enum batadv_forw_mode batadv_mcast_forw_mode(struct batadv_priv *bat_priv, struct sk_buff *skb, struct batadv_orig_node **mcast_single_orig); +int batadv_mcast_forw_send_orig (struct batadv_priv *bat_priv, +struct sk_buff *skb, +unsigned short vid, +struct batadv_orig_node *orig_node); +int batadv_mcast_forw_send (struct batadv_priv *bat_priv,struct sk_buff *skb,unsigned short vid);
@@ -71,6 +76,16 @@ batadv_mcast_forw_mode(struct batadv_priv *bat_priv, struct sk_buff *skb,return BATADV_FORW_ALL ; } +static inline int +batadv_mcast_forw_send_orig (struct batadv_priv *bat_priv, +struct sk_buff *skb, +unsigned short vid, +struct batadv_orig_node *orig_node) +{ +kfree_skb (skb); +return NET_XMIT_DROP ; +} +static inline int batadv_mcast_forw_send (struct batadv_priv *bat_priv,struct sk_buff *skb,unsigned short vid)
net/batman-adv/soft-interface.c +2 -3
@@ -364,9 +364,8 @@ static netdev_tx_t batadv_interface_tx(struct sk_buff *skb, goto dropped; ret =batadv_send_skb_via_gw (bat_priv, skb, vid); }else if (mcast_single_orig) { - ret =batadv_send_skb_unicast (bat_priv, skb, -BATADV_UNICAST ,0 , - mcast_single_orig, vid); + ret =batadv_mcast_forw_send_orig (bat_priv, skb, vid, + mcast_single_orig); }else if (forw_mode ==BATADV_FORW_SOME ) { ret =batadv_mcast_forw_send (bat_priv, skb, vid); }else {
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 50/99 batman-adv: mcast: fix duplicate mcast packets in BLA backbone from mesh
In reply to Greg Kroah-HartmanFrom: Linus Lüssing <[email protected]>
[ Upstream commit 74c09b7275126da1b642b90c9cdc3ae8b729ad4b ]
Scenario:
* Multicast frame send from mesh to a BLA backbone (multiple nodes with their bat0 bridged together, with BLA enabled)
Issue:
* BLA backbone nodes receive the frame multiple times on bat0, once from mesh->bat0 and once from each backbone_gw from LAN
For unicast, a node will send only to the best backbone gateway according to the TQ. However for multicast we currently cannot determine if multiple destination nodes share the same backbone if they don't share the same backbone with us. So we need to keep sending the unicasts to all backbone gateways and let the backbone gateways decide which one will forward the frame. We can use the CLAIM mechanism to make this decision.
One catch: The batman-adv gateway feature for DHCP packets potentially sends multicast packets in the same batman-adv unicast header as the multicast optimizations code. And we are not allowed to drop those even if we did not claim the source address of the sender, as for such packets there is only this one multicast-in-unicast packet.
How can we distinguish the two cases?
The gateway feature uses a batman-adv unicast 4 address header. While the multicast-to-unicasts feature uses a simple, 3 address batman-adv unicast header. So let's use this to distinguish.
--- net/batman-adv/bridge_loop_avoidance.c | 34 +++++++++++++++++++------- net/batman-adv/bridge_loop_avoidance.h | 4 +-- net/batman-adv/soft-interface.c | 6 ++--- 3 files changed, 30 insertions(+), 14 deletions(-)
net/batman-adv/bridge_loop_avoidance.c +25 -9
@@ -1814,7 +1814,7 @@ batadv_bla_loopdetect_check(struct batadv_priv *bat_priv, struct sk_buff *skb,* @bat_priv: the bat priv with all the soft interface information * @skb: the frame to be checked * @vid: the VLAN ID of the frame -* @is_bcast: the packet came in a broadcast packet type. +* @packet_type: the batman packet type this frame came in * * batadv_bla_rx avoidance checks if: * * we have to race for a claim
@@ -1826,7 +1826,7 @@ batadv_bla_loopdetect_check(struct batadv_priv *bat_priv, struct sk_buff *skb,* further process the skb. */ bool batadv_bla_rx (struct batadv_priv *bat_priv,struct sk_buff *skb, -unsigned short vid,bool is_bcast) +unsigned short vid,int packet_type) {struct batadv_bla_backbone_gw *backbone_gw;struct ethhdr *ethhdr;
@@ -1848,9 +1848,24 @@ bool batadv_bla_rx(struct batadv_priv *bat_priv, struct sk_buff *skb, goto handled;if (unlikely (atomic_read (&bat_priv->bla.num_requests))) -/* don't allow broadcasts while requests are in flight */ -if (is_multicast_ether_addr (ethhdr->h_dest) && is_bcast) - goto handled; +/* don't allow multicast packets while requests are in flight */ +if (is_multicast_ether_addr (ethhdr->h_dest)) +/* Both broadcast flooding or multicast-via-unicasts +* delivery might send to multiple backbone gateways +* sharing the same LAN and therefore need to coordinate +* which backbone gateway forwards into the LAN, +* by claiming the payload source address. +* +* Broadcast flooding and multicast-via-unicasts +* delivery use the following two batman packet types. +* Note: explicitly exclude BATADV_UNICAST_4ADDR, +* as the DHCP gateway feature will send explicitly +* to only one BLA gateway, so the claiming process +* should be avoided there. +*/ +if (packet_type ==BATADV_BCAST || + packet_type ==BATADV_UNICAST ) + goto handled;ether_addr_copy (search_claim.addr, ethhdr->h_source); search_claim.vid = vid;
@@ -1885,13 +1900,14 @@ bool batadv_bla_rx(struct batadv_priv *bat_priv, struct sk_buff *skb, goto allow; } -/* if it is a broadcast ... */ -if (is_multicast_ether_addr (ethhdr->h_dest) && is_bcast) { +/* if it is a multicast ... */ +if (is_multicast_ether_addr (ethhdr->h_dest) && + (packet_type ==BATADV_BCAST || packet_type ==BATADV_UNICAST )) {/* ... drop it. the responsible gateway is in charge. * -* We need to check is_bcast because with the gateway +* We need to check packet type because with the gateway * feature, broadcasts (like DHCP requests) may be sent -* using a unicast packet type. +* using a unicast 4 address packet type. See comment above. */ goto handled; }else {
net/batman-adv/bridge_loop_avoidance.h +2 -2
@@ -35,7 +35,7 @@ static inline bool batadv_bla_is_loopdetect_mac(const uint8_t *mac)#ifdef CONFIG_BATMAN_ADV_BLA bool batadv_bla_rx (struct batadv_priv *bat_priv,struct sk_buff *skb, -unsigned short vid,bool is_bcast); +unsigned short vid,int packet_type);bool batadv_bla_tx (struct batadv_priv *bat_priv,struct sk_buff *skb,unsigned short vid); bool batadv_bla_is_backbone_gw(struct sk_buff *skb,
@@ -66,7 +66,7 @@ bool batadv_bla_check_claim(struct batadv_priv *bat_priv, u8 *addr,static inline bool batadv_bla_rx (struct batadv_priv *bat_priv,struct sk_buff *skb,unsigned short vid, -bool is_bcast) +int packet_type) {return false; }
net/batman-adv/soft-interface.c +3 -3
@@ -424,10 +424,10 @@ void batadv_interface_rx(struct net_device *soft_iface,struct vlan_ethhdr *vhdr;struct ethhdr *ethhdr;unsigned short vid; -bool is_bcast; +int packet_type; batadv_bcast_packet = (struct batadv_bcast_packet *)skb->data; - is_bcast = (batadv_bcast_packet->packet_type ==BATADV_BCAST ); + packet_type = batadv_bcast_packet->packet_type;skb_pull_rcsum (skb, hdr_size);skb_reset_mac_header (skb);
@@ -470,7 +470,7 @@ void batadv_interface_rx(struct net_device *soft_iface,/* Let the bridge loop avoidance check the packet. If will * not handle it, we can safely push it up. */ -if (batadv_bla_rx (bat_priv, skb, vid, is_bcast)) +if (batadv_bla_rx (bat_priv, skb, vid, packet_type)) goto out;if (orig_node)
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 51/99 batman-adv: mcast: fix duplicate mcast packets from BLA backbone to mesh
In reply to Greg Kroah-HartmanFrom: Linus Lüssing <[email protected]>
[ Upstream commit 2369e827046920ef0599e6a36b975ac5c0a359c2 ]
Scenario:
* Multicast frame send from BLA backbone gateways (multiple nodes with their bat0 bridged together, with BLA enabled) sharing the same LAN to nodes in the mesh
Issue:
* Nodes receive the frame multiple times on bat0 from the mesh, once from each foreign BLA backbone gateway which shares the same LAN with another
For multicast frames via batman-adv broadcast packets coming from the same BLA backbone but from different backbone gateways duplicates are currently detected via a CRC history of previously received packets.
However this CRC so far was not performed for multicast frames received via batman-adv unicast packets. Fixing this by appyling the same check for such packets, too.
Room for improvements in the future: Ideally we would introduce the possibility to not only claim a client, but a complete originator, too. This would allow us to only send a multicast-in-unicast packet from a BLA backbone gateway claiming the node and by that avoid potential redundant transmissions in the first place.
--- net/batman-adv/bridge_loop_avoidance.c | 103 +++++++++++++++++++++---- 1 file changed, 87 insertions(+), 16 deletions(-)
net/batman-adv/bridge_loop_avoidance.c +87 -16
@@ -1581,13 +1581,16 @@ int batadv_bla_init(struct batadv_priv *bat_priv) }/** -* batadv_bla_check_bcast_duplist() - Check if a frame is in the broadcast dup. +* batadv_bla_check_duplist() - Check if a frame is in the broadcast dup. * @bat_priv: the bat priv with all the soft interface information -* @skb: contains the bcast_packet to be checked +* @skb: contains the multicast packet to be checked +* @payload_ptr: pointer to position inside the head buffer of the skb +* marking the start of the data to be CRC'ed +* @orig: originator mac address, NULL if unknown * -* check if it is on our broadcast list. Another gateway might -* have sent the same packet because it is connected to the same backbone, -* so we have to remove this duplicate. +* Check if it is on our broadcast list. Another gateway might have sent the +* same packet because it is connected to the same backbone, so we have to +* remove this duplicate. * * This is performed by checking the CRC, which will tell us * with a good chance that it is the same packet. If it is furthermore
@@ -1596,19 +1599,17 @@ int batadv_bla_init(struct batadv_priv *bat_priv)* * Return: true if a packet is in the duplicate list, false otherwise. */ -bool batadv_bla_check_bcast_duplist (struct batadv_priv *bat_priv, -struct sk_buff *skb) +static bool batadv_bla_check_duplist (struct batadv_priv *bat_priv, +struct sk_buff *skb,u8 *payload_ptr, +const u8 *orig) { -int i, curr; -__be32 crc; -struct batadv_bcast_packet *bcast_packet;struct batadv_bcast_duplist_entry *entry;bool ret = false; - - bcast_packet = (struct batadv_bcast_packet *)skb->data; +int i, curr; +__be32 crc;/* calculate the crc ... */ - crc =batadv_skb_crc32 (skb, (u8 *)(bcast_packet +1 )); + crc =batadv_skb_crc32 (skb, payload_ptr);spin_lock_bh (&bat_priv->bla.bcast_duplist_lock);
@@ -1627,8 +1628,21 @@ bool batadv_bla_check_bcast_duplist(struct batadv_priv *bat_priv,if (entry->crc != crc)continue ; -if (batadv_compare_eth (entry->orig, bcast_packet->orig)) -continue ; +/* are the originators both known and not anonymous? */ +if (orig && !is_zero_ether_addr (orig) && + !is_zero_ether_addr (entry->orig)) { +/* If known, check if the new frame came from +* the same originator: +* We are safe to take identical frames from the +* same orig, if known, as multiplications in +* the mesh are detected via the (orig, seqno) pair. +* So we can be a bit more liberal here and allow +* identical frames from the same orig which the source +* host might have sent multiple times on purpose. +*/ +if (batadv_compare_eth (entry->orig, orig)) +continue ; + }/* this entry seems to match: same crc, not too old, * and from another gw. therefore return true to forbid it.
@@ -1644,7 +1658,14 @@ bool batadv_bla_check_bcast_duplist(struct batadv_priv *bat_priv, entry = &bat_priv->bla.bcast_duplist[curr]; entry->crc = crc; entry->entrytime = jiffies; -ether_addr_copy (entry->orig, bcast_packet->orig); + +/* known originator */ +if (orig) +ether_addr_copy (entry->orig, orig); +/* anonymous originator */ +else +eth_zero_addr (entry->orig); + bat_priv->bla.bcast_duplist_curr = curr; out:
@@ -1653,6 +1674,48 @@ bool batadv_bla_check_bcast_duplist(struct batadv_priv *bat_priv,return ret; } +/** +* batadv_bla_check_ucast_duplist() - Check if a frame is in the broadcast dup. +* @bat_priv: the bat priv with all the soft interface information +* @skb: contains the multicast packet to be checked, decapsulated from a +* unicast_packet +* +* Check if it is on our broadcast list. Another gateway might have sent the +* same packet because it is connected to the same backbone, so we have to +* remove this duplicate. +* +* Return: true if a packet is in the duplicate list, false otherwise. +*/ +static bool batadv_bla_check_ucast_duplist (struct batadv_priv *bat_priv, +struct sk_buff *skb) +{ +return batadv_bla_check_duplist (bat_priv, skb, (u8 *)skb->data,NULL ); +} + +/** +* batadv_bla_check_bcast_duplist() - Check if a frame is in the broadcast dup. +* @bat_priv: the bat priv with all the soft interface information +* @skb: contains the bcast_packet to be checked +* +* Check if it is on our broadcast list. Another gateway might have sent the +* same packet because it is connected to the same backbone, so we have to +* remove this duplicate. +* +* Return: true if a packet is in the duplicate list, false otherwise. +*/ +bool batadv_bla_check_bcast_duplist (struct batadv_priv *bat_priv, +struct sk_buff *skb) +{ +struct batadv_bcast_packet *bcast_packet; +u8 *payload_ptr; + + bcast_packet = (struct batadv_bcast_packet *)skb->data; + payload_ptr = (u8 *)(bcast_packet +1 ); + +return batadv_bla_check_duplist (bat_priv, skb, payload_ptr, + bcast_packet->orig); +} +/** * batadv_bla_is_backbone_gw_orig() - Check if the originator is a gateway for * the VLAN identified by vid.
@@ -1867,6 +1930,14 @@ bool batadv_bla_rx(struct batadv_priv *bat_priv, struct sk_buff *skb, packet_type == BATADV_UNICAST) goto handled; +/* potential duplicates from foreign BLA backbone gateways via +* multicast-in-unicast packets +*/ +if (is_multicast_ether_addr (ethhdr->h_dest) && + packet_type ==BATADV_UNICAST && +batadv_bla_check_ucast_duplist (bat_priv, skb)) + goto handled; +ether_addr_copy (search_claim.addr, ethhdr->h_source); search_claim.vid = vid; claim =batadv_claim_hash_find (bat_priv, &search_claim);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 52/99 bpf: Fix a rcu warning for bpffs map pretty-print
In reply to Greg Kroah-HartmanFrom: Yonghong Song <[email protected]>
[ Upstream commit ce880cb825fcc22d4e39046a6c3a3a7f6603883d ]
Running selftest
./btf_btf -p
the kernel had the following warning:
[ 51.528185] WARNING: CPU: 3 PID: 1756 at kernel/bpf/hashtab.c:717 htab_map_get_next_key+0x2eb/0x300 [ 51.529217] Modules linked in: [ 51.529583] CPU: 3 PID: 1756 Comm: test_btf Not tainted 5.9.0-rc1+ #878 [ 51.530346] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.9.3-1.el7.centos 04/01/2014 [ 51.531410] RIP: 0010:htab_map_get_next_key+0x2eb/0x300 ... [ 51.542826] Call Trace: [ 51.543119] map_seq_next+0x53/0x80 [ 51.543528] seq_read+0x263/0x400 [ 51.543932] vfs_read+0xad/0x1c0 [ 51.544311] ksys_read+0x5f/0xe0 [ 51.544689] do_syscall_64+0x33/0x40 [ 51.545116] entry_SYSCALL_64_after_hwframe+0x44/0xa9
The related source code in kernel/bpf/hashtab.c:
709 static int htab_map_get_next_key(struct bpf_map *map, void *key, void *next_key) 710 {
711 struct bpf_htab *htab = container_of(map, struct bpf_htab, map); 712 struct hlist_nulls_head *head; 713 struct htab_elem *l, *next_l; 714 u32 hash, key_size; 715 int i = 0;
716
717 WARN_ON_ONCE(!rcu_read_lock_held());
In kernel/bpf/inode.c, bpffs map pretty print calls map->ops->map_get_next_key() without holding a rcu_read_lock(), hence causing the above warning.
To fix the issue, just surrounding map->ops->map_get_next_key() with rcu read lock.
--- kernel/bpf/inode.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
kernel/bpf/inode.c +3 -1
@@ -226,10 +226,12 @@ static void *map_seq_next(struct seq_file *m, void *v, loff_t *pos)else prev_key = key; +rcu_read_lock ();if (map->ops->map_get_next_key (map, prev_key, key)) {map_iter (m)->done = true; -return NULL ; + key =NULL ; } +rcu_read_unlock ();return key; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 53/99 lib80211: fix unmet direct dependendices config warning when !CRYPTO
In reply to Greg Kroah-HartmanFrom: Necip Fazil Yildiran <[email protected]>
[ Upstream commit b959ba9f468b1c581f40e92661ad58b093abaa03 ]
When LIB80211_CRYPT_CCMP is enabled and CRYPTO is disabled, it results in unmet direct dependencies config warning. The reason is that LIB80211_CRYPT_CCMP selects CRYPTO_AES and CRYPTO_CCM, which are subordinate to CRYPTO. This is reproducible with CRYPTO disabled and R8188EU enabled, where R8188EU selects LIB80211_CRYPT_CCMP but does not select or depend on CRYPTO.
Honor the kconfig menu hierarchy to remove kconfig dependency warnings.
--- net/wireless/Kconfig | 1 + 1 file changed, 1 insertion(+)
net/wireless/Kconfig +1 -0
@@ -217,6 +217,7 @@ config LIB80211_CRYPT_WEP config LIB80211_CRYPT_CCMP tristate + select CRYPTO select CRYPTO_AES select CRYPTO_CCM
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 54/99 mac80211: do not disable HE if HT is missing on 2.4 GHz
In reply to Greg Kroah-HartmanFrom: Wen Gong <[email protected]>
[ Upstream commit 780a8c9efc65f6d86acd44794495cedcd32eeb26 ]
VHT is not supported on 2.4 GHz, but HE is; don't disable HE if HT is missing there, do that only on 5 GHz (6 GHz is only HE).
--- net/mac80211/mlme.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
net/mac80211/mlme.c +2 -1
@@ -4853,6 +4853,7 @@ static int ieee80211_prep_channel(struct ieee80211_sub_if_data *sdata,struct ieee80211_supported_band *sband;struct cfg80211_chan_def chandef;bool is_6ghz = cbss->channel->band ==NL80211_BAND_6GHZ ; +bool is_5ghz = cbss->channel->band ==NL80211_BAND_5GHZ ;struct ieee80211_bss *bss = (void *)cbss->priv;int ret;u32 i;
@@ -4871,7 +4872,7 @@ static int ieee80211_prep_channel(struct ieee80211_sub_if_data *sdata, ifmgd->flags |=IEEE80211_STA_DISABLE_HE ; } -if (!sband->vht_cap.vht_supported && !is_6ghz) { +if (!sband->vht_cap.vht_supported && is_5ghz) { ifmgd->flags |=IEEE80211_STA_DISABLE_VHT ; ifmgd->flags |=IEEE80211_STA_DISABLE_HE ; }
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 55/99 cfg80211: fix 6 GHz channel conversion
In reply to Greg Kroah-HartmanFrom: Johannes Berg <[email protected]>
[ Upstream commit c0de8776af6543e10d1a5c8969679fd9f6b66fa9 ]
We shouldn't accept any channels bigger than 233, fix that.
--- net/wireless/util.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/wireless/util.c +1 -1
@@ -95,7 +95,7 @@ u32 ieee80211_channel_to_freq_khz(int chan, enum nl80211_band band)/* see 802.11ax D6.1 27.3.23.2 */ if (chan ==2 )return MHZ_TO_KHZ (5935 ); -if (chan <=253 ) +if (chan <=233 )return MHZ_TO_KHZ (5950 + chan *5 );break ;case NL80211_BAND_60GHZ :
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 56/99 mac80211: fix 80 MHz association to 160/80+80 AP on 6 GHz
In reply to Greg Kroah-HartmanFrom: John Crispin <[email protected]>
[ Upstream commit 75bcbd6913de649601f4e7d3fb6d2b5effc24e9e ]
When trying to associate to an AP support 180 or 80+80 MHz on 6 GHz with a STA that only has 80 Mhz support the cf2 field inside the chandef will get set causing the association to fail when trying to validate the chandef. Fix this by checking the support flags prior to setting cf2.
--- net/mac80211/util.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
net/mac80211/util.c +4 -3
@@ -3354,9 +3354,10 @@ bool ieee80211_chandef_he_6ghz_oper(struct ieee80211_sub_if_data *sdata, he_chandef.center_freq1 =ieee80211_channel_to_frequency (he_6ghz_oper->ccfs0,NL80211_BAND_6GHZ ); - he_chandef.center_freq2 = -ieee80211_channel_to_frequency (he_6ghz_oper->ccfs1, -NL80211_BAND_6GHZ ); +if (support_80_80 || support_160) + he_chandef.center_freq2 = +ieee80211_channel_to_frequency (he_6ghz_oper->ccfs1, +NL80211_BAND_6GHZ ); }if (!cfg80211_chandef_valid (&he_chandef)) {
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 57/99 ALSA: asihpi: fix iounmap in error handler
In reply to Greg Kroah-HartmanFrom: Tom Rix <[email protected]>
[ Upstream commit 472eb39103e885f302fd8fd6eff104fcf5503f1b ]
clang static analysis flags this problem hpioctl.c:513:7: warning: Branch condition evaluates to
a garbage value
if (pci.ap_mem_base[idx]) {
^~~~~~~~~~~~~~~~~~~~If there is a failure in the middle of the memory space loop, only some of the memory spaces need to be cleaned up.
At the error handler, idx holds the number of successful memory spaces mapped. So rework the handler loop to use the old idx.
There is a second problem, the memory space loop conditionally iomaps()/sets the mem_base so it is necessay to initize pci.
--- sound/pci/asihpi/hpioctl.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
sound/pci/asihpi/hpioctl.c +2 -2
@@ -343,7 +343,7 @@ int asihpi_adapter_probe(struct pci_dev *pci_dev,struct hpi_message hm;struct hpi_response hr;struct hpi_adapter adapter; -struct hpi_pci pci; +struct hpi_pci pci = {0 };memset (&adapter,0 ,sizeof (adapter));
@@ -499,7 +499,7 @@ int asihpi_adapter_probe(struct pci_dev *pci_dev,return 0 ; err: -for (idx =0 ; idx <HPI_MAX_ADAPTER_MEM_SPACES ; idx++) { +while (--idx >=0 ) {if (pci.ap_mem_base[idx]) {iounmap (pci.ap_mem_base[idx]); pci.ap_mem_base[idx] =NULL ;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 58/99 io_uring: fix openat/openat2 unified prep handling
In reply to Greg Kroah-HartmanFrom: Jens Axboe <[email protected]>
[ Upstream commit 4eb8dded6b82e184c09bb963bea0335fa3f30b55 ]
A previous commit unified how we handle prep for these two functions, but this means that we check the allowed context (SQPOLL, specifically) later than we should. Move the ring type checking into the two parent functions, instead of doing it after we've done some setup work.
--- fs/io_uring.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-)
fs/io_uring.c +4 -2
@@ -3056,8 +3056,6 @@ static int __io_openat_prep(struct io_kiocb *req, const struct io_uring_sqe *sqeconst char __user *fname;int ret; -if (unlikely (req->ctx->flags & (IORING_SETUP_IOPOLL |IORING_SETUP_SQPOLL ))) -return -EINVAL ;if (unlikely (sqe->ioprio || sqe->buf_index))return -EINVAL ;if (unlikely (req->flags &REQ_F_FIXED_FILE ))
@@ -3084,6 +3082,8 @@ static int io_openat_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe) {u64 flags, mode; +if (unlikely (req->ctx->flags & (IORING_SETUP_IOPOLL |IORING_SETUP_SQPOLL ))) +return -EINVAL ;if (req->flags &REQ_F_NEED_CLEANUP )return 0 ; mode =READ_ONCE (sqe->len);
@@ -3098,6 +3098,8 @@ static int io_openat2_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe)size_t len;int ret; +if (unlikely (req->ctx->flags & (IORING_SETUP_IOPOLL |IORING_SETUP_SQPOLL ))) +return -EINVAL ;if (req->flags &REQ_F_NEED_CLEANUP )return 0 ; how =u64_to_user_ptr (READ_ONCE (sqe->addr2));
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 59/99 SUNRPC: Fix svc_flush_dcache()
In reply to Greg Kroah-HartmanFrom: Chuck Lever <[email protected]>
[ Upstream commit 13a9a9d74d4d9689ad65938966dbc66386063648 ]
On platforms that implement flush_dcache_page(), a large NFS WRITE triggers the WARN_ONCE in bvec_iter_advance():
Sep 20 14:01:05 klimt.1015granger.net kernel: Attempted to advance past end of bvec iter Sep 20 14:01:05 klimt.1015granger.net kernel: WARNING: CPU: 0 PID: 1032 at include/linux/bvec.h:101 bvec_iter_advance.isra.0+0xa7/0x158 [sunrpc]
Sep 20 14:01:05 klimt.1015granger.net kernel: Call Trace: Sep 20 14:01:05 klimt.1015granger.net kernel: svc_tcp_recvfrom+0x60c/0x12c7 [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: ? bvec_iter_advance.isra.0+0x158/0x158 [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: ? del_timer_sync+0x4b/0x55 Sep 20 14:01:05 klimt.1015granger.net kernel: ? test_bit+0x1d/0x27 [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: svc_recv+0x1193/0x15e4 [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: ? try_to_freeze.isra.0+0x6f/0x6f [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: ? refcount_sub_and_test.constprop.0+0x13/0x40 [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: ? svc_xprt_put+0x1e/0x29f [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: ? svc_send+0x39f/0x3c1 [sunrpc] Sep 20 14:01:05 klimt.1015granger.net kernel: nfsd+0x282/0x345 [nfsd] Sep 20 14:01:05 klimt.1015granger.net kernel: ? __kthread_parkme+0x74/0xba Sep 20 14:01:05 klimt.1015granger.net kernel: kthread+0x2ad/0x2bc Sep 20 14:01:05 klimt.1015granger.net kernel: ? nfsd_destroy+0x124/0x124 [nfsd] Sep 20 14:01:05 klimt.1015granger.net kernel: ? test_bit+0x1d/0x27 Sep 20 14:01:05 klimt.1015granger.net kernel: ? kthread_mod_delayed_work+0x115/0x115 Sep 20 14:01:05 klimt.1015granger.net kernel: ret_from_fork+0x22/0x30
--- net/sunrpc/svcsock.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
net/sunrpc/svcsock.c +1 -1
@@ -228,7 +228,7 @@ static int svc_one_sock_name(struct svc_sock *svsk, char *buf, int remaining)static void svc_flush_bvec (const struct bio_vec *bvec,size_t size,size_t seek) {struct bvec_iter bi = { - .bi_size = size, + .bi_size = size + seek, };struct bio_vec bv;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 60/99 regmap: fix page selection for noinc reads
In reply to Greg Kroah-HartmanFrom: Dmitry Baryshkov <[email protected]>
[ Upstream commit 4003324856311faebb46cbd56a1616bd3f3b67c2 ]
Non-incrementing reads can fail if register + length crosses page border. However for non-incrementing reads we should not check for page border crossing. Fix this by passing additional flag to _regmap_raw_read and passing length to _regmap_select_page basing on the flag.
--- drivers/base/regmap/regmap.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-)
drivers/base/regmap/regmap.c +6 -6
@@ -2455,7 +2455,7 @@ int regmap_raw_write_async(struct regmap *map, unsigned int reg,EXPORT_SYMBOL_GPL (regmap_raw_write_async);static int _regmap_raw_read (struct regmap *map,unsigned int reg,void *val, -unsigned int val_len) +unsigned int val_len,bool noinc) {struct regmap_range_node *range;int ret;
@@ -2468,7 +2468,7 @@ static int _regmap_raw_read(struct regmap *map, unsigned int reg, void *val, range =_regmap_range_lookup (map, reg);if (range) { ret =_regmap_select_page (map, ®, range, - val_len / map->format.val_bytes); + noinc ?1 : val_len / map->format.val_bytes);if (ret !=0 )return ret; }
@@ -2506,7 +2506,7 @@ static int _regmap_bus_read(void *context, unsigned int reg,if (!map->format.parse_val)return -EINVAL ; - ret =_regmap_raw_read (map, reg, work_val, map->format.val_bytes); + ret =_regmap_raw_read (map, reg, work_val, map->format.val_bytes, false);if (ret ==0 ) *val = map->format.parse_val (work_val);
@@ -2622,7 +2622,7 @@ int regmap_raw_read(struct regmap *map, unsigned int reg, void *val,/* Read bytes that fit into whole chunks */ for (i =0 ; i < chunk_count; i++) { - ret =_regmap_raw_read (map, reg, val, chunk_bytes); + ret =_regmap_raw_read (map, reg, val, chunk_bytes, false);if (ret !=0 ) goto out;
@@ -2633,7 +2633,7 @@ int regmap_raw_read(struct regmap *map, unsigned int reg, void *val,/* Read remaining bytes */ if (val_len) { - ret =_regmap_raw_read (map, reg, val, val_len); + ret =_regmap_raw_read (map, reg, val, val_len, false);if (ret !=0 ) goto out; }
@@ -2708,7 +2708,7 @@ int regmap_noinc_read(struct regmap *map, unsigned int reg, read_len = map->max_raw_read; else read_len = val_len; - ret =_regmap_raw_read (map, reg, val, read_len); + ret =_regmap_raw_read (map, reg, val, read_len, true);if (ret) goto out_unlock; val = ((u8 *)val) + read_len;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 61/99 regmap: fix page selection for noinc writes
In reply to Greg Kroah-HartmanFrom: Dmitry Baryshkov <[email protected]>
[ Upstream commit 05669b63170771d554854c0e465b76dc98fc7c84 ]
Non-incrementing writes can fail if register + length crosses page border. However for non-incrementing writes we should not check for page border crossing. Fix this by passing additional flag to _regmap_raw_write and passing length to _regmap_select_page basing on the flag.
--- drivers/base/regmap/internal.h | 2 +- drivers/base/regmap/regcache.c | 2 +- drivers/base/regmap/regmap.c | 21 +++++++++++---------- 3 files changed, 13 insertions(+), 12 deletions(-)
drivers/base/regmap/internal.h +1 -1
@@ -259,7 +259,7 @@ bool regcache_set_val(struct regmap *map, void *base, unsigned int idx,int regcache_lookup_reg (struct regmap *map,unsigned int reg);int _regmap_raw_write (struct regmap *map,unsigned int reg, -const void *val,size_t val_len); +const void *val,size_t val_len,bool noinc);void regmap_async_complete_cb (struct regmap_async *async,int ret);
drivers/base/regmap/regcache.c +1 -1
@@ -717,7 +717,7 @@ static int regcache_sync_block_raw_flush(struct regmap *map, const void **data, map->cache_bypass = true; - ret =_regmap_raw_write (map, base, *data, count * val_bytes); + ret =_regmap_raw_write (map, base, *data, count * val_bytes, false);if (ret)dev_err (map->dev,"Unable to sync registers %#x-%#x. %d\n" , base, cur - map->reg_stride, ret);
drivers/base/regmap/regmap.c +11 -10
@@ -1469,7 +1469,7 @@ static void regmap_set_work_buf_flag_mask(struct regmap *map, int max_bytes, }static int _regmap_raw_write_impl (struct regmap *map,unsigned int reg, -const void *val,size_t val_len) +const void *val,size_t val_len,bool noinc) {struct regmap_range_node *range;unsigned long flags;
@@ -1528,7 +1528,7 @@ static int _regmap_raw_write_impl(struct regmap *map, unsigned int reg, win_residue, val_len / map->format.val_bytes); ret =_regmap_raw_write_impl (map, reg, val, win_residue * - map->format.val_bytes); + map->format.val_bytes, noinc);if (ret !=0 )return ret;
@@ -1542,7 +1542,7 @@ static int _regmap_raw_write_impl(struct regmap *map, unsigned int reg, win_residue = range->window_len - win_offset; } - ret =_regmap_select_page (map, ®, range, val_num); + ret =_regmap_select_page (map, ®, range, noinc ?1 : val_num);if (ret !=0 )return ret; }
@@ -1750,7 +1750,8 @@ static int _regmap_bus_raw_write(void *context, unsigned int reg, map->work_buf + map->format.reg_bytes + map->format.pad_bytes, - map->format.val_bytes); + map->format.val_bytes, + false); }static inline void *_regmap_map_get_context (struct regmap *map)
@@ -1844,7 +1845,7 @@ int regmap_write_async(struct regmap *map, unsigned int reg, unsigned int val)EXPORT_SYMBOL_GPL (regmap_write_async);int _regmap_raw_write (struct regmap *map,unsigned int reg, -const void *val,size_t val_len) +const void *val,size_t val_len,bool noinc) {size_t val_bytes = map->format.val_bytes;size_t val_count = val_len / val_bytes;
@@ -1865,7 +1866,7 @@ int _regmap_raw_write(struct regmap *map, unsigned int reg,/* Write as many bytes as possible with chunk_size */ for (i =0 ; i < chunk_count; i++) { - ret =_regmap_raw_write_impl (map, reg, val, chunk_bytes); + ret =_regmap_raw_write_impl (map, reg, val, chunk_bytes, noinc);if (ret)return ret;
@@ -1876,7 +1877,7 @@ int _regmap_raw_write(struct regmap *map, unsigned int reg,/* Write remaining bytes */ if (val_len) - ret =_regmap_raw_write_impl (map, reg, val, val_len); + ret =_regmap_raw_write_impl (map, reg, val, val_len, noinc);return ret; }
@@ -1909,7 +1910,7 @@ int regmap_raw_write(struct regmap *map, unsigned int reg, map->lock (map->lock_arg); - ret =_regmap_raw_write (map, reg, val, val_len); + ret =_regmap_raw_write (map, reg, val, val_len, false); map->unlock (map->lock_arg);
@@ -1967,7 +1968,7 @@ int regmap_noinc_write(struct regmap *map, unsigned int reg, write_len = map->max_raw_write; else write_len = val_len; - ret =_regmap_raw_write (map, reg, val, write_len); + ret =_regmap_raw_write (map, reg, val, write_len, true);if (ret) goto out_unlock; val = ((u8 *)val) + write_len;
@@ -2444,7 +2445,7 @@ int regmap_raw_write_async(struct regmap *map, unsigned int reg, map->async = true; - ret =_regmap_raw_write (map, reg, val, val_len); + ret =_regmap_raw_write (map, reg, val, val_len, false); map->async = false;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 62/99 net/mlx5e: mlx5e_fec_in_caps() returns a boolean
In reply to Greg Kroah-HartmanFrom: Saeed Mahameed <[email protected]>
[ Upstream commit cb39ccc5cbe1011d8d21886b75e2468070ac672c ]
Returning errno is a bug, fix that.
Also fixes smatch warnings:drivers/net/ethernet/mellanox/mlx5/core/en/port.c:453 mlx5e_fec_in_caps() warn: signedness bug returning '(-95)'
--- drivers/net/ethernet/mellanox/mlx5/core/en/port.c | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-)
drivers/net/ethernet/mellanox/mlx5/core/en/port.c +2 -5
@@ -487,11 +487,8 @@ bool mlx5e_fec_in_caps(struct mlx5_core_dev *dev, int fec_policy)int err;int i; -if (!MLX5_CAP_GEN (dev, pcam_reg)) -return -EOPNOTSUPP ; - -if (!MLX5_CAP_PCAM_REG (dev, pplm)) -return -EOPNOTSUPP ; +if (!MLX5_CAP_GEN (dev, pcam_reg) || !MLX5_CAP_PCAM_REG (dev, pplm)) +return false;MLX5_SET (pplm_reg, in, local_port,1 ); err =mlx5_core_access_reg (dev, in, sz, out, sz,MLX5_REG_PPLM ,0 ,0 );
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 63/99 MIPS: Loongson-3: Fix fp register access if MSA enabled
In reply to Greg Kroah-HartmanFrom: Huacai Chen <[email protected]>
[ Upstream commit 01ce6d4d2c8157b076425e3dd8319948652583c5 ]
If MSA is enabled, FPU_REG_WIDTH is 128 rather than 64, then get_fpr64() /set_fpr64() in the original unaligned instruction emulation code access the wrong fp registers. This is because the current code doesn't specify the correct index field, so fix it.
--- arch/mips/loongson64/cop2-ex.c | 24 ++++++++---------------- 1 file changed, 8 insertions(+), 16 deletions(-)
arch/mips/loongson64/cop2-ex.c +8 -16
@@ -95,10 +95,8 @@ static int loongson_cu2_call(struct notifier_block *nfb, unsigned long action,if (res) goto fault; -set_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lswc2_format.rt, value); -set_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lswc2_format.rq, value_next); +set_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lswc2_format.rt],0 , value); +set_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lswc2_format.rq],0 , value_next);compute_return_epc (regs);own_fpu (1 ); }
@@ -130,15 +128,13 @@ static int loongson_cu2_call(struct notifier_block *nfb, unsigned long action, goto sigbus;lose_fpu (1 ); - value_next =get_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lswc2_format.rq); + value_next =get_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lswc2_format.rq],0 );StoreDW (addr +8 , value_next, res);if (res) goto fault; - value =get_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lswc2_format.rt); + value =get_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lswc2_format.rt],0 );StoreDW (addr, value, res);if (res)
@@ -204,8 +200,7 @@ static int loongson_cu2_call(struct notifier_block *nfb, unsigned long action,if (res) goto fault; -set_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lsdc2_format.rt, value); +set_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lsdc2_format.rt],0 , value);compute_return_epc (regs);own_fpu (1 );
@@ -221,8 +216,7 @@ static int loongson_cu2_call(struct notifier_block *nfb, unsigned long action,if (res) goto fault; -set_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lsdc2_format.rt, value); +set_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lsdc2_format.rt],0 , value);compute_return_epc (regs);own_fpu (1 );break ;
@@ -286,8 +280,7 @@ static int loongson_cu2_call(struct notifier_block *nfb, unsigned long action, goto sigbus;lose_fpu (1 ); - value =get_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lsdc2_format.rt); + value =get_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lsdc2_format.rt],0 );StoreW (addr, value, res);if (res)
@@ -305,8 +298,7 @@ static int loongson_cu2_call(struct notifier_block *nfb, unsigned long action, goto sigbus;lose_fpu (1 ); - value =get_fpr64 (current->thread.fpu.fpr, - insn.loongson3_lsdc2_format.rt); + value =get_fpr64 (¤t->thread.fpu.fpr[insn.loongson3_lsdc2_format.rt],0 );StoreDW (addr, value, res);if (res)
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 64/99 PM / devfreq: tegra30: Disable clock on error in probe
In reply to Greg Kroah-HartmanFrom: Dan Carpenter <[email protected]>
[ Upstream commit 6bf560766a8ef5afe4faa3244220cf5b3a934549 ]
This error path needs to call clk_disable_unprepare().
--- drivers/devfreq/tegra30-devfreq.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/devfreq/tegra30-devfreq.c +3 -1
@@ -836,7 +836,8 @@ static int tegra_devfreq_probe(struct platform_device *pdev) rate =clk_round_rate (tegra->emc_clock,ULONG_MAX );if (rate <0 ) {dev_err (&pdev->dev,"Failed to round clock rate: %ld\n" , rate); -return rate; + err = rate; + goto disable_clk; } tegra->max_freq = rate /KHZ ;
@@ -897,6 +898,7 @@ static int tegra_devfreq_probe(struct platform_device *pdev)dev_pm_opp_remove_all_dynamic (&pdev->dev);reset_control_reset (tegra->reset); +disable_clk:clk_disable_unprepare (tegra->clock);return err;
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 65/99 MIPS: Add the missing CPU_1074K into __get_cpu_type()
In reply to Greg Kroah-HartmanFrom: Wei Li <[email protected]>
[ Upstream commit e393fbe6fa27af23f78df6e16a8fd2963578a8c4 ]
Commit 442e14a2c55e ("MIPS: Add 1074K CPU support explicitly.") split 1074K from the 74K as an unique CPU type, while it missed to add the 'CPU_1074K' in __get_cpu_type(). So let's add it back.
--- arch/mips/include/asm/cpu-type.h | 1 + 1 file changed, 1 insertion(+)
arch/mips/include/asm/cpu-type.h +1 -0
@@ -47,6 +47,7 @@ static inline int __pure __get_cpu_type(const int cpu_type)case CPU_34K :case CPU_1004K :case CPU_74K : +case CPU_1074K :case CPU_M14KC :case CPU_M14KEC :case CPU_INTERAPTIV :
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 66/99 regulator: axp20x: fix LDO2/4 description
In reply to Greg Kroah-HartmanFrom: Icenowy Zheng <[email protected]>
[ Upstream commit fbb5a79d2fe7b01c6424fbbc04368373b1672d61 ]
Currently we wrongly set the mask of value of LDO2/4 both to the mask of LDO2, and the LDO4 voltage configuration is left untouched. This leads to conflict when LDO2/4 are both in use.
Fix this issue by setting different vsel_mask to both regulators.
--- drivers/regulator/axp20x-regulator.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
drivers/regulator/axp20x-regulator.c +4 -3
@@ -42,8 +42,9 @@#define AXP20X_DCDC2_V_OUT_MASK GENMASK(5, 0)#define AXP20X_DCDC3_V_OUT_MASK GENMASK(7, 0) -#define AXP20X_LDO24_V_OUT_MASK GENMASK(7, 4) +#define AXP20X_LDO2_V_OUT_MASK GENMASK(7, 4)#define AXP20X_LDO3_V_OUT_MASK GENMASK(6, 0) +#define AXP20X_LDO4_V_OUT_MASK GENMASK(3, 0)#define AXP20X_LDO5_V_OUT_MASK GENMASK(7, 4)#define AXP20X_PWR_OUT_EXTEN_MASK BIT_MASK(0)
@@ -542,14 +543,14 @@ static const struct regulator_desc axp20x_regulators[] = { AXP20X_PWR_OUT_CTRL, AXP20X_PWR_OUT_DCDC3_MASK),AXP_DESC_FIXED (AXP20X ,LDO1 ,"ldo1" ,"acin" ,1300 ),AXP_DESC (AXP20X ,LDO2 ,"ldo2" ,"ldo24in" ,1800 ,3300 ,100 , -AXP20X_LDO24_V_OUT ,AXP20X_LDO24_V_OUT_MASK , +AXP20X_LDO24_V_OUT ,AXP20X_LDO2_V_OUT_MASK ,AXP20X_PWR_OUT_CTRL ,AXP20X_PWR_OUT_LDO2_MASK ),AXP_DESC (AXP20X ,LDO3 ,"ldo3" ,"ldo3in" ,700 ,3500 ,25 ,AXP20X_LDO3_V_OUT ,AXP20X_LDO3_V_OUT_MASK ,AXP20X_PWR_OUT_CTRL ,AXP20X_PWR_OUT_LDO3_MASK ),AXP_DESC_RANGES (AXP20X ,LDO4 ,"ldo4" ,"ldo24in" , axp20x_ldo4_ranges,AXP20X_LDO4_V_OUT_NUM_VOLTAGES , -AXP20X_LDO24_V_OUT ,AXP20X_LDO24_V_OUT_MASK , +AXP20X_LDO24_V_OUT ,AXP20X_LDO4_V_OUT_MASK ,AXP20X_PWR_OUT_CTRL ,AXP20X_PWR_OUT_LDO4_MASK ), AXP_DESC_IO(AXP20X, LDO5, "ldo5", "ldo5in", 1800, 3300, 100, AXP20X_LDO5_V_OUT, AXP20X_LDO5_V_OUT_MASK,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 67/99 spi: bcm-qspi: Fix probe regression on iProc platforms
In reply to Greg Kroah-HartmanFrom: Ray Jui <[email protected]>
[ Upstream commit 00fb259c618ea1198fc51b53a6167aa0d78672a9 ]
iProc chips have QSPI controller that does not have the MSPI_REV offset. Reading from that offset will cause a bus error. Fix it by having MSPI_REV query disabled in the generic compatible string.
--- drivers/spi/spi-bcm-qspi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/spi/spi-bcm-qspi.c +1 -1
@@ -1295,7 +1295,7 @@ static const struct of_device_id bcm_qspi_of_match[] = { }, { .compatible = "brcm,spi-bcm-qspi", - .data = &bcm_qspi_rev_data, + .data = &bcm_qspi_no_rev_data, }, { .compatible = "brcm,spi-bcm7216-qspi",
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 68/99 KVM: x86: Reset MMU context if guest toggles CR4.SMAP or CR4.PKE
In reply to Greg Kroah-HartmanFrom: Sean Christopherson <[email protected]>
[ Upstream commit 8d214c481611b29458a57913bd786f0ac06f0605 ]
Reset the MMU context during kvm_set_cr4() if SMAP or PKE is toggled. Recent commits to (correctly) not reload PDPTRs when SMAP/PKE are toggled inadvertantly skipped the MMU context reset due to the mask of bits that triggers PDPTR loads also being used to trigger MMU context resets.
Message-Id: <[email protected]>
--- arch/x86/kvm/x86.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
arch/x86/kvm/x86.c +2 -1
@@ -968,6 +968,7 @@ int kvm_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4)unsigned long old_cr4 =kvm_read_cr4 (vcpu);unsigned long pdptr_bits =X86_CR4_PGE |X86_CR4_PSE |X86_CR4_PAE |X86_CR4_SMEP ; +unsigned long mmu_role_bits = pdptr_bits |X86_CR4_SMAP |X86_CR4_PKE ;if (kvm_valid_cr4 (vcpu, cr4))return 1 ;
@@ -995,7 +996,7 @@ int kvm_set_cr4(struct kvm_vcpu *vcpu, unsigned long cr4)if (kvm_x86_ops.set_cr4 (vcpu, cr4))return 1 ; -if (((cr4 ^ old_cr4) & pdptr_bits) || +if (((cr4 ^ old_cr4) & mmu_role_bits) || (!(cr4 &X86_CR4_PCIDE ) && (old_cr4 &X86_CR4_PCIDE )))kvm_mmu_reset_context (vcpu);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 69/99 KVM: SVM: Add a dedicated INVD intercept routine
In reply to Greg Kroah-HartmanFrom: Tom Lendacky <[email protected]>
[ Upstream commit 4bb05f30483fd21ea5413eaf1182768f251cf625 ]
The INVD instruction intercept performs emulation. Emulation can't be done on an SEV guest because the guest memory is encrypted.
Provide a dedicated intercept routine for the INVD intercept. And since the instruction is emulated as a NOP, just skip it instead.
Message-Id: <a0b9a19ffa7fef86a3cc700c7ea01cb2731e04e5.1600972918.git.thomas.lendacky@amd.com>
--- arch/x86/kvm/svm/svm.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-)
arch/x86/kvm/svm/svm.c +7 -1
@@ -2169,6 +2169,12 @@ static int iret_interception(struct vcpu_svm *svm)return 1 ; } +static int invd_interception (struct vcpu_svm *svm) +{ +/* Treat an INVD instruction as a NOP and just skip it. */ +return kvm_skip_emulated_instruction (&svm->vcpu); +} +static int invlpg_interception (struct vcpu_svm *svm) {if (!static_cpu_has (X86_FEATURE_DECODEASSISTS ))
@@ -2758,7 +2764,7 @@ static int (*const svm_exit_handlers[])(struct vcpu_svm *svm) = { [SVM_EXIT_RDPMC] = rdpmc_interception, [SVM_EXIT_CPUID] = cpuid_interception, [SVM_EXIT_IRET] = iret_interception, - [SVM_EXIT_INVD] = emulate_on_interception, + [SVM_EXIT_INVD] = invd_interception, [SVM_EXIT_PAUSE] = pause_interception, [SVM_EXIT_HLT] = halt_interception, [SVM_EXIT_INVLPG] = invlpg_interception,
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 70/99 mm: validate pmd after splitting
In reply to Greg Kroah-HartmanFrom: Minchan Kim <[email protected]>
[ Upstream commit ce2684254bd4818ca3995c0d021fb62c4cf10a19 ]
syzbot reported the following KASAN splat:
general protection fault, probably for non-canonical address 0xdffffc0000000003: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000018-0x000000000000001f]
CPU: 1 PID: 6826 Comm: syz-executor142 Not tainted 5.9.0-rc4-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:__lock_acquire+0x84/0x2ae0 kernel/locking/lockdep.c:4296
Code: ff df 8a 04 30 84 c0 0f 85 e3 16 00 00 83 3d 56 58 35 08 00 0f 84 0e 17 00 00 83 3d 25 c7 f5 07 00 74 2c 4c 89 e8 48 c1 e8 03 <80> 3c 30 00 74 12 4c 89 ef e8 3e d1 5a 00 48 be 00 00 00 00 00 fc
RSP: 0018:ffffc90004b9f850 EFLAGS: 00010006
Call Trace:
lock_acquire+0x140/0x6f0 kernel/locking/lockdep.c:5006
__raw_spin_lock include/linux/spinlock_api_smp.h:142 [inline]
_raw_spin_lock+0x2a/0x40 kernel/locking/spinlock.c:151
spin_lock include/linux/spinlock.h:354 [inline]
madvise_cold_or_pageout_pte_range+0x52f/0x25c0 mm/madvise.c:389
walk_pmd_range mm/pagewalk.c:89 [inline]
walk_pud_range mm/pagewalk.c:160 [inline]
walk_p4d_range mm/pagewalk.c:193 [inline]
walk_pgd_range mm/pagewalk.c:229 [inline]
__walk_page_range+0xe7b/0x1da0 mm/pagewalk.c:331
walk_page_range+0x2c3/0x5c0 mm/pagewalk.c:427
madvise_pageout_page_range mm/madvise.c:521 [inline]
madvise_pageout mm/madvise.c:557 [inline]
madvise_vma mm/madvise.c:946 [inline]
do_madvise+0x12d0/0x2090 mm/madvise.c:1145
__do_sys_madvise mm/madvise.c:1171 [inline]
__se_sys_madvise mm/madvise.c:1169 [inline]
__x64_sys_madvise+0x76/0x80 mm/madvise.c:1169
do_syscall_64+0x31/0x70 arch/x86/entry/common.c:46
entry_SYSCALL_64_after_hwframe+0x44/0xa9The backing vma was shmem.
In case of split page of file-backed THP, madvise zaps the pmd instead of remapping of sub-pages. So we need to check pmd validity after split.
--- mm/madvise.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/madvise.c +1 -1
@@ -381,9 +381,9 @@ static int madvise_cold_or_pageout_pte_range(pmd_t *pmd, return 0; } +regular_page:if (pmd_trans_unstable (pmd))return 0 ; -regular_page:#endif tlb_change_page_size (tlb,PAGE_SIZE ); orig_pte = pte =pte_offset_map_lock (vma->vm_mm, pmd, addr, &ptl);
Signature · 1 line
2.25.1
Greg Kroah-Hartman
maintainerPATCH 71/99 arch/x86/lib/usercopy_64.c: fix __copy_user_flushcache() cache writeback
In reply to Greg Kroah-HartmanFrom: Mikulas Patocka <[email protected]>
commit a1cd6c2ae47ee10ff21e62475685d5b399e2ed4a upstream.
If we copy less than 8 bytes and if the destination crosses a cache line, __copy_user_flushcache would invalidate only the first cache line.
This patch makes it invalidate the second cache line as well.
--- arch/x86/lib/usercopy_64.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/lib/usercopy_64.c +1 -1
@@ -120,7 +120,7 @@ long __copy_user_flushcache(void *dst, c*/ if (size <8 ) {if (!IS_ALIGNED (dest,4 ) || size !=4 ) -clean_cache_range (dst,1 ); +clean_cache_range (dst, size); }else {if (!IS_ALIGNED (dest,8 )) { dest =ALIGN (dest, boot_cpu_data.x86_clflush_size);
Greg Kroah-Hartman
maintainerPATCH 72/99 x86/irq: Make run_on_irqstack_cond() typesafe
In reply to Greg Kroah-HartmanFrom: Thomas Gleixner <[email protected]>
commit a7b3474cbb2864d5500d5e4f48dd57c903975cab upstream.
Sami reported that run_on_irqstack_cond() requires the caller to cast functions to mismatching types, which trips indirect call Control-Flow Integrity (CFI) in Clang.
Instead of disabling CFI on that function, provide proper helpers for the three call variants. The actual ASM code stays the same as that is out of reach.
[ bp: Fix __run_on_irqstack() prototype to match. ]
--- arch/x86/entry/common.c | 2 - arch/x86/entry/entry_64.S | 2 + arch/x86/include/asm/idtentry.h | 2 - arch/x86/include/asm/irq_stack.h | 70 ++++++++++++++++++++++++++++++++++----- arch/x86/kernel/irq.c | 2 - arch/x86/kernel/irq_64.c | 2 - 6 files changed, 68 insertions(+), 12 deletions(-)
arch/x86/entry/common.c +1 -1
@@ -814,7 +814,7 @@ __visible noinstr void xen_pv_evtchn_do_ old_regs =set_irq_regs (regs);instrumentation_begin (); -run_on_irqstack_cond (__xen_pv_evtchn_do_upcall,NULL , regs); +run_on_irqstack_cond (__xen_pv_evtchn_do_upcall, regs);instrumentation_begin ();set_irq_regs (old_regs);
arch/x86/entry/entry_64.S +2 -0
@@ -687,6 +687,8 @@ SYM_CODE_END(.Lbad_gs) * rdx: Function argument (can be NULL if none) */ SYM_FUNC_START(asm_call_on_stack) +SYM_INNER_LABEL(asm_call_sysvec_on_stack, SYM_L_GLOBAL) +SYM_INNER_LABEL(asm_call_irq_on_stack, SYM_L_GLOBAL) /* * Save the frame pointer unconditionally. This allows the ORC * unwinder to handle the stack switch.
arch/x86/include/asm/idtentry.h +1 -1
@@ -246,7 +246,7 @@ __visible noinstr void func(struct pt_reinstrumentation_begin (); \irq_enter_rcu (); \kvm_set_cpu_l1tf_flush_l1d (); \ - run_on_irqstack_cond(__##func, regs, regs); \ + run_sysvec_on_irqstack_cond(__##func, regs); \ irq_exit_rcu(); \ instrumentation_end(); \ idtentry_exit_cond_rcu(regs, rcu_exit); \
arch/x86/include/asm/irq_stack.h +62 -8
105 lines not on this page · raw message
arch/x86/kernel/irq.c +1 -1
@@ -227,7 +227,7 @@ static __always_inline void handle_irq(s struct pt_regs *regs) {if (IS_ENABLED (CONFIG_X86_64 )) -run_on_irqstack_cond (desc->handle_irq, desc, regs); +run_irq_on_irqstack_cond (desc->handle_irq, desc, regs);else __handle_irq (desc, regs); }
arch/x86/kernel/irq_64.c +1 -1
@@ -74,5 +74,5 @@ int irq_init_percpu_irqstack(unsigned invoid do_softirq_own_stack (void ) { -run_on_irqstack_cond (__do_softirq,NULL ,NULL ); +run_on_irqstack_cond (__do_softirq,NULL ); }
Greg Kroah-Hartman
maintainerPATCH 73/99 x86/ioapic: Unbreak check_timer()
In reply to Greg Kroah-HartmanFrom: Thomas Gleixner <[email protected]>
commit 86a82ae0b5095ea24c55898a3f025791e7958b21 upstream.
Several people reported in the kernel bugzilla that between v4.12 and v4.13 the magic which works around broken hardware and BIOSes to find the proper timer interrupt delivery mode stopped working for some older affected platforms which need to fall back to ExtINT delivery mode.
The reason is that the core code changed to keep track of the masked and disabled state of an interrupt line more accurately to avoid the expensive hardware operations.
That broke an assumption in i8259_make_irq() which invokes
disable_irq_nosync();
irq_set_chip_and_handler();
enable_irq();Up to v4.12 this worked because enable_irq() unconditionally unmasked the interrupt line, but after the state tracking improvements this is not longer the case because the IO/APIC uses lazy disabling. So the line state is unmasked which means that enable_irq() does not call into the new irq chip to unmask it.
In principle this is a shortcoming of the core code, but it's more than unclear whether the core code should try to reset state. At least this cannot be done unconditionally as that would break other existing use cases where the chip type is changed, e.g. when changing the trigger type, but the callers expect the state to be preserved.
As the way how check_timer() is switching the delivery modes is truly unique, the obvious fix is to simply unmask the i8259 manually after changing the mode to ExtINT delivery and switching the irq chip to the legacy PIC.
Note, that the fixes tag is not really precise, but identifies the commit which broke the assumptions in the IO/APIC and i8259 code and that's the kernel version to which this needs to be backported.
--- arch/x86/kernel/apic/io_apic.c | 1 + 1 file changed, 1 insertion(+)
arch/x86/kernel/apic/io_apic.c +1 -0
@@ -2243,6 +2243,7 @@ static inline void __init check_timer(vo legacy_pic->init (0 ); legacy_pic->make_irq (0 );apic_write (APIC_LVT0 ,APIC_DM_EXTINT ); + legacy_pic->unmask (0 );unlock_ExtINT_logic ();
Greg Kroah-Hartman
maintainerPATCH 74/99 scsi: lpfc: Fix initial FLOGI failure due to BBSCN not supported
In reply to Greg Kroah-HartmanFrom: James Smart <[email protected]>
commit 7f04839ec4483563f38062b4dd90253e45447198 upstream.
Initial FLOGIs are failing with the following message:
lpfc 0000:13:00.1: 1:(0):0820 FLOGI Failed (x300). BBCredit Not Supported
In a prior patch, the READ_SPARAM command was re-ordered to post after CONFIG_LINK as the driver is expected to update the driver's copy of the service parameters for the FLOGI payload. If the bb-credit recovery feature is enabled, this is fine. But on adapters were bb-credit recovery isn't enabled, it would cause the FLOGI to fail.
Fix by restoring the original command order (READ_SPARAM before CONFIG_LINK), and after issuing CONFIG_LINK, detect bb-credit recovery support and reissuing READ_SPARAM to obtain the updated service parameters (effectively adding in the fix command order).
[mkp: corrected SHA]
--- drivers/scsi/lpfc/lpfc_hbadisc.c | 76 ++++++++++++++++++++++++++------------- 1 file changed, 52 insertions(+), 24 deletions(-)
drivers/scsi/lpfc/lpfc_hbadisc.c +52 -24
@@ -71,6 +71,7 @@ static void lpfc_disc_timeout_handler(ststatic void lpfc_disc_flush_list (struct lpfc_vport *vport);static void lpfc_unregister_fcfi_cmpl (struct lpfc_hba *,LPFC_MBOXQ_t *);static int lpfc_fcf_inuse (struct lpfc_hba *); +static void lpfc_mbx_cmpl_read_sparam (struct lpfc_hba *,LPFC_MBOXQ_t *);void lpfc_terminate_rport_io (struct fc_rport *rport)
@@ -1138,11 +1139,13 @@ out:return ; } -void lpfc_mbx_cmpl_local_config_link (struct lpfc_hba *phba,LPFC_MBOXQ_t *pmb) {struct lpfc_vport *vport = pmb->vport; +LPFC_MBOXQ_t *sparam_mb; +struct lpfc_dmabuf *sparam_mp; +int rc;if (pmb->u.mb.mbxStatus) goto out;
@@ -1167,12 +1170,42 @@ lpfc_mbx_cmpl_local_config_link(struct l }/* Start discovery by sending a FLOGI. port_state is identically -* LPFC_FLOGI while waiting for FLOGI cmpl. Check if sending -* the FLOGI is being deferred till after MBX_READ_SPARAM completes. +* LPFC_FLOGI while waiting for FLOGI cmpl. */ if (vport->port_state !=LPFC_FLOGI ) { -if (!(phba->hba_flag &HBA_DEFER_FLOGI )) +/* Issue MBX_READ_SPARAM to update CSPs before FLOGI if +* bb-credit recovery is in place. +*/ +if (phba->bbcredit_support && phba->cfg_enable_bbcr && + !(phba->link_flag &LS_LOOPBACK_MODE )) { + sparam_mb =mempool_alloc (phba->mbox_mem_pool, +GFP_KERNEL ); +if (!sparam_mb) + goto sparam_out; + + rc =lpfc_read_sparam (phba, sparam_mb,0 ); +if (rc) { +mempool_free (sparam_mb, phba->mbox_mem_pool); + goto sparam_out; + } + sparam_mb->vport = vport; + sparam_mb->mbox_cmpl = lpfc_mbx_cmpl_read_sparam; + rc =lpfc_sli_issue_mbox (phba, sparam_mb,MBX_NOWAIT ); +if (rc ==MBX_NOT_FINISHED ) { + sparam_mp = (struct lpfc_dmabuf *) + sparam_mb->ctx_buf; +lpfc_mbuf_free (phba, sparam_mp->virt, + sparam_mp->phys); +kfree (sparam_mp); + sparam_mb->ctx_buf =NULL ; +mempool_free (sparam_mb, phba->mbox_mem_pool); + goto sparam_out; + } + + phba->hba_flag |=HBA_DEFER_FLOGI ; + }else {lpfc_initial_flogi (vport); + } }else {if (vport->fc_flag &FC_PT2PT )lpfc_disc_start (vport);
@@ -1184,6 +1217,7 @@ out:"0306 CONFIG_LINK mbxStatus error x%x " "HBA state x%x\n" , pmb->u.mb.mbxStatus, vport->port_state); +sparam_out:mempool_free (pmb, phba->mbox_mem_pool);lpfc_linkdown (phba);
@@ -3239,21 +3273,6 @@ lpfc_mbx_process_link_up(struct lpfc_hbalpfc_linkup (phba); sparam_mbox =NULL ; -if (!(phba->hba_flag &HBA_FCOE_MODE )) { - cfglink_mbox =mempool_alloc (phba->mbox_mem_pool,GFP_KERNEL ); -if (!cfglink_mbox) - goto out; - vport->port_state =LPFC_LOCAL_CFG_LINK ; -lpfc_config_link (phba, cfglink_mbox); - cfglink_mbox->vport = vport; - cfglink_mbox->mbox_cmpl = lpfc_mbx_cmpl_local_config_link; - rc =lpfc_sli_issue_mbox (phba, cfglink_mbox,MBX_NOWAIT ); -if (rc ==MBX_NOT_FINISHED ) { -mempool_free (cfglink_mbox, phba->mbox_mem_pool); - goto out; - } - } - sparam_mbox =mempool_alloc (phba->mbox_mem_pool,GFP_KERNEL );if (!sparam_mbox) goto out;
@@ -3274,7 +3293,20 @@ lpfc_mbx_process_link_up(struct lpfc_hba goto out; } -if (phba->hba_flag &HBA_FCOE_MODE ) { +if (!(phba->hba_flag &HBA_FCOE_MODE )) { + cfglink_mbox =mempool_alloc (phba->mbox_mem_pool,GFP_KERNEL ); +if (!cfglink_mbox) + goto out; + vport->port_state =LPFC_LOCAL_CFG_LINK ; +lpfc_config_link (phba, cfglink_mbox); + cfglink_mbox->vport = vport; + cfglink_mbox->mbox_cmpl = lpfc_mbx_cmpl_local_config_link; + rc =lpfc_sli_issue_mbox (phba, cfglink_mbox,MBX_NOWAIT ); +if (rc ==MBX_NOT_FINISHED ) { +mempool_free (cfglink_mbox, phba->mbox_mem_pool); + goto out; + } + }else { vport->port_state =LPFC_VPORT_UNKNOWN ;/* * Add the driver's default FCF record at FCF index 0 now. This
@@ -3331,10 +3363,6 @@ lpfc_mbx_process_link_up(struct lpfc_hba }/* Reset FCF roundrobin bmask for new discovery */ lpfc_sli4_clear_fcf_rr_bmask (phba); - }else { -if (phba->bbcredit_support && phba->cfg_enable_bbcr && - !(phba->link_flag &LS_LOOPBACK_MODE )) - phba->hba_flag |=HBA_DEFER_FLOGI ; }/* Prepare for LINK up registrations */
Greg Kroah-Hartman
maintainerPATCH 75/99 ALSA: usb-audio: Add delay quirk for H570e USB headsets
In reply to Greg Kroah-HartmanFrom: Joakim Tjernlund <[email protected]>
commit 315c7ad7a701baba28c628c4c5426b3d9617ceed upstream.
Needs the same delay as H650e
--- sound/usb/quirks.c | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
sound/usb/quirks.c +4 -3
@@ -1668,12 +1668,13 @@ void snd_usb_ctl_msg_quirk(struct usb_de && (requesttype & USB_TYPE_MASK) == USB_TYPE_CLASS)msleep (20 ); -/* Zoom R16/24, Logitech H650e, Jabra 550a, Kingston HyperX needs a tiny -* delay here, otherwise requests like get/set frequency return as -* failed despite actually succeeding. +/* Zoom R16/24, Logitech H650e/H570e, Jabra 550a, Kingston HyperX +* needs a tiny delay here, otherwise requests like get/set +* frequency return as failed despite actually succeeding. */ if ((chip->usb_id ==USB_ID (0x1686 ,0x00dd ) || chip->usb_id ==USB_ID (0x046d ,0x0a46 ) || + chip->usb_id ==USB_ID (0x046d ,0x0a56 ) || chip->usb_id ==USB_ID (0x0b0e ,0x0349 ) || chip->usb_id ==USB_ID (0x0951 ,0x16ad )) && (requesttype &USB_TYPE_MASK ) ==USB_TYPE_CLASS )
Greg Kroah-Hartman
maintainerPATCH 76/99 ALSA: hda/realtek - Couldnt detect Mic if booting with headset plugged
In reply to Greg Kroah-HartmanFrom: Hui Wang <[email protected]>
commit 3f74249057827c5f6676c41c18f6be12ce1469ce upstream.
We found a Mic detection issue on many Lenovo laptops, those laptops belong to differnt models and they have different audio design like internal mic connects to the codec or PCH, they all have this problem, the problem is if plugging a headset before powerup/reboot the machine, after booting up, the headphone could be detected but Mic couldn't. If we plug out and plug in the headset, both headphone and Mic could be detected then.
Through debugging we found the codec on those laptops are same, it is alc257, and if we don't disable the 3k pulldown in alc256_shutup(), the issue will be fixed. So far there is no pop noise or power consumption regression on those laptops after this change.
--- sound/pci/hda/patch_realtek.c | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
sound/pci/hda/patch_realtek.c +5 -1
@@ -3419,7 +3419,11 @@ static void alc256_shutup(struct hda_cod/* 3k pull low control for Headset jack. */ /* NOTE: call this before clearing the pin, otherwise codec stalls */ -alc_update_coef_idx (codec,0x46 ,0 ,3 <<12 ); +/* If disable 3k pulldown control for alc257, the Mic detection will not work correctly +* when booting with headset plugged. So skip setting it for the codec alc257 +*/ +if (codec->core.vendor_id !=0x10ec0257 ) +alc_update_coef_idx (codec,0x46 ,0 ,3 <<12 );if (!spec->no_shutup_pins) snd_hda_codec_write(codec, hp_pin, 0,
Greg Kroah-Hartman
maintainerPATCH 77/99 ALSA: hda/realtek: Enable front panel headset LED on Lenovo ThinkStation P520
In reply to Greg Kroah-HartmanFrom: Kai-Heng Feng <[email protected]>
commit f73bbf639b32acb6b409e188fdde5644b301978f upstream.
On Lenovo P520, the front panel headset LED isn't lit up right now.
Realtek states that the LED needs to be enabled by ALC233's GPIO2, so let's do it accordingly to light the LED up.
--- sound/pci/hda/patch_realtek.c | 7 +++++++ 1 file changed, 7 insertions(+)
sound/pci/hda/patch_realtek.c +7 -0
@@ -6066,6 +6066,7 @@ static void alc_fixup_thinkpad_acpi(stru#include "hp_x360_helper.c" enum { +ALC269_FIXUP_GPIO2 ,ALC269_FIXUP_SONY_VAIO ,ALC275_FIXUP_SONY_VAIO_GPIO2 ,ALC269_FIXUP_DELL_M101Z ,
@@ -6247,6 +6248,10 @@ enum { };static const struct hda_fixup alc269_fixups[] = { + [ALC269_FIXUP_GPIO2 ] = { + .type =HDA_FIXUP_FUNC , + .v.func = alc_fixup_gpio2, + }, [ALC269_FIXUP_SONY_VAIO ] = { .type =HDA_FIXUP_PINCTLS , .v.pins = (const struct hda_pintbl []) {
@@ -7066,6 +7071,8 @@ static const struct hda_fixup alc269_fix [ALC233_FIXUP_LENOVO_MULTI_CODECS] = { .type = HDA_FIXUP_FUNC, .v.func = alc233_alc662_fixup_lenovo_dual_codecs, + .chained = true, + .chain_id =ALC269_FIXUP_GPIO2 }, [ALC233_FIXUP_ACER_HEADSET_MIC] = { .type = HDA_FIXUP_VERBS,
Greg Kroah-Hartman
maintainerPATCH 78/99 lib/string.c: implement stpcpy
In reply to Greg Kroah-HartmanFrom: Nick Desaulniers <[email protected]>
commit 1e1b6d63d6340764e00356873e5794225a2a03ea upstream.
LLVM implemented a recent "libcall optimization" that lowers calls to sprintf(dest, "%s", str) where the return value is used to stpcpy(dest, str) - dest.
This generally avoids the machinery involved in parsing format strings. stpcpy is just like strcpy except it returns the pointer to the new tail of dest. This optimization was introduced into clang-12.
Implement this so that we don't observe linkage failures due to missing symbol definitions for stpcpy.
Similar to last year's fire drill with: commit 5f074f3e192f ("lib/string.c: implement a basic bcmp")
The kernel is somewhere between a "freestanding" environment (no full libc) and "hosted" environment (many symbols from libc exist with the same type, function signature, and semantics).
As Peter Anvin notes, there's not really a great way to inform the compiler that you're targeting a freestanding environment but would like to opt-in to some libcall optimizations (see pr/47280 below), rather than opt-out.
Arvind notes, -fno-builtin-* behaves slightly differently between GCC and Clang, and Clang is missing many __builtin_* definitions, which I consider a bug in Clang and am working on fixing.
Masahiro summarizes the subtle distinction between compilers justly:
To prevent transformation from foo() into bar(), there are two ways in Clang to do that; -fno-builtin-foo, and -fno-builtin-bar. There is only one in GCC; -fno-buitin-foo.
(Any difference in that behavior in Clang is likely a bug from a missing __builtin_* definition.)
Masahiro also notes:
We want to disable optimization from foo() to bar(),
but we may still benefit from the optimization from foo() into something else. If GCC implements the same transform, we would run into a problem because it is not -fno-builtin-bar, but -fno-builtin-foo that disables that optimization.
In this regard, -fno-builtin-foo would be more future-proof than -fno-built-bar, but -fno-builtin-foo is still potentially overkill. We may want to prevent calls from foo() being optimized into calls to bar(), but we still may want other optimization on calls to foo().
It seems that compilers today don't quite provide the fine grain control over which libcall optimizations pseudo-freestanding environments would prefer.
Finally, Kees notes that this interface is unsafe, so we should not encourage its use. As such, I've removed the declaration from any header, but it still needs to be exported to avoid linkage errors in modules.
--- lib/string.c | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+)
lib/string.c +24 -0
@@ -272,6 +272,30 @@ ssize_t strscpy_pad(char *dest, const ch }EXPORT_SYMBOL (strscpy_pad); +/** +* stpcpy - copy a string from src to dest returning a pointer to the new end +* of dest, including src's %NUL-terminator. May overrun dest. +* @dest: pointer to end of string being copied into. Must be large enough +* to receive copy. +* @src: pointer to the beginning of string being copied from. Must not overlap +* dest. +* +* stpcpy differs from strcpy in a key way: the return value is a pointer +* to the new %NUL-terminating character in @dest. (For strcpy, the return +* value is a pointer to the start of @dest). This interface is considered +* unsafe as it doesn't perform bounds checking of the inputs. As such it's +* not recommended for usage. Instead, its definition is provided in case +* the compiler lowers other libcalls to stpcpy. +*/ +char *stpcpy (char *__restrict__ dest,const char *__restrict__ src); +char *stpcpy (char *__restrict__ dest,const char *__restrict__ src) +{ +while ((*dest++ = *src++) !='\0' ) +/* nothing */ ; +return --dest; +} +EXPORT_SYMBOL (stpcpy); +#ifndef __HAVE_ARCH_STRCAT/** * strcat - Append one %NUL-terminated string to another
Greg Kroah-Hartman
maintainerPATCH 79/99 tracing: fix double free
In reply to Greg Kroah-HartmanFrom: Tom Rix <[email protected]>
commit 46bbe5c671e06f070428b9be142cc4ee5cedebac upstream.
clang static analyzer reports this problem
trace_events_hist.c:3824:3: warning: Attempt to free
released memory
kfree(hist_data->attrs->var_defs.name[i]);
In parse_var_defs() if there is a problem allocating var_defs.expr, the earlier var_defs.name is freed. This free is duplicated by free_var_defs() which frees the rest of the list.
Because free_var_defs() has to run anyway, remove the second free fom parse_var_defs().
--- kernel/trace/trace_events_hist.c | 1 - 1 file changed, 1 deletion(-)
kernel/trace/trace_events_hist.c +0 -1
@@ -3865,7 +3865,6 @@ static int parse_var_defs(struct hist_tr s =kstrdup (field_str,GFP_KERNEL );if (!s) { -kfree (hist_data->attrs->var_defs.name[n_vars]); ret = -ENOMEM ; goto free; }
Greg Kroah-Hartman
maintainerPATCH 80/99 s390/dasd: Fix zero write for FBA devices
In reply to Greg Kroah-HartmanFrom: Jan Höppner <[email protected]>
commit 709192d531e5b0a91f20aa14abfe2fc27ddd47af upstream.
A discard request that writes zeros using the global kernel internal ZERO_PAGE will fail for machines with more than 2GB of memory due to the location of the ZERO_PAGE.
Fix this by using a driver owned global zero page allocated with GFP_DMA flag set.
--- drivers/s390/block/dasd_fba.c | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
drivers/s390/block/dasd_fba.c +8 -1
@@ -40,6 +40,7 @@MODULE_LICENSE ("GPL" );static struct dasd_discipline dasd_fba_discipline; +static void *dasd_fba_zero_page;struct dasd_fba_private {struct dasd_fba_characteristics rdc_data;
@@ -270,7 +271,7 @@ static void ccw_write_zero(struct ccw1 * ccw->cmd_code =DASD_FBA_CCW_WRITE ; ccw->flags |=CCW_FLAG_SLI ; ccw->count = count; - ccw->cda = (__u32 ) (addr_t )page_to_phys (ZERO_PAGE (0 )); + ccw->cda = (__u32 ) (addr_t ) dasd_fba_zero_page; }/*
@@ -830,6 +831,11 @@ dasd_fba_init(void)int ret;ASCEBC (dasd_fba_discipline.ebcname,4 ); + + dasd_fba_zero_page = (void *)get_zeroed_page (GFP_KERNEL |GFP_DMA ); +if (!dasd_fba_zero_page) +return -ENOMEM ; + ret =ccw_driver_register (&dasd_fba_driver);if (!ret)wait_for_device_probe ();
@@ -841,6 +847,7 @@ static void __exitdasd_fba_cleanup (void) {ccw_driver_unregister (&dasd_fba_driver); +free_page ((unsigned long )dasd_fba_zero_page); }module_init (dasd_fba_init);
Greg Kroah-Hartman
maintainerPATCH 81/99 mt76: mt7615: use v1 MCU API on MT7615 to fix issues with adding/removing stations
In reply to Greg Kroah-HartmanFrom: Felix Fietkau <[email protected]>
commit d1c9da9e4c938e8bbf8b0ef9e5772b97db5639e9 upstream.
The implementation of embedding WTBL update inside the STA_REC update is buggy on the MT7615 v2 firmware. This leads to connection issues after a station has connected and disconnected again.
Switch to the v1 MCU API ops, since they have received much more testing and should be more stable.
On MT7622 and later, the v2 API is more actively used, so we should keep using it as well.
--- drivers/net/wireless/mediatek/mt76/mt7615/mcu.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/wireless/mediatek/mt76/mt7615/mcu.c +2 -1
@@ -2014,7 +2014,8 @@ static int mt7615_load_n9(struct mt7615_sizeof (dev->mt76.hw->wiphy->fw_version), "%.10s-%.15s", hdr->fw_ver, hdr->build_date); -if (!strncmp (hdr->fw_ver,"2.0" ,sizeof (hdr->fw_ver))) { +if (!is_mt7615 (&dev->mt76) && + !strncmp (hdr->fw_ver,"2.0" ,sizeof (hdr->fw_ver))) { dev->fw_ver =MT7615_FIRMWARE_V2 ; dev->mcu_ops = &sta_update_ops; }else {
Greg Kroah-Hartman
maintainerPATCH 82/99 lib/bootconfig: Fix a bug of breaking existing tree nodes
In reply to Greg Kroah-HartmanFrom: Masami Hiramatsu <[email protected]>
commit ead1e19ad905b97261f0ad7a98bb64abb9323b2b upstream.
Fix a bug of breaking existing tree nodes by parsing the second and subsequent braces. Since the bootconfig parser uses the node.next field as a flag of current parent node, but this will break the existing tree if the same key node is specified again in the bootconfig.
For example, the following bootconfig should be foo.buz and bar.
foo
bar
foo { buz }
However, when parsing the brace "{", it breaks foo->bar link by marking open-brace node. So the bootconfig unlinks bar from the bootconfig internal tree.
This introduces a stack outside of the tree and record the last open-brace on the stack instead of using node.next field.
--- lib/bootconfig.c | 36 +++++++++++++++++++++++------------- 1 file changed, 23 insertions(+), 13 deletions(-)
lib/bootconfig.c +23 -13
@@ -31,6 +31,8 @@ static size_t xbc_data_size __initdata;static struct xbc_node *last_parent__initdata ;static const char *xbc_err_msg__initdata ;static int xbc_err_pos__initdata ; +static int open_brace[XBC_DEPTH_MAX ]__initdata ; +static int brace_index__initdata ;static int __init xbc_parse_error (const char *msg,const char *p) {
@@ -423,27 +425,27 @@ static char *skip_spaces_until_newline(creturn p; } -static int __init __xbc_open_brace (void ) +static int __init __xbc_open_brace (char *p) { -/* Mark the last key as open brace */ - last_parent->next =XBC_NODE_MAX ; +/* Push the last key as open brace */ + open_brace[brace_index++] =xbc_node_index (last_parent); +if (brace_index >=XBC_DEPTH_MAX ) +return xbc_parse_error ("Exceed max depth of braces" , p);return 0 ; }static int __init __xbc_close_brace (char *p) { -struct xbc_node *node; - -if (!last_parent || last_parent->next !=XBC_NODE_MAX ) + brace_index--; +if (!last_parent || brace_index <0 || + (open_brace[brace_index] !=xbc_node_index (last_parent)))return xbc_parse_error ("Unexpected closing brace" , p); - node = last_parent; - node->next =0 ; -do { - node =xbc_node_get_parent (node); - }while (node && node->next !=XBC_NODE_MAX ); - last_parent = node; +if (brace_index ==0 ) + last_parent =NULL ; +else + last_parent = &xbc_nodes[open_brace[brace_index -1 ]];return 0 ; }
@@ -651,7 +653,7 @@ static int __init xbc_open_brace(char **return ret; *k = n; -return __xbc_open_brace (); +return __xbc_open_brace (n -1 ); }static int __init xbc_close_brace (char **k,char *n)
@@ -671,6 +673,13 @@ static int __init xbc_verify_tree(void)int i, depth, len, wlen;struct xbc_node *n, *m; +/* Brace closing */ +if (brace_index) { + n = &xbc_nodes[open_brace[brace_index]]; +return xbc_parse_error ("Brace is not closed" , +xbc_node_get_data (n)); + } +/* Empty tree */ if (xbc_node_num ==0 ) {xbc_parse_error ("Empty config" , xbc_data);
@@ -735,6 +744,7 @@ void __init xbc_destroy_all(void) xbc_node_num =0 ;memblock_free (__pa (xbc_nodes),sizeof (struct xbc_node ) *XBC_NODE_MAX ); xbc_nodes =NULL ; + brace_index =0 ; }/**
Greg Kroah-Hartman
maintainerPATCH 83/99 lib/bootconfig: Fix to remove tailing spaces after value
In reply to Greg Kroah-HartmanFrom: Masami Hiramatsu <[email protected]>
commit c7af4ecdffe1537ba8aeed0ac12c3326f908df43 upstream.
Fix to remove tailing spaces after value. If there is a space after value, the bootconfig failed to remove it because it applies strim() before replacing the delimiter with null.
For example,
foo = var # comment
was parsed as below.
foo="var "
but user will expect
foo="var"
This fixes it by applying strim() after removing the delimiter.
--- lib/bootconfig.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
lib/bootconfig.c +1 -1
@@ -486,8 +486,8 @@ static int __init __xbc_parse_value(charbreak ; }if (strchr (",;\n#}" , c)) { - v =strim (v); *p++ ='\0' ; + v =strim (v);break ; } }
Greg Kroah-Hartman
maintainerPATCH 84/99 kprobes: Fix to check probe enabled before disarm_kprobe_ftrace()
In reply to Greg Kroah-HartmanFrom: Masami Hiramatsu <[email protected]>
commit 3031313eb3d549b7ad6f9fbcc52ba04412e3eb9e upstream.
Commit 0cb2f1372baa ("kprobes: Fix NULL pointer dereference at kprobe_ftrace_handler") fixed one bug but not completely fixed yet. If we run a kprobe_module.tc of ftracetest, kernel showed a warning as below.
# ./ftracetest test.d/kprobe/kprobe_module.tc === Ftrace unit tests === [1] Kprobe dynamic event - probing module ... [ 22.400215] ------------[ cut here ]------------ [ 22.400962] Failed to disarm kprobe-ftrace at trace_printk_irq_work+0x0/0x7e [trace_printk] (-2) [ 22.402139] WARNING: CPU: 7 PID: 200 at kernel/kprobes.c:1091 __disarm_kprobe_ftrace.isra.0+0x7e/0xa0 [ 22.403358] Modules linked in: trace_printk(-) [ 22.404028] CPU: 7 PID: 200 Comm: rmmod Not tainted 5.9.0-rc2+ #66 [ 22.404870] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014 [ 22.406139] RIP: 0010:__disarm_kprobe_ftrace.isra.0+0x7e/0xa0 [ 22.406947] Code: 30 8b 03 eb c9 80 3d e5 09 1f 01 00 75 dc 49 8b 34 24 89 c2 48 c7 c7 a0 c2 05 82 89 45 e4 c6 05 cc 09 1f 01 01 e8 a9 c7 f0 ff <0f> 0b 8b 45 e4 eb b9 89 c6 48 c7 c7 70 c2 05 82 89 45 e4 e8 91 c7 [ 22.409544] RSP: 0018:ffffc90000237df0 EFLAGS: 00010286 [ 22.410385] RAX: 0000000000000000 RBX: ffffffff83066024 RCX: 0000000000000000 [ 22.411434] RDX: 0000000000000001 RSI: ffffffff810de8d3 RDI: ffffffff810de8d3 [ 22.412687] RBP: ffffc90000237e10 R08: 0000000000000001 R09: 0000000000000001 [ 22.413762] R10: 0000000000000000 R11: 0000000000000001 R12: ffff88807c478640 [ 22.414852] R13: ffffffff8235ebc0 R14: ffffffffa00060c0 R15: 0000000000000000 [ 22.415941] FS: 00000000019d48c0(0000) GS:ffff88807d7c0000(0000) knlGS:0000000000000000 [ 22.417264] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 22.418176] CR2: 00000000005bb7e3 CR3: 0000000078f7a000 CR4: 00000000000006a0 [ 22.419309] Call Trace: [ 22.419990] kill_kprobe+0x94/0x160 [ 22.420652] kprobes_module_callback+0x64/0x230 [ 22.421470] notifier_call_chain+0x4f/0x70 [ 22.422184] blocking_notifier_call_chain+0x49/0x70 [ 22.422979] __x64_sys_delete_module+0x1ac/0x240 [ 22.423733] do_syscall_64+0x38/0x50 [ 22.424366] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 22.425176] RIP: 0033:0x4bb81d [ 22.425741] Code: 00 c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 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 e0 ff ff ff f7 d8 64 89 01 48 [ 22.428726] RSP: 002b:00007ffc70fef008 EFLAGS: 00000246 ORIG_RAX: 00000000000000b0 [ 22.430169] RAX: ffffffffffffffda RBX: 00000000019d48a0 RCX: 00000000004bb81d [ 22.431375] RDX: 0000000000000000 RSI: 0000000000000880 RDI: 00007ffc70fef028 [ 22.432543] RBP: 0000000000000880 R08: 00000000ffffffff R09: 00007ffc70fef320 [ 22.433692] R10: 0000000000656300 R11: 0000000000000246 R12: 00007ffc70fef028 [ 22.434635] R13: 0000000000000000 R14: 0000000000000002 R15: 0000000000000000 [ 22.435682] irq event stamp: 1169 [ 22.436240] hardirqs last enabled at (1179): [<ffffffff810df542>] console_unlock+0x422/0x580 [ 22.437466] hardirqs last disabled at (1188): [<ffffffff810df19b>] console_unlock+0x7b/0x580 [ 22.438608] softirqs last enabled at (866): [<ffffffff81c0038e>] __do_softirq+0x38e/0x490 [ 22.439637] softirqs last disabled at (859): [<ffffffff81a00f42>] asm_call_on_stack+0x12/0x20 [ 22.440690] ---[ end trace 1e7ce7e1e4567276 ]--- [ 22.472832] trace_kprobe: This probe might be able to register after target module is loaded. Continue.
This is because the kill_kprobe() calls disarm_kprobe_ftrace() even if the given probe is not enabled. In that case, ftrace_set_filter_ip() fails because the given probe point is not registered to ftrace.
Fix to check the given (going) probe is enabled before invoking disarm_kprobe_ftrace().
--- kernel/kprobes.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
kernel/kprobes.c +3 -2
@@ -2130,9 +2130,10 @@ static void kill_kprobe(struct kprobe *p/* * The module is going away. We should disarm the kprobe which -* is using ftrace. +* is using ftrace, because ftrace framework is still available at +* MODULE_STATE_GOING notification. */ -if (kprobe_ftrace (p)) +if (kprobe_ftrace (p) && !kprobe_disabled (p) && !kprobes_all_disarmed)disarm_kprobe_ftrace (p); }
Greg Kroah-Hartman
maintainerPATCH 85/99 kprobes: tracing/kprobes: Fix to kill kprobes on initmem after boot
In reply to Greg Kroah-HartmanFrom: Masami Hiramatsu <[email protected]>
commit 82d083ab60c3693201c6f5c7a5f23a6ed422098d upstream.
Since kprobe_event= cmdline option allows user to put kprobes on the functions in initmem, kprobe has to make such probes gone after boot. Currently the probes on the init functions in modules will be handled by module callback, but the kernel init text isn't handled. Without this, kprobes may access non-exist text area to disable or remove it.
--- include/linux/kprobes.h | 5 +++++ init/main.c | 2 ++ kernel/kprobes.c | 22 ++++++++++++++++++++++ 3 files changed, 29 insertions(+)
include/linux/kprobes.h +5 -0
@@ -369,6 +369,8 @@ void unregister_kretprobes(struct kretprvoid kprobe_flush_task (struct task_struct *tk);void recycle_rp_inst (struct kretprobe_instance *ri,struct hlist_head *head); +void kprobe_free_init_mem (void ); +int disable_kprobe (struct kprobe *kp);int enable_kprobe (struct kprobe *kp);
@@ -426,6 +428,9 @@ static inline void unregister_kretprobesstatic inline void kprobe_flush_task (struct task_struct *tk) { } +static inline void kprobe_free_init_mem (void ) +{ +}static inline int disable_kprobe (struct kprobe *kp) {return -ENOSYS ;
init/main.c +2 -0
@@ -33,6 +33,7 @@#include <linux/nmi.h> #include <linux/percpu.h> #include <linux/kmod.h> +#include <linux/kprobes.h> #include <linux/vmalloc.h> #include <linux/kernel_stat.h> #include <linux/start_kernel.h>
@@ -1401,6 +1402,7 @@ static int __ref kernel_init(void *unusekernel_init_freeable ();/* need to finish all async __init code before freeing the memory */ async_synchronize_full (); +kprobe_free_init_mem ();ftrace_free_init_mem ();free_initmem ();mark_readonly ();
kernel/kprobes.c +22 -0
@@ -2406,6 +2406,28 @@ static struct notifier_block kprobe_moduextern unsigned long __start_kprobe_blacklist[];extern unsigned long __stop_kprobe_blacklist[]; +void kprobe_free_init_mem (void ) +{ +void *start = (void *)(&__init_begin); +void *end = (void *)(&__init_end); +struct hlist_head *head; +struct kprobe *p; +int i; + +mutex_lock (&kprobe_mutex); + +/* Kill all kprobes on initmem */ +for (i =0 ; i <KPROBE_TABLE_SIZE ; i++) { + head = &kprobe_table[i]; +hlist_for_each_entry (p, head, hlist) { +if (start <= (void *)p->addr && (void *)p->addr < end) +kill_kprobe (p); + } + } + +mutex_unlock (&kprobe_mutex); +} +static int __init init_kprobes (void ) {int i, err =0 ;
Greg Kroah-Hartman
maintainerPATCH 86/99 btrfs: fix put of uninitialized kobject after seed device delete
In reply to Greg Kroah-HartmanFrom: Anand Jain <[email protected]>
commit b5ddcffa37778244d5e786fe32f778edf2bfc93e upstream.
The following test case leads to NULL kobject free error:
mount seed /mnt
add sprout to /mnt
umount /mnt
mount sprout to /mnt
delete seed
kobject: '(null)' (00000000dd2b87e4): is not initialized, yet kobject_put() is being called.
WARNING: CPU: 1 PID: 15784 at lib/kobject.c:736 kobject_put+0x80/0x350 RIP: 0010:kobject_put+0x80/0x350 :: Call Trace: btrfs_sysfs_remove_devices_dir+0x6e/0x160 [btrfs] btrfs_rm_device.cold+0xa8/0x298 [btrfs] btrfs_ioctl+0x206c/0x22a0 [btrfs] ksys_ioctl+0xe2/0x140 __x64_sys_ioctl+0x1e/0x29 do_syscall_64+0x96/0x150 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7f4047c6288b ::
This is because, at the end of the seed device-delete, we try to remove the seed's devid sysfs entry. But for the seed devices under the sprout fs, we don't initialize the devid kobject yet. So add a kobject state check, which takes care of the bug.
--- fs/btrfs/sysfs.c | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-)
fs/btrfs/sysfs.c +10 -6
@@ -1165,10 +1165,12 @@ int btrfs_sysfs_remove_devices_dir(struc disk_kobj->name); } -kobject_del (&one_device->devid_kobj); -kobject_put (&one_device->devid_kobj); +if (one_device->devid_kobj.state_initialized) { +kobject_del (&one_device->devid_kobj); +kobject_put (&one_device->devid_kobj); -wait_for_completion (&one_device->kobj_unregister); +wait_for_completion (&one_device->kobj_unregister); + }return 0 ; }
@@ -1181,10 +1183,12 @@ int btrfs_sysfs_remove_devices_dir(strucsysfs_remove_link (fs_devices->devices_kobj, disk_kobj->name); } -kobject_del (&one_device->devid_kobj); -kobject_put (&one_device->devid_kobj); +if (one_device->devid_kobj.state_initialized) { +kobject_del (&one_device->devid_kobj); +kobject_put (&one_device->devid_kobj); -wait_for_completion (&one_device->kobj_unregister); +wait_for_completion (&one_device->kobj_unregister); + } }return 0 ;
Greg Kroah-Hartman
maintainerPATCH 87/99 btrfs: fix overflow when copying corrupt csums for a message
In reply to Greg Kroah-HartmanFrom: Johannes Thumshirn <[email protected]>
commit 35be8851d172c6e3db836c0f28c19087b10c9e00 upstream.
Syzkaller reported a buffer overflow in btree_readpage_end_io_hook() when loop mounting a crafted image:
detected buffer overflow in memcpy
------------[ cut here ]------------ kernel BUG at lib/string.c:1129! invalid opcode: 0000 [#1] PREEMPT SMP KASAN CPU: 1 PID: 26 Comm: kworker/u4:2 Not tainted 5.9.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: btrfs-endio-meta btrfs_work_helper RIP: 0010:fortify_panic+0xf/0x20 lib/string.c:1129 RSP: 0018:ffffc90000e27980 EFLAGS: 00010286 RAX: 0000000000000022 RBX: ffff8880a80dca64 RCX: 0000000000000000 RDX: ffff8880a90860c0 RSI: ffffffff815dba07 RDI: fffff520001c4f22 RBP: ffff8880a80dca00 R08: 0000000000000022 R09: ffff8880ae7318e7 R10: 0000000000000000 R11: 0000000000077578 R12: 00000000ffffff6e R13: 0000000000000008 R14: ffffc90000e27a40 R15: 1ffff920001c4f3c FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 0000557335f440d0 CR3: 000000009647d000 CR4: 00000000001506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: memcpy include/linux/string.h:405 [inline] btree_readpage_end_io_hook.cold+0x206/0x221 fs/btrfs/disk-io.c:642 end_bio_extent_readpage+0x4de/0x10c0 fs/btrfs/extent_io.c:2854 bio_endio+0x3cf/0x7f0 block/bio.c:1449 end_workqueue_fn+0x114/0x170 fs/btrfs/disk-io.c:1695 btrfs_work_helper+0x221/0xe20 fs/btrfs/async-thread.c:318 process_one_work+0x94c/0x1670 kernel/workqueue.c:2269 worker_thread+0x64c/0x1120 kernel/workqueue.c:2415 kthread+0x3b5/0x4a0 kernel/kthread.c:292 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294 Modules linked in: ---[ end trace b68924293169feef ]--- RIP: 0010:fortify_panic+0xf/0x20 lib/string.c:1129 RSP: 0018:ffffc90000e27980 EFLAGS: 00010286 RAX: 0000000000000022 RBX: ffff8880a80dca64 RCX: 0000000000000000 RDX: ffff8880a90860c0 RSI: ffffffff815dba07 RDI: fffff520001c4f22 RBP: ffff8880a80dca00 R08: 0000000000000022 R09: ffff8880ae7318e7 R10: 0000000000000000 R11: 0000000000077578 R12: 00000000ffffff6e R13: 0000000000000008 R14: ffffc90000e27a40 R15: 1ffff920001c4f3c FS: 0000000000000000(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f95b7c4d008 CR3: 000000009647d000 CR4: 00000000001506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
The overflow happens, because in btree_readpage_end_io_hook() we assume that we have found a 4 byte checksum instead of the real possible 32 bytes we have for the checksums.
With the fix applied:
[ 35.726623] BTRFS: device fsid 815caf9a-dc43-4d2a-ac54-764b8333d765 devid 1 transid 5 /dev/loop0 scanned by syz-repro (215) [ 35.738994] BTRFS info (device loop0): disk space caching is enabled [ 35.738998] BTRFS info (device loop0): has skinny extents [ 35.743337] BTRFS warning (device loop0): loop0 checksum verify failed on 1052672 wanted 0xf9c035fc8d239a54 found 0x67a25c14b7eabcf9 level 0 [ 35.743420] BTRFS error (device loop0): failed to read chunk root [ 35.745899] BTRFS error (device loop0): open_ctree failed
--- fs/btrfs/disk-io.c | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-)
fs/btrfs/disk-io.c +5 -6
@@ -636,16 +636,15 @@ static int btree_readpage_end_io_hook(stcsum_tree_block (eb, result);if (memcmp_extent_buffer (eb, result,0 , csum_size)) { -u32 val; -u32 found =0 ; - -memcpy (&found, result, csum_size); +u8 val[BTRFS_CSUM_SIZE ] = {0 };read_extent_buffer (eb, &val,0 , csum_size);btrfs_warn_rl (fs_info, -"%s checksum verify failed on %llu wanted %x found %x level %d" , +"%s checksum verify failed on %llu wanted " CSUM_FMT " found " CSUM_FMT " level %d" , fs_info->sb->s_id, eb->start, - val, found,btrfs_header_level (eb)); +CSUM_FMT_VALUE (csum_size, val), +CSUM_FMT_VALUE (csum_size, result), +btrfs_header_level (eb)); ret = -EUCLEAN ; goto err; }
Greg Kroah-Hartman
maintainerPATCH 88/99 media: cec-adap.c: dont use flush_scheduled_work()
In reply to Greg Kroah-HartmanFrom: Hans Verkuil <[email protected]>
commit 288eceb0858323d66bff03cf386630a797b248ad upstream.
For some inexplicable reason I decided to call flush_scheduled_work() instead of cancel_delayed_work_sync(). The problem with that is that flush_scheduled_work() waits for *all* queued scheduled work to be completed instead of just the work itself.
This can cause a deadlock if a CEC driver also schedules work that takes the same lock. See the comments for flush_scheduled_work() in linux/workqueue.h.
This is exactly what has been observed a few times.
This patch simply replaces flush_scheduled_work() by cancel_delayed_work_sync().
--- drivers/media/cec/core/cec-adap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/media/cec/core/cec-adap.c +1 -1
@@ -1199,7 +1199,7 @@ void cec_received_msg_ts(struct cec_adap/* Cancel the pending timeout work */ if (!cancel_delayed_work (&data->work)) {mutex_unlock (&adap->lock); -flush_scheduled_work (); +cancel_delayed_work_sync (&data->work);mutex_lock (&adap->lock); }/*
Greg Kroah-Hartman
maintainerPATCH 89/99 MIPS: Loongson2ef: Disable Loongson MMI instructions
In reply to Greg Kroah-HartmanFrom: Jiaxun Yang <[email protected]>
commit b13812ddea615b6507beef24f76540c0c1143c5c upstream.
It was missed when I was forking Loongson2ef from Loongson64 but should be applied to Loongson2ef as march=loongson2f will also enable Loongson MMI in GCC-9+.
--- arch/mips/loongson2ef/Platform | 4 ++++ 1 file changed, 4 insertions(+)
arch/mips/loongson2ef/Platform +4 -0
@@ -22,6 +22,10 @@ ifdef CONFIG_CPU_LOONGSON2F_WORKAROUNDS endif endif +# Some -march= flags enable MMI instructions, and GCC complains about that +# support being enabled alongside -msoft-float. Thus explicitly disable MMI. +cflags-y += $(call cc-option,-mno-loongson-mmi) + # # Loongson Machines' Support #
Greg Kroah-Hartman
maintainerPATCH 90/99 dmabuf: fix NULL pointer dereference in dma_buf_release()
In reply to Greg Kroah-HartmanFrom: Charan Teja Reddy <[email protected]>
commit 19a508bd1ad8e444de86873bf2f2b2ab8edd6552 upstream.
NULL pointer dereference is observed while exporting the dmabuf but failed to allocate the 'struct file' which results into the dropping of the allocated dentry corresponding to this file in the dmabuf fs, which is ending up in dma_buf_release() and accessing the uninitialzed dentry->d_fsdata.
Call stack on 5.4 is below:
dma_buf_release+0x2c/0x254 drivers/dma-buf/dma-buf.c:88 __dentry_kill+0x294/0x31c fs/dcache.c:584 dentry_kill fs/dcache.c:673 [inline] dput+0x250/0x380 fs/dcache.c:859 path_put+0x24/0x40 fs/namei.c:485 alloc_file_pseudo+0x1a4/0x200 fs/file_table.c:235 dma_buf_getfile drivers/dma-buf/dma-buf.c:473 [inline] dma_buf_export+0x25c/0x3ec drivers/dma-buf/dma-buf.c:585
Fix this by checking for the valid pointer in the dentry->d_fsdata.
--- drivers/dma-buf/dma-buf.c | 2 ++ 1 file changed, 2 insertions(+)
drivers/dma-buf/dma-buf.c +2 -0
@@ -59,6 +59,8 @@ static void dma_buf_release(struct dentrstruct dma_buf *dmabuf; dmabuf = dentry->d_fsdata; +if (unlikely (!dmabuf)) +return ;BUG_ON (dmabuf->vmapping_counter);
Greg Kroah-Hartman
maintainerPATCH 91/99 mm, THP, swap: fix allocating cluster for swapfile by mistake
In reply to Greg Kroah-HartmanFrom: Gao Xiang <[email protected]>
commit 41663430588c737dd735bad5a0d1ba325dcabd59 upstream.
SWP_FS is used to make swap_{read,write}page() go through the filesystem, and it's only used for swap files over NFS. So, !SWP_FS means non NFS for now, it could be either file backed or device backed. Something similar goes with legacy SWP_FILE.
So in order to achieve the goal of the original patch, SWP_BLKDEV should be used instead.
FS corruption can be observed with SSD device + XFS + fragmented swapfile due to CONFIG_THP_SWAP=y.
I reproduced the issue with the following details:
Environment:
QEMU + upstream kernel + buildroot + NVMe (2 GB)
Kernel config:
CONFIG_BLK_DEV_NVME=y
CONFIG_THP_SWAP=y
Some reproducible steps:
mkfs.xfs -f /dev/nvme0n1
mkdir /tmp/mnt
mount /dev/nvme0n1 /tmp/mnt
bs="32k"
sz="1024m" # doesn't matter too much, I also tried 16m
xfs_io -f -c "pwrite -R -b $bs 0 $sz" -c "fdatasync" /tmp/mnt/sw xfs_io -f -c "pwrite -R -b $bs 0 $sz" -c "fdatasync" /tmp/mnt/sw xfs_io -f -c "pwrite -R -b $bs 0 $sz" -c "fdatasync" /tmp/mnt/sw xfs_io -f -c "pwrite -F -S 0 -b $bs 0 $sz" -c "fdatasync" /tmp/mnt/sw xfs_io -f -c "pwrite -R -b $bs 0 $sz" -c "fsync" /tmp/mnt/sw
mkswap /tmp/mnt/sw
swapon /tmp/mnt/sw
stress --vm 2 --vm-bytes 600M # doesn't matter too much as well
Symptoms:
- FS corruption (e.g. checksum failure)
- memory corruption at: 0xd2808010
- segfault
--- mm/swapfile.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
mm/swapfile.c +1 -1
@@ -1074,7 +1074,7 @@ start_over: goto nextsi; }if (size ==SWAPFILE_CLUSTER ) { -if (!(si->flags &SWP_FS )) +if (si->flags &SWP_BLKDEV ) n_ret =swap_alloc_cluster (si, swp_entries); }else n_ret = scan_swap_map_slots(si, SWAP_HAS_CACHE,
Greg Kroah-Hartman
maintainerPATCH 92/99 mm/gup: fix gup_fast with dynamic page table folding
In reply to Greg Kroah-HartmanFrom: Vasily Gorbik <[email protected]>
commit d3f7b1bb204099f2f7306318896223e8599bb6a2 upstream.
Currently to make sure that every page table entry is read just once gup_fast walks perform READ_ONCE and pass pXd value down to the next gup_pXd_range function by value e.g.:
static int gup_pud_range(p4d_t p4d, unsigned long addr, unsigned long end,
unsigned int flags, struct page **pages, int *nr)
...
pudp = pud_offset(&p4d, addr);
This function passes a reference on that local value copy to pXd_offset, and might get the very same pointer in return. This happens when the level is folded (on most arches), and that pointer should not be iterated.
On s390 due to the fact that each task might have different 5,4 or 3-level address translation and hence different levels folded the logic is more complex and non-iteratable pointer to a local copy leads to severe problems.
Here is an example of what happens with gup_fast on s390, for a task with 3-level paging, crossing a 2 GB pud boundary:
// addr = 0x1007ffff000, end = 0x10080001000
static int gup_pud_range(p4d_t p4d, unsigned long addr, unsigned long end,
unsigned int flags, struct page **pages, int *nr)
{
unsigned long next;
pud_t *pudp;
// pud_offset returns &p4d itself (a pointer to a value on stack)
pudp = pud_offset(&p4d, addr);
do {
// on second iteratation reading "random" stack value
pud_t pud = READ_ONCE(*pudp);
// next = 0x10080000000, due to PUD_SIZE/MASK != PGDIR_SIZE/MASK on s390
next = pud_addr_end(addr, end);
...
} while (pudp++, addr = next, addr != end); // pudp++ iterating over stack
return 1;}
This happens since s390 moved to common gup code with commit d1874a0c2805 ("s390/mm: make the pxd_offset functions more robust") and commit 1a42010cdc26 ("s390/mm: convert to the generic get_user_pages_fast code").
s390 tried to mimic static level folding by changing pXd_offset primitives to always calculate top level page table offset in pgd_offset and just return the value passed when pXd_offset has to act as folded.
What is crucial for gup_fast and what has been overlooked is that PxD_SIZE/MASK and thus pXd_addr_end should also change correspondingly. And the latter is not possible with dynamic folding.
To fix the issue in addition to pXd values pass original pXdp pointers down to gup_pXd_range functions. And introduce pXd_offset_lockless helpers, which take an additional pXd entry value parameter. This has already been discussed in
https://lkml.kernel.org/r/20190418100218.0a4afd51@mschwideX1
--- arch/s390/include/asm/pgtable.h | 42 ++++++++++++++++++++++++++++------------ include/linux/pgtable.h | 10 +++++++++ mm/gup.c | 18 ++++++++--------- 3 files changed, 49 insertions(+), 21 deletions(-)
arch/s390/include/asm/pgtable.h +30 -12
@@ -1260,26 +1260,44 @@ static inline pgd_t *pgd_offset_raw(pgd_#define pgd_offset (mm, address) pgd_offset_raw(READ_ONCE((mm)->pgd), address) -static inline p4d_t *p4d_offset (pgd_t *pgd,unsigned long address) +static inline p4d_t *p4d_offset_lockless (pgd_t *pgdp,pgd_t pgd,unsigned long address) { -if ((pgd_val (*pgd) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R1) -return (p4d_t *)pgd_deref (*pgd) +p4d_index (address); -return (p4d_t *) pgd; +if ((pgd_val (pgd) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R1) +return (p4d_t *)pgd_deref (pgd) +p4d_index (address); +return (p4d_t *) pgdp; } +#define p4d_offset_lockless p4d_offset_lockless -static inline pud_t *pud_offset (p4d_t *p4d,unsigned long address) +static inline p4d_t *p4d_offset (pgd_t *pgdp,unsigned long address) { -if ((p4d_val (*p4d) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R2) -return (pud_t *)p4d_deref (*p4d) +pud_index (address); -return (pud_t *) p4d; +return p4d_offset_lockless (pgdp, *pgdp, address); +} + +static inline pud_t *pud_offset_lockless (p4d_t *p4dp,p4d_t p4d,unsigned long address) +{ +if ((p4d_val (p4d) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R2) +return (pud_t *)p4d_deref (p4d) +pud_index (address); +return (pud_t *) p4dp; +} +#define pud_offset_lockless pud_offset_lockless + +static inline pud_t *pud_offset (p4d_t *p4dp,unsigned long address) +{ +return pud_offset_lockless (p4dp, *p4dp, address); }#define pud_offset pud_offset -static inline pmd_t *pmd_offset (pud_t *pud,unsigned long address) +static inline pmd_t *pmd_offset_lockless (pud_t *pudp,pud_t pud,unsigned long address) +{ +if ((pud_val (pud) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R3) +return (pmd_t *)pud_deref (pud) +pmd_index (address); +return (pmd_t *) pudp; +} +#define pmd_offset_lockless pmd_offset_lockless + +static inline pmd_t *pmd_offset (pud_t *pudp,unsigned long address) { -if ((pud_val (*pud) & _REGION_ENTRY_TYPE_MASK) >= _REGION_ENTRY_TYPE_R3) -return (pmd_t *)pud_deref (*pud) +pmd_index (address); -return (pmd_t *) pud; +return pmd_offset_lockless (pudp, *pudp, address); }#define pmd_offset pmd_offset
include/linux/pgtable.h +10 -0
@@ -1424,6 +1424,16 @@ typedef unsigned int pgtbl_mod_mask;#define mm_pmd_folded (mm) __is_defined(__PAGETABLE_PMD_FOLDED)#endif +#ifndef p4d_offset_lockless +#define p4d_offset_lockless (pgdp, pgd, address) p4d_offset(&(pgd), address) +#endif +#ifndef pud_offset_lockless +#define pud_offset_lockless (p4dp, p4d, address) pud_offset(&(p4d), address) +#endif +#ifndef pmd_offset_lockless +#define pmd_offset_lockless (pudp, pud, address) pmd_offset(&(pud), address) +#endif +/* * p?d_leaf() - true if this entry is a final mapping to a physical address. * This differs from p?d_huge() by the fact that they are always available (if
mm/gup.c +9 -9
@@ -2574,13 +2574,13 @@ static int gup_huge_pgd(pgd_t orig, pgd_return 1 ; } -static int gup_pmd_range (pud_t pud,unsigned long addr,unsigned long end, +static int gup_pmd_range (pud_t *pudp,pud_t pud,unsigned long addr,unsigned long end,unsigned int flags,struct page **pages,int *nr) {unsigned long next;pmd_t *pmdp; - pmdp =pmd_offset (&pud, addr); + pmdp =pmd_offset_lockless (pudp, pud, addr); do { pmd_t pmd = READ_ONCE(*pmdp);
@@ -2617,13 +2617,13 @@ static int gup_pmd_range(pud_t pud, unsireturn 1 ; } -static int gup_pud_range (p4d_t p4d,unsigned long addr,unsigned long end, +static int gup_pud_range (p4d_t *p4dp,p4d_t p4d,unsigned long addr,unsigned long end,unsigned int flags,struct page **pages,int *nr) {unsigned long next;pud_t *pudp; - pudp =pud_offset (&p4d, addr); + pudp =pud_offset_lockless (p4dp, p4d, addr); do { pud_t pud = READ_ONCE(*pudp);
@@ -2638,20 +2638,20 @@ static int gup_pud_range(p4d_t p4d, unsiif (!gup_huge_pd (__hugepd (pud_val (pud)), addr,PUD_SHIFT , next, flags, pages, nr))return 0 ; - }else if (!gup_pmd_range (pud, addr, next, flags, pages, nr)) + }else if (!gup_pmd_range (pudp, pud, addr, next, flags, pages, nr))return 0 ; }while (pudp++, addr = next, addr != end);return 1 ; } -static int gup_p4d_range (pgd_t pgd,unsigned long addr,unsigned long end, +static int gup_p4d_range (pgd_t *pgdp,pgd_t pgd,unsigned long addr,unsigned long end,unsigned int flags,struct page **pages,int *nr) {unsigned long next;p4d_t *p4dp; - p4dp =p4d_offset (&pgd, addr); + p4dp =p4d_offset_lockless (pgdp, pgd, addr); do { p4d_t p4d = READ_ONCE(*p4dp);
@@ -2663,7 +2663,7 @@ static int gup_p4d_range(pgd_t pgd, unsiif (!gup_huge_pd (__hugepd (p4d_val (p4d)), addr,P4D_SHIFT , next, flags, pages, nr))return 0 ; - }else if (!gup_pud_range (p4d, addr, next, flags, pages, nr)) + }else if (!gup_pud_range (p4dp, p4d, addr, next, flags, pages, nr))return 0 ; }while (p4dp++, addr = next, addr != end);
@@ -2691,7 +2691,7 @@ static void gup_pgd_range(unsigned longif (!gup_huge_pd (__hugepd (pgd_val (pgd)), addr,PGDIR_SHIFT , next, flags, pages, nr))return ; - }else if (!gup_p4d_range (pgd, addr, next, flags, pages, nr)) + }else if (!gup_p4d_range (pgdp, pgd, addr, next, flags, pages, nr))return ; }while (pgdp++, addr = next, addr != end); }
Greg Kroah-Hartman
maintainerPATCH 93/99 mm: replace memmap_context by meminit_context
In reply to Greg Kroah-HartmanFrom: Laurent Dufour <[email protected]>
commit c1d0da83358a2316d9be7f229f26126dbaa07468 upstream.
Patch series "mm: fix memory to node bad links in sysfs", v3.
Sometimes, firmware may expose interleaved memory layout like this:
Early memory node ranges
node 1: [mem 0x0000000000000000-0x000000011fffffff] node 2: [mem 0x0000000120000000-0x000000014fffffff] node 1: [mem 0x0000000150000000-0x00000001ffffffff] node 0: [mem 0x0000000200000000-0x000000048fffffff] node 2: [mem 0x0000000490000000-0x00000007ffffffff]
In that case, we can see memory blocks assigned to multiple nodes in sysfs:
$ ls -l /sys/devices/system/memory/memory21 total 0 lrwxrwxrwx 1 root root 0 Aug 24 05:27 node1 -> ../../node/node1 lrwxrwxrwx 1 root root 0 Aug 24 05:27 node2 -> ../../node/node2 -rw-r--r-- 1 root root 65536 Aug 24 05:27 online -r--r--r-- 1 root root 65536 Aug 24 05:27 phys_device -r--r--r-- 1 root root 65536 Aug 24 05:27 phys_index drwxr-xr-x 2 root root 0 Aug 24 05:27 power -r--r--r-- 1 root root 65536 Aug 24 05:27 removable -rw-r--r-- 1 root root 65536 Aug 24 05:27 state lrwxrwxrwx 1 root root 0 Aug 24 05:25 subsystem -> ../../../../bus/memory -rw-r--r-- 1 root root 65536 Aug 24 05:25 uevent -r--r--r-- 1 root root 65536 Aug 24 05:27 valid_zones
The same applies in the node's directory with a memory21 link in both the node1 and node2's directory.
This is wrong but doesn't prevent the system to run. However when later, one of these memory blocks is hot-unplugged and then hot-plugged, the system is detecting an inconsistency in the sysfs layout and a BUG_ON() is raised:
kernel BUG at /Users/laurent/src/linux-ppc/mm/memory_hotplug.c:1084! LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
Modules linked in: rpadlpar_io rpaphp pseries_rng rng_core vmx_crypto gf128mul binfmt_misc ip_tables x_tables xfs libcrc32c crc32c_vpmsum autofs4
CPU: 8 PID: 10256 Comm: drmgr Not tainted 5.9.0-rc1+ #25
Call Trace:
add_memory_resource+0x23c/0x340 (unreliable)
__add_memory+0x5c/0xf0
dlpar_add_lmb+0x1b4/0x500
dlpar_memory+0x1f8/0xb80
handle_dlpar_errorlog+0xc0/0x190
dlpar_store+0x198/0x4a0
kobj_attr_store+0x30/0x50
sysfs_kf_write+0x64/0x90
kernfs_fop_write+0x1b0/0x290
vfs_write+0xe8/0x290
ksys_write+0xdc/0x130
system_call_exception+0x160/0x270
system_call_common+0xf0/0x27cThis has been seen on PowerPC LPAR.
The root cause of this issue is that when node's memory is registered, the range used can overlap another node's range, thus the memory block is registered to multiple nodes in sysfs.
There are two issues here:
(a) The sysfs memory and node's layouts are broken due to these multiple links
(b) The link errors in link_mem_sections() should not lead to a system panic.
To address (a) register_mem_sect_under_node should not rely on the system state to detect whether the link operation is triggered by a hot plug operation or not. This is addressed by the patches 1 and 2 of this series.
Issue (b) will be addressed separately.
This patch (of 2):
The memmap_context enum is used to detect whether a memory operation is due to a hot-add operation or happening at boot time.
Make it general to the hotplug operation and rename it as meminit_context.
There is no functional change introduced by this patch
--- arch/ia64/mm/init.c | 6 +++--- include/linux/mm.h | 2 +- include/linux/mmzone.h | 11 ++++++++--- mm/memory_hotplug.c | 2 +- mm/page_alloc.c | 10 +++++----- 5 files changed, 18 insertions(+), 13 deletions(-)
arch/ia64/mm/init.c +3 -3
@@ -538,7 +538,7 @@ virtual_memmap_init(u64 start, u64 end,if (map_start < map_end)memmap_init_zone ((unsigned long )(map_end - map_start), args->nid, args->zone,page_to_pfn (map_start), -MEMMAP_EARLY ,NULL ); +MEMINIT_EARLY ,NULL );return 0 ; }
@@ -547,8 +547,8 @@ memmap_init (unsigned long size, int nid unsigned long start_pfn) {if (!vmem_map) { -memmap_init_zone (size, nid, zone, start_pfn,MEMMAP_EARLY , -NULL ); +memmap_init_zone (size, nid, zone, start_pfn, +MEMINIT_EARLY ,NULL ); }else {struct page *start;struct memmap_init_callback_data args;
include/linux/mm.h +1 -1
@@ -2445,7 +2445,7 @@ extern int __meminit __early_pfn_to_nid(extern void set_dma_reserve (unsigned long new_dma_reserve);extern void memmap_init_zone (unsigned long ,int ,unsigned long ,unsigned long , -enum memmap_context ,struct vmem_altmap *); +enum meminit_context ,struct vmem_altmap *);extern void setup_per_zone_wmarks (void );extern int __meminit init_per_zone_wmark_min (void );extern void mem_init (void );
include/linux/mmzone.h +8 -3
@@ -799,10 +799,15 @@ bool zone_watermark_ok(struct zone *z, u unsigned int alloc_flags);bool zone_watermark_ok_safe (struct zone *z,unsigned int order,unsigned long mark,int highest_zoneidx); -enum memmap_context { -MEMMAP_EARLY , -MEMMAP_HOTPLUG , +/* +* Memory initialization context, use to differentiate memory added by +* the platform statically or via memory hotplug interface. +*/ +enum meminit_context { +MEMINIT_EARLY , +MEMINIT_HOTPLUG , }; +extern void init_currently_empty_zone (struct zone *zone,unsigned long start_pfn,unsigned long size);
mm/memory_hotplug.c +1 -1
@@ -719,7 +719,7 @@ void __ref move_pfn_range_to_zone(struct* are reserved so nobody should be touching them so we should be safe */ memmap_init_zone (nr_pages, nid,zone_idx (zone), start_pfn, -MEMMAP_HOTPLUG , altmap); +MEMINIT_HOTPLUG , altmap);set_zone_contiguous (zone); }
mm/page_alloc.c +5 -5
@@ -5952,7 +5952,7 @@ overlap_memmap_init(unsigned long zone,* done. Non-atomic initialization, single-pass. */ void __meminit memmap_init_zone (unsigned long size,int nid,unsigned long zone, -unsigned long start_pfn,enum memmap_context context, +unsigned long start_pfn,enum meminit_context context,struct vmem_altmap *altmap) {unsigned long pfn, end_pfn = start_pfn + size;
@@ -5984,7 +5984,7 @@ void __meminit memmap_init_zone(unsigned* There can be holes in boot-time mem_map[]s handed to this * function. They do not exist on hotplugged memory. */ -if (context ==MEMMAP_EARLY ) { +if (context ==MEMINIT_EARLY ) {if (overlap_memmap_init (zone, &pfn))continue ;if (defer_init (nid, pfn, end_pfn))
@@ -5993,7 +5993,7 @@ void __meminit memmap_init_zone(unsigned page =pfn_to_page (pfn);__init_single_page (page, pfn, zone, nid); -if (context ==MEMMAP_HOTPLUG ) +if (context ==MEMINIT_HOTPLUG )__SetPageReserved (page);/*
@@ -6076,7 +6076,7 @@ void __ref memmap_init_zone_device(struc* check here not to call set_pageblock_migratetype() against * pfn out of zone. * -* Please note that MEMMAP_HOTPLUG path doesn't clear memmap +* Please note that MEMINIT_HOTPLUG path doesn't clear memmap * because this is done early in section_activate() */ if (!(pfn & (pageblock_nr_pages -1 ))) {
@@ -6114,7 +6114,7 @@ void __meminit __weak memmap_init(unsignif (end_pfn > start_pfn) { size = end_pfn - start_pfn;memmap_init_zone (size, nid, zone, start_pfn, -MEMMAP_EARLY ,NULL ); +MEMINIT_EARLY ,NULL ); } } }
Greg Kroah-Hartman
maintainerPATCH 94/99 mm: dont rely on system state to detect hot-plug operations
In reply to Greg Kroah-HartmanFrom: Laurent Dufour <[email protected]>
commit f85086f95fa36194eb0db5cd5c12e56801b98523 upstream.
In register_mem_sect_under_node() the system_state's value is checked to detect whether the call is made during boot time or during an hot-plug operation. Unfortunately, that check against SYSTEM_BOOTING is wrong because regular memory is registered at SYSTEM_SCHEDULING state. In addition, memory hot-plug operation can be triggered at this system state by the ACPI [1]. So checking against the system state is not enough.
The consequence is that on system with interleaved node's ranges like this:
Early memory node ranges
node 1: [mem 0x0000000000000000-0x000000011fffffff] node 2: [mem 0x0000000120000000-0x000000014fffffff] node 1: [mem 0x0000000150000000-0x00000001ffffffff] node 0: [mem 0x0000000200000000-0x000000048fffffff] node 2: [mem 0x0000000490000000-0x00000007ffffffff]
This can be seen on PowerPC LPAR after multiple memory hot-plug and hot-unplug operations are done. At the next reboot the node's memory ranges can be interleaved and since the call to link_mem_sections() is made in topology_init() while the system is in the SYSTEM_SCHEDULING state, the node's id is not checked, and the sections registered to multiple nodes:
$ ls -l /sys/devices/system/memory/memory21/node* total 0 lrwxrwxrwx 1 root root 0 Aug 24 05:27 node1 -> ../../node/node1 lrwxrwxrwx 1 root root 0 Aug 24 05:27 node2 -> ../../node/node2
In that case, the system is able to boot but if later one of theses memory blocks is hot-unplugged and then hot-plugged, the sysfs inconsistency is detected and this is triggering a BUG_ON():
kernel BUG at /Users/laurent/src/linux-ppc/mm/memory_hotplug.c:1084!
Oops: Exception in kernel mode, sig: 5 [#1]
LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries
Modules linked in: rpadlpar_io rpaphp pseries_rng rng_core vmx_crypto gf128mul binfmt_misc ip_tables x_tables xfs libcrc32c crc32c_vpmsum autofs4
CPU: 8 PID: 10256 Comm: drmgr Not tainted 5.9.0-rc1+ #25
Call Trace:
add_memory_resource+0x23c/0x340 (unreliable)
__add_memory+0x5c/0xf0
dlpar_add_lmb+0x1b4/0x500
dlpar_memory+0x1f8/0xb80
handle_dlpar_errorlog+0xc0/0x190
dlpar_store+0x198/0x4a0
kobj_attr_store+0x30/0x50
sysfs_kf_write+0x64/0x90
kernfs_fop_write+0x1b0/0x290
vfs_write+0xe8/0x290
ksys_write+0xdc/0x130
system_call_exception+0x160/0x270
system_call_common+0xf0/0x27cThis patch addresses the root cause by not relying on the system_state value to detect whether the call is due to a hot-plug operation. An extra parameter is added to link_mem_sections() detailing whether the operation is due to a hot-plug operation.
[1] According to Oscar Salvador, using this qemu command line, ACPI memory hotplug operations are raised at SYSTEM_SCHEDULING state:
$QEMU -enable-kvm -machine pc -smp 4,sockets=4,cores=1,threads=1 -cpu host -monitor pty \
-m size=$MEM,slots=255,maxmem=4294967296k \
-numa node,nodeid=0,cpus=0-3,mem=512 -numa node,nodeid=1,mem=512 \
-object memory-backend-ram,id=memdimm0,size=134217728 -device pc-dimm,node=0,memdev=memdimm0,id=dimm0,slot=0 \
-object memory-backend-ram,id=memdimm1,size=134217728 -device pc-dimm,node=0,memdev=memdimm1,id=dimm1,slot=1 \
-object memory-backend-ram,id=memdimm2,size=134217728 -device pc-dimm,node=0,memdev=memdimm2,id=dimm2,slot=2 \
-object memory-backend-ram,id=memdimm3,size=134217728 -device pc-dimm,node=0,memdev=memdimm3,id=dimm3,slot=3 \
-object memory-backend-ram,id=memdimm4,size=134217728 -device pc-dimm,node=1,memdev=memdimm4,id=dimm4,slot=4 \
-object memory-backend-ram,id=memdimm5,size=134217728 -device pc-dimm,node=1,memdev=memdimm5,id=dimm5,slot=5 \
-object memory-backend-ram,id=memdimm6,size=134217728 -device pc-dimm,node=1,memdev=memdimm6,id=dimm6,slot=6 \--- drivers/base/node.c | 85 +++++++++++++++++++++++++++++++++------------------ include/linux/node.h | 11 ++++-- mm/memory_hotplug.c | 3 + 3 files changed, 64 insertions(+), 35 deletions(-)
drivers/base/node.c +55 -30
@@ -761,14 +761,36 @@ static int __ref get_nid_for_pfn(unsignereturn pfn_to_nid (pfn); } +static int do_register_memory_block_under_node (int nid, +struct memory_block *mem_blk) +{ +int ret; + +/* +* If this memory block spans multiple nodes, we only indicate +* the last processed node. +*/ + mem_blk->nid = nid; + + ret =sysfs_create_link_nowarn (&node_devices[nid]->dev.kobj, + &mem_blk->dev.kobj, +kobject_name (&mem_blk->dev.kobj)); +if (ret) +return ret; + +return sysfs_create_link_nowarn (&mem_blk->dev.kobj, + &node_devices[nid]->dev.kobj, +kobject_name (&node_devices[nid]->dev.kobj)); +} +/* register memory section under specified node if it spans that node */ -static int register_mem_sect_under_node (struct memory_block *mem_blk, -void *arg) +static int register_mem_block_under_node_early (struct memory_block *mem_blk, +void *arg) {unsigned long memory_block_pfns =memory_block_size_bytes () /PAGE_SIZE ;unsigned long start_pfn =section_nr_to_pfn (mem_blk->start_section_nr);unsigned long end_pfn = start_pfn + memory_block_pfns -1 ; -int ret, nid = *(int *)arg; +int nid = *(int *)arg;unsigned long pfn;for (pfn = start_pfn; pfn <= end_pfn; pfn++) {
@@ -785,39 +807,34 @@ static int register_mem_sect_under_node( }/* -* We need to check if page belongs to nid only for the boot -* case, during hotplug we know that all pages in the memory -* block belong to the same node. -*/ -if (system_state ==SYSTEM_BOOTING ) { - page_nid =get_nid_for_pfn (pfn); -if (page_nid <0 ) -continue ; -if (page_nid != nid) -continue ; - } - -/* -* If this memory block spans multiple nodes, we only indicate -* the last processed node. +* We need to check if page belongs to nid only at the boot +* case because node's ranges can be interleaved. */ - mem_blk->nid = nid; - - ret =sysfs_create_link_nowarn (&node_devices[nid]->dev.kobj, - &mem_blk->dev.kobj, -kobject_name (&mem_blk->dev.kobj)); -if (ret) -return ret; + page_nid =get_nid_for_pfn (pfn); +if (page_nid <0 ) +continue ; +if (page_nid != nid) +continue ; -return sysfs_create_link_nowarn (&mem_blk->dev.kobj, - &node_devices[nid]->dev.kobj, -kobject_name (&node_devices[nid]->dev.kobj)); +return do_register_memory_block_under_node (nid, mem_blk); }/* mem section does not span the specified node */ return 0 ; }/* +* During hotplug we know that all pages in the memory block belong to the same +* node. +*/ +static int register_mem_block_under_node_hotplug (struct memory_block *mem_blk, +void *arg) +{ +int nid = *(int *)arg; + +return do_register_memory_block_under_node (nid, mem_blk); +} + +/* * Unregister a memory block device under the node it spans. Memory blocks * with multiple nodes cannot be offlined and therefore also never be removed. */
@@ -832,11 +849,19 @@ void unregister_memory_block_under_nodes kobject_name(&node_devices[mem_blk->nid]->dev.kobj)); } -int link_mem_sections (int nid,unsigned long start_pfn,unsigned long end_pfn) +int link_mem_sections (int nid,unsigned long start_pfn,unsigned long end_pfn, +enum meminit_context context) { +walk_memory_blocks_func_t func; + +if (context ==MEMINIT_HOTPLUG ) + func = register_mem_block_under_node_hotplug; +else + func = register_mem_block_under_node_early; +return walk_memory_blocks (PFN_PHYS (start_pfn),PFN_PHYS (end_pfn - start_pfn), (void *)&nid, - register_mem_sect_under_node); + func); }#ifdef CONFIG_HUGETLBFS
include/linux/node.h +7 -4
@@ -99,11 +99,13 @@ extern struct node *node_devices[];typedef void (*node_registration_func_t )(struct node *);#if defined(CONFIG_MEMORY_HOTPLUG_SPARSE ) && defined(CONFIG_NUMA ) -extern int link_mem_sections (int nid,unsigned long start_pfn, -unsigned long end_pfn); +int link_mem_sections (int nid,unsigned long start_pfn, +unsigned long end_pfn, +enum meminit_context context);#else static inline int link_mem_sections (int nid,unsigned long start_pfn, -unsigned long end_pfn) +unsigned long end_pfn, +enum meminit_context context) {return 0 ; }
@@ -128,7 +130,8 @@ static inline int register_one_node(intif (error)return error;/* link memory sections under this node */ - error =link_mem_sections (nid, start_pfn, end_pfn); + error =link_mem_sections (nid, start_pfn, end_pfn, +MEMINIT_EARLY ); }return error;
mm/memory_hotplug.c +2 -1
@@ -1065,7 +1065,8 @@ int __ref add_memory_resource(int nid, s }/* link memory sections under this node.*/ - ret =link_mem_sections (nid,PFN_DOWN (start),PFN_UP (start + size -1 )); + ret =link_mem_sections (nid,PFN_DOWN (start),PFN_UP (start + size -1 ), +MEMINIT_HOTPLUG );BUG_ON (ret);/* create new memmap entry */
Greg Kroah-Hartman
maintainerPATCH 95/99 s390/zcrypt: Fix ZCRYPT_PERDEV_REQCNT ioctl
In reply to Greg Kroah-HartmanFrom: Christian Borntraeger <[email protected]>
commit f7e80983f0cf470bb82036e73bff4d5a7daf8fc2 upstream.
reqcnt is an u32 pointer but we do copy sizeof(reqcnt) which is the size of the pointer. This means we only copy 8 byte. Let us copy the full monty.
--- drivers/s390/crypto/zcrypt_api.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/s390/crypto/zcrypt_api.c +2 -1
@@ -1429,7 +1429,8 @@ static long zcrypt_unlocked_ioctl(structif (!reqcnt)return -ENOMEM ;zcrypt_perdev_reqcnt (reqcnt,AP_DEVICES ); -if (copy_to_user ((int __user *) arg, reqcnt,sizeof (reqcnt))) +if (copy_to_user ((int __user *) arg, reqcnt, +sizeof (u32) *AP_DEVICES )) rc = -EFAULT ;kfree (reqcnt);return rc;
Greg Kroah-Hartman
maintainerPATCH 96/99 io_uring: ensure open/openat2 name is cleaned on cancelation
In reply to Greg Kroah-HartmanFrom: Jens Axboe <[email protected]>
commit f3cd4850504ff612d0ea77a0aaf29b66c98fcefe upstream.
If we cancel these requests, we'll leak the memory associated with the filename. Add them to the table of ops that need cleaning, if REQ_F_NEED_CLEANUP is set.
--- fs/io_uring.c | 2 ++ 1 file changed, 2 insertions(+)
fs/io_uring.c +2 -0
@@ -5254,6 +5254,8 @@ static void io_cleanup_req(struct io_kiobreak ;case IORING_OP_OPENAT :case IORING_OP_OPENAT2 : +if (req->open.filename) +putname (req->open.filename);break ;case IORING_OP_SPLICE :case IORING_OP_TEE :
Greg Kroah-Hartman
maintainerPATCH 97/99 KVM: arm64: Assume write fault on S1PTW permission fault on instruction fetch
In reply to Greg Kroah-HartmanFrom: Marc Zyngier <[email protected]>
commit c4ad98e4b72cb5be30ea282fce935248f2300e62 upstream.
KVM currently assumes that an instruction abort can never be a write. This is in general true, except when the abort is triggered by a S1PTW on instruction fetch that tries to update the S1 page tables (to set AF, for example).
This can happen if the page tables have been paged out and brought back in without seeing a direct write to them (they are thus marked read only), and the fault handling code will make the PT executable(!) instead of writable. The guest gets stuck forever.
In these conditions, the permission fault must be considered as a write so that the Stage-1 update can take place. This is essentially the I-side equivalent of the problem fixed by 60e21a0ef54c ("arm64: KVM:
Take S1 walks into account when determining S2 write faults").
Update kvm_is_write_fault() to return true on IABT+S1PTW, and introduce kvm_vcpu_trap_is_exec_fault() that only return true when no faulting on a S1 fault. Additionally, kvm_vcpu_dabt_iss1tw() is renamed to kvm_vcpu_abt_iss1tw(), as the above makes it plain that it isn't specific to data abort.
--- arch/arm64/include/asm/kvm_emulate.h | 12 ++++++++++-- arch/arm64/kvm/hyp/switch.c | 2 +- arch/arm64/kvm/mmio.c | 2 +- arch/arm64/kvm/mmu.c | 2 +- 4 files changed, 13 insertions(+), 5 deletions(-)
arch/arm64/include/asm/kvm_emulate.h +10 -2
@@ -319,7 +319,7 @@ static __always_inline int kvm_vcpu_dabtreturn (kvm_vcpu_get_hsr (vcpu) & ESR_ELx_SRT_MASK) >> ESR_ELx_SRT_SHIFT; } -static __always_inline bool kvm_vcpu_dabt_iss1tw(const struct kvm_vcpu *vcpu) +static __always_inline bool kvm_vcpu_abt_iss1tw(const struct kvm_vcpu *vcpu) {return !!(kvm_vcpu_get_hsr (vcpu) & ESR_ELx_S1PTW); }
@@ -327,7 +327,7 @@ static __always_inline bool kvm_vcpu_dab static __always_inline bool kvm_vcpu_dabt_iswrite(const struct kvm_vcpu *vcpu) {return !!(kvm_vcpu_get_hsr (vcpu) & ESR_ELx_WNR) || -kvm_vcpu_dabt_iss1tw (vcpu);/* AF/DBM update */ +kvm_vcpu_abt_iss1tw (vcpu);/* AF/DBM update */ }static inline bool kvm_vcpu_dabt_is_cm (const struct kvm_vcpu *vcpu)
@@ -356,6 +356,11 @@ static inline bool kvm_vcpu_trap_is_iabtreturn kvm_vcpu_trap_get_class (vcpu) == ESR_ELx_EC_IABT_LOW; } +static inline bool kvm_vcpu_trap_is_exec_fault (const struct kvm_vcpu *vcpu) +{ +return kvm_vcpu_trap_is_iabt (vcpu) && !kvm_vcpu_abt_iss1tw (vcpu); +} + static __always_inline u8 kvm_vcpu_trap_get_fault(const struct kvm_vcpu *vcpu) {return kvm_vcpu_get_hsr (vcpu) & ESR_ELx_FSC;
@@ -393,6 +398,9 @@ static __always_inline int kvm_vcpu_sys_static inline bool kvm_is_write_fault (struct kvm_vcpu *vcpu) { +if (kvm_vcpu_abt_iss1tw (vcpu)) +return true; +if (kvm_vcpu_trap_is_iabt (vcpu))return false;
arch/arm64/kvm/hyp/switch.c +1 -1
@@ -599,7 +599,7 @@ static bool __hyp_text fixup_guest_exit(kvm_vcpu_trap_get_fault_type (vcpu) ==FSC_FAULT &&kvm_vcpu_dabt_isvalid (vcpu) && !kvm_vcpu_dabt_isextabt (vcpu) && - !kvm_vcpu_dabt_iss1tw (vcpu); + !kvm_vcpu_abt_iss1tw (vcpu);if (valid) {int ret =__vgic_v2_perform_cpuif_access (vcpu);
arch/arm64/kvm/mmio.c +1 -1
@@ -146,7 +146,7 @@ int io_mem_abort(struct kvm_vcpu *vcpu, }/* Page table accesses IO mem: tell guest to fix its TTBR */ -if (kvm_vcpu_dabt_iss1tw (vcpu)) { +if (kvm_vcpu_abt_iss1tw (vcpu)) {kvm_inject_dabt (vcpu,kvm_vcpu_get_hfar (vcpu));return 1 ; }
arch/arm64/kvm/mmu.c +1 -1
@@ -1845,7 +1845,7 @@ static int user_mem_abort(struct kvm_vcpunsigned long vma_pagesize, flags =0 ; write_fault =kvm_is_write_fault (vcpu); - exec_fault =kvm_vcpu_trap_is_iabt (vcpu); + exec_fault =kvm_vcpu_trap_is_exec_fault (vcpu);VM_BUG_ON (write_fault && exec_fault);if (fault_status ==FSC_PERM && !write_fault && !exec_fault) {
Greg Kroah-Hartman
maintainerPATCH 98/99 dm: fix bio splitting and its bio completion order for regular IO
In reply to Greg Kroah-HartmanFrom: Mike Snitzer <[email protected]>
commit ee1dfad5325ff1cfb2239e564cd411b3bfe8667a upstream.
dm_queue_split() is removed because __split_and_process_bio() _must_ handle splitting bios to ensure proper bio submission and completion ordering as a bio is split.
Otherwise, multiple recursive calls to ->submit_bio will cause multiple split bios to be allocated from the same ->bio_split mempool at the same time. This would result in deadlock in low memory conditions because no progress could be made (only one bio is available in ->bio_split mempool).
This fix has been verified to still fix the loss of performance, due to excess splitting, that commit 120c9257f5f1 provided.
--- drivers/md/dm.c | 23 ++--------------------- 1 file changed, 2 insertions(+), 21 deletions(-)
drivers/md/dm.c +2 -21
@@ -1728,23 +1728,6 @@ out:return ret; } -static void dm_queue_split (struct mapped_device *md,struct dm_target *ti,struct bio **bio) -{ -unsigned len, sector_count; - - sector_count =bio_sectors (*bio); - len =min_t (sector_t,max_io_len ((*bio)->bi_iter.bi_sector, ti), sector_count); - -if (sector_count > len) { -struct bio *split =bio_split (*bio, len,GFP_NOIO , &md->queue->bio_split); - -bio_chain (split, *bio); -trace_block_split (md->queue, split, (*bio)->bi_iter.bi_sector); -generic_make_request (*bio); - *bio = split; - } -} -static blk_qc_t dm_process_bio (struct mapped_device *md,struct dm_table *map,struct bio *bio) {
@@ -1772,14 +1755,12 @@ static blk_qc_t dm_process_bio(struct maif (current->bio_list) {if (is_abnormal_io (bio))blk_queue_split (md->queue, &bio); -else -dm_queue_split (md, ti, &bio); +/* regular IO is split by __split_and_process_bio */ }if (dm_get_md_type (md) ==DM_TYPE_NVME_BIO_BASED )return __process_bio (md, map, bio, ti); -else -return __split_and_process_bio (md, map, bio); +return __split_and_process_bio (md, map, bio); }static blk_qc_t dm_make_request (struct request_queue *q,struct bio *bio)
Greg Kroah-Hartman
maintainerPATCH 99/99 clocksource/drivers/timer-ti-dm: Do reset before enable
In reply to Greg Kroah-HartmanFrom: Tony Lindgren <[email protected]>
commit 164805157f3c6834670afbaff563353c773131f1 upstream.
Commit 6cfcd5563b4f ("clocksource/drivers/timer-ti-dm: Fix suspend and resume for am3 and am4") exposed a new issue for type2 dual mode timers on at least omap5 where the clockevent will stop when the SoC starts entering idle states during the boot.
Turns out we are wrongly first enabling the system timer and then resetting it, while we must also re-enable it after reset. The current sequence leaves the timer module in a partially initialized state. This issue went unnoticed earlier with ti-sysc driver reconfiguring the timer module until we fixed the issue of ti-sysc reconfiguring system timers.
Let's fix the issue by calling dmtimer_systimer_enable() from reset for both type1 and type2 timers, and switch the order of reset and enable in dmtimer_systimer_setup(). Let's also move dmtimer_systimer_enable() and dmtimer_systimer_disable() to do this without adding forward declarations.
--- drivers/clocksource/timer-ti-dm-systimer.c | 44 +++++++++++++++-------------- 1 file changed, 23 insertions(+), 21 deletions(-)
drivers/clocksource/timer-ti-dm-systimer.c +23 -21
@@ -69,12 +69,33 @@ static bool dmtimer_systimer_revision1(sreturn !(tidr >>16 ); } +static void dmtimer_systimer_enable (struct dmtimer_systimer *t) +{ +u32 val; + +if (dmtimer_systimer_revision1 (t)) + val =DMTIMER_TYPE1_ENABLE ; +else + val =DMTIMER_TYPE2_ENABLE ; + +writel_relaxed (val, t->base + t->sysc); +} + +static void dmtimer_systimer_disable (struct dmtimer_systimer *t) +{ +if (!dmtimer_systimer_revision1 (t)) +return ; + +writel_relaxed (DMTIMER_TYPE1_DISABLE , t->base + t->sysc); +} +static int __init dmtimer_systimer_type1_reset (struct dmtimer_systimer *t) {void __iomem *syss = t->base +OMAP_TIMER_V1_SYS_STAT_OFFSET ;int ret;u32 l; +dmtimer_systimer_enable (t);writel_relaxed (BIT (1 ) |BIT (2 ), t->base + t->ifctrl); ret =readl_poll_timeout_atomic (syss, l, l &BIT (0 ),100 ,DMTIMER_RESET_WAIT );
@@ -88,6 +109,7 @@ static int __init dmtimer_systimer_type2void __iomem *sysc = t->base + t->sysc;u32 l; +dmtimer_systimer_enable (t); l =readl_relaxed (sysc); l |=BIT (0 );writel_relaxed (l, sysc);
@@ -336,26 +358,6 @@ static int __init dmtimer_systimer_init_return 0 ; } -static void dmtimer_systimer_enable (struct dmtimer_systimer *t) -{ -u32 val; - -if (dmtimer_systimer_revision1 (t)) - val =DMTIMER_TYPE1_ENABLE ; -else - val =DMTIMER_TYPE2_ENABLE ; - -writel_relaxed (val, t->base + t->sysc); -} - -static void dmtimer_systimer_disable (struct dmtimer_systimer *t) -{ -if (!dmtimer_systimer_revision1 (t)) -return ; - -writel_relaxed (DMTIMER_TYPE1_DISABLE , t->base + t->sysc); -} -static int __init dmtimer_systimer_setup (struct device_node *np,struct dmtimer_systimer *t) {
@@ -409,8 +411,8 @@ static int __init dmtimer_systimer_setup t->wakeup = regbase + _OMAP_TIMER_WAKEUP_EN_OFFSET; t->ifctrl = regbase + _OMAP_TIMER_IF_CTRL_OFFSET; -dmtimer_systimer_enable (t);dmtimer_systimer_reset (t); +dmtimer_systimer_enable (t);pr_debug ("dmtimer rev %08x sysc %08x\n" ,readl_relaxed (t->base),readl_relaxed (t->base + t->sysc));
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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.
Compiled and booted 5.8.13-rc1+ .
"dmesg -l err" did not report any error or errors.
Signature · 2 lines
software engineer rajagiri school of engineering and technology
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.8.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.8:
14 builds: 14 pass, 0 fail
26 boots: 26 pass, 0 fail
60 tests: 60 pass, 0 failLinux version: 5.8.13-rc1-g2bea8b771966
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04Jon
Greg Kroah-Hartman
maintainerQuoted 26 lines · Jon Hunter
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.8.y
and the diffstat can be found below.thanks,
greg k-h
All tests passing for Tegra ...
Test results for stable-v5.8:
14 builds: 14 pass, 0 fail 26 boots: 26 pass, 0 fail 60 tests: 60 pass, 0 fail
Quoted 7 lines
Linux version: 5.8.13-rc1-g2bea8b771966
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,tegra194-p2972-0000, tegra20-ventana, tegra210-p2371-2180, tegra210-p3450-0000, tegra30-cardhu-a04Tested-by Jon Hunter <[email protected]>
Thanks for testing all of these and letting me know.
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. Anything received after that time might be too late.
Build results:
total: 154 pass: 153 fail: 1 Failed builds: powerpc:allmodconfig Qemu test results: total: 430 pass: 430 fail: 0
powerpc link problem as usual. The fix has still not landed in mainline.
Guenter
Greg Kroah-Hartman
maintainerQuoted 17 lines · Guenter Roeck
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. Anything received after that time might be too late.
Build results:
total: 154 pass: 153 fail: 1 Failed builds: powerpc:allmodconfig Qemu test results: total: 430 pass: 430 fail: 0
Quoted 3 lines
powerpc link problem as usual. The fix has still not landed in mainline.
Tested-by Guenter Roeck <[email protected]>
Thanks for testing all of these and letting me know.
greg k-h
Quoted 10 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.8.y
and the diffstat can be found below.thanks,
greg k-h
[Sorry earlier email was in Non-plain text so re-sending]
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Summary
------------------------------------------------------------------------
kernel: 5.8.13-rc1
git repo: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
git branch: linux-5.8.y
git commit: 2bea8b771966a8b5b009c261dfb9c97df1c62af4
git describe: v5.8.12-100-g2bea8b771966
Test details: https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-5.8.y/build/v5.8.12-100-g2bea8b771966
No regressions (compared to build v5.8.12)
No fixes (compared to build v5.8.12)
Ran 38153 total tests in the following environments and test suites.
Environments
--------------
- dragonboard-410c
- hi6220-hikey
- i386
- juno-r2
- juno-r2-compat
- juno-r2-kasan
- nxp-ls2088
- qemu_arm
- qemu_arm64
- qemu_i386
- qemu_x86_64
- x15
- x86
- x86-kasan
Test Suites
-----------
* build
* install-android-platform-tools-r2600
* kselftest
* libhugetlbfs
* linux-log-parser
* ltp-containers-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-mm-tests
* ltp-nptl-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* perf
* ltp-commands-tests
* ltp-controllers-tests
* ltp-math-tests
* network-basic-tests
* v4l2-compliance
* ltp-cap_bounds-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-open-posix-tests
* kselftest-vsyscall-mode-native
* kselftest-vsyscall-mode-none
* ssuite
Signature · 2 lines
Linaro LKFT https://lkft.linaro.org
Greg Kroah-Hartman
maintainerQuoted 19 lines · Naresh Kamboju
Quoted 17 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.8.y
and the diffstat can be found below.thanks,
Quoted 8 lines
Quoted 1 line
greg k-h
[Sorry earlier email was in Non-plain text so re-sending]
Results from Linaro’s test farm.
No regressions on arm64, arm,x86_64, and i386.
Thanks for testing them all and letting me know.
greg k-
Quoted 9 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.8.y
and the diffstat can be found below.thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
thanks,
-- Shuah
Greg Kroah-Hartman
maintainerQuoted 15 lines · Shuah Khan
Quoted 14 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 5.8.13 release. There are 99 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 Thu, 01 Oct 2020 10:59:03 +0000. 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/v5.x/stable-review/patch-5.8.13-rc1.gzor in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.gitlinux-5.8.y
and the diffstat can be found below.
Quoted 8 lines
Quoted 4 lines
thanks,
greg k-h
Compiled and booted on my test system. No dmesg regressions.
Tested-by Shuah Khan <[email protected]>
Thanks for testing them all and letting me know.
greg k-h