From 47e4cce2e747496d8aac71b3fd91d42241db4fa1 Mon Sep 17 00:00:00 2001 From: Sasha Levin Date: Mon, 6 Jun 2022 06:34:11 -0400 Subject: [PATCH] Fixes for 4.9 Signed-off-by: Sasha Levin --- ...-cache-flush-inside-virtual-machines.patch | 71 ++++++++ ...sa-jack-access-input_dev-under-mutex.patch | 157 +++++++++++++++++ ...dd-atmel-24c128-fallback-to-samsung-.patch | 45 +++++ ...sing-of_node_put-after-of_find_compa.patch | 52 ++++++ ...ck-fix-uart-rate-reporting-algorithm.patch | 37 ++++ ...dd-missing-of_node_put-in-dcscb_init.patch | 37 ++++ ...fold-register-value-changes-into-not.patch | 51 ++++++ ...x-error-handling-in-mt8173_max98090_.patch | 49 ++++++ ...-fix-refcount-leak-in-mxs_saif_probe.patch | 36 ++++ ...-rt5645-fix-errorenous-cleanup-order.patch | 50 ++++++ ...missing-clk_disable_unprepare-on-err.patch | 55 ++++++ .../ath9k-fix-qca9561-pa-bias-level.patch | 54 ++++++ ...tential-out-of-bounds-access-with-in.patch | 51 ++++++ ...g-negative-value-to-unsigned-variabl.patch | 37 ++++ ...signing-negative-value-to-unsigned-v.patch | 37 ++++ ...ngling-sco_conn-and-use-after-free-i.patch | 88 ++++++++++ ...-allocation-mode-from-gfp_nowait-to-.patch | 41 +++++ ...ode.c-fix-compaction-sysfs-file-leak.patch | 44 +++++ ...-double-free-in-si_parse_power_table.patch | 70 ++++++++ .../drm-amd-pm-fix-the-compile-warning.patch | 51 ++++++ ...-edid-struct-for-old-arm-oabi-format.patch | 114 +++++++++++++ queue-4.9/drm-mediatek-fix-mtk_cec_mask.patch | 45 +++++ ...error-checks-and-return-values-for-d.patch | 85 +++++++++ ...ck-return-value-after-calling-platfo.patch | 42 +++++ ...n-error-pointer-in-msm_gem_prime_get.patch | 40 +++++ ...-fix-possible-null-ptr-deref-in-vop_.patch | 41 +++++ ...ull-pointer-dereference-in-virtio_gp.patch | 88 ++++++++++ ...ence-the-gcc-12-array-bounds-warning.patch | 47 +++++ .../fat-add-ratelimit-to-fat-_ent_bread.patch | 50 ++++++ ...ble-null-pointer-dereference-in-dbfr.patch | 59 +++++++ ...-maximum-brightness-for-dream-cheeky.patch | 38 +++++ ...ow-inotify-mask-flags-in-proc-fdinfo.patch | 86 ++++++++++ ...-fix-refcount-leak-in-bbc_beep_probe.patch | 38 +++++ ...se-timeout-waiting-for-ga-log-enable.patch | 54 ++++++ ...for-null-msg-when-handling-events-an.patch | 75 ++++++++ ...rs-packets-to-the-interface-of-arphr.patch | 50 ++++++ ...ntial-null-dereference-in-libipw_xmi.patch | 36 ++++ ...x-dependencies-of-math-emulation-sup.patch | 56 ++++++ ...u-fix-build-failure-when-config_inpu.patch | 82 +++++++++ ...x-the-warning-when-removing-the-modu.patch | 57 +++++++ ...-change-clk_disable-to-clk_disable_u.patch | 39 +++++ ...media-exynos4-is-fix-compile-warning.patch | 39 +++++ ...x-array-index-out-of-bounds-in-pvr2_.patch | 58 +++++++ ...ix-missing-check-to-determine-if-ele.patch | 87 ++++++++++ ...ix-error-check-return-value-of-platf.patch | 39 +++++ ...x-lock-for-call-in-mwifiex_dfs_chan_.patch | 49 ++++++ ...emove-two-bug-from-skb_checksum_help.patch | 49 ++++++ ...ll-out-the-dev-rfkill-to-prevent-uaf.patch | 150 ++++++++++++++++ ...ull-pointer-dereference-in-nvme_allo.patch | 45 +++++ ...enrisc-start-cpu-timer-early-in-boot.patch | 62 +++++++ ...v_lock-ab-ba-deadlock-with-sriov_num.patch | 90 ++++++++++ ...-fix-return-value-of-__setup-handler.patch | 44 +++++ ...pc-8xx-export-cpm_setbrg-for-modules.patch | 40 +++++ ...-fix-return-value-of-__setup-handler.patch | 45 +++++ ...s-fix-refcount-leak-in-icp_opal_init.patch | 36 ++++ ...00-fix-refcount-leak-in-pfuze_parse_.patch | 44 +++++ ...to-resend-the-request-if-we-re-recei.patch | 45 +++++ ...-setting-the-bar-too-high-for-the-pr.patch | 74 ++++++++ ...n-an-error-to-sendmsg-if-call-failed.patch | 84 +++++++++ ...tringop-overflow-warnings-in-fcoe_ww.patch | 130 ++++++++++++++ ...x-error-check-return-value-of-regist.patch | 38 +++++ ...-sk-sk_bound_dev_if-once-in-sctp_rcv.patch | 49 ++++++ queue-4.9/series | 71 ++++++++ ...ix-missing-of_node_put-in-smp2p_pars.patch | 36 ++++ ...x-missing-of_node_put-in-smsm_parse_.patch | 36 ++++ ...x-pm_runtime_get_sync-error-checking.patch | 38 +++++ ...fix-return-value-handling-of-wait_fo.patch | 51 ++++++ ...-caused-by-calling-printk-under-tty_.patch | 143 ++++++++++++++++ ...fb-fix-refcount-leak-in-clcdfb_of_vr.patch | 45 +++++ ...e-wrong-asm-constraint-in-delay_loop.patch | 51 ++++++ ...he-control_va_addr_alignment-__setup.patch | 59 +++++++ ...-positive-kmemleak-report-in-msr_bui.patch | 161 ++++++++++++++++++ 72 files changed, 4323 insertions(+) create mode 100644 queue-4.9/acpica-avoid-cache-flush-inside-virtual-machines.patch create mode 100644 queue-4.9/alsa-jack-access-input_dev-under-mutex.patch create mode 100644 queue-4.9/arm-dts-exynos-add-atmel-24c128-fallback-to-samsung-.patch create mode 100644 queue-4.9/arm-hisi-add-missing-of_node_put-after-of_find_compa.patch create mode 100644 queue-4.9/arm-omap1-clock-fix-uart-rate-reporting-algorithm.patch create mode 100644 queue-4.9/arm-versatile-add-missing-of_node_put-in-dcscb_init.patch create mode 100644 queue-4.9/asoc-dapm-don-t-fold-register-value-changes-into-not.patch create mode 100644 queue-4.9/asoc-mediatek-fix-error-handling-in-mt8173_max98090_.patch create mode 100644 queue-4.9/asoc-mxs-saif-fix-refcount-leak-in-mxs_saif_probe.patch create mode 100644 queue-4.9/asoc-rt5645-fix-errorenous-cleanup-order.patch create mode 100644 queue-4.9/asoc-wm2000-fix-missing-clk_disable_unprepare-on-err.patch create mode 100644 queue-4.9/ath9k-fix-qca9561-pa-bias-level.patch create mode 100644 queue-4.9/ath9k_htc-fix-potential-out-of-bounds-access-with-in.patch create mode 100644 queue-4.9/b43-fix-assigning-negative-value-to-unsigned-variabl.patch create mode 100644 queue-4.9/b43legacy-fix-assigning-negative-value-to-unsigned-v.patch create mode 100644 queue-4.9/bluetooth-fix-dangling-sco_conn-and-use-after-free-i.patch create mode 100644 queue-4.9/dma-debug-change-allocation-mode-from-gfp_nowait-to-.patch create mode 100644 queue-4.9/drivers-base-node.c-fix-compaction-sysfs-file-leak.patch create mode 100644 queue-4.9/drm-amd-pm-fix-double-free-in-si_parse_power_table.patch create mode 100644 queue-4.9/drm-amd-pm-fix-the-compile-warning.patch create mode 100644 queue-4.9/drm-fix-edid-struct-for-old-arm-oabi-format.patch create mode 100644 queue-4.9/drm-mediatek-fix-mtk_cec_mask.patch create mode 100644 queue-4.9/drm-msm-dsi-fix-error-checks-and-return-values-for-d.patch create mode 100644 queue-4.9/drm-msm-hdmi-check-return-value-after-calling-platfo.patch create mode 100644 queue-4.9/drm-msm-return-an-error-pointer-in-msm_gem_prime_get.patch create mode 100644 queue-4.9/drm-rockchip-vop-fix-possible-null-ptr-deref-in-vop_.patch create mode 100644 queue-4.9/drm-virtio-fix-null-pointer-dereference-in-virtio_gp.patch create mode 100644 queue-4.9/eth-tg3-silence-the-gcc-12-array-bounds-warning.patch create mode 100644 queue-4.9/fat-add-ratelimit-to-fat-_ent_bread.patch create mode 100644 queue-4.9/fs-jfs-fix-possible-null-pointer-dereference-in-dbfr.patch create mode 100644 queue-4.9/hid-hid-led-fix-maximum-brightness-for-dream-cheeky.patch create mode 100644 queue-4.9/inotify-show-inotify-mask-flags-in-proc-fdinfo.patch create mode 100644 queue-4.9/input-sparcspkr-fix-refcount-leak-in-bbc_beep_probe.patch create mode 100644 queue-4.9/iommu-amd-increase-timeout-waiting-for-ga-log-enable.patch create mode 100644 queue-4.9/ipmi-ssif-check-for-null-msg-when-handling-events-an.patch create mode 100644 queue-4.9/ipv6-don-t-send-rs-packets-to-the-interface-of-arphr.patch create mode 100644 queue-4.9/ipw2x00-fix-potential-null-dereference-in-libipw_xmi.patch create mode 100644 queue-4.9/m68k-math-emu-fix-dependencies-of-math-emulation-sup.patch create mode 100644 queue-4.9/macintosh-via-pmu-fix-build-failure-when-config_inpu.patch create mode 100644 queue-4.9/media-cx25821-fix-the-warning-when-removing-the-modu.patch create mode 100644 queue-4.9/media-exynos4-is-change-clk_disable-to-clk_disable_u.patch create mode 100644 queue-4.9/media-exynos4-is-fix-compile-warning.patch create mode 100644 queue-4.9/media-pvrusb2-fix-array-index-out-of-bounds-in-pvr2_.patch create mode 100644 queue-4.9/media-uvcvideo-fix-missing-check-to-determine-if-ele.patch create mode 100644 queue-4.9/mfd-ipaq-micro-fix-error-check-return-value-of-platf.patch create mode 100644 queue-4.9/mwifiex-add-mutex-lock-for-call-in-mwifiex_dfs_chan_.patch create mode 100644 queue-4.9/net-remove-two-bug-from-skb_checksum_help.patch create mode 100644 queue-4.9/nfc-null-out-the-dev-rfkill-to-prevent-uaf.patch create mode 100644 queue-4.9/nvme-pci-fix-a-null-pointer-dereference-in-nvme_allo.patch create mode 100644 queue-4.9/openrisc-start-cpu-timer-early-in-boot.patch create mode 100644 queue-4.9/pci-avoid-pci_dev_lock-ab-ba-deadlock-with-sriov_num.patch create mode 100644 queue-4.9/powerpc-4xx-cpm-fix-return-value-of-__setup-handler.patch create mode 100644 queue-4.9/powerpc-8xx-export-cpm_setbrg-for-modules.patch create mode 100644 queue-4.9/powerpc-idle-fix-return-value-of-__setup-handler.patch create mode 100644 queue-4.9/powerpc-xics-fix-refcount-leak-in-icp_opal_init.patch create mode 100644 queue-4.9/regulator-pfuze100-fix-refcount-leak-in-pfuze_parse_.patch create mode 100644 queue-4.9/rxrpc-don-t-try-to-resend-the-request-if-we-re-recei.patch create mode 100644 queue-4.9/rxrpc-fix-listen-setting-the-bar-too-high-for-the-pr.patch create mode 100644 queue-4.9/rxrpc-return-an-error-to-sendmsg-if-call-failed.patch create mode 100644 queue-4.9/scsi-fcoe-fix-wstringop-overflow-warnings-in-fcoe_ww.patch create mode 100644 queue-4.9/scsi-megaraid-fix-error-check-return-value-of-regist.patch create mode 100644 queue-4.9/sctp-read-sk-sk_bound_dev_if-once-in-sctp_rcv.patch create mode 100644 queue-4.9/soc-qcom-smp2p-fix-missing-of_node_put-in-smp2p_pars.patch create mode 100644 queue-4.9/soc-qcom-smsm-fix-missing-of_node_put-in-smsm_parse_.patch create mode 100644 queue-4.9/spi-img-spfi-fix-pm_runtime_get_sync-error-checking.patch create mode 100644 queue-4.9/spi-spi-ti-qspi-fix-return-value-handling-of-wait_fo.patch create mode 100644 queue-4.9/tty-fix-deadlock-caused-by-calling-printk-under-tty_.patch create mode 100644 queue-4.9/video-fbdev-clcdfb-fix-refcount-leak-in-clcdfb_of_vr.patch create mode 100644 queue-4.9/x86-delay-fix-the-wrong-asm-constraint-in-delay_loop.patch create mode 100644 queue-4.9/x86-mm-cleanup-the-control_va_addr_alignment-__setup.patch create mode 100644 queue-4.9/x86-pm-fix-false-positive-kmemleak-report-in-msr_bui.patch diff --git a/queue-4.9/acpica-avoid-cache-flush-inside-virtual-machines.patch b/queue-4.9/acpica-avoid-cache-flush-inside-virtual-machines.patch new file mode 100644 index 00000000000..6168119157b --- /dev/null +++ b/queue-4.9/acpica-avoid-cache-flush-inside-virtual-machines.patch @@ -0,0 +1,71 @@ +From 4dcd49405b52438a7cc16f6acf4aab3b1e268f39 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 6 Apr 2022 02:29:38 +0300 +Subject: ACPICA: Avoid cache flush inside virtual machines + +From: Kirill A. Shutemov + +[ Upstream commit e2efb6359e620521d1e13f69b2257de8ceaa9475 ] + +While running inside virtual machine, the kernel can bypass cache +flushing. Changing sleep state in a virtual machine doesn't affect the +host system sleep state and cannot lead to data loss. + +Before entering sleep states, the ACPI code flushes caches to prevent +data loss using the WBINVD instruction. This mechanism is required on +bare metal. + +But, any use WBINVD inside of a guest is worthless. Changing sleep +state in a virtual machine doesn't affect the host system sleep state +and cannot lead to data loss, so most hypervisors simply ignore it. +Despite this, the ACPI code calls WBINVD unconditionally anyway. +It's useless, but also normally harmless. + +In TDX guests, though, WBINVD stops being harmless; it triggers a +virtualization exception (#VE). If the ACPI cache-flushing WBINVD +were left in place, TDX guests would need handling to recover from +the exception. + +Avoid using WBINVD whenever running under a hypervisor. This both +removes the useless WBINVDs and saves TDX from implementing WBINVD +handling. + +Signed-off-by: Kirill A. Shutemov +Signed-off-by: Dave Hansen +Reviewed-by: Dave Hansen +Reviewed-by: Dan Williams +Reviewed-by: Thomas Gleixner +Link: https://lkml.kernel.org/r/20220405232939.73860-30-kirill.shutemov@linux.intel.com +Signed-off-by: Sasha Levin +--- + arch/x86/include/asm/acenv.h | 14 +++++++++++++- + 1 file changed, 13 insertions(+), 1 deletion(-) + +diff --git a/arch/x86/include/asm/acenv.h b/arch/x86/include/asm/acenv.h +index 1b010a859b8b..6de59a4f723c 100644 +--- a/arch/x86/include/asm/acenv.h ++++ b/arch/x86/include/asm/acenv.h +@@ -16,7 +16,19 @@ + + /* Asm macros */ + +-#define ACPI_FLUSH_CPU_CACHE() wbinvd() ++/* ++ * ACPI_FLUSH_CPU_CACHE() flushes caches on entering sleep states. ++ * It is required to prevent data loss. ++ * ++ * While running inside virtual machine, the kernel can bypass cache flushing. ++ * Changing sleep state in a virtual machine doesn't affect the host system ++ * sleep state and cannot lead to data loss. ++ */ ++#define ACPI_FLUSH_CPU_CACHE() \ ++do { \ ++ if (!cpu_feature_enabled(X86_FEATURE_HYPERVISOR)) \ ++ wbinvd(); \ ++} while (0) + + int __acpi_acquire_global_lock(unsigned int *lock); + int __acpi_release_global_lock(unsigned int *lock); +-- +2.35.1 + diff --git a/queue-4.9/alsa-jack-access-input_dev-under-mutex.patch b/queue-4.9/alsa-jack-access-input_dev-under-mutex.patch new file mode 100644 index 00000000000..5fbc1b01eb6 --- /dev/null +++ b/queue-4.9/alsa-jack-access-input_dev-under-mutex.patch @@ -0,0 +1,157 @@ +From f3db2e2feafd8c0699fbd2d33c27ed5ea951b9d2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 11:16:28 +0200 +Subject: ALSA: jack: Access input_dev under mutex +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Amadeusz Sławiński + +[ Upstream commit 1b6a6fc5280e97559287b61eade2d4b363e836f2 ] + +It is possible when using ASoC that input_dev is unregistered while +calling snd_jack_report, which causes NULL pointer dereference. +In order to prevent this serialize access to input_dev using mutex lock. + +Signed-off-by: Amadeusz Sławiński +Reviewed-by: Cezary Rojewski +Link: https://lore.kernel.org/r/20220412091628.3056922-1-amadeuszx.slawinski@linux.intel.com +Signed-off-by: Takashi Iwai +Signed-off-by: Sasha Levin +--- + include/sound/jack.h | 1 + + sound/core/jack.c | 34 +++++++++++++++++++++++++++------- + 2 files changed, 28 insertions(+), 7 deletions(-) + +diff --git a/include/sound/jack.h b/include/sound/jack.h +index 1e84bfb553cf..4742f842b457 100644 +--- a/include/sound/jack.h ++++ b/include/sound/jack.h +@@ -77,6 +77,7 @@ struct snd_jack { + const char *id; + #ifdef CONFIG_SND_JACK_INPUT_DEV + struct input_dev *input_dev; ++ struct mutex input_dev_lock; + int registered; + int type; + char name[100]; +diff --git a/sound/core/jack.c b/sound/core/jack.c +index 36cfe1c54109..d2f9a92453f2 100644 +--- a/sound/core/jack.c ++++ b/sound/core/jack.c +@@ -48,8 +48,11 @@ static int snd_jack_dev_disconnect(struct snd_device *device) + #ifdef CONFIG_SND_JACK_INPUT_DEV + struct snd_jack *jack = device->device_data; + +- if (!jack->input_dev) ++ mutex_lock(&jack->input_dev_lock); ++ if (!jack->input_dev) { ++ mutex_unlock(&jack->input_dev_lock); + return 0; ++ } + + /* If the input device is registered with the input subsystem + * then we need to use a different deallocator. */ +@@ -58,6 +61,7 @@ static int snd_jack_dev_disconnect(struct snd_device *device) + else + input_free_device(jack->input_dev); + jack->input_dev = NULL; ++ mutex_unlock(&jack->input_dev_lock); + #endif /* CONFIG_SND_JACK_INPUT_DEV */ + return 0; + } +@@ -96,8 +100,11 @@ static int snd_jack_dev_register(struct snd_device *device) + snprintf(jack->name, sizeof(jack->name), "%s %s", + card->shortname, jack->id); + +- if (!jack->input_dev) ++ mutex_lock(&jack->input_dev_lock); ++ if (!jack->input_dev) { ++ mutex_unlock(&jack->input_dev_lock); + return 0; ++ } + + jack->input_dev->name = jack->name; + +@@ -122,6 +129,7 @@ static int snd_jack_dev_register(struct snd_device *device) + if (err == 0) + jack->registered = 1; + ++ mutex_unlock(&jack->input_dev_lock); + return err; + } + #endif /* CONFIG_SND_JACK_INPUT_DEV */ +@@ -242,9 +250,11 @@ int snd_jack_new(struct snd_card *card, const char *id, int type, + return -ENOMEM; + } + +- /* don't creat input device for phantom jack */ +- if (!phantom_jack) { + #ifdef CONFIG_SND_JACK_INPUT_DEV ++ mutex_init(&jack->input_dev_lock); ++ ++ /* don't create input device for phantom jack */ ++ if (!phantom_jack) { + int i; + + jack->input_dev = input_allocate_device(); +@@ -262,8 +272,8 @@ int snd_jack_new(struct snd_card *card, const char *id, int type, + input_set_capability(jack->input_dev, EV_SW, + jack_switch_types[i]); + +-#endif /* CONFIG_SND_JACK_INPUT_DEV */ + } ++#endif /* CONFIG_SND_JACK_INPUT_DEV */ + + err = snd_device_new(card, SNDRV_DEV_JACK, jack, &ops); + if (err < 0) +@@ -303,10 +313,14 @@ EXPORT_SYMBOL(snd_jack_new); + void snd_jack_set_parent(struct snd_jack *jack, struct device *parent) + { + WARN_ON(jack->registered); +- if (!jack->input_dev) ++ mutex_lock(&jack->input_dev_lock); ++ if (!jack->input_dev) { ++ mutex_unlock(&jack->input_dev_lock); + return; ++ } + + jack->input_dev->dev.parent = parent; ++ mutex_unlock(&jack->input_dev_lock); + } + EXPORT_SYMBOL(snd_jack_set_parent); + +@@ -354,6 +368,8 @@ EXPORT_SYMBOL(snd_jack_set_key); + + /** + * snd_jack_report - Report the current status of a jack ++ * Note: This function uses mutexes and should be called from a ++ * context which can sleep (such as a workqueue). + * + * @jack: The jack to report status for + * @status: The current status of the jack +@@ -373,8 +389,11 @@ void snd_jack_report(struct snd_jack *jack, int status) + status & jack_kctl->mask_bits); + + #ifdef CONFIG_SND_JACK_INPUT_DEV +- if (!jack->input_dev) ++ mutex_lock(&jack->input_dev_lock); ++ if (!jack->input_dev) { ++ mutex_unlock(&jack->input_dev_lock); + return; ++ } + + for (i = 0; i < ARRAY_SIZE(jack->key); i++) { + int testbit = SND_JACK_BTN_0 >> i; +@@ -393,6 +412,7 @@ void snd_jack_report(struct snd_jack *jack, int status) + } + + input_sync(jack->input_dev); ++ mutex_unlock(&jack->input_dev_lock); + #endif /* CONFIG_SND_JACK_INPUT_DEV */ + } + EXPORT_SYMBOL(snd_jack_report); +-- +2.35.1 + diff --git a/queue-4.9/arm-dts-exynos-add-atmel-24c128-fallback-to-samsung-.patch b/queue-4.9/arm-dts-exynos-add-atmel-24c128-fallback-to-samsung-.patch new file mode 100644 index 00000000000..3d8d4b75901 --- /dev/null +++ b/queue-4.9/arm-dts-exynos-add-atmel-24c128-fallback-to-samsung-.patch @@ -0,0 +1,45 @@ +From 68fe25b9691edbe9cbba8c257225470af47858a1 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 26 Apr 2022 20:34:43 +0200 +Subject: ARM: dts: exynos: add atmel,24c128 fallback to Samsung EEPROM + +From: Krzysztof Kozlowski + +[ Upstream commit f038e8186fbc5723d7d38c6fa1d342945107347e ] + +The Samsung s524ad0xd1 EEPROM should use atmel,24c128 fallback, +according to the AT24 EEPROM bindings. + +Reported-by: Rob Herring +Signed-off-by: Krzysztof Kozlowski +Link: https://lore.kernel.org/r/20220426183443.243113-1-krzysztof.kozlowski@linaro.org +Signed-off-by: Sasha Levin +--- + arch/arm/boot/dts/exynos5250-smdk5250.dts | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/arch/arm/boot/dts/exynos5250-smdk5250.dts b/arch/arm/boot/dts/exynos5250-smdk5250.dts +index 54e79f6887ff..3dda0569f86a 100644 +--- a/arch/arm/boot/dts/exynos5250-smdk5250.dts ++++ b/arch/arm/boot/dts/exynos5250-smdk5250.dts +@@ -129,7 +129,7 @@ + samsung,i2c-max-bus-freq = <20000>; + + eeprom@50 { +- compatible = "samsung,s524ad0xd1"; ++ compatible = "samsung,s524ad0xd1", "atmel,24c128"; + reg = <0x50>; + }; + +@@ -288,7 +288,7 @@ + samsung,i2c-max-bus-freq = <20000>; + + eeprom@51 { +- compatible = "samsung,s524ad0xd1"; ++ compatible = "samsung,s524ad0xd1", "atmel,24c128"; + reg = <0x51>; + }; + +-- +2.35.1 + diff --git a/queue-4.9/arm-hisi-add-missing-of_node_put-after-of_find_compa.patch b/queue-4.9/arm-hisi-add-missing-of_node_put-after-of_find_compa.patch new file mode 100644 index 00000000000..dbd27f91fa3 --- /dev/null +++ b/queue-4.9/arm-hisi-add-missing-of_node_put-after-of_find_compa.patch @@ -0,0 +1,52 @@ +From 27e8693525113004ecbf519691f007db0ccb6f8a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 28 Apr 2022 10:43:06 +0000 +Subject: ARM: hisi: Add missing of_node_put after of_find_compatible_node + +From: Peng Wu + +[ Upstream commit 9bc72e47d4630d58a840a66a869c56b29554cfe4 ] + +of_find_compatible_node will increment the refcount of the returned +device_node. Calling of_node_put() to avoid the refcount leak + +Signed-off-by: Peng Wu +Signed-off-by: Wei Xu +Signed-off-by: Sasha Levin +--- + arch/arm/mach-hisi/platsmp.c | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/arch/arm/mach-hisi/platsmp.c b/arch/arm/mach-hisi/platsmp.c +index e1d67648d5d0..fccceab33325 100644 +--- a/arch/arm/mach-hisi/platsmp.c ++++ b/arch/arm/mach-hisi/platsmp.c +@@ -70,14 +70,17 @@ static void __init hi3xxx_smp_prepare_cpus(unsigned int max_cpus) + } + ctrl_base = of_iomap(np, 0); + if (!ctrl_base) { ++ of_node_put(np); + pr_err("failed to map address\n"); + return; + } + if (of_property_read_u32(np, "smp-offset", &offset) < 0) { ++ of_node_put(np); + pr_err("failed to find smp-offset property\n"); + return; + } + ctrl_base += offset; ++ of_node_put(np); + } + } + +@@ -163,6 +166,7 @@ static int hip01_boot_secondary(unsigned int cpu, struct task_struct *idle) + if (WARN_ON(!node)) + return -1; + ctrl_base = of_iomap(node, 0); ++ of_node_put(node); + + /* set the secondary core boot from DDR */ + remap_reg_value = readl_relaxed(ctrl_base + REG_SC_CTRL); +-- +2.35.1 + diff --git a/queue-4.9/arm-omap1-clock-fix-uart-rate-reporting-algorithm.patch b/queue-4.9/arm-omap1-clock-fix-uart-rate-reporting-algorithm.patch new file mode 100644 index 00000000000..146d8cc30fc --- /dev/null +++ b/queue-4.9/arm-omap1-clock-fix-uart-rate-reporting-algorithm.patch @@ -0,0 +1,37 @@ +From f2433798ed782a13c8322d1022d3e9075ae3d600 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 10 Apr 2022 15:07:54 +0200 +Subject: ARM: OMAP1: clock: Fix UART rate reporting algorithm + +From: Janusz Krzysztofik + +[ Upstream commit 338d5d476cde853dfd97378d20496baabc2ce3c0 ] + +Since its introduction to the mainline kernel, omap1_uart_recalc() helper +makes incorrect use of clk->enable_bit as a ready to use bitmap mask while +it only provides the bit number. Fix it. + +Signed-off-by: Janusz Krzysztofik +Acked-by: Tony Lindgren +Signed-off-by: Arnd Bergmann +Signed-off-by: Sasha Levin +--- + arch/arm/mach-omap1/clock.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/arm/mach-omap1/clock.c b/arch/arm/mach-omap1/clock.c +index 034b89499bd7..a3599696e7cc 100644 +--- a/arch/arm/mach-omap1/clock.c ++++ b/arch/arm/mach-omap1/clock.c +@@ -44,7 +44,7 @@ static DEFINE_SPINLOCK(clockfw_lock); + unsigned long omap1_uart_recalc(struct clk *clk) + { + unsigned int val = __raw_readl(clk->enable_reg); +- return val & clk->enable_bit ? 48000000 : 12000000; ++ return val & 1 << clk->enable_bit ? 48000000 : 12000000; + } + + unsigned long omap1_sossi_recalc(struct clk *clk) +-- +2.35.1 + diff --git a/queue-4.9/arm-versatile-add-missing-of_node_put-in-dcscb_init.patch b/queue-4.9/arm-versatile-add-missing-of_node_put-in-dcscb_init.patch new file mode 100644 index 00000000000..096a3dabbd7 --- /dev/null +++ b/queue-4.9/arm-versatile-add-missing-of_node_put-in-dcscb_init.patch @@ -0,0 +1,37 @@ +From b7c554291dddd45dfa604733e57b83d5c162159c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 29 Apr 2022 01:03:56 +0200 +Subject: ARM: versatile: Add missing of_node_put in dcscb_init + +From: Peng Wu + +[ Upstream commit 23b44f9c649bbef10b45fa33080cd8b4166800ae ] + +The device_node pointer is returned by of_find_compatible_node +with refcount incremented. We should use of_node_put() to avoid +the refcount leak. + +Signed-off-by: Peng Wu +Signed-off-by: Linus Walleij +Link: https://lore.kernel.org/r/20220428230356.69418-1-linus.walleij@linaro.org' +Signed-off-by: Arnd Bergmann +Signed-off-by: Sasha Levin +--- + arch/arm/mach-vexpress/dcscb.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/arm/mach-vexpress/dcscb.c b/arch/arm/mach-vexpress/dcscb.c +index 5cedcf572104..3e86cff1d4d3 100644 +--- a/arch/arm/mach-vexpress/dcscb.c ++++ b/arch/arm/mach-vexpress/dcscb.c +@@ -146,6 +146,7 @@ static int __init dcscb_init(void) + if (!node) + return -ENODEV; + dcscb_base = of_iomap(node, 0); ++ of_node_put(node); + if (!dcscb_base) + return -EADDRNOTAVAIL; + cfg = readl_relaxed(dcscb_base + DCS_CFG_R); +-- +2.35.1 + diff --git a/queue-4.9/asoc-dapm-don-t-fold-register-value-changes-into-not.patch b/queue-4.9/asoc-dapm-don-t-fold-register-value-changes-into-not.patch new file mode 100644 index 00000000000..544b8165117 --- /dev/null +++ b/queue-4.9/asoc-dapm-don-t-fold-register-value-changes-into-not.patch @@ -0,0 +1,51 @@ +From 97db1d59d1ff1ee2cdbbe889e40fd6b95bfdfc68 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 28 Apr 2022 17:18:32 +0100 +Subject: ASoC: dapm: Don't fold register value changes into notifications + +From: Mark Brown + +[ Upstream commit ad685980469b9f9b99d4d6ea05f4cb8f57cb2234 ] + +DAPM tracks and reports the value presented to the user from DAPM controls +separately to the register value, these may diverge during initialisation +or when an autodisable control is in use. + +When writing DAPM controls we currently report that a change has occurred +if either the DAPM value or the value stored in the register has changed, +meaning that if the two are out of sync we may appear to report a spurious +event to userspace. Since we use this folded in value for nothing other +than the value reported to userspace simply drop the folding in of the +register change. + +Signed-off-by: Mark Brown +Link: https://lore.kernel.org/r/20220428161833.3690050-1-broonie@kernel.org +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + sound/soc/soc-dapm.c | 2 -- + 1 file changed, 2 deletions(-) + +diff --git a/sound/soc/soc-dapm.c b/sound/soc/soc-dapm.c +index 878a4fc97f04..40bf50cd87bc 100644 +--- a/sound/soc/soc-dapm.c ++++ b/sound/soc/soc-dapm.c +@@ -3165,7 +3165,6 @@ int snd_soc_dapm_put_volsw(struct snd_kcontrol *kcontrol, + update.val = val; + card->update = &update; + } +- change |= reg_change; + + ret = soc_dapm_mixer_update_power(card, kcontrol, connect); + +@@ -3270,7 +3269,6 @@ int snd_soc_dapm_put_enum_double(struct snd_kcontrol *kcontrol, + update.val = val; + card->update = &update; + } +- change |= reg_change; + + ret = soc_dapm_mux_update_power(card, kcontrol, item[0], e); + +-- +2.35.1 + diff --git a/queue-4.9/asoc-mediatek-fix-error-handling-in-mt8173_max98090_.patch b/queue-4.9/asoc-mediatek-fix-error-handling-in-mt8173_max98090_.patch new file mode 100644 index 00000000000..11ac370c4ba --- /dev/null +++ b/queue-4.9/asoc-mediatek-fix-error-handling-in-mt8173_max98090_.patch @@ -0,0 +1,49 @@ +From 476afac8e18f490050fe12089e51c3818183633e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 4 Apr 2022 09:29:01 +0000 +Subject: ASoC: mediatek: Fix error handling in mt8173_max98090_dev_probe + +From: Miaoqian Lin + +[ Upstream commit 4f4e0454e226de3bf4efd7e7924d1edc571c52d5 ] + +Call of_node_put(platform_node) to avoid refcount leak in +the error path. + +Fixes: 94319ba10eca ("ASoC: mediatek: Use platform_of_node for machine drivers") +Fixes: 493433785df0 ("ASoC: mediatek: mt8173: fix device_node leak") +Signed-off-by: Miaoqian Lin +Reviewed-by: AngeloGioacchino Del Regno +Link: https://lore.kernel.org/r/20220404092903.26725-1-linmq006@gmail.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + sound/soc/mediatek/mt8173/mt8173-max98090.c | 5 ++++- + 1 file changed, 4 insertions(+), 1 deletion(-) + +diff --git a/sound/soc/mediatek/mt8173/mt8173-max98090.c b/sound/soc/mediatek/mt8173/mt8173-max98090.c +index cab30cb48366..85bf9eafda49 100644 +--- a/sound/soc/mediatek/mt8173/mt8173-max98090.c ++++ b/sound/soc/mediatek/mt8173/mt8173-max98090.c +@@ -170,7 +170,8 @@ static int mt8173_max98090_dev_probe(struct platform_device *pdev) + if (!codec_node) { + dev_err(&pdev->dev, + "Property 'audio-codec' missing or invalid\n"); +- return -EINVAL; ++ ret = -EINVAL; ++ goto put_platform_node; + } + for (i = 0; i < card->num_links; i++) { + if (mt8173_max98090_dais[i].codec_name) +@@ -185,6 +186,8 @@ static int mt8173_max98090_dev_probe(struct platform_device *pdev) + __func__, ret); + + of_node_put(codec_node); ++ ++put_platform_node: + of_node_put(platform_node); + return ret; + } +-- +2.35.1 + diff --git a/queue-4.9/asoc-mxs-saif-fix-refcount-leak-in-mxs_saif_probe.patch b/queue-4.9/asoc-mxs-saif-fix-refcount-leak-in-mxs_saif_probe.patch new file mode 100644 index 00000000000..9ebbd15c6b1 --- /dev/null +++ b/queue-4.9/asoc-mxs-saif-fix-refcount-leak-in-mxs_saif_probe.patch @@ -0,0 +1,36 @@ +From 2dec31196f4278ac399e5ffb4fe85ac0dd09b4a0 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 11 May 2022 17:37:22 +0400 +Subject: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe + +From: Miaoqian Lin + +[ Upstream commit 2be84f73785fa9ed6443e3c5b158730266f1c2ee ] + +of_parse_phandle() returns a node pointer with refcount +incremented, we should use of_node_put() on it when done. + +Fixes: 08641c7c74dd ("ASoC: mxs: add device tree support for mxs-saif") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220511133725.39039-1-linmq006@gmail.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + sound/soc/mxs/mxs-saif.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/sound/soc/mxs/mxs-saif.c b/sound/soc/mxs/mxs-saif.c +index 5977a2011d9e..76e1059e7f15 100644 +--- a/sound/soc/mxs/mxs-saif.c ++++ b/sound/soc/mxs/mxs-saif.c +@@ -748,6 +748,7 @@ static int mxs_saif_probe(struct platform_device *pdev) + saif->master_id = saif->id; + } else { + ret = of_alias_get_id(master, "saif"); ++ of_node_put(master); + if (ret < 0) + return ret; + else +-- +2.35.1 + diff --git a/queue-4.9/asoc-rt5645-fix-errorenous-cleanup-order.patch b/queue-4.9/asoc-rt5645-fix-errorenous-cleanup-order.patch new file mode 100644 index 00000000000..e873ab430ca --- /dev/null +++ b/queue-4.9/asoc-rt5645-fix-errorenous-cleanup-order.patch @@ -0,0 +1,50 @@ +From fff694b89df2479cd1c46076a69ac3294a602001 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 16 May 2022 17:20:35 +0800 +Subject: ASoC: rt5645: Fix errorenous cleanup order + +From: Lin Ma + +[ Upstream commit 2def44d3aec59e38d2701c568d65540783f90f2f ] + +There is a logic error when removing rt5645 device as the function +rt5645_i2c_remove() first cancel the &rt5645->jack_detect_work and +delete the &rt5645->btn_check_timer latter. However, since the timer +handler rt5645_btn_check_callback() will re-queue the jack_detect_work, +this cleanup order is buggy. + +That is, once the del_timer_sync in rt5645_i2c_remove is concurrently +run with the rt5645_btn_check_callback, the canceled jack_detect_work +will be rescheduled again, leading to possible use-after-free. + +This patch fix the issue by placing the del_timer_sync function before +the cancel_delayed_work_sync. + +Signed-off-by: Lin Ma +Link: https://lore.kernel.org/r/20220516092035.28283-1-linma@zju.edu.cn +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + sound/soc/codecs/rt5645.c | 6 ++++++ + 1 file changed, 6 insertions(+) + +diff --git a/sound/soc/codecs/rt5645.c b/sound/soc/codecs/rt5645.c +index 1ac96ef9ee20..703b26ec4e15 100644 +--- a/sound/soc/codecs/rt5645.c ++++ b/sound/soc/codecs/rt5645.c +@@ -3878,6 +3878,12 @@ static int rt5645_i2c_remove(struct i2c_client *i2c) + if (i2c->irq) + free_irq(i2c->irq, rt5645); + ++ /* ++ * Since the rt5645_btn_check_callback() can queue jack_detect_work, ++ * the timer need to be delted first ++ */ ++ del_timer_sync(&rt5645->btn_check_timer); ++ + cancel_delayed_work_sync(&rt5645->jack_detect_work); + cancel_delayed_work_sync(&rt5645->rcclock_work); + +-- +2.35.1 + diff --git a/queue-4.9/asoc-wm2000-fix-missing-clk_disable_unprepare-on-err.patch b/queue-4.9/asoc-wm2000-fix-missing-clk_disable_unprepare-on-err.patch new file mode 100644 index 00000000000..399c301dc87 --- /dev/null +++ b/queue-4.9/asoc-wm2000-fix-missing-clk_disable_unprepare-on-err.patch @@ -0,0 +1,55 @@ +From d57b4088c1311ee33271e30666af8ec720e0564b Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 14 May 2022 17:10:53 +0800 +Subject: ASoC: wm2000: fix missing clk_disable_unprepare() on error in + wm2000_anc_transition() + +From: Yang Yingliang + +[ Upstream commit be2af740e2a9c7134f2d8ab4f104006e110b13de ] + +Fix the missing clk_disable_unprepare() before return +from wm2000_anc_transition() in the error handling case. + +Fixes: 514cfd6dd725 ("ASoC: wm2000: Integrate with clock API") +Signed-off-by: Yang Yingliang +Acked-by: Charles Keepax +Link: https://lore.kernel.org/r/20220514091053.686416-1-yangyingliang@huawei.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + sound/soc/codecs/wm2000.c | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/sound/soc/codecs/wm2000.c b/sound/soc/codecs/wm2000.c +index 23cde3a0dc11..73cda3c2a861 100644 +--- a/sound/soc/codecs/wm2000.c ++++ b/sound/soc/codecs/wm2000.c +@@ -545,7 +545,7 @@ static int wm2000_anc_transition(struct wm2000_priv *wm2000, + { + struct i2c_client *i2c = wm2000->i2c; + int i, j; +- int ret; ++ int ret = 0; + + if (wm2000->anc_mode == mode) + return 0; +@@ -575,13 +575,13 @@ static int wm2000_anc_transition(struct wm2000_priv *wm2000, + ret = anc_transitions[i].step[j](i2c, + anc_transitions[i].analogue); + if (ret != 0) +- return ret; ++ break; + } + + if (anc_transitions[i].dest == ANC_OFF) + clk_disable_unprepare(wm2000->mclk); + +- return 0; ++ return ret; + } + + static int wm2000_anc_set_mode(struct wm2000_priv *wm2000) +-- +2.35.1 + diff --git a/queue-4.9/ath9k-fix-qca9561-pa-bias-level.patch b/queue-4.9/ath9k-fix-qca9561-pa-bias-level.patch new file mode 100644 index 00000000000..7b79cec49e8 --- /dev/null +++ b/queue-4.9/ath9k-fix-qca9561-pa-bias-level.patch @@ -0,0 +1,54 @@ +From 9c7104896c2d6ce7b9dde787031a4827efcf9153 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 17 Apr 2022 16:51:45 +0200 +Subject: ath9k: fix QCA9561 PA bias level +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Thibaut VARÈNE + +[ Upstream commit e999a5da28a0e0f7de242d841ef7d5e48f4646ae ] + +This patch fixes an invalid TX PA DC bias level on QCA9561, which +results in a very low output power and very low throughput as devices +are further away from the AP (compared to other 2.4GHz APs). + +This patch was suggested by Felix Fietkau, who noted[1]: +"The value written to that register is wrong, because while the mask +definition AR_CH0_TOP2_XPABIASLVL uses a different value for 9561, the +shift definition AR_CH0_TOP2_XPABIASLVL_S is hardcoded to 12, which is +wrong for 9561." + +In real life testing, without this patch the 2.4GHz throughput on +Yuncore XD3200 is around 10Mbps sitting next to the AP, and closer to +practical maximum with the patch applied. + +[1] https://lore.kernel.org/all/91c58969-c60e-2f41-00ac-737786d435ae@nbd.name + +Signed-off-by: Thibaut VARÈNE +Acked-by: Felix Fietkau +Acked-by: Toke Høiland-Jørgensen +Signed-off-by: Kalle Valo +Link: https://lore.kernel.org/r/20220417145145.1847-1-hacks+kernel@slashdirt.org +Signed-off-by: Sasha Levin +--- + drivers/net/wireless/ath/ath9k/ar9003_phy.h | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/wireless/ath/ath9k/ar9003_phy.h b/drivers/net/wireless/ath/ath9k/ar9003_phy.h +index a171dbb29fbb..ad949eb02f3d 100644 +--- a/drivers/net/wireless/ath/ath9k/ar9003_phy.h ++++ b/drivers/net/wireless/ath/ath9k/ar9003_phy.h +@@ -720,7 +720,7 @@ + #define AR_CH0_TOP2 (AR_SREV_9300(ah) ? 0x1628c : \ + (AR_SREV_9462(ah) ? 0x16290 : 0x16284)) + #define AR_CH0_TOP2_XPABIASLVL (AR_SREV_9561(ah) ? 0x1e00 : 0xf000) +-#define AR_CH0_TOP2_XPABIASLVL_S 12 ++#define AR_CH0_TOP2_XPABIASLVL_S (AR_SREV_9561(ah) ? 9 : 12) + + #define AR_CH0_XTAL (AR_SREV_9300(ah) ? 0x16294 : \ + ((AR_SREV_9462(ah) || AR_SREV_9565(ah)) ? 0x16298 : \ +-- +2.35.1 + diff --git a/queue-4.9/ath9k_htc-fix-potential-out-of-bounds-access-with-in.patch b/queue-4.9/ath9k_htc-fix-potential-out-of-bounds-access-with-in.patch new file mode 100644 index 00000000000..8f77570883c --- /dev/null +++ b/queue-4.9/ath9k_htc-fix-potential-out-of-bounds-access-with-in.patch @@ -0,0 +1,51 @@ +From 3fd03101a325c518f081669eeb774e1a95f10d1a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 9 Apr 2022 09:12:25 +0300 +Subject: ath9k_htc: fix potential out of bounds access with invalid + rxstatus->rs_keyix +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Dan Carpenter + +[ Upstream commit 2dc509305cf956381532792cb8dceef2b1504765 ] + +The "rxstatus->rs_keyix" eventually gets passed to test_bit() so we need to +ensure that it is within the bitmap. + +drivers/net/wireless/ath/ath9k/common.c:46 ath9k_cmn_rx_accept() +error: passing untrusted data 'rx_stats->rs_keyix' to 'test_bit()' + +Fixes: 4ed1a8d4a257 ("ath9k_htc: use ath9k_cmn_rx_accept") +Signed-off-by: Dan Carpenter +Acked-by: Toke Høiland-Jørgensen +Signed-off-by: Kalle Valo +Link: https://lore.kernel.org/r/20220409061225.GA5447@kili +Signed-off-by: Sasha Levin +--- + drivers/net/wireless/ath/ath9k/htc_drv_txrx.c | 8 ++++++++ + 1 file changed, 8 insertions(+) + +diff --git a/drivers/net/wireless/ath/ath9k/htc_drv_txrx.c b/drivers/net/wireless/ath/ath9k/htc_drv_txrx.c +index 6a9c9b4ef2c9..fe4491eff8ca 100644 +--- a/drivers/net/wireless/ath/ath9k/htc_drv_txrx.c ++++ b/drivers/net/wireless/ath/ath9k/htc_drv_txrx.c +@@ -1004,6 +1004,14 @@ static bool ath9k_rx_prepare(struct ath9k_htc_priv *priv, + goto rx_next; + } + ++ if (rxstatus->rs_keyix >= ATH_KEYMAX && ++ rxstatus->rs_keyix != ATH9K_RXKEYIX_INVALID) { ++ ath_dbg(common, ANY, ++ "Invalid keyix, dropping (keyix: %d)\n", ++ rxstatus->rs_keyix); ++ goto rx_next; ++ } ++ + /* Get the RX status information */ + + memset(rx_status, 0, sizeof(struct ieee80211_rx_status)); +-- +2.35.1 + diff --git a/queue-4.9/b43-fix-assigning-negative-value-to-unsigned-variabl.patch b/queue-4.9/b43-fix-assigning-negative-value-to-unsigned-variabl.patch new file mode 100644 index 00000000000..bba0d8f7c5b --- /dev/null +++ b/queue-4.9/b43-fix-assigning-negative-value-to-unsigned-variabl.patch @@ -0,0 +1,37 @@ +From 4f4682a787f4f5e4447ef095baaaeb66d4d69c58 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 25 Mar 2022 18:15:15 +0800 +Subject: b43: Fix assigning negative value to unsigned variable + +From: Haowen Bai + +[ Upstream commit 11800d893b38e0e12d636c170c1abc19c43c730c ] + +fix warning reported by smatch: +drivers/net/wireless/broadcom/b43/phy_n.c:585 b43_nphy_adjust_lna_gain_table() +warn: assigning (-2) to unsigned variable '*(lna_gain[0])' + +Signed-off-by: Haowen Bai +Signed-off-by: Kalle Valo +Link: https://lore.kernel.org/r/1648203315-28093-1-git-send-email-baihaowen@meizu.com +Signed-off-by: Sasha Levin +--- + drivers/net/wireless/broadcom/b43/phy_n.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/wireless/broadcom/b43/phy_n.c b/drivers/net/wireless/broadcom/b43/phy_n.c +index d1afa74aa144..9cbc17c2751c 100644 +--- a/drivers/net/wireless/broadcom/b43/phy_n.c ++++ b/drivers/net/wireless/broadcom/b43/phy_n.c +@@ -594,7 +594,7 @@ static void b43_nphy_adjust_lna_gain_table(struct b43_wldev *dev) + u16 data[4]; + s16 gain[2]; + u16 minmax[2]; +- static const u16 lna_gain[4] = { -2, 10, 19, 25 }; ++ static const s16 lna_gain[4] = { -2, 10, 19, 25 }; + + if (nphy->hang_avoid) + b43_nphy_stay_in_carrier_search(dev, 1); +-- +2.35.1 + diff --git a/queue-4.9/b43legacy-fix-assigning-negative-value-to-unsigned-v.patch b/queue-4.9/b43legacy-fix-assigning-negative-value-to-unsigned-v.patch new file mode 100644 index 00000000000..182da29d864 --- /dev/null +++ b/queue-4.9/b43legacy-fix-assigning-negative-value-to-unsigned-v.patch @@ -0,0 +1,37 @@ +From b75cba446b76a6a3a82992e1ad1b20d59d9fc8ab Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 25 Mar 2022 18:17:13 +0800 +Subject: b43legacy: Fix assigning negative value to unsigned variable + +From: Haowen Bai + +[ Upstream commit 3f6b867559b3d43a7ce1b4799b755e812fc0d503 ] + +fix warning reported by smatch: +drivers/net/wireless/broadcom/b43legacy/phy.c:1181 b43legacy_phy_lo_b_measure() +warn: assigning (-772) to unsigned variable 'fval' + +Signed-off-by: Haowen Bai +Signed-off-by: Kalle Valo +Link: https://lore.kernel.org/r/1648203433-8736-1-git-send-email-baihaowen@meizu.com +Signed-off-by: Sasha Levin +--- + drivers/net/wireless/broadcom/b43legacy/phy.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/wireless/broadcom/b43legacy/phy.c b/drivers/net/wireless/broadcom/b43legacy/phy.c +index 995c7d0c212a..11ee5ee48976 100644 +--- a/drivers/net/wireless/broadcom/b43legacy/phy.c ++++ b/drivers/net/wireless/broadcom/b43legacy/phy.c +@@ -1148,7 +1148,7 @@ void b43legacy_phy_lo_b_measure(struct b43legacy_wldev *dev) + struct b43legacy_phy *phy = &dev->phy; + u16 regstack[12] = { 0 }; + u16 mls; +- u16 fval; ++ s16 fval; + int i; + int j; + +-- +2.35.1 + diff --git a/queue-4.9/bluetooth-fix-dangling-sco_conn-and-use-after-free-i.patch b/queue-4.9/bluetooth-fix-dangling-sco_conn-and-use-after-free-i.patch new file mode 100644 index 00000000000..91f29afa140 --- /dev/null +++ b/queue-4.9/bluetooth-fix-dangling-sco_conn-and-use-after-free-i.patch @@ -0,0 +1,88 @@ +From d774b024f088a772328f7ae1793c555f0532a949 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 26 Mar 2022 07:09:28 +0000 +Subject: Bluetooth: fix dangling sco_conn and use-after-free in + sco_sock_timeout + +From: Ying Hsu + +[ Upstream commit 7aa1e7d15f8a5b65f67bacb100d8fc033b21efa2 ] + +Connecting the same socket twice consecutively in sco_sock_connect() +could lead to a race condition where two sco_conn objects are created +but only one is associated with the socket. If the socket is closed +before the SCO connection is established, the timer associated with the +dangling sco_conn object won't be canceled. As the sock object is being +freed, the use-after-free problem happens when the timer callback +function sco_sock_timeout() accesses the socket. Here's the call trace: + +dump_stack+0x107/0x163 +? refcount_inc+0x1c/ +print_address_description.constprop.0+0x1c/0x47e +? refcount_inc+0x1c/0x7b +kasan_report+0x13a/0x173 +? refcount_inc+0x1c/0x7b +check_memory_region+0x132/0x139 +refcount_inc+0x1c/0x7b +sco_sock_timeout+0xb2/0x1ba +process_one_work+0x739/0xbd1 +? cancel_delayed_work+0x13f/0x13f +? __raw_spin_lock_init+0xf0/0xf0 +? to_kthread+0x59/0x85 +worker_thread+0x593/0x70e +kthread+0x346/0x35a +? drain_workqueue+0x31a/0x31a +? kthread_bind+0x4b/0x4b +ret_from_fork+0x1f/0x30 + +Link: https://syzkaller.appspot.com/bug?extid=2bef95d3ab4daa10155b +Reported-by: syzbot+2bef95d3ab4daa10155b@syzkaller.appspotmail.com +Fixes: e1dee2c1de2b ("Bluetooth: fix repeated calls to sco_sock_kill") +Signed-off-by: Ying Hsu +Reviewed-by: Joseph Hwang +Signed-off-by: Marcel Holtmann +Signed-off-by: Sasha Levin +--- + net/bluetooth/sco.c | 21 +++++++++++++-------- + 1 file changed, 13 insertions(+), 8 deletions(-) + +diff --git a/net/bluetooth/sco.c b/net/bluetooth/sco.c +index b3b4ffaa394f..9892ce82cbdf 100644 +--- a/net/bluetooth/sco.c ++++ b/net/bluetooth/sco.c +@@ -542,19 +542,24 @@ static int sco_sock_connect(struct socket *sock, struct sockaddr *addr, int alen + addr->sa_family != AF_BLUETOOTH) + return -EINVAL; + +- if (sk->sk_state != BT_OPEN && sk->sk_state != BT_BOUND) +- return -EBADFD; ++ lock_sock(sk); ++ if (sk->sk_state != BT_OPEN && sk->sk_state != BT_BOUND) { ++ err = -EBADFD; ++ goto done; ++ } + +- if (sk->sk_type != SOCK_SEQPACKET) +- return -EINVAL; ++ if (sk->sk_type != SOCK_SEQPACKET) { ++ err = -EINVAL; ++ goto done; ++ } + + hdev = hci_get_route(&sa->sco_bdaddr, &sco_pi(sk)->src, BDADDR_BREDR); +- if (!hdev) +- return -EHOSTUNREACH; ++ if (!hdev) { ++ err = -EHOSTUNREACH; ++ goto done; ++ } + hci_dev_lock(hdev); + +- lock_sock(sk); +- + /* Set destination address and psm */ + bacpy(&sco_pi(sk)->dst, &sa->sco_bdaddr); + +-- +2.35.1 + diff --git a/queue-4.9/dma-debug-change-allocation-mode-from-gfp_nowait-to-.patch b/queue-4.9/dma-debug-change-allocation-mode-from-gfp_nowait-to-.patch new file mode 100644 index 00000000000..99808da47b0 --- /dev/null +++ b/queue-4.9/dma-debug-change-allocation-mode-from-gfp_nowait-to-.patch @@ -0,0 +1,41 @@ +From e763d0fb330060b5d9df6b2bbebe67b811a96f8d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 10 May 2022 13:17:32 -0400 +Subject: dma-debug: change allocation mode from GFP_NOWAIT to GFP_ATIOMIC + +From: Mikulas Patocka + +[ Upstream commit 84bc4f1dbbbb5f8aa68706a96711dccb28b518e5 ] + +We observed the error "cacheline tracking ENOMEM, dma-debug disabled" +during a light system load (copying some files). The reason for this error +is that the dma_active_cacheline radix tree uses GFP_NOWAIT allocation - +so it can't access the emergency memory reserves and it fails as soon as +anybody reaches the watermark. + +This patch changes GFP_NOWAIT to GFP_ATOMIC, so that it can access the +emergency memory reserves. + +Signed-off-by: Mikulas Patocka +Signed-off-by: Christoph Hellwig +Signed-off-by: Sasha Levin +--- + lib/dma-debug.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/lib/dma-debug.c b/lib/dma-debug.c +index 4435bec55fb5..baafebabe3ac 100644 +--- a/lib/dma-debug.c ++++ b/lib/dma-debug.c +@@ -463,7 +463,7 @@ EXPORT_SYMBOL(debug_dma_dump_mappings); + * At any time debug_dma_assert_idle() can be called to trigger a + * warning if any cachelines in the given page are in the active set. + */ +-static RADIX_TREE(dma_active_cacheline, GFP_NOWAIT); ++static RADIX_TREE(dma_active_cacheline, GFP_ATOMIC); + static DEFINE_SPINLOCK(radix_lock); + #define ACTIVE_CACHELINE_MAX_OVERLAP ((1 << RADIX_TREE_MAX_TAGS) - 1) + #define CACHELINE_PER_PAGE_SHIFT (PAGE_SHIFT - L1_CACHE_SHIFT) +-- +2.35.1 + diff --git a/queue-4.9/drivers-base-node.c-fix-compaction-sysfs-file-leak.patch b/queue-4.9/drivers-base-node.c-fix-compaction-sysfs-file-leak.patch new file mode 100644 index 00000000000..2166f2a80eb --- /dev/null +++ b/queue-4.9/drivers-base-node.c-fix-compaction-sysfs-file-leak.patch @@ -0,0 +1,44 @@ +From 62e93c1a8966e5791881b038912fd1fde305d04e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 28 Apr 2022 23:16:06 -0700 +Subject: drivers/base/node.c: fix compaction sysfs file leak + +From: Miaohe Lin + +[ Upstream commit da63dc84befaa9e6079a0bc363ff0eaa975f9073 ] + +Compaction sysfs file is created via compaction_register_node in +register_node. But we forgot to remove it in unregister_node. Thus +compaction sysfs file is leaked. Using compaction_unregister_node to fix +this issue. + +Link: https://lkml.kernel.org/r/20220401070905.43679-1-linmiaohe@huawei.com +Fixes: ed4a6d7f0676 ("mm: compaction: add /sys trigger for per-node memory compaction") +Signed-off-by: Miaohe Lin +Cc: Greg Kroah-Hartman +Cc: Rafael J. Wysocki +Cc: Mel Gorman +Cc: Minchan Kim +Cc: KAMEZAWA Hiroyuki +Cc: KOSAKI Motohiro +Signed-off-by: Andrew Morton +Signed-off-by: Sasha Levin +--- + drivers/base/node.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/base/node.c b/drivers/base/node.c +index 5548f9686016..7f9126633080 100644 +--- a/drivers/base/node.c ++++ b/drivers/base/node.c +@@ -315,6 +315,7 @@ static int register_node(struct node *node, int num, struct node *parent) + */ + void unregister_node(struct node *node) + { ++ compaction_unregister_node(node); + hugetlb_unregister_node(node); /* no-op, if memoryless node */ + + device_unregister(&node->dev); +-- +2.35.1 + diff --git a/queue-4.9/drm-amd-pm-fix-double-free-in-si_parse_power_table.patch b/queue-4.9/drm-amd-pm-fix-double-free-in-si_parse_power_table.patch new file mode 100644 index 00000000000..dcfa913ff8c --- /dev/null +++ b/queue-4.9/drm-amd-pm-fix-double-free-in-si_parse_power_table.patch @@ -0,0 +1,70 @@ +From 880eaf7526232be6b01ae6763ec9f59455e6de40 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 19 Apr 2022 10:37:19 +0000 +Subject: drm/amd/pm: fix double free in si_parse_power_table() + +From: Keita Suzuki + +[ Upstream commit f3fa2becf2fc25b6ac7cf8d8b1a2e4a86b3b72bd ] + +In function si_parse_power_table(), array adev->pm.dpm.ps and its member +is allocated. If the allocation of each member fails, the array itself +is freed and returned with an error code. However, the array is later +freed again in si_dpm_fini() function which is called when the function +returns an error. + +This leads to potential double free of the array adev->pm.dpm.ps, as +well as leak of its array members, since the members are not freed in +the allocation function and the array is not nulled when freed. +In addition adev->pm.dpm.num_ps, which keeps track of the allocated +array member, is not updated until the member allocation is +successfully finished, this could also lead to either use after free, +or uninitialized variable access in si_dpm_fini(). + +Fix this by postponing the free of the array until si_dpm_fini() and +increment adev->pm.dpm.num_ps everytime the array member is allocated. + +Signed-off-by: Keita Suzuki +Signed-off-by: Alex Deucher +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/amd/amdgpu/si_dpm.c | 8 +++----- + 1 file changed, 3 insertions(+), 5 deletions(-) + +diff --git a/drivers/gpu/drm/amd/amdgpu/si_dpm.c b/drivers/gpu/drm/amd/amdgpu/si_dpm.c +index 4826befc1bc3..fe6fda42fde8 100644 +--- a/drivers/gpu/drm/amd/amdgpu/si_dpm.c ++++ b/drivers/gpu/drm/amd/amdgpu/si_dpm.c +@@ -7313,17 +7313,15 @@ static int si_parse_power_table(struct amdgpu_device *adev) + if (!adev->pm.dpm.ps) + return -ENOMEM; + power_state_offset = (u8 *)state_array->states; +- for (i = 0; i < state_array->ucNumEntries; i++) { ++ for (adev->pm.dpm.num_ps = 0, i = 0; i < state_array->ucNumEntries; i++) { + u8 *idx; + power_state = (union pplib_power_state *)power_state_offset; + non_clock_array_index = power_state->v2.nonClockInfoIndex; + non_clock_info = (struct _ATOM_PPLIB_NONCLOCK_INFO *) + &non_clock_info_array->nonClockInfo[non_clock_array_index]; + ps = kzalloc(sizeof(struct si_ps), GFP_KERNEL); +- if (ps == NULL) { +- kfree(adev->pm.dpm.ps); ++ if (ps == NULL) + return -ENOMEM; +- } + adev->pm.dpm.ps[i].ps_priv = ps; + si_parse_pplib_non_clock_info(adev, &adev->pm.dpm.ps[i], + non_clock_info, +@@ -7345,8 +7343,8 @@ static int si_parse_power_table(struct amdgpu_device *adev) + k++; + } + power_state_offset += 2 + power_state->v2.ucNumDPMLevels; ++ adev->pm.dpm.num_ps++; + } +- adev->pm.dpm.num_ps = state_array->ucNumEntries; + + /* fill in the vce power states */ + for (i = 0; i < AMDGPU_MAX_VCE_LEVELS; i++) { +-- +2.35.1 + diff --git a/queue-4.9/drm-amd-pm-fix-the-compile-warning.patch b/queue-4.9/drm-amd-pm-fix-the-compile-warning.patch new file mode 100644 index 00000000000..b35c9380305 --- /dev/null +++ b/queue-4.9/drm-amd-pm-fix-the-compile-warning.patch @@ -0,0 +1,51 @@ +From c9c7186a306836ff243b283ed54e71bcebdda040 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 25 Apr 2022 10:16:46 +0800 +Subject: drm/amd/pm: fix the compile warning + +From: Evan Quan + +[ Upstream commit 555238d92ac32dbad2d77ad2bafc48d17391990c ] + +Fix the compile warning below: +drivers/gpu/drm/amd/amdgpu/../pm/legacy-dpm/kv_dpm.c:1641 +kv_get_acp_boot_level() warn: always true condition '(table->entries[i]->clk >= 0) => (0-u32max >= 0)' + +Reported-by: kernel test robot +CC: Alex Deucher +Signed-off-by: Evan Quan +Reviewed-by: Alex Deucher +Signed-off-by: Alex Deucher +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/amd/amdgpu/kv_dpm.c | 14 +------------- + 1 file changed, 1 insertion(+), 13 deletions(-) + +diff --git a/drivers/gpu/drm/amd/amdgpu/kv_dpm.c b/drivers/gpu/drm/amd/amdgpu/kv_dpm.c +index f61c489e5f6d..81f1591a9be9 100644 +--- a/drivers/gpu/drm/amd/amdgpu/kv_dpm.c ++++ b/drivers/gpu/drm/amd/amdgpu/kv_dpm.c +@@ -1617,19 +1617,7 @@ static int kv_update_samu_dpm(struct amdgpu_device *adev, bool gate) + + static u8 kv_get_acp_boot_level(struct amdgpu_device *adev) + { +- u8 i; +- struct amdgpu_clock_voltage_dependency_table *table = +- &adev->pm.dpm.dyn_state.acp_clock_voltage_dependency_table; +- +- for (i = 0; i < table->count; i++) { +- if (table->entries[i].clk >= 0) /* XXX */ +- break; +- } +- +- if (i >= table->count) +- i = table->count - 1; +- +- return i; ++ return 0; + } + + static void kv_update_acp_boot_level(struct amdgpu_device *adev) +-- +2.35.1 + diff --git a/queue-4.9/drm-fix-edid-struct-for-old-arm-oabi-format.patch b/queue-4.9/drm-fix-edid-struct-for-old-arm-oabi-format.patch new file mode 100644 index 00000000000..17a5f8acd38 --- /dev/null +++ b/queue-4.9/drm-fix-edid-struct-for-old-arm-oabi-format.patch @@ -0,0 +1,114 @@ +From b216342f2b771cefd53e325a93f1b5a05e54f554 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 28 May 2022 11:08:48 -0700 +Subject: drm: fix EDID struct for old ARM OABI format + +From: Linus Torvalds + +[ Upstream commit 47f15561b69e226bfc034e94ff6dbec51a4662af ] + +When building the kernel for arm with the "-mabi=apcs-gnu" option, gcc +will force alignment of all structures and unions to a word boundary +(see also STRUCTURE_SIZE_BOUNDARY and the "-mstructure-size-boundary=XX" +option if you're a gcc person), even when the members of said structures +do not want or need said alignment. + +This completely messes up the structure alignment of 'struct edid' on +those targets, because even though all the embedded structures are +marked with "__attribute__((packed))", the unions that contain them are +not. + +This was exposed by commit f1e4c916f97f ("drm/edid: add EDID block count +and size helpers"), but the bug is pre-existing. That commit just made +the structure layout problem cause a build failure due to the addition +of the + + BUILD_BUG_ON(sizeof(*edid) != EDID_LENGTH); + +sanity check in drivers/gpu/drm/drm_edid.c:edid_block_data(). + +This legacy union alignment should probably not be used in the first +place, but we can fix the layout by adding the packed attribute to the +union entries even when each member is already packed and it shouldn't +matter in a sane build environment. + +You can see this issue with a trivial test program: + + union { + struct { + char c[5]; + }; + struct { + char d; + unsigned e; + } __attribute__((packed)); + } a = { "1234" }; + +where building this with a normal "gcc -S" will result in the expected +5-byte size of said union: + + .type a, @object + .size a, 5 + +but with an ARM compiler and the old ABI: + + arm-linux-gnu-gcc -mabi=apcs-gnu -mfloat-abi=soft -S t.c + +you get + + .type a, %object + .size a, 8 + +instead, because even though each member of the union is packed, the +union itself still gets aligned. + +This was reported by Sudip for the spear3xx_defconfig target. + +Link: https://lore.kernel.org/lkml/YpCUzStDnSgQLNFN@debian/ +Reported-by: Sudip Mukherjee +Acked-by: Arnd Bergmann +Cc: Maarten Lankhorst +Cc: Maxime Ripard +Cc: Thomas Zimmermann +Cc: David Airlie +Cc: Daniel Vetter +Signed-off-by: Linus Torvalds +Signed-off-by: Sasha Levin +--- + include/drm/drm_edid.h | 6 +++--- + 1 file changed, 3 insertions(+), 3 deletions(-) + +diff --git a/include/drm/drm_edid.h b/include/drm/drm_edid.h +index c3a7d440bc11..514a02095983 100644 +--- a/include/drm/drm_edid.h ++++ b/include/drm/drm_edid.h +@@ -114,7 +114,7 @@ struct detailed_data_monitor_range { + u8 supported_scalings; + u8 preferred_refresh; + } __attribute__((packed)) cvt; +- } formula; ++ } __attribute__((packed)) formula; + } __attribute__((packed)); + + struct detailed_data_wpindex { +@@ -147,7 +147,7 @@ struct detailed_non_pixel { + struct detailed_data_wpindex color; + struct std_timing timings[6]; + struct cvt_timing cvt[4]; +- } data; ++ } __attribute__((packed)) data; + } __attribute__((packed)); + + #define EDID_DETAIL_EST_TIMINGS 0xf7 +@@ -165,7 +165,7 @@ struct detailed_timing { + union { + struct detailed_pixel_timing pixel_data; + struct detailed_non_pixel other_data; +- } data; ++ } __attribute__((packed)) data; + } __attribute__((packed)); + + #define DRM_EDID_INPUT_SERRATION_VSYNC (1 << 0) +-- +2.35.1 + diff --git a/queue-4.9/drm-mediatek-fix-mtk_cec_mask.patch b/queue-4.9/drm-mediatek-fix-mtk_cec_mask.patch new file mode 100644 index 00000000000..ee13ff22809 --- /dev/null +++ b/queue-4.9/drm-mediatek-fix-mtk_cec_mask.patch @@ -0,0 +1,45 @@ +From e50804df8ced195053177b9d6593435c05c66b2c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 16 Mar 2022 07:23:00 +0800 +Subject: drm/mediatek: Fix mtk_cec_mask() + +From: Miles Chen + +[ Upstream commit 2c5d69b0a141e1e98febe3111e6f4fd8420493a5 ] + +In current implementation, mtk_cec_mask() writes val into target register +and ignores the mask. After talking to our hdmi experts, mtk_cec_mask() +should read a register, clean only mask bits, and update (val | mask) bits +to the register. + +Link: https://patchwork.kernel.org/project/linux-mediatek/patch/20220315232301.2434-1-miles.chen@mediatek.com/ +Fixes: 8f83f26891e1 ("drm/mediatek: Add HDMI support") +Signed-off-by: Miles Chen +Reviewed-by: AngeloGioacchino Del Regno +Reviewed-by: Matthias Brugger +Cc: Zhiqiang Lin +Cc: CK Hu +Cc: Matthias Brugger +Cc: AngeloGioacchino Del Regno +Signed-off-by: Chun-Kuang Hu +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/mediatek/mtk_cec.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/gpu/drm/mediatek/mtk_cec.c b/drivers/gpu/drm/mediatek/mtk_cec.c +index 7a3eb8c17ef9..4e5482986dc2 100644 +--- a/drivers/gpu/drm/mediatek/mtk_cec.c ++++ b/drivers/gpu/drm/mediatek/mtk_cec.c +@@ -91,7 +91,7 @@ static void mtk_cec_mask(struct mtk_cec *cec, unsigned int offset, + u32 tmp = readl(cec->regs + offset) & ~mask; + + tmp |= val & mask; +- writel(val, cec->regs + offset); ++ writel(tmp, cec->regs + offset); + } + + void mtk_cec_set_hpd_event(struct device *dev, +-- +2.35.1 + diff --git a/queue-4.9/drm-msm-dsi-fix-error-checks-and-return-values-for-d.patch b/queue-4.9/drm-msm-dsi-fix-error-checks-and-return-values-for-d.patch new file mode 100644 index 00000000000..6b72bb3a752 --- /dev/null +++ b/queue-4.9/drm-msm-dsi-fix-error-checks-and-return-values-for-d.patch @@ -0,0 +1,85 @@ +From 062b8bbffe6815e668419fa70ef3416833d7e1dc Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 2 Apr 2022 02:11:04 +0300 +Subject: drm/msm/dsi: fix error checks and return values for DSI xmit + functions + +From: Dmitry Baryshkov + +[ Upstream commit f0e7e9ed379c012c4d6b09a09b868accc426223c ] + +As noticed by Dan ([1] an the followup thread) there are multiple issues +with the return values for MSM DSI command transmission callback. In +the error case it can easily return a positive value when it should +have returned a proper error code. + +This commits attempts to fix these issues both in TX and in RX paths. + +[1]: https://lore.kernel.org/linux-arm-msm/20211001123617.GH2283@kili/ + +Fixes: a689554ba6ed ("drm/msm: Initial add DSI connector support") +Reported-by: Dan Carpenter +Signed-off-by: Dmitry Baryshkov +Reviewed-by: Abhinav Kumar +Tested-by: Marijn Suijten +Patchwork: https://patchwork.freedesktop.org/patch/480501/ +Link: https://lore.kernel.org/r/20220401231104.967193-1-dmitry.baryshkov@linaro.org +Signed-off-by: Dmitry Baryshkov +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/msm/dsi/dsi_host.c | 21 ++++++++++++++------- + 1 file changed, 14 insertions(+), 7 deletions(-) + +diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c b/drivers/gpu/drm/msm/dsi/dsi_host.c +index 246336a9f47d..bea4969900ab 100644 +--- a/drivers/gpu/drm/msm/dsi/dsi_host.c ++++ b/drivers/gpu/drm/msm/dsi/dsi_host.c +@@ -1240,10 +1240,10 @@ static int dsi_cmds2buf_tx(struct msm_dsi_host *msm_host, + dsi_get_bpp(msm_host->format) / 8; + + len = dsi_cmd_dma_add(msm_host, msg); +- if (!len) { ++ if (len < 0) { + pr_err("%s: failed to add cmd type = 0x%x\n", + __func__, msg->type); +- return -EINVAL; ++ return len; + } + + /* for video mode, do not send cmds more than +@@ -1262,10 +1262,14 @@ static int dsi_cmds2buf_tx(struct msm_dsi_host *msm_host, + } + + ret = dsi_cmd_dma_tx(msm_host, len); +- if (ret < len) { +- pr_err("%s: cmd dma tx failed, type=0x%x, data0=0x%x, len=%d\n", +- __func__, msg->type, (*(u8 *)(msg->tx_buf)), len); +- return -ECOMM; ++ if (ret < 0) { ++ pr_err("%s: cmd dma tx failed, type=0x%x, data0=0x%x, len=%d, ret=%d\n", ++ __func__, msg->type, (*(u8 *)(msg->tx_buf)), len, ret); ++ return ret; ++ } else if (ret < len) { ++ pr_err("%s: cmd dma tx failed, type=0x%x, data0=0x%x, ret=%d len=%d\n", ++ __func__, msg->type, (*(u8 *)(msg->tx_buf)), ret, len); ++ return -EIO; + } + + return len; +@@ -1979,9 +1983,12 @@ int msm_dsi_host_cmd_rx(struct mipi_dsi_host *host, + } + + ret = dsi_cmds2buf_tx(msm_host, msg); +- if (ret < msg->tx_len) { ++ if (ret < 0) { + pr_err("%s: Read cmd Tx failed, %d\n", __func__, ret); + return ret; ++ } else if (ret < msg->tx_len) { ++ pr_err("%s: Read cmd Tx failed, too short: %d\n", __func__, ret); ++ return -ECOMM; + } + + /* +-- +2.35.1 + diff --git a/queue-4.9/drm-msm-hdmi-check-return-value-after-calling-platfo.patch b/queue-4.9/drm-msm-hdmi-check-return-value-after-calling-platfo.patch new file mode 100644 index 00000000000..ba53dd8237e --- /dev/null +++ b/queue-4.9/drm-msm-hdmi-check-return-value-after-calling-platfo.patch @@ -0,0 +1,42 @@ +From 8a51a9c2b9ff246982524669c7cef9b3d742e57a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 11:22:27 +0800 +Subject: drm/msm/hdmi: check return value after calling + platform_get_resource_byname() + +From: Yang Yingliang + +[ Upstream commit a36e506711548df923ceb7ec9f6001375be799a5 ] + +It will cause null-ptr-deref if platform_get_resource_byname() returns NULL, +we need check the return value. + +Fixes: c6a57a50ad56 ("drm/msm/hdmi: add hdmi hdcp support (V3)") +Signed-off-by: Yang Yingliang +Reviewed-by: Dmitry Baryshkov +Patchwork: https://patchwork.freedesktop.org/patch/482992/ +Link: https://lore.kernel.org/r/20220422032227.2991553-1-yangyingliang@huawei.com +Signed-off-by: Dmitry Baryshkov +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/msm/hdmi/hdmi.c | 4 ++++ + 1 file changed, 4 insertions(+) + +diff --git a/drivers/gpu/drm/msm/hdmi/hdmi.c b/drivers/gpu/drm/msm/hdmi/hdmi.c +index a968cad509c2..48ab46726707 100644 +--- a/drivers/gpu/drm/msm/hdmi/hdmi.c ++++ b/drivers/gpu/drm/msm/hdmi/hdmi.c +@@ -148,6 +148,10 @@ static struct hdmi *msm_hdmi_init(struct platform_device *pdev) + /* HDCP needs physical address of hdmi register */ + res = platform_get_resource_byname(pdev, IORESOURCE_MEM, + config->mmio_name); ++ if (!res) { ++ ret = -EINVAL; ++ goto fail; ++ } + hdmi->mmio_phy_addr = res->start; + + hdmi->qfprom_mmio = msm_ioremap(pdev, +-- +2.35.1 + diff --git a/queue-4.9/drm-msm-return-an-error-pointer-in-msm_gem_prime_get.patch b/queue-4.9/drm-msm-return-an-error-pointer-in-msm_gem_prime_get.patch new file mode 100644 index 00000000000..d5b3974be8c --- /dev/null +++ b/queue-4.9/drm-msm-return-an-error-pointer-in-msm_gem_prime_get.patch @@ -0,0 +1,40 @@ +From 18757da828c993a8c58ff9ddfb0e25892dc23cb3 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 5 May 2022 13:28:05 +0300 +Subject: drm/msm: return an error pointer in msm_gem_prime_get_sg_table() + +From: Dan Carpenter + +[ Upstream commit cf575e31611eb6dccf08fad02e57e35b2187704d ] + +The msm_gem_prime_get_sg_table() needs to return error pointers on +error. This is called from drm_gem_map_dma_buf() and returning a +NULL will lead to a crash in that function. + +Fixes: ac45146733b0 ("drm/msm: fix msm_gem_prime_get_sg_table()") +Signed-off-by: Dan Carpenter +Reviewed-by: Dmitry Baryshkov +Patchwork: https://patchwork.freedesktop.org/patch/485023/ +Link: https://lore.kernel.org/r/YnOmtS5tfENywR9m@kili +Signed-off-by: Dmitry Baryshkov +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/msm/msm_gem_prime.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/gpu/drm/msm/msm_gem_prime.c b/drivers/gpu/drm/msm/msm_gem_prime.c +index 13403c6da6c7..7e4664968106 100644 +--- a/drivers/gpu/drm/msm/msm_gem_prime.c ++++ b/drivers/gpu/drm/msm/msm_gem_prime.c +@@ -26,7 +26,7 @@ struct sg_table *msm_gem_prime_get_sg_table(struct drm_gem_object *obj) + int npages = obj->size >> PAGE_SHIFT; + + if (WARN_ON(!msm_obj->pages)) /* should have already pinned! */ +- return NULL; ++ return ERR_PTR(-ENOMEM); + + return drm_prime_pages_to_sg(msm_obj->pages, npages); + } +-- +2.35.1 + diff --git a/queue-4.9/drm-rockchip-vop-fix-possible-null-ptr-deref-in-vop_.patch b/queue-4.9/drm-rockchip-vop-fix-possible-null-ptr-deref-in-vop_.patch new file mode 100644 index 00000000000..5dc97869978 --- /dev/null +++ b/queue-4.9/drm-rockchip-vop-fix-possible-null-ptr-deref-in-vop_.patch @@ -0,0 +1,41 @@ +From 16c5419f3c5188d59506f13173d45ab7a79e6187 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 11:28:54 +0800 +Subject: drm/rockchip: vop: fix possible null-ptr-deref in vop_bind() + +From: Yang Yingliang + +[ Upstream commit f8c242908ad15bbd604d3bcb54961b7d454c43f8 ] + +It will cause null-ptr-deref in resource_size(), if platform_get_resource() +returns NULL, move calling resource_size() after devm_ioremap_resource() that +will check 'res' to avoid null-ptr-deref. + +Fixes: 2048e3286f34 ("drm: rockchip: Add basic drm driver") +Signed-off-by: Yang Yingliang +Signed-off-by: Heiko Stuebner +Link: https://patchwork.freedesktop.org/patch/msgid/20220422032854.2995175-1-yangyingliang@huawei.com +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c +index 5bed63eee5f0..050f9a59ed54 100644 +--- a/drivers/gpu/drm/rockchip/rockchip_drm_vop.c ++++ b/drivers/gpu/drm/rockchip/rockchip_drm_vop.c +@@ -1524,10 +1524,10 @@ static int vop_bind(struct device *dev, struct device *master, void *data) + vop_win_init(vop); + + res = platform_get_resource(pdev, IORESOURCE_MEM, 0); +- vop->len = resource_size(res); + vop->regs = devm_ioremap_resource(dev, res); + if (IS_ERR(vop->regs)) + return PTR_ERR(vop->regs); ++ vop->len = resource_size(res); + + vop->regsbak = devm_kzalloc(dev, vop->len, GFP_KERNEL); + if (!vop->regsbak) +-- +2.35.1 + diff --git a/queue-4.9/drm-virtio-fix-null-pointer-dereference-in-virtio_gp.patch b/queue-4.9/drm-virtio-fix-null-pointer-dereference-in-virtio_gp.patch new file mode 100644 index 00000000000..258164cf704 --- /dev/null +++ b/queue-4.9/drm-virtio-fix-null-pointer-dereference-in-virtio_gp.patch @@ -0,0 +1,88 @@ +From 4f77d444e856729087b3d65a75623ef61443ca79 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 22 Mar 2022 17:17:30 +0800 +Subject: drm/virtio: fix NULL pointer dereference in virtio_gpu_conn_get_modes + +From: Liu Zixian + +[ Upstream commit 194d250cdc4a40ccbd179afd522a9e9846957402 ] + +drm_cvt_mode may return NULL and we should check it. + +This bug is found by syzkaller: + +FAULT_INJECTION stacktrace: +[ 168.567394] FAULT_INJECTION: forcing a failure. +name failslab, interval 1, probability 0, space 0, times 1 +[ 168.567403] CPU: 1 PID: 6425 Comm: syz Kdump: loaded Not tainted 4.19.90-vhulk2201.1.0.h1035.kasan.eulerosv2r10.aarch64 #1 +[ 168.567406] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 +[ 168.567408] Call trace: +[ 168.567414] dump_backtrace+0x0/0x310 +[ 168.567418] show_stack+0x28/0x38 +[ 168.567423] dump_stack+0xec/0x15c +[ 168.567427] should_fail+0x3ac/0x3d0 +[ 168.567437] __should_failslab+0xb8/0x120 +[ 168.567441] should_failslab+0x28/0xc0 +[ 168.567445] kmem_cache_alloc_trace+0x50/0x640 +[ 168.567454] drm_mode_create+0x40/0x90 +[ 168.567458] drm_cvt_mode+0x48/0xc78 +[ 168.567477] virtio_gpu_conn_get_modes+0xa8/0x140 [virtio_gpu] +[ 168.567485] drm_helper_probe_single_connector_modes+0x3a4/0xd80 +[ 168.567492] drm_mode_getconnector+0x2e0/0xa70 +[ 168.567496] drm_ioctl_kernel+0x11c/0x1d8 +[ 168.567514] drm_ioctl+0x558/0x6d0 +[ 168.567522] do_vfs_ioctl+0x160/0xf30 +[ 168.567525] ksys_ioctl+0x98/0xd8 +[ 168.567530] __arm64_sys_ioctl+0x50/0xc8 +[ 168.567536] el0_svc_common+0xc8/0x320 +[ 168.567540] el0_svc_handler+0xf8/0x160 +[ 168.567544] el0_svc+0x10/0x218 + +KASAN stacktrace: +[ 168.567561] BUG: KASAN: null-ptr-deref in virtio_gpu_conn_get_modes+0xb4/0x140 [virtio_gpu] +[ 168.567565] Read of size 4 at addr 0000000000000054 by task syz/6425 +[ 168.567566] +[ 168.567571] CPU: 1 PID: 6425 Comm: syz Kdump: loaded Not tainted 4.19.90-vhulk2201.1.0.h1035.kasan.eulerosv2r10.aarch64 #1 +[ 168.567573] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015 +[ 168.567575] Call trace: +[ 168.567578] dump_backtrace+0x0/0x310 +[ 168.567582] show_stack+0x28/0x38 +[ 168.567586] dump_stack+0xec/0x15c +[ 168.567591] kasan_report+0x244/0x2f0 +[ 168.567594] __asan_load4+0x58/0xb0 +[ 168.567607] virtio_gpu_conn_get_modes+0xb4/0x140 [virtio_gpu] +[ 168.567612] drm_helper_probe_single_connector_modes+0x3a4/0xd80 +[ 168.567617] drm_mode_getconnector+0x2e0/0xa70 +[ 168.567621] drm_ioctl_kernel+0x11c/0x1d8 +[ 168.567624] drm_ioctl+0x558/0x6d0 +[ 168.567628] do_vfs_ioctl+0x160/0xf30 +[ 168.567632] ksys_ioctl+0x98/0xd8 +[ 168.567636] __arm64_sys_ioctl+0x50/0xc8 +[ 168.567641] el0_svc_common+0xc8/0x320 +[ 168.567645] el0_svc_handler+0xf8/0x160 +[ 168.567649] el0_svc+0x10/0x218 + +Signed-off-by: Liu Zixian +Link: http://patchwork.freedesktop.org/patch/msgid/20220322091730.1653-1-liuzixian4@huawei.com +Signed-off-by: Gerd Hoffmann +Signed-off-by: Sasha Levin +--- + drivers/gpu/drm/virtio/virtgpu_display.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/gpu/drm/virtio/virtgpu_display.c b/drivers/gpu/drm/virtio/virtgpu_display.c +index 58048709c34e..1e528f13959d 100644 +--- a/drivers/gpu/drm/virtio/virtgpu_display.c ++++ b/drivers/gpu/drm/virtio/virtgpu_display.c +@@ -184,6 +184,8 @@ static int virtio_gpu_conn_get_modes(struct drm_connector *connector) + DRM_DEBUG("add mode: %dx%d\n", width, height); + mode = drm_cvt_mode(connector->dev, width, height, 60, + false, false, false); ++ if (!mode) ++ return count; + mode->type |= DRM_MODE_TYPE_PREFERRED; + drm_mode_probed_add(connector, mode); + count++; +-- +2.35.1 + diff --git a/queue-4.9/eth-tg3-silence-the-gcc-12-array-bounds-warning.patch b/queue-4.9/eth-tg3-silence-the-gcc-12-array-bounds-warning.patch new file mode 100644 index 00000000000..d82ae114c04 --- /dev/null +++ b/queue-4.9/eth-tg3-silence-the-gcc-12-array-bounds-warning.patch @@ -0,0 +1,47 @@ +From b59b22268a4ea09a1d960171b41228cdd64e2f90 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 20 May 2022 12:56:05 -0700 +Subject: eth: tg3: silence the GCC 12 array-bounds warning +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Jakub Kicinski + +[ Upstream commit 9dec850fd7c210a04b4707df8e6c95bfafdd6a4b ] + +GCC 12 currently generates a rather inconsistent warning: + +drivers/net/ethernet/broadcom/tg3.c:17795:51: warning: array subscript 5 is above array bounds of ‘struct tg3_napi[5]’ [-Warray-bounds] +17795 | struct tg3_napi *tnapi = &tp->napi[i]; + | ~~~~~~~~^~~ + +i is guaranteed < tp->irq_max which in turn is either 1 or 5. +There are more loops like this one in the driver, but strangely +GCC 12 dislikes only this single one. + +Silence this silliness for now. + +Signed-off-by: Jakub Kicinski +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + drivers/net/ethernet/broadcom/Makefile | 5 +++++ + 1 file changed, 5 insertions(+) + +diff --git a/drivers/net/ethernet/broadcom/Makefile b/drivers/net/ethernet/broadcom/Makefile +index 79f2372c66ec..4211c6cd6b35 100644 +--- a/drivers/net/ethernet/broadcom/Makefile ++++ b/drivers/net/ethernet/broadcom/Makefile +@@ -15,3 +15,8 @@ obj-$(CONFIG_BGMAC_BCMA) += bgmac-bcma.o bgmac-bcma-mdio.o + obj-$(CONFIG_BGMAC_PLATFORM) += bgmac-platform.o + obj-$(CONFIG_SYSTEMPORT) += bcmsysport.o + obj-$(CONFIG_BNXT) += bnxt/ ++ ++# FIXME: temporarily silence -Warray-bounds on non W=1+ builds ++ifndef KBUILD_EXTRA_WARN ++CFLAGS_tg3.o += -Wno-array-bounds ++endif +-- +2.35.1 + diff --git a/queue-4.9/fat-add-ratelimit-to-fat-_ent_bread.patch b/queue-4.9/fat-add-ratelimit-to-fat-_ent_bread.patch new file mode 100644 index 00000000000..740abf95002 --- /dev/null +++ b/queue-4.9/fat-add-ratelimit-to-fat-_ent_bread.patch @@ -0,0 +1,50 @@ +From b1b717c5976b96f1102ffb1bf0ced8c56d731bd2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 29 Apr 2022 14:38:02 -0700 +Subject: fat: add ratelimit to fat*_ent_bread() + +From: OGAWA Hirofumi + +[ Upstream commit 183c3237c928109d2008c0456dff508baf692b20 ] + +fat*_ent_bread() can be the cause of too many report on I/O error path. +So use fat_msg_ratelimit() instead. + +Link: https://lkml.kernel.org/r/87bkxogfeq.fsf@mail.parknet.co.jp +Signed-off-by: OGAWA Hirofumi +Reported-by: qianfan +Tested-by: qianfan +Signed-off-by: Andrew Morton +Signed-off-by: Sasha Levin +--- + fs/fat/fatent.c | 7 ++++--- + 1 file changed, 4 insertions(+), 3 deletions(-) + +diff --git a/fs/fat/fatent.c b/fs/fat/fatent.c +index 0129d4d07a54..b0b1a71c07b7 100644 +--- a/fs/fat/fatent.c ++++ b/fs/fat/fatent.c +@@ -92,7 +92,8 @@ static int fat12_ent_bread(struct super_block *sb, struct fat_entry *fatent, + err_brelse: + brelse(bhs[0]); + err: +- fat_msg(sb, KERN_ERR, "FAT read failed (blocknr %llu)", (llu)blocknr); ++ fat_msg_ratelimit(sb, KERN_ERR, "FAT read failed (blocknr %llu)", ++ (llu)blocknr); + return -EIO; + } + +@@ -105,8 +106,8 @@ static int fat_ent_bread(struct super_block *sb, struct fat_entry *fatent, + fatent->fat_inode = MSDOS_SB(sb)->fat_inode; + fatent->bhs[0] = sb_bread(sb, blocknr); + if (!fatent->bhs[0]) { +- fat_msg(sb, KERN_ERR, "FAT read failed (blocknr %llu)", +- (llu)blocknr); ++ fat_msg_ratelimit(sb, KERN_ERR, "FAT read failed (blocknr %llu)", ++ (llu)blocknr); + return -EIO; + } + fatent->nr_bhs = 1; +-- +2.35.1 + diff --git a/queue-4.9/fs-jfs-fix-possible-null-pointer-dereference-in-dbfr.patch b/queue-4.9/fs-jfs-fix-possible-null-pointer-dereference-in-dbfr.patch new file mode 100644 index 00000000000..71c30a7bd44 --- /dev/null +++ b/queue-4.9/fs-jfs-fix-possible-null-pointer-dereference-in-dbfr.patch @@ -0,0 +1,59 @@ +From 46f129f75b3574feb3fed1101b27485e18a0ce7f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 11 Apr 2022 18:45:34 +0800 +Subject: fs: jfs: fix possible NULL pointer dereference in dbFree() + +From: Zixuan Fu + +[ Upstream commit 0d4837fdb796f99369cf7691d33de1b856bcaf1f ] + +In our fault-injection testing, the variable "nblocks" in dbFree() can be +zero when kmalloc_array() fails in dtSearch(). In this case, the variable + "mp" in dbFree() would be NULL and then it is dereferenced in +"write_metapage(mp)". + +The failure log is listed as follows: + +[ 13.824137] BUG: kernel NULL pointer dereference, address: 0000000000000020 +... +[ 13.827416] RIP: 0010:dbFree+0x5f7/0x910 [jfs] +[ 13.834341] Call Trace: +[ 13.834540] +[ 13.834713] txFreeMap+0x7b4/0xb10 [jfs] +[ 13.835038] txUpdateMap+0x311/0x650 [jfs] +[ 13.835375] jfs_lazycommit+0x5f2/0xc70 [jfs] +[ 13.835726] ? sched_dynamic_update+0x1b0/0x1b0 +[ 13.836092] kthread+0x3c2/0x4a0 +[ 13.836355] ? txLockFree+0x160/0x160 [jfs] +[ 13.836763] ? kthread_unuse_mm+0x160/0x160 +[ 13.837106] ret_from_fork+0x1f/0x30 +[ 13.837402] +... + +This patch adds a NULL check of "mp" before "write_metapage(mp)" is called. + +Reported-by: TOTE Robot +Signed-off-by: Zixuan Fu +Signed-off-by: Dave Kleikamp +Signed-off-by: Sasha Levin +--- + fs/jfs/jfs_dmap.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/fs/jfs/jfs_dmap.c b/fs/jfs/jfs_dmap.c +index 6dac48e29d28..a07fbb60ac3c 100644 +--- a/fs/jfs/jfs_dmap.c ++++ b/fs/jfs/jfs_dmap.c +@@ -398,7 +398,8 @@ int dbFree(struct inode *ip, s64 blkno, s64 nblocks) + } + + /* write the last buffer. */ +- write_metapage(mp); ++ if (mp) ++ write_metapage(mp); + + IREAD_UNLOCK(ipbmap); + +-- +2.35.1 + diff --git a/queue-4.9/hid-hid-led-fix-maximum-brightness-for-dream-cheeky.patch b/queue-4.9/hid-hid-led-fix-maximum-brightness-for-dream-cheeky.patch new file mode 100644 index 00000000000..2a810865e98 --- /dev/null +++ b/queue-4.9/hid-hid-led-fix-maximum-brightness-for-dream-cheeky.patch @@ -0,0 +1,38 @@ +From 4cd6cd846bb21ff9d3d16d7d5336d4bc7620f21d Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 13 Mar 2022 19:48:18 +0000 +Subject: HID: hid-led: fix maximum brightness for Dream Cheeky + +From: Jonathan Teh + +[ Upstream commit 116c3f4a78ebe478d5ad5a038baf931e93e7d748 ] + +Increase maximum brightness for Dream Cheeky to 63. Emperically +determined based on testing in kernel 4.4 on this device: + +Bus 003 Device 002: ID 1d34:0004 Dream Cheeky Webmail Notifier + +Fixes: 6c7ad07e9e05 ("HID: migrate USB LED driver from usb misc to hid") +Signed-off-by: Jonathan Teh +Signed-off-by: Jiri Kosina +Signed-off-by: Sasha Levin +--- + drivers/hid/hid-led.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/hid/hid-led.c b/drivers/hid/hid-led.c +index d3e1ab162f7c..7fc5982a0ca4 100644 +--- a/drivers/hid/hid-led.c ++++ b/drivers/hid/hid-led.c +@@ -369,7 +369,7 @@ static const struct hidled_config hidled_configs[] = { + .type = DREAM_CHEEKY, + .name = "Dream Cheeky Webmail Notifier", + .short_name = "dream_cheeky", +- .max_brightness = 31, ++ .max_brightness = 63, + .num_leds = 1, + .report_size = 9, + .report_type = RAW_REQUEST, +-- +2.35.1 + diff --git a/queue-4.9/inotify-show-inotify-mask-flags-in-proc-fdinfo.patch b/queue-4.9/inotify-show-inotify-mask-flags-in-proc-fdinfo.patch new file mode 100644 index 00000000000..e0e8def3cf9 --- /dev/null +++ b/queue-4.9/inotify-show-inotify-mask-flags-in-proc-fdinfo.patch @@ -0,0 +1,86 @@ +From 9b6fa061775617616f77651e7851f9691cb2dccf Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 15:03:12 +0300 +Subject: inotify: show inotify mask flags in proc fdinfo + +From: Amir Goldstein + +[ Upstream commit a32e697cda27679a0327ae2cafdad8c7170f548f ] + +The inotify mask flags IN_ONESHOT and IN_EXCL_UNLINK are not "internal +to kernel" and should be exposed in procfs fdinfo so CRIU can restore +them. + +Fixes: 6933599697c9 ("inotify: hide internal kernel bits from fdinfo") +Link: https://lore.kernel.org/r/20220422120327.3459282-2-amir73il@gmail.com +Signed-off-by: Amir Goldstein +Signed-off-by: Jan Kara +Signed-off-by: Sasha Levin +--- + fs/notify/fdinfo.c | 11 ++--------- + fs/notify/inotify/inotify.h | 12 ++++++++++++ + fs/notify/inotify/inotify_user.c | 2 +- + 3 files changed, 15 insertions(+), 10 deletions(-) + +diff --git a/fs/notify/fdinfo.c b/fs/notify/fdinfo.c +index fd98e5100cab..317b7e7eb2e7 100644 +--- a/fs/notify/fdinfo.c ++++ b/fs/notify/fdinfo.c +@@ -83,16 +83,9 @@ static void inotify_fdinfo(struct seq_file *m, struct fsnotify_mark *mark) + inode_mark = container_of(mark, struct inotify_inode_mark, fsn_mark); + inode = igrab(mark->inode); + if (inode) { +- /* +- * IN_ALL_EVENTS represents all of the mask bits +- * that we expose to userspace. There is at +- * least one bit (FS_EVENT_ON_CHILD) which is +- * used only internally to the kernel. +- */ +- u32 mask = mark->mask & IN_ALL_EVENTS; +- seq_printf(m, "inotify wd:%x ino:%lx sdev:%x mask:%x ignored_mask:%x ", ++ seq_printf(m, "inotify wd:%x ino:%lx sdev:%x mask:%x ignored_mask:0 ", + inode_mark->wd, inode->i_ino, inode->i_sb->s_dev, +- mask, mark->ignored_mask); ++ inotify_mark_user_mask(mark)); + show_mark_fhandle(m, inode); + seq_putc(m, '\n'); + iput(inode); +diff --git a/fs/notify/inotify/inotify.h b/fs/notify/inotify/inotify.h +index ed855ef6f077..b0440287d7dd 100644 +--- a/fs/notify/inotify/inotify.h ++++ b/fs/notify/inotify/inotify.h +@@ -20,6 +20,18 @@ static inline struct inotify_event_info *INOTIFY_E(struct fsnotify_event *fse) + return container_of(fse, struct inotify_event_info, fse); + } + ++/* ++ * INOTIFY_USER_FLAGS represents all of the mask bits that we expose to ++ * userspace. There is at least one bit (FS_EVENT_ON_CHILD) which is ++ * used only internally to the kernel. ++ */ ++#define INOTIFY_USER_MASK (IN_ALL_EVENTS | IN_ONESHOT | IN_EXCL_UNLINK) ++ ++static inline __u32 inotify_mark_user_mask(struct fsnotify_mark *fsn_mark) ++{ ++ return fsn_mark->mask & INOTIFY_USER_MASK; ++} ++ + extern void inotify_ignored_and_remove_idr(struct fsnotify_mark *fsn_mark, + struct fsnotify_group *group); + extern int inotify_handle_event(struct fsnotify_group *group, +diff --git a/fs/notify/inotify/inotify_user.c b/fs/notify/inotify/inotify_user.c +index 69d1ea3d292a..bb60bf1527e4 100644 +--- a/fs/notify/inotify/inotify_user.c ++++ b/fs/notify/inotify/inotify_user.c +@@ -97,7 +97,7 @@ static inline __u32 inotify_arg_to_mask(u32 arg) + mask = (FS_IN_IGNORED | FS_EVENT_ON_CHILD | FS_UNMOUNT); + + /* mask off the flags used to open the fd */ +- mask |= (arg & (IN_ALL_EVENTS | IN_ONESHOT | IN_EXCL_UNLINK)); ++ mask |= (arg & INOTIFY_USER_MASK); + + return mask; + } +-- +2.35.1 + diff --git a/queue-4.9/input-sparcspkr-fix-refcount-leak-in-bbc_beep_probe.patch b/queue-4.9/input-sparcspkr-fix-refcount-leak-in-bbc_beep_probe.patch new file mode 100644 index 00000000000..4d9178f3e08 --- /dev/null +++ b/queue-4.9/input-sparcspkr-fix-refcount-leak-in-bbc_beep_probe.patch @@ -0,0 +1,38 @@ +From 5a98ff656c419817bf73101a9553f11ea4085656 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 16 May 2022 14:55:55 -0700 +Subject: Input: sparcspkr - fix refcount leak in bbc_beep_probe + +From: Miaoqian Lin + +[ Upstream commit c8994b30d71d64d5dcc9bc0edbfdf367171aa96f ] + +of_find_node_by_path() calls of_find_node_opts_by_path(), +which returns a node pointer with refcount +incremented, we should use of_node_put() on it when done. +Add missing of_node_put() to avoid refcount leak. + +Fixes: 9c1a5077fdca ("input: Rewrite sparcspkr device probing.") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220516081018.42728-1-linmq006@gmail.com +Signed-off-by: Dmitry Torokhov +Signed-off-by: Sasha Levin +--- + drivers/input/misc/sparcspkr.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/input/misc/sparcspkr.c b/drivers/input/misc/sparcspkr.c +index 4a5afc7fe96e..f6e1f38267d9 100644 +--- a/drivers/input/misc/sparcspkr.c ++++ b/drivers/input/misc/sparcspkr.c +@@ -204,6 +204,7 @@ static int bbc_beep_probe(struct platform_device *op) + + info = &state->u.bbc; + info->clock_freq = of_getintprop_default(dp, "clock-frequency", 0); ++ of_node_put(dp); + if (!info->clock_freq) + goto out_free; + +-- +2.35.1 + diff --git a/queue-4.9/iommu-amd-increase-timeout-waiting-for-ga-log-enable.patch b/queue-4.9/iommu-amd-increase-timeout-waiting-for-ga-log-enable.patch new file mode 100644 index 00000000000..6272085c5cd --- /dev/null +++ b/queue-4.9/iommu-amd-increase-timeout-waiting-for-ga-log-enable.patch @@ -0,0 +1,54 @@ +From 04d5f7d5d0ab881b909fb6f94dd773d36760c985 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 20 May 2022 12:22:14 +0200 +Subject: iommu/amd: Increase timeout waiting for GA log enablement +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Joerg Roedel + +[ Upstream commit 42bb5aa043382f09bef2cc33b8431be867c70f8e ] + +On some systems it can take a long time for the hardware to enable the +GA log of the AMD IOMMU. The current wait time is only 0.1ms, but +testing showed that it can take up to 14ms for the GA log to enter +running state after it has been enabled. + +Sometimes the long delay happens when booting the system, sometimes +only on resume. Adjust the timeout accordingly to not print a warning +when hardware takes a longer than usual. + +There has already been an attempt to fix this with commit + + 9b45a7738eec ("iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()") + +But that commit was based on some wrong math and did not fix the issue +in all cases. + +Cc: "D. Ziegfeld" +Cc: Jörg-Volker Peetz +Fixes: 8bda0cfbdc1a ("iommu/amd: Detect and initialize guest vAPIC log") +Signed-off-by: Joerg Roedel +Link: https://lore.kernel.org/r/20220520102214.12563-1-joro@8bytes.org +Signed-off-by: Sasha Levin +--- + drivers/iommu/amd_iommu_init.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/iommu/amd_iommu_init.c b/drivers/iommu/amd_iommu_init.c +index 45c809f3d24f..03bf538eabda 100644 +--- a/drivers/iommu/amd_iommu_init.c ++++ b/drivers/iommu/amd_iommu_init.c +@@ -86,7 +86,7 @@ + #define ACPI_DEVFLAG_LINT1 0x80 + #define ACPI_DEVFLAG_ATSDIS 0x10000000 + +-#define LOOP_TIMEOUT 100000 ++#define LOOP_TIMEOUT 2000000 + /* + * ACPI table definitions + * +-- +2.35.1 + diff --git a/queue-4.9/ipmi-ssif-check-for-null-msg-when-handling-events-an.patch b/queue-4.9/ipmi-ssif-check-for-null-msg-when-handling-events-an.patch new file mode 100644 index 00000000000..2c91efc129c --- /dev/null +++ b/queue-4.9/ipmi-ssif-check-for-null-msg-when-handling-events-an.patch @@ -0,0 +1,75 @@ +From 78e972fb163176bc185b0fd7ecdd23c7b3f25260 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 1 Apr 2022 07:44:53 -0500 +Subject: ipmi:ssif: Check for NULL msg when handling events and messages + +From: Corey Minyard + +[ Upstream commit 7602b957e2404e5f98d9a40b68f1fd27f0028712 ] + +Even though it's not possible to get into the SSIF_GETTING_MESSAGES and +SSIF_GETTING_EVENTS states without a valid message in the msg field, +it's probably best to be defensive here and check and print a log, since +that means something else went wrong. + +Also add a default clause to that switch statement to release the lock +and print a log, in case the state variable gets messed up somehow. + +Reported-by: Haowen Bai +Signed-off-by: Corey Minyard +Signed-off-by: Sasha Levin +--- + drivers/char/ipmi/ipmi_ssif.c | 23 +++++++++++++++++++++++ + 1 file changed, 23 insertions(+) + +diff --git a/drivers/char/ipmi/ipmi_ssif.c b/drivers/char/ipmi/ipmi_ssif.c +index a4ef9a6bd367..45117728e735 100644 +--- a/drivers/char/ipmi/ipmi_ssif.c ++++ b/drivers/char/ipmi/ipmi_ssif.c +@@ -812,6 +812,14 @@ static void msg_done_handler(struct ssif_info *ssif_info, int result, + break; + + case SSIF_GETTING_EVENTS: ++ if (!msg) { ++ /* Should never happen, but just in case. */ ++ dev_warn(&ssif_info->client->dev, ++ "No message set while getting events\n"); ++ ipmi_ssif_unlock_cond(ssif_info, flags); ++ break; ++ } ++ + if ((result < 0) || (len < 3) || (msg->rsp[2] != 0)) { + /* Error getting event, probably done. */ + msg->done(msg); +@@ -835,6 +843,14 @@ static void msg_done_handler(struct ssif_info *ssif_info, int result, + break; + + case SSIF_GETTING_MESSAGES: ++ if (!msg) { ++ /* Should never happen, but just in case. */ ++ dev_warn(&ssif_info->client->dev, ++ "No message set while getting messages\n"); ++ ipmi_ssif_unlock_cond(ssif_info, flags); ++ break; ++ } ++ + if ((result < 0) || (len < 3) || (msg->rsp[2] != 0)) { + /* Error getting event, probably done. */ + msg->done(msg); +@@ -857,6 +873,13 @@ static void msg_done_handler(struct ssif_info *ssif_info, int result, + deliver_recv_msg(ssif_info, msg); + } + break; ++ ++ default: ++ /* Should never happen, but just in case. */ ++ dev_warn(&ssif_info->client->dev, ++ "Invalid state in message done handling: %d\n", ++ ssif_info->ssif_state); ++ ipmi_ssif_unlock_cond(ssif_info, flags); + } + + flags = ipmi_ssif_lock_cond(ssif_info, &oflags); +-- +2.35.1 + diff --git a/queue-4.9/ipv6-don-t-send-rs-packets-to-the-interface-of-arphr.patch b/queue-4.9/ipv6-don-t-send-rs-packets-to-the-interface-of-arphr.patch new file mode 100644 index 00000000000..eb10252b572 --- /dev/null +++ b/queue-4.9/ipv6-don-t-send-rs-packets-to-the-interface-of-arphr.patch @@ -0,0 +1,50 @@ +From 9be721a828bb39d2003f563aee6842aa5763e2fd Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 29 Apr 2022 13:38:02 +0800 +Subject: ipv6: Don't send rs packets to the interface of ARPHRD_TUNNEL + +From: jianghaoran + +[ Upstream commit b52e1cce31ca721e937d517411179f9196ee6135 ] + +ARPHRD_TUNNEL interface can't process rs packets +and will generate TX errors + +ex: +ip tunnel add ethn mode ipip local 192.168.1.1 remote 192.168.1.2 +ifconfig ethn x.x.x.x + +ethn: flags=209 mtu 1480 + inet x.x.x.x netmask 255.255.255.255 destination x.x.x.x + inet6 fe80::5efe:ac1e:3cdb prefixlen 64 scopeid 0x20 + tunnel txqueuelen 1000 (IPIP Tunnel) + RX packets 0 bytes 0 (0.0 B) + RX errors 0 dropped 0 overruns 0 frame 0 + TX packets 0 bytes 0 (0.0 B) + TX errors 3 dropped 0 overruns 0 carrier 0 collisions 0 + +Signed-off-by: jianghaoran +Link: https://lore.kernel.org/r/20220429053802.246681-1-jianghaoran@kylinos.cn +Signed-off-by: Jakub Kicinski +Signed-off-by: Sasha Levin +--- + net/ipv6/addrconf.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/net/ipv6/addrconf.c b/net/ipv6/addrconf.c +index 30ca73c78125..02f62253a835 100644 +--- a/net/ipv6/addrconf.c ++++ b/net/ipv6/addrconf.c +@@ -3993,7 +3993,8 @@ static void addrconf_dad_completed(struct inet6_ifaddr *ifp, bool bump_id) + send_rs = send_mld && + ipv6_accept_ra(ifp->idev) && + ifp->idev->cnf.rtr_solicits != 0 && +- (dev->flags&IFF_LOOPBACK) == 0; ++ (dev->flags & IFF_LOOPBACK) == 0 && ++ (dev->type != ARPHRD_TUNNEL); + read_unlock_bh(&ifp->idev->lock); + + /* While dad is in progress mld report's source address is in6_addrany. +-- +2.35.1 + diff --git a/queue-4.9/ipw2x00-fix-potential-null-dereference-in-libipw_xmi.patch b/queue-4.9/ipw2x00-fix-potential-null-dereference-in-libipw_xmi.patch new file mode 100644 index 00000000000..ff113798642 --- /dev/null +++ b/queue-4.9/ipw2x00-fix-potential-null-dereference-in-libipw_xmi.patch @@ -0,0 +1,36 @@ +From 4afc781333869375c9b938df1f22a700a2bede5e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 1 Apr 2022 15:10:54 +0800 +Subject: ipw2x00: Fix potential NULL dereference in libipw_xmit() + +From: Haowen Bai + +[ Upstream commit e8366bbabe1d207cf7c5b11ae50e223ae6fc278b ] + +crypt and crypt->ops could be null, so we need to checking null +before dereference + +Signed-off-by: Haowen Bai +Signed-off-by: Kalle Valo +Link: https://lore.kernel.org/r/1648797055-25730-1-git-send-email-baihaowen@meizu.com +Signed-off-by: Sasha Levin +--- + drivers/net/wireless/intel/ipw2x00/libipw_tx.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/net/wireless/intel/ipw2x00/libipw_tx.c b/drivers/net/wireless/intel/ipw2x00/libipw_tx.c +index e8c039879b05..cb30b3b63635 100644 +--- a/drivers/net/wireless/intel/ipw2x00/libipw_tx.c ++++ b/drivers/net/wireless/intel/ipw2x00/libipw_tx.c +@@ -397,7 +397,7 @@ netdev_tx_t libipw_xmit(struct sk_buff *skb, struct net_device *dev) + + /* Each fragment may need to have room for encryption + * pre/postfix */ +- if (host_encrypt) ++ if (host_encrypt && crypt && crypt->ops) + bytes_per_frag -= crypt->ops->extra_mpdu_prefix_len + + crypt->ops->extra_mpdu_postfix_len; + +-- +2.35.1 + diff --git a/queue-4.9/m68k-math-emu-fix-dependencies-of-math-emulation-sup.patch b/queue-4.9/m68k-math-emu-fix-dependencies-of-math-emulation-sup.patch new file mode 100644 index 00000000000..6c88e68617f --- /dev/null +++ b/queue-4.9/m68k-math-emu-fix-dependencies-of-math-emulation-sup.patch @@ -0,0 +1,56 @@ +From f8e46cd7c3ceb026e77f7ad04656feda70df949c Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 13 May 2022 14:50:28 +0200 +Subject: m68k: math-emu: Fix dependencies of math emulation support + +From: Geert Uytterhoeven + +[ Upstream commit ed6bc6bf0a7d75e80eb1df883c09975ebb74e590 ] + +If CONFIG_M54xx=y, CONFIG_MMU=y, and CONFIG_M68KFPU_EMU=y: + + {standard input}:272: Error: invalid instruction for this architecture; needs 68000 or higher (68000 [68ec000, 68hc000, 68hc001, 68008, 68302, 68306, 68307, 68322, 68356], 68010, 68020 [68k, 68ec020], 68030 [68ec030], 68040 [68ec040], 68060 [68ec060], cpu32 [68330, 68331, 68332, 68333, 68334, 68336, 68340, 68341, 68349, 68360], fidoa [fido]) -- statement `sub.b %d1,%d3' ignored + {standard input}:609: Error: invalid instruction for this architecture; needs 68020 or higher (68020 [68k, 68ec020], 68030 [68ec030], 68040 [68ec040], 68060 [68ec060]) -- statement `bfextu 4(%a1){%d0,#8},%d0' ignored + {standard input}:752: Error: operands mismatch -- statement `mulu.l 4(%a0),%d3:%d0' ignored + {standard input}:1155: Error: operands mismatch -- statement `divu.l %d0,%d3:%d7' ignored + +The math emulation support code is intended for 68020 and higher, and +uses several instructions or instruction modes not available on coldfire +or 68000. + +Originally, the dependency of M68KFPU_EMU on MMU was fine, as MMU +support was only available on 68020 or higher. But this assumption +was broken by the introduction of MMU support for M547x and M548x. + +Drop the dependency on MMU, as the code should work fine on 68020 and up +without MMU (which are not yet supported by Linux, though). +Add dependencies on M68KCLASSIC (to rule out Coldfire) and FPU (kernel +has some type of floating-point support --- be it hardware or software +emulated, to rule out anything below 68020). + +Fixes: 1f7034b9616e6f14 ("m68k: allow ColdFire 547x and 548x CPUs to be built with MMU enabled") +Reported-by: kernel test robot +Signed-off-by: Geert Uytterhoeven +Reviewed-by: Greg Ungerer +Link: https://lore.kernel.org/r/18c34695b7c95107f60ccca82a4ff252f3edf477.1652446117.git.geert@linux-m68k.org +Signed-off-by: Sasha Levin +--- + arch/m68k/Kconfig.cpu | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/m68k/Kconfig.cpu b/arch/m68k/Kconfig.cpu +index d2219f30b78f..2268d19cc915 100644 +--- a/arch/m68k/Kconfig.cpu ++++ b/arch/m68k/Kconfig.cpu +@@ -307,7 +307,7 @@ comment "Processor Specific Options" + + config M68KFPU_EMU + bool "Math emulation support" +- depends on MMU ++ depends on M68KCLASSIC && FPU + help + At some point in the future, this will cause floating-point math + instructions to be emulated by the kernel on machines that lack a +-- +2.35.1 + diff --git a/queue-4.9/macintosh-via-pmu-fix-build-failure-when-config_inpu.patch b/queue-4.9/macintosh-via-pmu-fix-build-failure-when-config_inpu.patch new file mode 100644 index 00000000000..30d50b62bf7 --- /dev/null +++ b/queue-4.9/macintosh-via-pmu-fix-build-failure-when-config_inpu.patch @@ -0,0 +1,82 @@ +From 2ac7707447b66561ee254a65db7a8ae3dd24425a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 7 Apr 2022 20:11:32 +1000 +Subject: macintosh/via-pmu: Fix build failure when CONFIG_INPUT is disabled + +From: Finn Thain + +[ Upstream commit 86ce436e30d86327c9f5260f718104ae7b21f506 ] + +drivers/macintosh/via-pmu-event.o: In function `via_pmu_event': +via-pmu-event.c:(.text+0x44): undefined reference to `input_event' +via-pmu-event.c:(.text+0x68): undefined reference to `input_event' +via-pmu-event.c:(.text+0x94): undefined reference to `input_event' +via-pmu-event.c:(.text+0xb8): undefined reference to `input_event' +drivers/macintosh/via-pmu-event.o: In function `via_pmu_event_init': +via-pmu-event.c:(.init.text+0x20): undefined reference to `input_allocate_device' +via-pmu-event.c:(.init.text+0xc4): undefined reference to `input_register_device' +via-pmu-event.c:(.init.text+0xd4): undefined reference to `input_free_device' +make[1]: *** [Makefile:1155: vmlinux] Error 1 +make: *** [Makefile:350: __build_one_by_one] Error 2 + +Don't call into the input subsystem unless CONFIG_INPUT is built-in. + +Reported-by: kernel test robot +Signed-off-by: Finn Thain +Tested-by: Randy Dunlap +Reviewed-by: Christophe Leroy +Acked-by: Randy Dunlap +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/5edbe76ce68227f71e09af4614cc4c1bd61c7ec8.1649326292.git.fthain@linux-m68k.org +Signed-off-by: Sasha Levin +--- + drivers/macintosh/Kconfig | 4 ++++ + drivers/macintosh/Makefile | 3 ++- + drivers/macintosh/via-pmu.c | 2 +- + 3 files changed, 7 insertions(+), 2 deletions(-) + +diff --git a/drivers/macintosh/Kconfig b/drivers/macintosh/Kconfig +index d28690f6e262..9e226e143473 100644 +--- a/drivers/macintosh/Kconfig ++++ b/drivers/macintosh/Kconfig +@@ -87,6 +87,10 @@ config ADB_PMU + this device; you should do so if your machine is one of those + mentioned above. + ++config ADB_PMU_EVENT ++ def_bool y ++ depends on ADB_PMU && INPUT=y ++ + config ADB_PMU_LED + bool "Support for the Power/iBook front LED" + depends on ADB_PMU +diff --git a/drivers/macintosh/Makefile b/drivers/macintosh/Makefile +index 383ba920085b..8513c8aa2faf 100644 +--- a/drivers/macintosh/Makefile ++++ b/drivers/macintosh/Makefile +@@ -11,7 +11,8 @@ obj-$(CONFIG_MAC_EMUMOUSEBTN) += mac_hid.o + obj-$(CONFIG_INPUT_ADBHID) += adbhid.o + obj-$(CONFIG_ANSLCD) += ans-lcd.o + +-obj-$(CONFIG_ADB_PMU) += via-pmu.o via-pmu-event.o ++obj-$(CONFIG_ADB_PMU) += via-pmu.o ++obj-$(CONFIG_ADB_PMU_EVENT) += via-pmu-event.o + obj-$(CONFIG_ADB_PMU_LED) += via-pmu-led.o + obj-$(CONFIG_PMAC_BACKLIGHT) += via-pmu-backlight.o + obj-$(CONFIG_ADB_CUDA) += via-cuda.o +diff --git a/drivers/macintosh/via-pmu.c b/drivers/macintosh/via-pmu.c +index 32c696799300..9bdb7d2055b1 100644 +--- a/drivers/macintosh/via-pmu.c ++++ b/drivers/macintosh/via-pmu.c +@@ -1439,7 +1439,7 @@ pmu_handle_data(unsigned char *data, int len) + pmu_pass_intr(data, len); + /* len == 6 is probably a bad check. But how do I + * know what PMU versions send what events here? */ +- if (len == 6) { ++ if (IS_ENABLED(CONFIG_ADB_PMU_EVENT) && len == 6) { + via_pmu_event(PMU_EVT_POWER, !!(data[1]&8)); + via_pmu_event(PMU_EVT_LID, data[1]&1); + } +-- +2.35.1 + diff --git a/queue-4.9/media-cx25821-fix-the-warning-when-removing-the-modu.patch b/queue-4.9/media-cx25821-fix-the-warning-when-removing-the-modu.patch new file mode 100644 index 00000000000..8071b1a7b27 --- /dev/null +++ b/queue-4.9/media-cx25821-fix-the-warning-when-removing-the-modu.patch @@ -0,0 +1,57 @@ +From 5e6e9a21d75b4ecb07b678cdb1a76e03792f756e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sun, 10 Apr 2022 08:44:09 +0100 +Subject: media: cx25821: Fix the warning when removing the module + +From: Zheyu Ma + +[ Upstream commit 2203436a4d24302871617373a7eb21bc17e38762 ] + +When removing the module, we will get the following warning: + +[ 14.746697] remove_proc_entry: removing non-empty directory 'irq/21', leaking at least 'cx25821[1]' +[ 14.747449] WARNING: CPU: 4 PID: 368 at fs/proc/generic.c:717 remove_proc_entry+0x389/0x3f0 +[ 14.751611] RIP: 0010:remove_proc_entry+0x389/0x3f0 +[ 14.759589] Call Trace: +[ 14.759792] +[ 14.759975] unregister_irq_proc+0x14c/0x170 +[ 14.760340] irq_free_descs+0x94/0xe0 +[ 14.760640] mp_unmap_irq+0xb6/0x100 +[ 14.760937] acpi_unregister_gsi_ioapic+0x27/0x40 +[ 14.761334] acpi_pci_irq_disable+0x1d3/0x320 +[ 14.761688] pci_disable_device+0x1ad/0x380 +[ 14.762027] ? _raw_spin_unlock_irqrestore+0x2d/0x60 +[ 14.762442] ? cx25821_shutdown+0x20/0x9f0 [cx25821] +[ 14.762848] cx25821_finidev+0x48/0xc0 [cx25821] +[ 14.763242] pci_device_remove+0x92/0x240 + +Fix this by freeing the irq before call pci_disable_device(). + +Signed-off-by: Zheyu Ma +Signed-off-by: Hans Verkuil +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/pci/cx25821/cx25821-core.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/media/pci/cx25821/cx25821-core.c b/drivers/media/pci/cx25821/cx25821-core.c +index d58c58e61bde..acd896ca1339 100644 +--- a/drivers/media/pci/cx25821/cx25821-core.c ++++ b/drivers/media/pci/cx25821/cx25821-core.c +@@ -1354,11 +1354,11 @@ static void cx25821_finidev(struct pci_dev *pci_dev) + struct cx25821_dev *dev = get_cx25821(v4l2_dev); + + cx25821_shutdown(dev); +- pci_disable_device(pci_dev); + + /* unregister stuff */ + if (pci_dev->irq) + free_irq(pci_dev->irq, dev); ++ pci_disable_device(pci_dev); + + cx25821_dev_unregister(dev); + v4l2_device_unregister(v4l2_dev); +-- +2.35.1 + diff --git a/queue-4.9/media-exynos4-is-change-clk_disable-to-clk_disable_u.patch b/queue-4.9/media-exynos4-is-change-clk_disable-to-clk_disable_u.patch new file mode 100644 index 00000000000..27bc2312dc5 --- /dev/null +++ b/queue-4.9/media-exynos4-is-change-clk_disable-to-clk_disable_u.patch @@ -0,0 +1,39 @@ +From f6dd27f7533b5700f0ef55f8bb90fe2b088f799f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 18 Mar 2022 12:01:01 +0100 +Subject: media: exynos4-is: Change clk_disable to clk_disable_unprepare + +From: Miaoqian Lin + +[ Upstream commit 9fadab72a6916c7507d7fedcd644859eef995078 ] + +The corresponding API for clk_prepare_enable is clk_disable_unprepare, +other than clk_disable. + +Fix this by changing clk_disable to clk_disable_unprepare. + +Fixes: b4155d7d5b2c ("[media] exynos4-is: Ensure fimc-is clocks are not enabled until properly configured") +Signed-off-by: Miaoqian Lin +Signed-off-by: Hans Verkuil +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/platform/exynos4-is/fimc-is.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/media/platform/exynos4-is/fimc-is.c b/drivers/media/platform/exynos4-is/fimc-is.c +index f9456f26ff4f..590ec04de827 100644 +--- a/drivers/media/platform/exynos4-is/fimc-is.c ++++ b/drivers/media/platform/exynos4-is/fimc-is.c +@@ -144,7 +144,7 @@ static int fimc_is_enable_clocks(struct fimc_is *is) + dev_err(&is->pdev->dev, "clock %s enable failed\n", + fimc_is_clocks[i]); + for (--i; i >= 0; i--) +- clk_disable(is->clocks[i]); ++ clk_disable_unprepare(is->clocks[i]); + return ret; + } + pr_debug("enabled clock: %s\n", fimc_is_clocks[i]); +-- +2.35.1 + diff --git a/queue-4.9/media-exynos4-is-fix-compile-warning.patch b/queue-4.9/media-exynos4-is-fix-compile-warning.patch new file mode 100644 index 00000000000..2659e50b288 --- /dev/null +++ b/queue-4.9/media-exynos4-is-fix-compile-warning.patch @@ -0,0 +1,39 @@ +From f353863de2428d5e29dd37bf70e8a2e9ea756926 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 27 Apr 2022 03:16:45 +0200 +Subject: media: exynos4-is: Fix compile warning + +From: Kwanghoon Son + +[ Upstream commit e080f5c1f2b6d02c02ee5d674e0e392ccf63bbaf ] + +Declare static on function 'fimc_isp_video_device_unregister'. + +When VIDEO_EXYNOS4_ISP_DMA_CAPTURE=n, compiler warns about +warning: no previous prototype for function [-Wmissing-prototypes] + +Reported-by: kernel test robot +Signed-off-by: Kwanghoon Son +Signed-off-by: Sakari Ailus +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/platform/exynos4-is/fimc-isp-video.h | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/media/platform/exynos4-is/fimc-isp-video.h b/drivers/media/platform/exynos4-is/fimc-isp-video.h +index f79a1b348aa6..67ef85249912 100644 +--- a/drivers/media/platform/exynos4-is/fimc-isp-video.h ++++ b/drivers/media/platform/exynos4-is/fimc-isp-video.h +@@ -35,7 +35,7 @@ static inline int fimc_isp_video_device_register(struct fimc_isp *isp, + return 0; + } + +-void fimc_isp_video_device_unregister(struct fimc_isp *isp, ++static inline void fimc_isp_video_device_unregister(struct fimc_isp *isp, + enum v4l2_buf_type type) + { + } +-- +2.35.1 + diff --git a/queue-4.9/media-pvrusb2-fix-array-index-out-of-bounds-in-pvr2_.patch b/queue-4.9/media-pvrusb2-fix-array-index-out-of-bounds-in-pvr2_.patch new file mode 100644 index 00000000000..e8d2ebeb871 --- /dev/null +++ b/queue-4.9/media-pvrusb2-fix-array-index-out-of-bounds-in-pvr2_.patch @@ -0,0 +1,58 @@ +From dd77b1260f8c2fc98ffbaf6ac11eb5d90601d8fa Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 15 Apr 2022 23:24:48 +0200 +Subject: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init + +From: Pavel Skripkin + +[ Upstream commit 471bec68457aaf981add77b4f590d65dd7da1059 ] + +Syzbot reported that -1 is used as array index. The problem was in +missing validation check. + +hdw->unit_number is initialized with -1 and then if init table walk fails +this value remains unchanged. Since code blindly uses this member for +array indexing adding sanity check is the easiest fix for that. + +hdw->workpoll initialization moved upper to prevent warning in +__flush_work. + +Reported-and-tested-by: syzbot+1a247e36149ffd709a9b@syzkaller.appspotmail.com + +Fixes: d855497edbfb ("V4L/DVB (4228a): pvrusb2 to kernel 2.6.18") +Signed-off-by: Pavel Skripkin +Signed-off-by: Hans Verkuil +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/usb/pvrusb2/pvrusb2-hdw.c | 7 +++++-- + 1 file changed, 5 insertions(+), 2 deletions(-) + +diff --git a/drivers/media/usb/pvrusb2/pvrusb2-hdw.c b/drivers/media/usb/pvrusb2/pvrusb2-hdw.c +index 40535db585a0..b868a77a048c 100644 +--- a/drivers/media/usb/pvrusb2/pvrusb2-hdw.c ++++ b/drivers/media/usb/pvrusb2/pvrusb2-hdw.c +@@ -2615,6 +2615,11 @@ struct pvr2_hdw *pvr2_hdw_create(struct usb_interface *intf, + } while (0); + mutex_unlock(&pvr2_unit_mtx); + ++ INIT_WORK(&hdw->workpoll, pvr2_hdw_worker_poll); ++ ++ if (hdw->unit_number == -1) ++ goto fail; ++ + cnt1 = 0; + cnt2 = scnprintf(hdw->name+cnt1,sizeof(hdw->name)-cnt1,"pvrusb2"); + cnt1 += cnt2; +@@ -2626,8 +2631,6 @@ struct pvr2_hdw *pvr2_hdw_create(struct usb_interface *intf, + if (cnt1 >= sizeof(hdw->name)) cnt1 = sizeof(hdw->name)-1; + hdw->name[cnt1] = 0; + +- INIT_WORK(&hdw->workpoll,pvr2_hdw_worker_poll); +- + pvr2_trace(PVR2_TRACE_INIT,"Driver unit number is %d, name is %s", + hdw->unit_number,hdw->name); + +-- +2.35.1 + diff --git a/queue-4.9/media-uvcvideo-fix-missing-check-to-determine-if-ele.patch b/queue-4.9/media-uvcvideo-fix-missing-check-to-determine-if-ele.patch new file mode 100644 index 00000000000..495cd8aafce --- /dev/null +++ b/queue-4.9/media-uvcvideo-fix-missing-check-to-determine-if-ele.patch @@ -0,0 +1,87 @@ +From 0fd85b3ab396e16f1fb1170441a74e02822f92b7 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 19 Mar 2022 11:22:22 +0100 +Subject: media: uvcvideo: Fix missing check to determine if element is found + in list + +From: Xiaomeng Tong + +[ Upstream commit 261f33388c29f6f3c12a724e6d89172b7f6d5996 ] + +The list iterator will point to a bogus position containing HEAD if +the list is empty or the element is not found in list. This case +should be checked before any use of the iterator, otherwise it will +lead to a invalid memory access. The missing check here is before +"pin = iterm->id;", just add check here to fix the security bug. + +In addition, the list iterator value will *always* be set and non-NULL +by list_for_each_entry(), so it is incorrect to assume that the iterator +value will be NULL if the element is not found in list, considering +the (mis)use here: "if (iterm == NULL". + +Use a new value 'it' as the list iterator, while use the old value +'iterm' as a dedicated pointer to point to the found element, which +1. can fix this bug, due to 'iterm' is NULL only if it's not found. +2. do not need to change all the uses of 'iterm' after the loop. +3. can also limit the scope of the list iterator 'it' *only inside* + the traversal loop by simply declaring 'it' inside the loop in the + future, as usage of the iterator outside of the list_for_each_entry + is considered harmful. https://lkml.org/lkml/2022/2/17/1032 + +Fixes: d5e90b7a6cd1c ("[media] uvcvideo: Move to video_ioctl2") +Signed-off-by: Xiaomeng Tong +Signed-off-by: Laurent Pinchart +Signed-off-by: Mauro Carvalho Chehab +Signed-off-by: Sasha Levin +--- + drivers/media/usb/uvc/uvc_v4l2.c | 20 +++++++++++--------- + 1 file changed, 11 insertions(+), 9 deletions(-) + +diff --git a/drivers/media/usb/uvc/uvc_v4l2.c b/drivers/media/usb/uvc/uvc_v4l2.c +index 2b1e06e825f0..53d81ef9a4be 100644 +--- a/drivers/media/usb/uvc/uvc_v4l2.c ++++ b/drivers/media/usb/uvc/uvc_v4l2.c +@@ -846,29 +846,31 @@ static int uvc_ioctl_enum_input(struct file *file, void *fh, + struct uvc_video_chain *chain = handle->chain; + const struct uvc_entity *selector = chain->selector; + struct uvc_entity *iterm = NULL; ++ struct uvc_entity *it; + u32 index = input->index; +- int pin = 0; + + if (selector == NULL || + (chain->dev->quirks & UVC_QUIRK_IGNORE_SELECTOR_UNIT)) { + if (index != 0) + return -EINVAL; +- list_for_each_entry(iterm, &chain->entities, chain) { +- if (UVC_ENTITY_IS_ITERM(iterm)) ++ list_for_each_entry(it, &chain->entities, chain) { ++ if (UVC_ENTITY_IS_ITERM(it)) { ++ iterm = it; + break; ++ } + } +- pin = iterm->id; + } else if (index < selector->bNrInPins) { +- pin = selector->baSourceID[index]; +- list_for_each_entry(iterm, &chain->entities, chain) { +- if (!UVC_ENTITY_IS_ITERM(iterm)) ++ list_for_each_entry(it, &chain->entities, chain) { ++ if (!UVC_ENTITY_IS_ITERM(it)) + continue; +- if (iterm->id == pin) ++ if (it->id == selector->baSourceID[index]) { ++ iterm = it; + break; ++ } + } + } + +- if (iterm == NULL || iterm->id != pin) ++ if (iterm == NULL) + return -EINVAL; + + memset(input, 0, sizeof(*input)); +-- +2.35.1 + diff --git a/queue-4.9/mfd-ipaq-micro-fix-error-check-return-value-of-platf.patch b/queue-4.9/mfd-ipaq-micro-fix-error-check-return-value-of-platf.patch new file mode 100644 index 00000000000..643808832fb --- /dev/null +++ b/queue-4.9/mfd-ipaq-micro-fix-error-check-return-value-of-platf.patch @@ -0,0 +1,39 @@ +From eaabe63fea9bac79465ebacb6598f5ff32f3122e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 08:53:05 +0000 +Subject: mfd: ipaq-micro: Fix error check return value of platform_get_irq() + +From: Lv Ruyi + +[ Upstream commit 3b49ae380ce1a3054e0c505dd9a356b82a5b48e8 ] + +platform_get_irq() return negative value on failure, so null check of +irq is incorrect. Fix it by comparing whether it is less than zero. + +Fixes: dcc21cc09e3c ("mfd: Add driver for Atmel Microcontroller on iPaq h3xxx") +Reported-by: Zeal Robot +Signed-off-by: Lv Ruyi +Reviewed-by: Linus Walleij +Signed-off-by: Lee Jones +Link: https://lore.kernel.org/r/20220412085305.2533030-1-lv.ruyi@zte.com.cn +Signed-off-by: Sasha Levin +--- + drivers/mfd/ipaq-micro.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/mfd/ipaq-micro.c b/drivers/mfd/ipaq-micro.c +index df16fd1df68b..b03489268252 100644 +--- a/drivers/mfd/ipaq-micro.c ++++ b/drivers/mfd/ipaq-micro.c +@@ -418,7 +418,7 @@ static int __init micro_probe(struct platform_device *pdev) + micro_reset_comm(micro); + + irq = platform_get_irq(pdev, 0); +- if (!irq) ++ if (irq < 0) + return -EINVAL; + ret = devm_request_irq(&pdev->dev, irq, micro_serial_isr, + IRQF_SHARED, "ipaq-micro", +-- +2.35.1 + diff --git a/queue-4.9/mwifiex-add-mutex-lock-for-call-in-mwifiex_dfs_chan_.patch b/queue-4.9/mwifiex-add-mutex-lock-for-call-in-mwifiex_dfs_chan_.patch new file mode 100644 index 00000000000..5bd42298ada --- /dev/null +++ b/queue-4.9/mwifiex-add-mutex-lock-for-call-in-mwifiex_dfs_chan_.patch @@ -0,0 +1,49 @@ +From 68c35705619b3960112c3efbb2a845d016cbddea Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 21 Mar 2022 23:55:16 +0100 +Subject: mwifiex: add mutex lock for call in mwifiex_dfs_chan_sw_work_queue + +From: Niels Dossche + +[ Upstream commit 3e12968f6d12a34b540c39cbd696a760cc4616f0 ] + +cfg80211_ch_switch_notify uses ASSERT_WDEV_LOCK to assert that +net_device->ieee80211_ptr->mtx (which is the same as priv->wdev.mtx) +is held during the function's execution. +mwifiex_dfs_chan_sw_work_queue is one of its callers, which does not +hold that lock, therefore violating the assertion. +Add a lock around the call. + +Disclaimer: +I am currently working on a static analyser to detect missing locks. +This was a reported case. I manually verified the report by looking +at the code, so that I do not send wrong information or patches. +After concluding that this seems to be a true positive, I created +this patch. +However, as I do not in fact have this particular hardware, +I was unable to test it. + +Reviewed-by: Brian Norris +Signed-off-by: Niels Dossche +Signed-off-by: Kalle Valo +Link: https://lore.kernel.org/r/20220321225515.32113-1-dossche.niels@gmail.com +Signed-off-by: Sasha Levin +--- + drivers/net/wireless/marvell/mwifiex/11h.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/net/wireless/marvell/mwifiex/11h.c b/drivers/net/wireless/marvell/mwifiex/11h.c +index 43dccd5b0291..3024a83c0f33 100644 +--- a/drivers/net/wireless/marvell/mwifiex/11h.c ++++ b/drivers/net/wireless/marvell/mwifiex/11h.c +@@ -308,5 +308,7 @@ void mwifiex_dfs_chan_sw_work_queue(struct work_struct *work) + + mwifiex_dbg(priv->adapter, MSG, + "indicating channel switch completion to kernel\n"); ++ mutex_lock(&priv->wdev.mtx); + cfg80211_ch_switch_notify(priv->netdev, &priv->dfs_chandef); ++ mutex_unlock(&priv->wdev.mtx); + } +-- +2.35.1 + diff --git a/queue-4.9/net-remove-two-bug-from-skb_checksum_help.patch b/queue-4.9/net-remove-two-bug-from-skb_checksum_help.patch new file mode 100644 index 00000000000..45f08096999 --- /dev/null +++ b/queue-4.9/net-remove-two-bug-from-skb_checksum_help.patch @@ -0,0 +1,49 @@ +From e4b2ae55fd84627100243eb002ef7e93da392781 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 9 May 2022 20:57:40 -0700 +Subject: net: remove two BUG() from skb_checksum_help() + +From: Eric Dumazet + +[ Upstream commit d7ea0d9df2a6265b2b180d17ebc64b38105968fc ] + +I have a syzbot report that managed to get a crash in skb_checksum_help() + +If syzbot can trigger these BUG(), it makes sense to replace +them with more friendly WARN_ON_ONCE() since skb_checksum_help() +can instead return an error code. + +Note that syzbot will still crash there, until real bug is fixed. + +Signed-off-by: Eric Dumazet +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/core/dev.c | 8 ++++++-- + 1 file changed, 6 insertions(+), 2 deletions(-) + +diff --git a/net/core/dev.c b/net/core/dev.c +index 47468fc5d0c9..d725ca4d4455 100644 +--- a/net/core/dev.c ++++ b/net/core/dev.c +@@ -2518,11 +2518,15 @@ int skb_checksum_help(struct sk_buff *skb) + } + + offset = skb_checksum_start_offset(skb); +- BUG_ON(offset >= skb_headlen(skb)); ++ ret = -EINVAL; ++ if (WARN_ON_ONCE(offset >= skb_headlen(skb))) ++ goto out; ++ + csum = skb_checksum(skb, offset, skb->len - offset, 0); + + offset += skb->csum_offset; +- BUG_ON(offset + sizeof(__sum16) > skb_headlen(skb)); ++ if (WARN_ON_ONCE(offset + sizeof(__sum16) > skb_headlen(skb))) ++ goto out; + + if (skb_cloned(skb) && + !skb_clone_writable(skb, offset + sizeof(__sum16))) { +-- +2.35.1 + diff --git a/queue-4.9/nfc-null-out-the-dev-rfkill-to-prevent-uaf.patch b/queue-4.9/nfc-null-out-the-dev-rfkill-to-prevent-uaf.patch new file mode 100644 index 00000000000..7628e9da1a0 --- /dev/null +++ b/queue-4.9/nfc-null-out-the-dev-rfkill-to-prevent-uaf.patch @@ -0,0 +1,150 @@ +From 1f8f029cb550a82ee25876f5a4b7d7759cb7dfdb Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 12 Apr 2022 13:32:08 +0800 +Subject: NFC: NULL out the dev->rfkill to prevent UAF + +From: Lin Ma + +[ Upstream commit 1b0e81416a24d6e9b8c2341e22e8bf48f8b8bfc9 ] + +Commit 3e3b5dfcd16a ("NFC: reorder the logic in nfc_{un,}register_device") +assumes the device_is_registered() in function nfc_dev_up() will help +to check when the rfkill is unregistered. However, this check only +take effect when device_del(&dev->dev) is done in nfc_unregister_device(). +Hence, the rfkill object is still possible be dereferenced. + +The crash trace in latest kernel (5.18-rc2): + +[ 68.760105] ================================================================== +[ 68.760330] BUG: KASAN: use-after-free in __lock_acquire+0x3ec1/0x6750 +[ 68.760756] Read of size 8 at addr ffff888009c93018 by task fuzz/313 +[ 68.760756] +[ 68.760756] CPU: 0 PID: 313 Comm: fuzz Not tainted 5.18.0-rc2 #4 +[ 68.760756] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 +[ 68.760756] Call Trace: +[ 68.760756] +[ 68.760756] dump_stack_lvl+0x57/0x7d +[ 68.760756] print_report.cold+0x5e/0x5db +[ 68.760756] ? __lock_acquire+0x3ec1/0x6750 +[ 68.760756] kasan_report+0xbe/0x1c0 +[ 68.760756] ? __lock_acquire+0x3ec1/0x6750 +[ 68.760756] __lock_acquire+0x3ec1/0x6750 +[ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 +[ 68.760756] ? register_lock_class+0x18d0/0x18d0 +[ 68.760756] lock_acquire+0x1ac/0x4f0 +[ 68.760756] ? rfkill_blocked+0xe/0x60 +[ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 +[ 68.760756] ? mutex_lock_io_nested+0x12c0/0x12c0 +[ 68.760756] ? nla_get_range_signed+0x540/0x540 +[ 68.760756] ? _raw_spin_lock_irqsave+0x4e/0x50 +[ 68.760756] _raw_spin_lock_irqsave+0x39/0x50 +[ 68.760756] ? rfkill_blocked+0xe/0x60 +[ 68.760756] rfkill_blocked+0xe/0x60 +[ 68.760756] nfc_dev_up+0x84/0x260 +[ 68.760756] nfc_genl_dev_up+0x90/0xe0 +[ 68.760756] genl_family_rcv_msg_doit+0x1f4/0x2f0 +[ 68.760756] ? genl_family_rcv_msg_attrs_parse.constprop.0+0x230/0x230 +[ 68.760756] ? security_capable+0x51/0x90 +[ 68.760756] genl_rcv_msg+0x280/0x500 +[ 68.760756] ? genl_get_cmd+0x3c0/0x3c0 +[ 68.760756] ? lock_acquire+0x1ac/0x4f0 +[ 68.760756] ? nfc_genl_dev_down+0xe0/0xe0 +[ 68.760756] ? lockdep_hardirqs_on_prepare+0x410/0x410 +[ 68.760756] netlink_rcv_skb+0x11b/0x340 +[ 68.760756] ? genl_get_cmd+0x3c0/0x3c0 +[ 68.760756] ? netlink_ack+0x9c0/0x9c0 +[ 68.760756] ? netlink_deliver_tap+0x136/0xb00 +[ 68.760756] genl_rcv+0x1f/0x30 +[ 68.760756] netlink_unicast+0x430/0x710 +[ 68.760756] ? memset+0x20/0x40 +[ 68.760756] ? netlink_attachskb+0x740/0x740 +[ 68.760756] ? __build_skb_around+0x1f4/0x2a0 +[ 68.760756] netlink_sendmsg+0x75d/0xc00 +[ 68.760756] ? netlink_unicast+0x710/0x710 +[ 68.760756] ? netlink_unicast+0x710/0x710 +[ 68.760756] sock_sendmsg+0xdf/0x110 +[ 68.760756] __sys_sendto+0x19e/0x270 +[ 68.760756] ? __ia32_sys_getpeername+0xa0/0xa0 +[ 68.760756] ? fd_install+0x178/0x4c0 +[ 68.760756] ? fd_install+0x195/0x4c0 +[ 68.760756] ? kernel_fpu_begin_mask+0x1c0/0x1c0 +[ 68.760756] __x64_sys_sendto+0xd8/0x1b0 +[ 68.760756] ? lockdep_hardirqs_on+0xbf/0x130 +[ 68.760756] ? syscall_enter_from_user_mode+0x1d/0x50 +[ 68.760756] do_syscall_64+0x3b/0x90 +[ 68.760756] entry_SYSCALL_64_after_hwframe+0x44/0xae +[ 68.760756] RIP: 0033:0x7f67fb50e6b3 +... +[ 68.760756] RSP: 002b:00007f67fa91fe90 EFLAGS: 00000293 ORIG_RAX: 000000000000002c +[ 68.760756] RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f67fb50e6b3 +[ 68.760756] RDX: 000000000000001c RSI: 0000559354603090 RDI: 0000000000000003 +[ 68.760756] RBP: 00007f67fa91ff00 R08: 00007f67fa91fedc R09: 000000000000000c +[ 68.760756] R10: 0000000000000000 R11: 0000000000000293 R12: 00007ffe824d496e +[ 68.760756] R13: 00007ffe824d496f R14: 00007f67fa120000 R15: 0000000000000003 + +[ 68.760756] +[ 68.760756] +[ 68.760756] Allocated by task 279: +[ 68.760756] kasan_save_stack+0x1e/0x40 +[ 68.760756] __kasan_kmalloc+0x81/0xa0 +[ 68.760756] rfkill_alloc+0x7f/0x280 +[ 68.760756] nfc_register_device+0xa3/0x1a0 +[ 68.760756] nci_register_device+0x77a/0xad0 +[ 68.760756] nfcmrvl_nci_register_dev+0x20b/0x2c0 +[ 68.760756] nfcmrvl_nci_uart_open+0xf2/0x1dd +[ 68.760756] nci_uart_tty_ioctl+0x2c3/0x4a0 +[ 68.760756] tty_ioctl+0x764/0x1310 +[ 68.760756] __x64_sys_ioctl+0x122/0x190 +[ 68.760756] do_syscall_64+0x3b/0x90 +[ 68.760756] entry_SYSCALL_64_after_hwframe+0x44/0xae +[ 68.760756] +[ 68.760756] Freed by task 314: +[ 68.760756] kasan_save_stack+0x1e/0x40 +[ 68.760756] kasan_set_track+0x21/0x30 +[ 68.760756] kasan_set_free_info+0x20/0x30 +[ 68.760756] __kasan_slab_free+0x108/0x170 +[ 68.760756] kfree+0xb0/0x330 +[ 68.760756] device_release+0x96/0x200 +[ 68.760756] kobject_put+0xf9/0x1d0 +[ 68.760756] nfc_unregister_device+0x77/0x190 +[ 68.760756] nfcmrvl_nci_unregister_dev+0x88/0xd0 +[ 68.760756] nci_uart_tty_close+0xdf/0x180 +[ 68.760756] tty_ldisc_kill+0x73/0x110 +[ 68.760756] tty_ldisc_hangup+0x281/0x5b0 +[ 68.760756] __tty_hangup.part.0+0x431/0x890 +[ 68.760756] tty_release+0x3a8/0xc80 +[ 68.760756] __fput+0x1f0/0x8c0 +[ 68.760756] task_work_run+0xc9/0x170 +[ 68.760756] exit_to_user_mode_prepare+0x194/0x1a0 +[ 68.760756] syscall_exit_to_user_mode+0x19/0x50 +[ 68.760756] do_syscall_64+0x48/0x90 +[ 68.760756] entry_SYSCALL_64_after_hwframe+0x44/0xae + +This patch just add the null out of dev->rfkill to make sure such +dereference cannot happen. This is safe since the device_lock() already +protect the check/write from data race. + +Fixes: 3e3b5dfcd16a ("NFC: reorder the logic in nfc_{un,}register_device") +Signed-off-by: Lin Ma +Reviewed-by: Krzysztof Kozlowski +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/nfc/core.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/net/nfc/core.c b/net/nfc/core.c +index 8c38a21fb0c6..120259c2b6a7 100644 +--- a/net/nfc/core.c ++++ b/net/nfc/core.c +@@ -1174,6 +1174,7 @@ void nfc_unregister_device(struct nfc_dev *dev) + if (dev->rfkill) { + rfkill_unregister(dev->rfkill); + rfkill_destroy(dev->rfkill); ++ dev->rfkill = NULL; + } + dev->shutting_down = true; + device_unlock(&dev->dev); +-- +2.35.1 + diff --git a/queue-4.9/nvme-pci-fix-a-null-pointer-dereference-in-nvme_allo.patch b/queue-4.9/nvme-pci-fix-a-null-pointer-dereference-in-nvme_allo.patch new file mode 100644 index 00000000000..2b4c3ff68a4 --- /dev/null +++ b/queue-4.9/nvme-pci-fix-a-null-pointer-dereference-in-nvme_allo.patch @@ -0,0 +1,45 @@ +From 3f1c883e8a5c53e427a5aea482b36c7c838ff12e Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 14:40:32 +0000 +Subject: nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags + +From: Smith, Kyle Miller (Nimble Kernel) + +[ Upstream commit da42761181627e9bdc37d18368b827948a583929 ] + +In nvme_alloc_admin_tags, the admin_q can be set to an error (typically +-ENOMEM) if the blk_mq_init_queue call fails to set up the queue, which +is checked immediately after the call. However, when we return the error +message up the stack, to nvme_reset_work the error takes us to +nvme_remove_dead_ctrl() + nvme_dev_disable() + nvme_suspend_queue(&dev->queues[0]). + +Here, we only check that the admin_q is non-NULL, rather than not +an error or NULL, and begin quiescing a queue that never existed, leading +to bad / NULL pointer dereference. + +Signed-off-by: Kyle Smith +Reviewed-by: Chaitanya Kulkarni +Reviewed-by: Hannes Reinecke +Signed-off-by: Christoph Hellwig +Signed-off-by: Sasha Levin +--- + drivers/nvme/host/pci.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/nvme/host/pci.c b/drivers/nvme/host/pci.c +index c87f27d3ee31..e7b872592f36 100644 +--- a/drivers/nvme/host/pci.c ++++ b/drivers/nvme/host/pci.c +@@ -1203,6 +1203,7 @@ static int nvme_alloc_admin_tags(struct nvme_dev *dev) + dev->ctrl.admin_q = blk_mq_init_queue(&dev->admin_tagset); + if (IS_ERR(dev->ctrl.admin_q)) { + blk_mq_free_tag_set(&dev->admin_tagset); ++ dev->ctrl.admin_q = NULL; + return -ENOMEM; + } + if (!blk_get_queue(dev->ctrl.admin_q)) { +-- +2.35.1 + diff --git a/queue-4.9/openrisc-start-cpu-timer-early-in-boot.patch b/queue-4.9/openrisc-start-cpu-timer-early-in-boot.patch new file mode 100644 index 00000000000..e30272f0a07 --- /dev/null +++ b/queue-4.9/openrisc-start-cpu-timer-early-in-boot.patch @@ -0,0 +1,62 @@ +From fa98668b2dbe8becf9167177378e0c2681bc0846 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 23 Apr 2022 21:11:41 +0200 +Subject: openrisc: start CPU timer early in boot + +From: Jason A. Donenfeld + +[ Upstream commit 516dd4aacd67a0f27da94f3fe63fe0f4dbab6e2b ] + +In order to measure the boot process, the timer should be switched on as +early in boot as possible. As well, the commit defines the get_cycles +macro, like the previous patches in this series, so that generic code is +aware that it's implemented by the platform, as is done on other archs. + +Cc: Thomas Gleixner +Cc: Arnd Bergmann +Cc: Jonas Bonn +Cc: Stefan Kristiansson +Acked-by: Stafford Horne +Reported-by: Guenter Roeck +Signed-off-by: Jason A. Donenfeld +Signed-off-by: Sasha Levin +--- + arch/openrisc/include/asm/timex.h | 1 + + arch/openrisc/kernel/head.S | 9 +++++++++ + 2 files changed, 10 insertions(+) + +diff --git a/arch/openrisc/include/asm/timex.h b/arch/openrisc/include/asm/timex.h +index 9935cad1b9b9..34d015bf0462 100644 +--- a/arch/openrisc/include/asm/timex.h ++++ b/arch/openrisc/include/asm/timex.h +@@ -27,6 +27,7 @@ static inline cycles_t get_cycles(void) + { + return mfspr(SPR_TTCR); + } ++#define get_cycles get_cycles + + /* This isn't really used any more */ + #define CLOCK_TICK_RATE 1000 +diff --git a/arch/openrisc/kernel/head.S b/arch/openrisc/kernel/head.S +index 98dd6860bc0b..0b6be5b3522b 100644 +--- a/arch/openrisc/kernel/head.S ++++ b/arch/openrisc/kernel/head.S +@@ -452,6 +452,15 @@ _start: + l.ori r3,r0,0x1 + l.mtspr r0,r3,SPR_SR + ++ /* ++ * Start the TTCR as early as possible, so that the RNG can make use of ++ * measurements of boot time from the earliest opportunity. Especially ++ * important is that the TTCR does not return zero by the time we reach ++ * rand_initialize(). ++ */ ++ l.movhi r3,hi(SPR_TTMR_CR) ++ l.mtspr r0,r3,SPR_TTMR ++ + CLEAR_GPR(r1) + CLEAR_GPR(r2) + CLEAR_GPR(r3) +-- +2.35.1 + diff --git a/queue-4.9/pci-avoid-pci_dev_lock-ab-ba-deadlock-with-sriov_num.patch b/queue-4.9/pci-avoid-pci_dev_lock-ab-ba-deadlock-with-sriov_num.patch new file mode 100644 index 00000000000..f839b17d41a --- /dev/null +++ b/queue-4.9/pci-avoid-pci_dev_lock-ab-ba-deadlock-with-sriov_num.patch @@ -0,0 +1,90 @@ +From 74caadc0392d7fdf8ead8a0851830733e6df28ab Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 4 Apr 2022 14:25:39 +0800 +Subject: PCI: Avoid pci_dev_lock() AB/BA deadlock with sriov_numvfs_store() + +From: Yicong Yang + +[ Upstream commit a91ee0e9fca9d7501286cfbced9b30a33e52740a ] + +The sysfs sriov_numvfs_store() path acquires the device lock before the +config space access lock: + + sriov_numvfs_store + device_lock # A (1) acquire device lock + sriov_configure + vfio_pci_sriov_configure # (for example) + vfio_pci_core_sriov_configure + pci_disable_sriov + sriov_disable + pci_cfg_access_lock + pci_wait_cfg # B (4) wait for dev->block_cfg_access == 0 + +Previously, pci_dev_lock() acquired the config space access lock before the +device lock: + + pci_dev_lock + pci_cfg_access_lock + dev->block_cfg_access = 1 # B (2) set dev->block_cfg_access = 1 + device_lock # A (3) wait for device lock + +Any path that uses pci_dev_lock(), e.g., pci_reset_function(), may +deadlock with sriov_numvfs_store() if the operations occur in the sequence +(1) (2) (3) (4). + +Avoid the deadlock by reversing the order in pci_dev_lock() so it acquires +the device lock before the config space access lock, the same as the +sriov_numvfs_store() path. + +[bhelgaas: combined and adapted commit log from Jay Zhou's independent +subsequent posting: +https://lore.kernel.org/r/20220404062539.1710-1-jianjay.zhou@huawei.com] +Link: https://lore.kernel.org/linux-pci/1583489997-17156-1-git-send-email-yangyicong@hisilicon.com/ +Also-posted-by: Jay Zhou +Signed-off-by: Yicong Yang +Signed-off-by: Bjorn Helgaas +Signed-off-by: Sasha Levin +--- + drivers/pci/pci.c | 10 +++++----- + 1 file changed, 5 insertions(+), 5 deletions(-) + +diff --git a/drivers/pci/pci.c b/drivers/pci/pci.c +index 2cf13578fe75..e6e0012269cd 100644 +--- a/drivers/pci/pci.c ++++ b/drivers/pci/pci.c +@@ -4079,18 +4079,18 @@ static int __pci_dev_reset(struct pci_dev *dev, int probe) + + static void pci_dev_lock(struct pci_dev *dev) + { +- pci_cfg_access_lock(dev); + /* block PM suspend, driver probe, etc. */ + device_lock(&dev->dev); ++ pci_cfg_access_lock(dev); + } + + /* Return 1 on successful lock, 0 on contention */ + static int pci_dev_trylock(struct pci_dev *dev) + { +- if (pci_cfg_access_trylock(dev)) { +- if (device_trylock(&dev->dev)) ++ if (device_trylock(&dev->dev)) { ++ if (pci_cfg_access_trylock(dev)) + return 1; +- pci_cfg_access_unlock(dev); ++ device_unlock(&dev->dev); + } + + return 0; +@@ -4098,8 +4098,8 @@ static int pci_dev_trylock(struct pci_dev *dev) + + static void pci_dev_unlock(struct pci_dev *dev) + { +- device_unlock(&dev->dev); + pci_cfg_access_unlock(dev); ++ device_unlock(&dev->dev); + } + + /** +-- +2.35.1 + diff --git a/queue-4.9/powerpc-4xx-cpm-fix-return-value-of-__setup-handler.patch b/queue-4.9/powerpc-4xx-cpm-fix-return-value-of-__setup-handler.patch new file mode 100644 index 00000000000..046e55ada8e --- /dev/null +++ b/queue-4.9/powerpc-4xx-cpm-fix-return-value-of-__setup-handler.patch @@ -0,0 +1,44 @@ +From 4c2379f827e7d39cdec4efe84c531e6cd6d52cc7 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 2 May 2022 12:29:41 -0700 +Subject: powerpc/4xx/cpm: Fix return value of __setup() handler + +From: Randy Dunlap + +[ Upstream commit 5bb99fd4090fe1acfdb90a97993fcda7f8f5a3d6 ] + +__setup() handlers should return 1 to obsolete_checksetup() in +init/main.c to indicate that the boot option has been handled. + +A return of 0 causes the boot option/value to be listed as an Unknown +kernel parameter and added to init's (limited) argument or environment +strings. + +Also, error return codes don't mean anything to obsolete_checksetup() -- +only non-zero (usually 1) or zero. So return 1 from cpm_powersave_off(). + +Fixes: d164f6d4f910 ("powerpc/4xx: Add suspend and idle support") +Reported-by: Igor Zhbanov +Signed-off-by: Randy Dunlap +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/20220502192941.20955-1-rdunlap@infradead.org +Signed-off-by: Sasha Levin +--- + arch/powerpc/sysdev/ppc4xx_cpm.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/powerpc/sysdev/ppc4xx_cpm.c b/arch/powerpc/sysdev/ppc4xx_cpm.c +index ba95adf81d8d..05047cf32dbb 100644 +--- a/arch/powerpc/sysdev/ppc4xx_cpm.c ++++ b/arch/powerpc/sysdev/ppc4xx_cpm.c +@@ -341,6 +341,6 @@ late_initcall(cpm_init); + static int __init cpm_powersave_off(char *arg) + { + cpm.powersave_off = 1; +- return 0; ++ return 1; + } + __setup("powersave=off", cpm_powersave_off); +-- +2.35.1 + diff --git a/queue-4.9/powerpc-8xx-export-cpm_setbrg-for-modules.patch b/queue-4.9/powerpc-8xx-export-cpm_setbrg-for-modules.patch new file mode 100644 index 00000000000..47261f6661a --- /dev/null +++ b/queue-4.9/powerpc-8xx-export-cpm_setbrg-for-modules.patch @@ -0,0 +1,40 @@ +From 71bb861c4942ce9214967290e26857edaaea1aff Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 21 Jan 2021 17:08:19 -0800 +Subject: powerpc/8xx: export 'cpm_setbrg' for modules + +From: Randy Dunlap + +[ Upstream commit 22f8e625ebabd7ed3185b82b44b4f12fc0402113 ] + +Fix missing export for a loadable module build: + +ERROR: modpost: "cpm_setbrg" [drivers/tty/serial/cpm_uart/cpm_uart.ko] undefined! + +Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc") +Signed-off-by: Randy Dunlap +Reported-by: kernel test robot +[chleroy: Changed Fixes: tag] +Signed-off-by: Christophe Leroy +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/20210122010819.30986-1-rdunlap@infradead.org +Signed-off-by: Sasha Levin +--- + arch/powerpc/sysdev/cpm1.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/powerpc/sysdev/cpm1.c b/arch/powerpc/sysdev/cpm1.c +index 986cd111d4df..8f2dc4ea9376 100644 +--- a/arch/powerpc/sysdev/cpm1.c ++++ b/arch/powerpc/sysdev/cpm1.c +@@ -290,6 +290,7 @@ cpm_setbrg(uint brg, uint rate) + out_be32(bp, (((BRG_UART_CLK_DIV16 / rate) - 1) << 1) | + CPM_BRG_EN | CPM_BRG_DIV16); + } ++EXPORT_SYMBOL(cpm_setbrg); + + struct cpm_ioport16 { + __be16 dir, par, odr_sor, dat, intr; +-- +2.35.1 + diff --git a/queue-4.9/powerpc-idle-fix-return-value-of-__setup-handler.patch b/queue-4.9/powerpc-idle-fix-return-value-of-__setup-handler.patch new file mode 100644 index 00000000000..f142b23ec0b --- /dev/null +++ b/queue-4.9/powerpc-idle-fix-return-value-of-__setup-handler.patch @@ -0,0 +1,45 @@ +From a7d33f2170b22f003d41d6eb09e11cb70da311c9 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 2 May 2022 12:29:25 -0700 +Subject: powerpc/idle: Fix return value of __setup() handler + +From: Randy Dunlap + +[ Upstream commit b793a01000122d2bd133ba451a76cc135b5e162c ] + +__setup() handlers should return 1 to obsolete_checksetup() in +init/main.c to indicate that the boot option has been handled. + +A return of 0 causes the boot option/value to be listed as an Unknown +kernel parameter and added to init's (limited) argument or environment +strings. + +Also, error return codes don't mean anything to obsolete_checksetup() -- +only non-zero (usually 1) or zero. So return 1 from powersave_off(). + +Fixes: 302eca184fb8 ("[POWERPC] cell: use ppc_md->power_save instead of cbe_idle_loop") +Reported-by: Igor Zhbanov +Signed-off-by: Randy Dunlap +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/20220502192925.19954-1-rdunlap@infradead.org +Signed-off-by: Sasha Levin +--- + arch/powerpc/kernel/idle.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/arch/powerpc/kernel/idle.c b/arch/powerpc/kernel/idle.c +index d7216c9abda1..ca79aacfeda2 100644 +--- a/arch/powerpc/kernel/idle.c ++++ b/arch/powerpc/kernel/idle.c +@@ -41,7 +41,7 @@ static int __init powersave_off(char *arg) + { + ppc_md.power_save = NULL; + cpuidle_disable = IDLE_POWERSAVE_OFF; +- return 0; ++ return 1; + } + __setup("powersave=off", powersave_off); + +-- +2.35.1 + diff --git a/queue-4.9/powerpc-xics-fix-refcount-leak-in-icp_opal_init.patch b/queue-4.9/powerpc-xics-fix-refcount-leak-in-icp_opal_init.patch new file mode 100644 index 00000000000..bc670cc2289 --- /dev/null +++ b/queue-4.9/powerpc-xics-fix-refcount-leak-in-icp_opal_init.patch @@ -0,0 +1,36 @@ +From b8fbdbaa2e4a68358f6deaf402ea09a8e2f39f1f Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 2 Apr 2022 01:34:19 +0000 +Subject: powerpc/xics: fix refcount leak in icp_opal_init() + +From: Lv Ruyi + +[ Upstream commit 5dd9e27ea4a39f7edd4bf81e9e70208e7ac0b7c9 ] + +The of_find_compatible_node() function returns a node pointer with +refcount incremented, use of_node_put() on it when done. + +Reported-by: Zeal Robot +Signed-off-by: Lv Ruyi +Signed-off-by: Michael Ellerman +Link: https://lore.kernel.org/r/20220402013419.2410298-1-lv.ruyi@zte.com.cn +Signed-off-by: Sasha Levin +--- + arch/powerpc/sysdev/xics/icp-opal.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/arch/powerpc/sysdev/xics/icp-opal.c b/arch/powerpc/sysdev/xics/icp-opal.c +index b53f80f0b4d8..80a4fa6dcc55 100644 +--- a/arch/powerpc/sysdev/xics/icp-opal.c ++++ b/arch/powerpc/sysdev/xics/icp-opal.c +@@ -199,6 +199,7 @@ int icp_opal_init(void) + + printk("XICS: Using OPAL ICP fallbacks\n"); + ++ of_node_put(np); + return 0; + } + +-- +2.35.1 + diff --git a/queue-4.9/regulator-pfuze100-fix-refcount-leak-in-pfuze_parse_.patch b/queue-4.9/regulator-pfuze100-fix-refcount-leak-in-pfuze_parse_.patch new file mode 100644 index 00000000000..e955dec5614 --- /dev/null +++ b/queue-4.9/regulator-pfuze100-fix-refcount-leak-in-pfuze_parse_.patch @@ -0,0 +1,44 @@ +From eaf90f327460693541554557e9fe855195c35442 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Wed, 11 May 2022 15:35:05 +0400 +Subject: regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt + +From: Miaoqian Lin + +[ Upstream commit afaa7b933ef00a2d3262f4d1252087613fb5c06d ] + +of_node_get() returns a node with refcount incremented. +Calling of_node_put() to drop the reference when not needed anymore. + +Fixes: 3784b6d64dc5 ("regulator: pfuze100: add pfuze100 regulator driver") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220511113506.45185-1-linmq006@gmail.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + drivers/regulator/pfuze100-regulator.c | 2 ++ + 1 file changed, 2 insertions(+) + +diff --git a/drivers/regulator/pfuze100-regulator.c b/drivers/regulator/pfuze100-regulator.c +index ffb1f61d2c75..998c7c972e60 100644 +--- a/drivers/regulator/pfuze100-regulator.c ++++ b/drivers/regulator/pfuze100-regulator.c +@@ -407,6 +407,7 @@ static int pfuze_parse_regulators_dt(struct pfuze_chip *chip) + parent = of_get_child_by_name(np, "regulators"); + if (!parent) { + dev_err(dev, "regulators node not found\n"); ++ of_node_put(np); + return -EINVAL; + } + +@@ -431,6 +432,7 @@ static int pfuze_parse_regulators_dt(struct pfuze_chip *chip) + } + + of_node_put(parent); ++ of_node_put(np); + if (ret < 0) { + dev_err(dev, "Error parsing regulator init data: %d\n", + ret); +-- +2.35.1 + diff --git a/queue-4.9/rxrpc-don-t-try-to-resend-the-request-if-we-re-recei.patch b/queue-4.9/rxrpc-don-t-try-to-resend-the-request-if-we-re-recei.patch new file mode 100644 index 00000000000..879a1a60938 --- /dev/null +++ b/queue-4.9/rxrpc-don-t-try-to-resend-the-request-if-we-re-recei.patch @@ -0,0 +1,45 @@ +From c85482733351ecb3276213bb26484a352dc01e93 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 21 May 2022 09:03:11 +0100 +Subject: rxrpc: Don't try to resend the request if we're receiving the reply + +From: David Howells + +[ Upstream commit 114af61f88fbe34d641b13922d098ffec4c1be1b ] + +rxrpc has a timer to trigger resending of unacked data packets in a call. +This is not cancelled when a client call switches to the receive phase on +the basis that most calls don't last long enough for it to ever expire. +However, if it *does* expire after we've started to receive the reply, we +shouldn't then go into trying to retransmit or pinging the server to find +out if an ack got lost. + +Fix this by skipping the resend code if we're into receiving the reply to a +client call. + +Fixes: 17926a79320a ("[AF_RXRPC]: Provide secure RxRPC sockets for use by userspace and kernel both") +Signed-off-by: David Howells +cc: linux-afs@lists.infradead.org +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/rxrpc/call_event.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/net/rxrpc/call_event.c b/net/rxrpc/call_event.c +index 97a17ada4431..4aae0904ae1b 100644 +--- a/net/rxrpc/call_event.c ++++ b/net/rxrpc/call_event.c +@@ -403,7 +403,8 @@ void rxrpc_process_call(struct work_struct *work) + goto recheck_state; + } + +- if (test_and_clear_bit(RXRPC_CALL_EV_RESEND, &call->events)) { ++ if (test_and_clear_bit(RXRPC_CALL_EV_RESEND, &call->events) && ++ call->state != RXRPC_CALL_CLIENT_RECV_REPLY) { + rxrpc_resend(call, now); + goto recheck_state; + } +-- +2.35.1 + diff --git a/queue-4.9/rxrpc-fix-listen-setting-the-bar-too-high-for-the-pr.patch b/queue-4.9/rxrpc-fix-listen-setting-the-bar-too-high-for-the-pr.patch new file mode 100644 index 00000000000..2640de2919f --- /dev/null +++ b/queue-4.9/rxrpc-fix-listen-setting-the-bar-too-high-for-the-pr.patch @@ -0,0 +1,74 @@ +From b86d9419ae55fd04381f2e0a92d235939420e9ac Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 21 May 2022 09:03:04 +0100 +Subject: rxrpc: Fix listen() setting the bar too high for the prealloc rings + +From: David Howells + +[ Upstream commit 88e22159750b0d55793302eeed8ee603f5c1a95c ] + +AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump +up the sysctl), but whilst the preallocation circular buffers have 32 slots +in them, one of them has to be a dead slot because we're using CIRC_CNT(). + +This means that listen(rxrpc_sock, 32) will cause an oops when the socket +is closed because rxrpc_service_prealloc_one() allocated one too many calls +and rxrpc_discard_prealloc() won't then be able to get rid of them because +it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries +to abort them, but oopses because call->peer isn't yet set. + +Fix this by setting the maximum backlog to RXRPC_BACKLOG_MAX - 1 to match +the ring capacity. + + BUG: kernel NULL pointer dereference, address: 0000000000000086 + ... + RIP: 0010:rxrpc_send_abort_packet+0x73/0x240 [rxrpc] + Call Trace: + + ? __wake_up_common_lock+0x7a/0x90 + ? rxrpc_notify_socket+0x8e/0x140 [rxrpc] + ? rxrpc_abort_call+0x4c/0x60 [rxrpc] + rxrpc_release_calls_on_socket+0x107/0x1a0 [rxrpc] + rxrpc_release+0xc9/0x1c0 [rxrpc] + __sock_release+0x37/0xa0 + sock_close+0x11/0x20 + __fput+0x89/0x240 + task_work_run+0x59/0x90 + do_exit+0x319/0xaa0 + +Fixes: 00e907127e6f ("rxrpc: Preallocate peers, conns and calls for incoming service requests") +Reported-by: Marc Dionne +Signed-off-by: David Howells +cc: linux-afs@lists.infradead.org +Link: https://lists.infradead.org/pipermail/linux-afs/2022-March/005079.html +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/rxrpc/sysctl.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/net/rxrpc/sysctl.c b/net/rxrpc/sysctl.c +index 34c706d2f79c..f9afc21b7e2c 100644 +--- a/net/rxrpc/sysctl.c ++++ b/net/rxrpc/sysctl.c +@@ -18,7 +18,7 @@ static struct ctl_table_header *rxrpc_sysctl_reg_table; + static const unsigned int zero = 0; + static const unsigned int one = 1; + static const unsigned int four = 4; +-static const unsigned int thirtytwo = 32; ++static const unsigned int max_backlog = RXRPC_BACKLOG_MAX - 1; + static const unsigned int n_65535 = 65535; + static const unsigned int n_max_acks = RXRPC_RXTX_BUFF_SIZE - 1; + +@@ -114,7 +114,7 @@ static struct ctl_table rxrpc_sysctl_table[] = { + .mode = 0644, + .proc_handler = proc_dointvec_minmax, + .extra1 = (void *)&four, +- .extra2 = (void *)&thirtytwo, ++ .extra2 = (void *)&max_backlog, + }, + { + .procname = "rx_window_size", +-- +2.35.1 + diff --git a/queue-4.9/rxrpc-return-an-error-to-sendmsg-if-call-failed.patch b/queue-4.9/rxrpc-return-an-error-to-sendmsg-if-call-failed.patch new file mode 100644 index 00000000000..9d7ae7f90d6 --- /dev/null +++ b/queue-4.9/rxrpc-return-an-error-to-sendmsg-if-call-failed.patch @@ -0,0 +1,84 @@ +From 6738a59c8537a7615fbc8d8ca8cf2d8851da7ba2 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 21 May 2022 08:45:41 +0100 +Subject: rxrpc: Return an error to sendmsg if call failed + +From: David Howells + +[ Upstream commit 4ba68c5192554876bd8c3afd904e3064d2915341 ] + +If at the end of rxrpc sendmsg() or rxrpc_kernel_send_data() the call that +was being given data was aborted remotely or otherwise failed, return an +error rather than returning the amount of data buffered for transmission. + +The call (presumably) did not complete, so there's not much point +continuing with it. AF_RXRPC considers it "complete" and so will be +unwilling to do anything else with it - and won't send a notification for +it, deeming the return from sendmsg sufficient. + +Not returning an error causes afs to incorrectly handle a StoreData +operation that gets interrupted by a change of address due to NAT +reconfiguration. + +This doesn't normally affect most operations since their request parameters +tend to fit into a single UDP packet and afs_make_call() returns before the +server responds; StoreData is different as it involves transmission of a +lot of data. + +This can be triggered on a client by doing something like: + + dd if=/dev/zero of=/afs/example.com/foo bs=1M count=512 + +at one prompt, and then changing the network address at another prompt, +e.g.: + + ifconfig enp6s0 inet 192.168.6.2 && route add 192.168.6.1 dev enp6s0 + +Tracing packets on an Auristor fileserver looks something like: + +192.168.6.1 -> 192.168.6.3 RX 107 ACK Idle Seq: 0 Call: 4 Source Port: 7000 Destination Port: 7001 +192.168.6.3 -> 192.168.6.1 AFS (RX) 1482 FS Request: Unknown(64538) (64538) +192.168.6.3 -> 192.168.6.1 AFS (RX) 1482 FS Request: Unknown(64538) (64538) +192.168.6.1 -> 192.168.6.3 RX 107 ACK Idle Seq: 0 Call: 4 Source Port: 7000 Destination Port: 7001 + +192.168.6.2 -> 192.168.6.1 AFS (RX) 1482 FS Request: Unknown(0) (0) +192.168.6.2 -> 192.168.6.1 AFS (RX) 1482 FS Request: Unknown(0) (0) +192.168.6.1 -> 192.168.6.2 RX 107 ACK Exceeds Window Seq: 0 Call: 4 Source Port: 7000 Destination Port: 7001 +192.168.6.1 -> 192.168.6.2 RX 74 ABORT Seq: 0 Call: 4 Source Port: 7000 Destination Port: 7001 +192.168.6.1 -> 192.168.6.2 RX 74 ABORT Seq: 29321 Call: 4 Source Port: 7000 Destination Port: 7001 + +The Auristor fileserver logs code -453 (RXGEN_SS_UNMARSHAL), but the abort +code received by kafs is -5 (RX_PROTOCOL_ERROR) as the rx layer sees the +condition and generates an abort first and the unmarshal error is a +consequence of that at the application layer. + +Reported-by: Marc Dionne +Signed-off-by: David Howells +cc: linux-afs@lists.infradead.org +Link: http://lists.infradead.org/pipermail/linux-afs/2021-December/004810.html # v1 +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/rxrpc/sendmsg.c | 6 ++++++ + 1 file changed, 6 insertions(+) + +diff --git a/net/rxrpc/sendmsg.c b/net/rxrpc/sendmsg.c +index 2ec1c29eeba4..b8e87804296c 100644 +--- a/net/rxrpc/sendmsg.c ++++ b/net/rxrpc/sendmsg.c +@@ -336,6 +336,12 @@ static int rxrpc_send_data(struct rxrpc_sock *rx, + + success: + ret = copied; ++ if (READ_ONCE(call->state) == RXRPC_CALL_COMPLETE) { ++ read_lock_bh(&call->state_lock); ++ if (call->error < 0) ++ ret = call->error; ++ read_unlock_bh(&call->state_lock); ++ } + out: + call->tx_pending = skb; + _leave(" = %d", ret); +-- +2.35.1 + diff --git a/queue-4.9/scsi-fcoe-fix-wstringop-overflow-warnings-in-fcoe_ww.patch b/queue-4.9/scsi-fcoe-fix-wstringop-overflow-warnings-in-fcoe_ww.patch new file mode 100644 index 00000000000..0a23c52a8e4 --- /dev/null +++ b/queue-4.9/scsi-fcoe-fix-wstringop-overflow-warnings-in-fcoe_ww.patch @@ -0,0 +1,130 @@ +From b9e35e8233ed4e894b469c6c60297f174907b750 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 3 Mar 2022 17:55:21 -0600 +Subject: scsi: fcoe: Fix Wstringop-overflow warnings in fcoe_wwn_from_mac() +MIME-Version: 1.0 +Content-Type: text/plain; charset=UTF-8 +Content-Transfer-Encoding: 8bit + +From: Gustavo A. R. Silva + +[ Upstream commit 54db804d5d7d36709d1ce70bde3b9a6c61b290b6 ] + +Fix the following Wstringop-overflow warnings when building with GCC-11: + +drivers/scsi/fcoe/fcoe.c: In function ‘fcoe_netdev_config’: +drivers/scsi/fcoe/fcoe.c:744:32: warning: ‘fcoe_wwn_from_mac’ accessing 32 bytes in a region of size 6 [-Wstringop-overflow=] + 744 | wwnn = fcoe_wwn_from_mac(ctlr->ctl_src_addr, 1, 0); + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +drivers/scsi/fcoe/fcoe.c:744:32: note: referencing argument 1 of type ‘unsigned char *’ +In file included from drivers/scsi/fcoe/fcoe.c:36: +./include/scsi/libfcoe.h:252:5: note: in a call to function ‘fcoe_wwn_from_mac’ + 252 | u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); + | ^~~~~~~~~~~~~~~~~ +drivers/scsi/fcoe/fcoe.c:747:32: warning: ‘fcoe_wwn_from_mac’ accessing 32 bytes in a region of size 6 [-Wstringop-overflow=] + 747 | wwpn = fcoe_wwn_from_mac(ctlr->ctl_src_addr, + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + 748 | 2, 0); + | ~~~~~ +drivers/scsi/fcoe/fcoe.c:747:32: note: referencing argument 1 of type ‘unsigned char *’ +In file included from drivers/scsi/fcoe/fcoe.c:36: +./include/scsi/libfcoe.h:252:5: note: in a call to function ‘fcoe_wwn_from_mac’ + 252 | u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); + | ^~~~~~~~~~~~~~~~~ + CC drivers/scsi/bnx2fc/bnx2fc_io.o +In function ‘bnx2fc_net_config’, + inlined from ‘bnx2fc_if_create’ at drivers/scsi/bnx2fc/bnx2fc_fcoe.c:1543:7: +drivers/scsi/bnx2fc/bnx2fc_fcoe.c:833:32: warning: ‘fcoe_wwn_from_mac’ accessing 32 bytes in a region of size 6 [-Wstringop-overflow=] + 833 | wwnn = fcoe_wwn_from_mac(ctlr->ctl_src_addr, + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + 834 | 1, 0); + | ~~~~~ +drivers/scsi/bnx2fc/bnx2fc_fcoe.c: In function ‘bnx2fc_if_create’: +drivers/scsi/bnx2fc/bnx2fc_fcoe.c:833:32: note: referencing argument 1 of type ‘unsigned char *’ +In file included from drivers/scsi/bnx2fc/bnx2fc.h:53, + from drivers/scsi/bnx2fc/bnx2fc_fcoe.c:17: +./include/scsi/libfcoe.h:252:5: note: in a call to function ‘fcoe_wwn_from_mac’ + 252 | u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); + | ^~~~~~~~~~~~~~~~~ +In function ‘bnx2fc_net_config’, + inlined from ‘bnx2fc_if_create’ at drivers/scsi/bnx2fc/bnx2fc_fcoe.c:1543:7: +drivers/scsi/bnx2fc/bnx2fc_fcoe.c:839:32: warning: ‘fcoe_wwn_from_mac’ accessing 32 bytes in a region of size 6 [-Wstringop-overflow=] + 839 | wwpn = fcoe_wwn_from_mac(ctlr->ctl_src_addr, + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + 840 | 2, 0); + | ~~~~~ +drivers/scsi/bnx2fc/bnx2fc_fcoe.c: In function ‘bnx2fc_if_create’: +drivers/scsi/bnx2fc/bnx2fc_fcoe.c:839:32: note: referencing argument 1 of type ‘unsigned char *’ +In file included from drivers/scsi/bnx2fc/bnx2fc.h:53, + from drivers/scsi/bnx2fc/bnx2fc_fcoe.c:17: +./include/scsi/libfcoe.h:252:5: note: in a call to function ‘fcoe_wwn_from_mac’ + 252 | u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); + | ^~~~~~~~~~~~~~~~~ +drivers/scsi/qedf/qedf_main.c: In function ‘__qedf_probe’: +drivers/scsi/qedf/qedf_main.c:3520:30: warning: ‘fcoe_wwn_from_mac’ accessing 32 bytes in a region of size 6 [-Wstringop-overflow=] + 3520 | qedf->wwnn = fcoe_wwn_from_mac(qedf->mac, 1, 0); + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +drivers/scsi/qedf/qedf_main.c:3520:30: note: referencing argument 1 of type ‘unsigned char *’ +In file included from drivers/scsi/qedf/qedf.h:9, + from drivers/scsi/qedf/qedf_main.c:23: +./include/scsi/libfcoe.h:252:5: note: in a call to function ‘fcoe_wwn_from_mac’ + 252 | u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); + | ^~~~~~~~~~~~~~~~~ +drivers/scsi/qedf/qedf_main.c:3521:30: warning: ‘fcoe_wwn_from_mac’ accessing 32 bytes in a region of size 6 [-Wstringop-overflow=] + 3521 | qedf->wwpn = fcoe_wwn_from_mac(qedf->mac, 2, 0); + | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +drivers/scsi/qedf/qedf_main.c:3521:30: note: referencing argument 1 of type ‘unsigned char *’ +In file included from drivers/scsi/qedf/qedf.h:9, + from drivers/scsi/qedf/qedf_main.c:23: +./include/scsi/libfcoe.h:252:5: note: in a call to function ‘fcoe_wwn_from_mac’ + 252 | u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); + | ^~~~~~~~~~~~~~~~~ + +by changing the array size to the correct value of ETH_ALEN in the +argument declaration. + +Also, fix a couple of checkpatch warnings: +WARNING: function definition argument 'unsigned int' should also have an identifier name + +This helps with the ongoing efforts to globally enable +-Wstringop-overflow. + +Link: https://github.com/KSPP/linux/issues/181 +Fixes: 85b4aa4926a5 ("[SCSI] fcoe: Fibre Channel over Ethernet") +Signed-off-by: Gustavo A. R. Silva +Signed-off-by: Sasha Levin +--- + drivers/scsi/fcoe/fcoe_ctlr.c | 2 +- + include/scsi/libfcoe.h | 3 ++- + 2 files changed, 3 insertions(+), 2 deletions(-) + +diff --git a/drivers/scsi/fcoe/fcoe_ctlr.c b/drivers/scsi/fcoe/fcoe_ctlr.c +index f5f3a8113bc5..5bb85b424eba 100644 +--- a/drivers/scsi/fcoe/fcoe_ctlr.c ++++ b/drivers/scsi/fcoe/fcoe_ctlr.c +@@ -1945,7 +1945,7 @@ EXPORT_SYMBOL(fcoe_ctlr_recv_flogi); + * + * Returns: u64 fc world wide name + */ +-u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], ++u64 fcoe_wwn_from_mac(unsigned char mac[ETH_ALEN], + unsigned int scheme, unsigned int port) + { + u64 wwn; +diff --git a/include/scsi/libfcoe.h b/include/scsi/libfcoe.h +index a911f993219d..ac14f3798e84 100644 +--- a/include/scsi/libfcoe.h ++++ b/include/scsi/libfcoe.h +@@ -261,7 +261,8 @@ int fcoe_ctlr_recv_flogi(struct fcoe_ctlr *, struct fc_lport *, + struct fc_frame *); + + /* libfcoe funcs */ +-u64 fcoe_wwn_from_mac(unsigned char mac[MAX_ADDR_LEN], unsigned int, unsigned int); ++u64 fcoe_wwn_from_mac(unsigned char mac[ETH_ALEN], unsigned int scheme, ++ unsigned int port); + int fcoe_libfc_config(struct fc_lport *, struct fcoe_ctlr *, + const struct libfc_function_template *, int init_fcp); + u32 fcoe_fc_crc(struct fc_frame *fp); +-- +2.35.1 + diff --git a/queue-4.9/scsi-megaraid-fix-error-check-return-value-of-regist.patch b/queue-4.9/scsi-megaraid-fix-error-check-return-value-of-regist.patch new file mode 100644 index 00000000000..9fa276f1e56 --- /dev/null +++ b/queue-4.9/scsi-megaraid-fix-error-check-return-value-of-regist.patch @@ -0,0 +1,38 @@ +From e98e1cd1b5e59210fc2c4b37dc16319cb8923416 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 18 Apr 2022 10:57:55 +0000 +Subject: scsi: megaraid: Fix error check return value of register_chrdev() + +From: Lv Ruyi + +[ Upstream commit c5acd61dbb32b6bda0f3a354108f2b8dcb788985 ] + +If major equals 0, register_chrdev() returns an error code when it fails. +This function dynamically allocates a major and returns its number on +success, so we should use "< 0" to check it instead of "!". + +Link: https://lore.kernel.org/r/20220418105755.2558828-1-lv.ruyi@zte.com.cn +Reported-by: Zeal Robot +Signed-off-by: Lv Ruyi +Signed-off-by: Martin K. Petersen +Signed-off-by: Sasha Levin +--- + drivers/scsi/megaraid.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/scsi/megaraid.c b/drivers/scsi/megaraid.c +index 2cbfec6a7466..2f7132edcd3f 100644 +--- a/drivers/scsi/megaraid.c ++++ b/drivers/scsi/megaraid.c +@@ -4705,7 +4705,7 @@ static int __init megaraid_init(void) + * major number allocation. + */ + major = register_chrdev(0, "megadev_legacy", &megadev_fops); +- if (!major) { ++ if (major < 0) { + printk(KERN_WARNING + "megaraid: failed to register char device\n"); + } +-- +2.35.1 + diff --git a/queue-4.9/sctp-read-sk-sk_bound_dev_if-once-in-sctp_rcv.patch b/queue-4.9/sctp-read-sk-sk_bound_dev_if-once-in-sctp_rcv.patch new file mode 100644 index 00000000000..e512f3d677c --- /dev/null +++ b/queue-4.9/sctp-read-sk-sk_bound_dev_if-once-in-sctp_rcv.patch @@ -0,0 +1,49 @@ +From ae216d4249310227d56f53f4274f8683e4087638 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 13 May 2022 11:55:42 -0700 +Subject: sctp: read sk->sk_bound_dev_if once in sctp_rcv() + +From: Eric Dumazet + +[ Upstream commit a20ea298071f46effa3aaf965bf9bb34c901db3f ] + +sctp_rcv() reads sk->sk_bound_dev_if twice while the socket +is not locked. Another cpu could change this field under us. + +Fixes: 0fd9a65a76e8 ("[SCTP] Support SO_BINDTODEVICE socket option on incoming packets.") +Signed-off-by: Eric Dumazet +Cc: Neil Horman +Cc: Vlad Yasevich +Cc: Marcelo Ricardo Leitner +Acked-by: Marcelo Ricardo Leitner +Signed-off-by: David S. Miller +Signed-off-by: Sasha Levin +--- + net/sctp/input.c | 4 +++- + 1 file changed, 3 insertions(+), 1 deletion(-) + +diff --git a/net/sctp/input.c b/net/sctp/input.c +index 9c1670b4a687..ed3a8a66a00b 100644 +--- a/net/sctp/input.c ++++ b/net/sctp/input.c +@@ -103,6 +103,7 @@ int sctp_rcv(struct sk_buff *skb) + struct sctp_chunk *chunk; + union sctp_addr src; + union sctp_addr dest; ++ int bound_dev_if; + int family; + struct sctp_af *af; + struct net *net = dev_net(skb->dev); +@@ -180,7 +181,8 @@ int sctp_rcv(struct sk_buff *skb) + * If a frame arrives on an interface and the receiving socket is + * bound to another interface, via SO_BINDTODEVICE, treat it as OOTB + */ +- if (sk->sk_bound_dev_if && (sk->sk_bound_dev_if != af->skb_iif(skb))) { ++ bound_dev_if = READ_ONCE(sk->sk_bound_dev_if); ++ if (bound_dev_if && (bound_dev_if != af->skb_iif(skb))) { + if (transport) { + sctp_transport_put(transport); + asoc = NULL; +-- +2.35.1 + diff --git a/queue-4.9/series b/queue-4.9/series index 9d4be7c6f4d..394f52368c0 100644 --- a/queue-4.9/series +++ b/queue-4.9/series @@ -2,3 +2,74 @@ usb-new-quirk-for-dell-gen-2-devices.patch ptrace-xtensa-replace-pt_singlestep-with-tif_singlestep.patch ptrace-reimplement-ptrace_kill-by-always-sending-sigkill.patch btrfs-add-0x-prefix-for-unsupported-optional-features.patch +drm-virtio-fix-null-pointer-dereference-in-virtio_gp.patch +mwifiex-add-mutex-lock-for-call-in-mwifiex_dfs_chan_.patch +b43legacy-fix-assigning-negative-value-to-unsigned-v.patch +b43-fix-assigning-negative-value-to-unsigned-variabl.patch +ipw2x00-fix-potential-null-dereference-in-libipw_xmi.patch +acpica-avoid-cache-flush-inside-virtual-machines.patch +alsa-jack-access-input_dev-under-mutex.patch +drm-amd-pm-fix-double-free-in-si_parse_power_table.patch +ath9k-fix-qca9561-pa-bias-level.patch +media-cx25821-fix-the-warning-when-removing-the-modu.patch +scsi-megaraid-fix-error-check-return-value-of-regist.patch +drm-amd-pm-fix-the-compile-warning.patch +ipv6-don-t-send-rs-packets-to-the-interface-of-arphr.patch +asoc-dapm-don-t-fold-register-value-changes-into-not.patch +net-remove-two-bug-from-skb_checksum_help.patch +dma-debug-change-allocation-mode-from-gfp_nowait-to-.patch +ipmi-ssif-check-for-null-msg-when-handling-events-an.patch +openrisc-start-cpu-timer-early-in-boot.patch +nvme-pci-fix-a-null-pointer-dereference-in-nvme_allo.patch +asoc-rt5645-fix-errorenous-cleanup-order.patch +media-exynos4-is-fix-compile-warning.patch +rxrpc-return-an-error-to-sendmsg-if-call-failed.patch +eth-tg3-silence-the-gcc-12-array-bounds-warning.patch +fs-jfs-fix-possible-null-pointer-dereference-in-dbfr.patch +arm-omap1-clock-fix-uart-rate-reporting-algorithm.patch +fat-add-ratelimit-to-fat-_ent_bread.patch +arm-versatile-add-missing-of_node_put-in-dcscb_init.patch +arm-dts-exynos-add-atmel-24c128-fallback-to-samsung-.patch +arm-hisi-add-missing-of_node_put-after-of_find_compa.patch +pci-avoid-pci_dev_lock-ab-ba-deadlock-with-sriov_num.patch +powerpc-xics-fix-refcount-leak-in-icp_opal_init.patch +macintosh-via-pmu-fix-build-failure-when-config_inpu.patch +drm-fix-edid-struct-for-old-arm-oabi-format.patch +asoc-mediatek-fix-error-handling-in-mt8173_max98090_.patch +x86-delay-fix-the-wrong-asm-constraint-in-delay_loop.patch +drm-mediatek-fix-mtk_cec_mask.patch +spi-spi-ti-qspi-fix-return-value-handling-of-wait_fo.patch +nfc-null-out-the-dev-rfkill-to-prevent-uaf.patch +hid-hid-led-fix-maximum-brightness-for-dream-cheeky.patch +spi-img-spfi-fix-pm_runtime_get_sync-error-checking.patch +ath9k_htc-fix-potential-out-of-bounds-access-with-in.patch +inotify-show-inotify-mask-flags-in-proc-fdinfo.patch +x86-pm-fix-false-positive-kmemleak-report-in-msr_bui.patch +drm-msm-dsi-fix-error-checks-and-return-values-for-d.patch +drm-msm-hdmi-check-return-value-after-calling-platfo.patch +drm-rockchip-vop-fix-possible-null-ptr-deref-in-vop_.patch +x86-mm-cleanup-the-control_va_addr_alignment-__setup.patch +drm-msm-return-an-error-pointer-in-msm_gem_prime_get.patch +media-uvcvideo-fix-missing-check-to-determine-if-ele.patch +asoc-mxs-saif-fix-refcount-leak-in-mxs_saif_probe.patch +regulator-pfuze100-fix-refcount-leak-in-pfuze_parse_.patch +media-exynos4-is-change-clk_disable-to-clk_disable_u.patch +media-pvrusb2-fix-array-index-out-of-bounds-in-pvr2_.patch +bluetooth-fix-dangling-sco_conn-and-use-after-free-i.patch +m68k-math-emu-fix-dependencies-of-math-emulation-sup.patch +sctp-read-sk-sk_bound_dev_if-once-in-sctp_rcv.patch +asoc-wm2000-fix-missing-clk_disable_unprepare-on-err.patch +rxrpc-fix-listen-setting-the-bar-too-high-for-the-pr.patch +rxrpc-don-t-try-to-resend-the-request-if-we-re-recei.patch +soc-qcom-smp2p-fix-missing-of_node_put-in-smp2p_pars.patch +soc-qcom-smsm-fix-missing-of_node_put-in-smsm_parse_.patch +mfd-ipaq-micro-fix-error-check-return-value-of-platf.patch +scsi-fcoe-fix-wstringop-overflow-warnings-in-fcoe_ww.patch +drivers-base-node.c-fix-compaction-sysfs-file-leak.patch +powerpc-8xx-export-cpm_setbrg-for-modules.patch +powerpc-idle-fix-return-value-of-__setup-handler.patch +powerpc-4xx-cpm-fix-return-value-of-__setup-handler.patch +tty-fix-deadlock-caused-by-calling-printk-under-tty_.patch +input-sparcspkr-fix-refcount-leak-in-bbc_beep_probe.patch +video-fbdev-clcdfb-fix-refcount-leak-in-clcdfb_of_vr.patch +iommu-amd-increase-timeout-waiting-for-ga-log-enable.patch diff --git a/queue-4.9/soc-qcom-smp2p-fix-missing-of_node_put-in-smp2p_pars.patch b/queue-4.9/soc-qcom-smp2p-fix-missing-of_node_put-in-smp2p_pars.patch new file mode 100644 index 00000000000..f0689f6f082 --- /dev/null +++ b/queue-4.9/soc-qcom-smp2p-fix-missing-of_node_put-in-smp2p_pars.patch @@ -0,0 +1,36 @@ +From 89690de10af23e0c41d341eeb11e99b0941da448 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 8 Mar 2022 07:19:42 +0000 +Subject: soc: qcom: smp2p: Fix missing of_node_put() in smp2p_parse_ipc + +From: Miaoqian Lin + +[ Upstream commit 8fd3f18ea31a398ecce4a6d3804433658678b0a3 ] + +The device_node pointer is returned by of_parse_phandle() with refcount +incremented. We should use of_node_put() on it when done. + +Fixes: 50e99641413e ("soc: qcom: smp2p: Qualcomm Shared Memory Point to Point") +Signed-off-by: Miaoqian Lin +Signed-off-by: Bjorn Andersson +Link: https://lore.kernel.org/r/20220308071942.22942-1-linmq006@gmail.com +Signed-off-by: Sasha Levin +--- + drivers/soc/qcom/smp2p.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/soc/qcom/smp2p.c b/drivers/soc/qcom/smp2p.c +index 4c5767c73b7a..a0562dec9604 100644 +--- a/drivers/soc/qcom/smp2p.c ++++ b/drivers/soc/qcom/smp2p.c +@@ -416,6 +416,7 @@ static int smp2p_parse_ipc(struct qcom_smp2p *smp2p) + } + + smp2p->ipc_regmap = syscon_node_to_regmap(syscon); ++ of_node_put(syscon); + if (IS_ERR(smp2p->ipc_regmap)) + return PTR_ERR(smp2p->ipc_regmap); + +-- +2.35.1 + diff --git a/queue-4.9/soc-qcom-smsm-fix-missing-of_node_put-in-smsm_parse_.patch b/queue-4.9/soc-qcom-smsm-fix-missing-of_node_put-in-smsm_parse_.patch new file mode 100644 index 00000000000..5c2a6b46102 --- /dev/null +++ b/queue-4.9/soc-qcom-smsm-fix-missing-of_node_put-in-smsm_parse_.patch @@ -0,0 +1,36 @@ +From 52976304366fdbd9904ad463d8ba314077a6944a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 8 Mar 2022 07:36:48 +0000 +Subject: soc: qcom: smsm: Fix missing of_node_put() in smsm_parse_ipc + +From: Miaoqian Lin + +[ Upstream commit aad66a3c78da668f4506356c2fdb70b7a19ecc76 ] + +The device_node pointer is returned by of_parse_phandle() with refcount +incremented. We should use of_node_put() on it when done. + +Fixes: c97c4090ff72 ("soc: qcom: smsm: Add driver for Qualcomm SMSM") +Signed-off-by: Miaoqian Lin +Signed-off-by: Bjorn Andersson +Link: https://lore.kernel.org/r/20220308073648.24634-1-linmq006@gmail.com +Signed-off-by: Sasha Levin +--- + drivers/soc/qcom/smsm.c | 1 + + 1 file changed, 1 insertion(+) + +diff --git a/drivers/soc/qcom/smsm.c b/drivers/soc/qcom/smsm.c +index 783cb3364599..01bc8528f24d 100644 +--- a/drivers/soc/qcom/smsm.c ++++ b/drivers/soc/qcom/smsm.c +@@ -367,6 +367,7 @@ static int smsm_parse_ipc(struct qcom_smsm *smsm, unsigned host_id) + return 0; + + host->ipc_regmap = syscon_node_to_regmap(syscon); ++ of_node_put(syscon); + if (IS_ERR(host->ipc_regmap)) + return PTR_ERR(host->ipc_regmap); + +-- +2.35.1 + diff --git a/queue-4.9/spi-img-spfi-fix-pm_runtime_get_sync-error-checking.patch b/queue-4.9/spi-img-spfi-fix-pm_runtime_get_sync-error-checking.patch new file mode 100644 index 00000000000..3b55cf6cd4a --- /dev/null +++ b/queue-4.9/spi-img-spfi-fix-pm_runtime_get_sync-error-checking.patch @@ -0,0 +1,38 @@ +From 91ae4e2b1d3b74b30e1b1bcd1a75d31eb07a3110 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Fri, 22 Apr 2022 06:26:41 +0000 +Subject: spi: img-spfi: Fix pm_runtime_get_sync() error checking + +From: Zheng Yongjun + +[ Upstream commit cc470d55343056d6b2a5c32e10e0aad06f324078 ] + +If the device is already in a runtime PM enabled state +pm_runtime_get_sync() will return 1, so a test for negative +value should be used to check for errors. + +Fixes: deba25800a12b ("spi: Add driver for IMG SPFI controller") +Signed-off-by: Zheng Yongjun +Link: https://lore.kernel.org/r/20220422062641.10486-1-zhengyongjun3@huawei.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + drivers/spi/spi-img-spfi.c | 2 +- + 1 file changed, 1 insertion(+), 1 deletion(-) + +diff --git a/drivers/spi/spi-img-spfi.c b/drivers/spi/spi-img-spfi.c +index 2a340234c85c..82ab1bc2196a 100644 +--- a/drivers/spi/spi-img-spfi.c ++++ b/drivers/spi/spi-img-spfi.c +@@ -771,7 +771,7 @@ static int img_spfi_resume(struct device *dev) + int ret; + + ret = pm_runtime_get_sync(dev); +- if (ret) { ++ if (ret < 0) { + pm_runtime_put_noidle(dev); + return ret; + } +-- +2.35.1 + diff --git a/queue-4.9/spi-spi-ti-qspi-fix-return-value-handling-of-wait_fo.patch b/queue-4.9/spi-spi-ti-qspi-fix-return-value-handling-of-wait_fo.patch new file mode 100644 index 00000000000..2748fc2a895 --- /dev/null +++ b/queue-4.9/spi-spi-ti-qspi-fix-return-value-handling-of-wait_fo.patch @@ -0,0 +1,51 @@ +From 162800f8080fdc94aa466d007b401a0b73731a08 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 11 Apr 2022 11:10:33 +0000 +Subject: spi: spi-ti-qspi: Fix return value handling of + wait_for_completion_timeout + +From: Miaoqian Lin + +[ Upstream commit 8b1ea69a63eb62f97cef63e6d816b64ed84e8760 ] + +wait_for_completion_timeout() returns unsigned long not int. +It returns 0 if timed out, and positive if completed. +The check for <= 0 is ambiguous and should be == 0 here +indicating timeout which is the only error case. + +Fixes: 5720ec0a6d26 ("spi: spi-ti-qspi: Add DMA support for QSPI mmap read") +Signed-off-by: Miaoqian Lin +Link: https://lore.kernel.org/r/20220411111034.24447-1-linmq006@gmail.com +Signed-off-by: Mark Brown +Signed-off-by: Sasha Levin +--- + drivers/spi/spi-ti-qspi.c | 5 +++-- + 1 file changed, 3 insertions(+), 2 deletions(-) + +diff --git a/drivers/spi/spi-ti-qspi.c b/drivers/spi/spi-ti-qspi.c +index b0a5486936c0..0b0f69551da0 100644 +--- a/drivers/spi/spi-ti-qspi.c ++++ b/drivers/spi/spi-ti-qspi.c +@@ -401,6 +401,7 @@ static int ti_qspi_dma_xfer(struct ti_qspi *qspi, dma_addr_t dma_dst, + enum dma_ctrl_flags flags = DMA_CTRL_ACK | DMA_PREP_INTERRUPT; + struct dma_async_tx_descriptor *tx; + int ret; ++ unsigned long time_left; + + tx = dma_dev->device_prep_dma_memcpy(chan, dma_dst, dma_src, + len, flags); +@@ -420,9 +421,9 @@ static int ti_qspi_dma_xfer(struct ti_qspi *qspi, dma_addr_t dma_dst, + } + + dma_async_issue_pending(chan); +- ret = wait_for_completion_timeout(&qspi->transfer_complete, ++ time_left = wait_for_completion_timeout(&qspi->transfer_complete, + msecs_to_jiffies(len)); +- if (ret <= 0) { ++ if (time_left == 0) { + dmaengine_terminate_sync(chan); + dev_err(qspi->dev, "DMA wait_for_completion_timeout\n"); + return -ETIMEDOUT; +-- +2.35.1 + diff --git a/queue-4.9/tty-fix-deadlock-caused-by-calling-printk-under-tty_.patch b/queue-4.9/tty-fix-deadlock-caused-by-calling-printk-under-tty_.patch new file mode 100644 index 00000000000..82226755054 --- /dev/null +++ b/queue-4.9/tty-fix-deadlock-caused-by-calling-printk-under-tty_.patch @@ -0,0 +1,143 @@ +From 8de3efc8b2bd15af9e7b3819de1e5fb1faf110f4 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 12 May 2022 20:38:37 -0700 +Subject: tty: fix deadlock caused by calling printk() under tty_port->lock + +From: Qi Zheng + +[ Upstream commit 6b9dbedbe3499fef862c4dff5217cf91f34e43b3 ] + +pty_write() invokes kmalloc() which may invoke a normal printk() to print +failure message. This can cause a deadlock in the scenario reported by +syz-bot below: + + CPU0 CPU1 CPU2 + ---- ---- ---- + lock(console_owner); + lock(&port_lock_key); + lock(&port->lock); + lock(&port_lock_key); + lock(&port->lock); + lock(console_owner); + +As commit dbdda842fe96 ("printk: Add console owner and waiter logic to +load balance console writes") said, such deadlock can be prevented by +using printk_deferred() in kmalloc() (which is invoked in the section +guarded by the port->lock). But there are too many printk() on the +kmalloc() path, and kmalloc() can be called from anywhere, so changing +printk() to printk_deferred() is too complicated and inelegant. + +Therefore, this patch chooses to specify __GFP_NOWARN to kmalloc(), so +that printk() will not be called, and this deadlock problem can be +avoided. + +Syzbot reported the following lockdep error: + +====================================================== +WARNING: possible circular locking dependency detected +5.4.143-00237-g08ccc19a-dirty #10 Not tainted +------------------------------------------------------ +syz-executor.4/29420 is trying to acquire lock: +ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: console_trylock_spinning kernel/printk/printk.c:1752 [inline] +ffffffff8aedb2a0 (console_owner){....}-{0:0}, at: vprintk_emit+0x2ca/0x470 kernel/printk/printk.c:2023 + +but task is already holding lock: +ffff8880119c9158 (&port->lock){-.-.}-{2:2}, at: pty_write+0xf4/0x1f0 drivers/tty/pty.c:120 + +which lock already depends on the new lock. + +the existing dependency chain (in reverse order) is: + +-> #2 (&port->lock){-.-.}-{2:2}: + __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] + _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159 + tty_port_tty_get drivers/tty/tty_port.c:288 [inline] <-- lock(&port->lock); + tty_port_default_wakeup+0x1d/0xb0 drivers/tty/tty_port.c:47 + serial8250_tx_chars+0x530/0xa80 drivers/tty/serial/8250/8250_port.c:1767 + serial8250_handle_irq.part.0+0x31f/0x3d0 drivers/tty/serial/8250/8250_port.c:1854 + serial8250_handle_irq drivers/tty/serial/8250/8250_port.c:1827 [inline] <-- lock(&port_lock_key); + serial8250_default_handle_irq+0xb2/0x220 drivers/tty/serial/8250/8250_port.c:1870 + serial8250_interrupt+0xfd/0x200 drivers/tty/serial/8250/8250_core.c:126 + __handle_irq_event_percpu+0x109/0xa50 kernel/irq/handle.c:156 + [...] + +-> #1 (&port_lock_key){-.-.}-{2:2}: + __raw_spin_lock_irqsave include/linux/spinlock_api_smp.h:110 [inline] + _raw_spin_lock_irqsave+0x35/0x50 kernel/locking/spinlock.c:159 + serial8250_console_write+0x184/0xa40 drivers/tty/serial/8250/8250_port.c:3198 + <-- lock(&port_lock_key); + call_console_drivers kernel/printk/printk.c:1819 [inline] + console_unlock+0x8cb/0xd00 kernel/printk/printk.c:2504 + vprintk_emit+0x1b5/0x470 kernel/printk/printk.c:2024 <-- lock(console_owner); + vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 + printk+0xba/0xed kernel/printk/printk.c:2084 + register_console+0x8b3/0xc10 kernel/printk/printk.c:2829 + univ8250_console_init+0x3a/0x46 drivers/tty/serial/8250/8250_core.c:681 + console_init+0x49d/0x6d3 kernel/printk/printk.c:2915 + start_kernel+0x5e9/0x879 init/main.c:713 + secondary_startup_64+0xa4/0xb0 arch/x86/kernel/head_64.S:241 + +-> #0 (console_owner){....}-{0:0}: + [...] + lock_acquire+0x127/0x340 kernel/locking/lockdep.c:4734 + console_trylock_spinning kernel/printk/printk.c:1773 [inline] <-- lock(console_owner); + vprintk_emit+0x307/0x470 kernel/printk/printk.c:2023 + vprintk_func+0x8d/0x250 kernel/printk/printk_safe.c:394 + printk+0xba/0xed kernel/printk/printk.c:2084 + fail_dump lib/fault-inject.c:45 [inline] + should_fail+0x67b/0x7c0 lib/fault-inject.c:144 + __should_failslab+0x152/0x1c0 mm/failslab.c:33 + should_failslab+0x5/0x10 mm/slab_common.c:1224 + slab_pre_alloc_hook mm/slab.h:468 [inline] + slab_alloc_node mm/slub.c:2723 [inline] + slab_alloc mm/slub.c:2807 [inline] + __kmalloc+0x72/0x300 mm/slub.c:3871 + kmalloc include/linux/slab.h:582 [inline] + tty_buffer_alloc+0x23f/0x2a0 drivers/tty/tty_buffer.c:175 + __tty_buffer_request_room+0x156/0x2a0 drivers/tty/tty_buffer.c:273 + tty_insert_flip_string_fixed_flag+0x93/0x250 drivers/tty/tty_buffer.c:318 + tty_insert_flip_string include/linux/tty_flip.h:37 [inline] + pty_write+0x126/0x1f0 drivers/tty/pty.c:122 <-- lock(&port->lock); + n_tty_write+0xa7a/0xfc0 drivers/tty/n_tty.c:2356 + do_tty_write drivers/tty/tty_io.c:961 [inline] + tty_write+0x512/0x930 drivers/tty/tty_io.c:1045 + __vfs_write+0x76/0x100 fs/read_write.c:494 + [...] + +other info that might help us debug this: + +Chain exists of: + console_owner --> &port_lock_key --> &port->lock + +Link: https://lkml.kernel.org/r/20220511061951.1114-2-zhengqi.arch@bytedance.com +Link: https://lkml.kernel.org/r/20220510113809.80626-2-zhengqi.arch@bytedance.com +Fixes: b6da31b2c07c ("tty: Fix data race in tty_insert_flip_string_fixed_flag") +Signed-off-by: Qi Zheng +Acked-by: Jiri Slaby +Acked-by: Greg Kroah-Hartman +Cc: Akinobu Mita +Cc: Vlastimil Babka +Cc: Steven Rostedt (Google) +Signed-off-by: Andrew Morton +Signed-off-by: Sasha Levin +--- + drivers/tty/tty_buffer.c | 3 ++- + 1 file changed, 2 insertions(+), 1 deletion(-) + +diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c +index dfccc102c1dd..e65faa98146e 100644 +--- a/drivers/tty/tty_buffer.c ++++ b/drivers/tty/tty_buffer.c +@@ -166,7 +166,8 @@ static struct tty_buffer *tty_buffer_alloc(struct tty_port *port, size_t size) + have queued and recycle that ? */ + if (atomic_read(&port->buf.mem_used) > port->buf.mem_limit) + return NULL; +- p = kmalloc(sizeof(struct tty_buffer) + 2 * size, GFP_ATOMIC); ++ p = kmalloc(sizeof(struct tty_buffer) + 2 * size, ++ GFP_ATOMIC | __GFP_NOWARN); + if (p == NULL) + return NULL; + +-- +2.35.1 + diff --git a/queue-4.9/video-fbdev-clcdfb-fix-refcount-leak-in-clcdfb_of_vr.patch b/queue-4.9/video-fbdev-clcdfb-fix-refcount-leak-in-clcdfb_of_vr.patch new file mode 100644 index 00000000000..722e98dca74 --- /dev/null +++ b/queue-4.9/video-fbdev-clcdfb-fix-refcount-leak-in-clcdfb_of_vr.patch @@ -0,0 +1,45 @@ +From a437f4293a4cb5a05e8cecc4e25b8da0011eec99 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Thu, 12 May 2022 15:59:08 +0400 +Subject: video: fbdev: clcdfb: Fix refcount leak in clcdfb_of_vram_setup + +From: Miaoqian Lin + +[ Upstream commit b23789a59fa6f00e98a319291819f91fbba0deb8 ] + +of_parse_phandle() returns a node pointer with refcount incremented, we should +use of_node_put() on it when not need anymore. Add missing of_node_put() to +avoid refcount leak. + +Fixes: d10715be03bd ("video: ARM CLCD: Add DT support") +Signed-off-by: Miaoqian Lin +Signed-off-by: Helge Deller +Signed-off-by: Sasha Levin +--- + drivers/video/fbdev/amba-clcd.c | 5 ++++- + 1 file changed, 4 insertions(+), 1 deletion(-) + +diff --git a/drivers/video/fbdev/amba-clcd.c b/drivers/video/fbdev/amba-clcd.c +index 89880b70cc28..ca3707e59633 100644 +--- a/drivers/video/fbdev/amba-clcd.c ++++ b/drivers/video/fbdev/amba-clcd.c +@@ -849,12 +849,15 @@ static int clcdfb_of_vram_setup(struct clcd_fb *fb) + return -ENODEV; + + fb->fb.screen_base = of_iomap(memory, 0); +- if (!fb->fb.screen_base) ++ if (!fb->fb.screen_base) { ++ of_node_put(memory); + return -ENOMEM; ++ } + + fb->fb.fix.smem_start = of_translate_address(memory, + of_get_address(memory, 0, &size, NULL)); + fb->fb.fix.smem_len = size; ++ of_node_put(memory); + + return 0; + } +-- +2.35.1 + diff --git a/queue-4.9/x86-delay-fix-the-wrong-asm-constraint-in-delay_loop.patch b/queue-4.9/x86-delay-fix-the-wrong-asm-constraint-in-delay_loop.patch new file mode 100644 index 00000000000..af2caf3a9f4 --- /dev/null +++ b/queue-4.9/x86-delay-fix-the-wrong-asm-constraint-in-delay_loop.patch @@ -0,0 +1,51 @@ +From 3a636d178fd77891d0924137db2bd074b0b7deed Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Tue, 29 Mar 2022 17:47:04 +0700 +Subject: x86/delay: Fix the wrong asm constraint in delay_loop() + +From: Ammar Faizi + +[ Upstream commit b86eb74098a92afd789da02699b4b0dd3f73b889 ] + +The asm constraint does not reflect the fact that the asm statement can +modify the value of the local variable loops. Which it does. + +Specifying the wrong constraint may lead to undefined behavior, it may +clobber random stuff (e.g. local variable, important temporary value in +regs, etc.). This is especially dangerous when the compiler decides to +inline the function and since it doesn't know that the value gets +modified, it might decide to use it from a register directly without +reloading it. + +Change the constraint to "+a" to denote that the first argument is an +input and an output argument. + + [ bp: Fix typo, massage commit message. ] + +Fixes: e01b70ef3eb3 ("x86: fix bug in arch/i386/lib/delay.c file, delay_loop function") +Signed-off-by: Ammar Faizi +Signed-off-by: Borislav Petkov +Link: https://lore.kernel.org/r/20220329104705.65256-2-ammarfaizi2@gnuweeb.org +Signed-off-by: Sasha Levin +--- + arch/x86/lib/delay.c | 4 ++-- + 1 file changed, 2 insertions(+), 2 deletions(-) + +diff --git a/arch/x86/lib/delay.c b/arch/x86/lib/delay.c +index 71a3759a2d4e..60cc4f222cbf 100644 +--- a/arch/x86/lib/delay.c ++++ b/arch/x86/lib/delay.c +@@ -42,8 +42,8 @@ static void delay_loop(unsigned long loops) + " jnz 2b \n" + "3: dec %0 \n" + +- : /* we don't need output */ +- :"a" (loops) ++ : "+a" (loops) ++ : + ); + } + +-- +2.35.1 + diff --git a/queue-4.9/x86-mm-cleanup-the-control_va_addr_alignment-__setup.patch b/queue-4.9/x86-mm-cleanup-the-control_va_addr_alignment-__setup.patch new file mode 100644 index 00000000000..2c5062dbcae --- /dev/null +++ b/queue-4.9/x86-mm-cleanup-the-control_va_addr_alignment-__setup.patch @@ -0,0 +1,59 @@ +From 047f8b1f046d33222db5dd775a96191f88bfb234 Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Mon, 14 Mar 2022 17:10:45 -0700 +Subject: x86/mm: Cleanup the control_va_addr_alignment() __setup handler + +From: Randy Dunlap + +[ Upstream commit 1ef64b1e89e6d4018da46e08ffc32779a31160c7 ] + +Clean up control_va_addr_alignment(): + +a. Make '=' required instead of optional (as documented). +b. Print a warning if an invalid option value is used. +c. Return 1 from the __setup handler when an invalid option value is + used. This prevents the kernel from polluting init's (limited) + environment space with the entire string. + +Fixes: dfb09f9b7ab0 ("x86, amd: Avoid cache aliasing penalties on AMD family 15h") +Reported-by: Igor Zhbanov +Signed-off-by: Randy Dunlap +Signed-off-by: Borislav Petkov +Link: https://lore.kernel.org/r/64644a2f-4a20-bab3-1e15-3b2cdd0defe3@omprussia.ru +Link: https://lore.kernel.org/r/20220315001045.7680-1-rdunlap@infradead.org +Signed-off-by: Sasha Levin +--- + arch/x86/kernel/sys_x86_64.c | 7 ++----- + 1 file changed, 2 insertions(+), 5 deletions(-) + +diff --git a/arch/x86/kernel/sys_x86_64.c b/arch/x86/kernel/sys_x86_64.c +index 1d4e7fd3e66d..1078705292fc 100644 +--- a/arch/x86/kernel/sys_x86_64.c ++++ b/arch/x86/kernel/sys_x86_64.c +@@ -66,9 +66,6 @@ static int __init control_va_addr_alignment(char *str) + if (*str == 0) + return 1; + +- if (*str == '=') +- str++; +- + if (!strcmp(str, "32")) + va_align.flags = ALIGN_VA_32; + else if (!strcmp(str, "64")) +@@ -78,11 +75,11 @@ static int __init control_va_addr_alignment(char *str) + else if (!strcmp(str, "on")) + va_align.flags = ALIGN_VA_32 | ALIGN_VA_64; + else +- return 0; ++ pr_warn("invalid option value: 'align_va_addr=%s'\n", str); + + return 1; + } +-__setup("align_va_addr", control_va_addr_alignment); ++__setup("align_va_addr=", control_va_addr_alignment); + + SYSCALL_DEFINE6(mmap, unsigned long, addr, unsigned long, len, + unsigned long, prot, unsigned long, flags, +-- +2.35.1 + diff --git a/queue-4.9/x86-pm-fix-false-positive-kmemleak-report-in-msr_bui.patch b/queue-4.9/x86-pm-fix-false-positive-kmemleak-report-in-msr_bui.patch new file mode 100644 index 00000000000..4d685210e91 --- /dev/null +++ b/queue-4.9/x86-pm-fix-false-positive-kmemleak-report-in-msr_bui.patch @@ -0,0 +1,161 @@ +From 7273846f06e25752112cb6056b3adefaccc70e0a Mon Sep 17 00:00:00 2001 +From: Sasha Levin +Date: Sat, 23 Apr 2022 20:24:10 +0200 +Subject: x86/pm: Fix false positive kmemleak report in msr_build_context() + +From: Matthieu Baerts + +[ Upstream commit b0b592cf08367719e1d1ef07c9f136e8c17f7ec3 ] + +Since + + e2a1256b17b1 ("x86/speculation: Restore speculation related MSRs during S3 resume") + +kmemleak reports this issue: + + unreferenced object 0xffff888009cedc00 (size 256): + comm "swapper/0", pid 1, jiffies 4294693823 (age 73.764s) + hex dump (first 32 bytes): + 00 00 00 00 00 00 00 00 48 00 00 00 00 00 00 00 ........H....... + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ + backtrace: + msr_build_context (include/linux/slab.h:621) + pm_check_save_msr (arch/x86/power/cpu.c:520) + do_one_initcall (init/main.c:1298) + kernel_init_freeable (init/main.c:1370) + kernel_init (init/main.c:1504) + ret_from_fork (arch/x86/entry/entry_64.S:304) + +Reproducer: + + - boot the VM with a debug kernel config (see + https://github.com/multipath-tcp/mptcp_net-next/issues/268) + - wait ~1 minute + - start a kmemleak scan + +The root cause here is alignment within the packed struct saved_context +(from suspend_64.h). Kmemleak only searches for pointers that are +aligned (see how pointers are scanned in kmemleak.c), but pahole shows +that the saved_msrs struct member and all members after it in the +structure are unaligned: + + struct saved_context { + struct pt_regs regs; /* 0 168 */ + /* --- cacheline 2 boundary (128 bytes) was 40 bytes ago --- */ + u16 ds; /* 168 2 */ + + ... + + u64 misc_enable; /* 232 8 */ + bool misc_enable_saved; /* 240 1 */ + + /* Note below odd offset values for the remainder of this struct */ + + struct saved_msrs saved_msrs; /* 241 16 */ + /* --- cacheline 4 boundary (256 bytes) was 1 bytes ago --- */ + long unsigned int efer; /* 257 8 */ + u16 gdt_pad; /* 265 2 */ + struct desc_ptr gdt_desc; /* 267 10 */ + u16 idt_pad; /* 277 2 */ + struct desc_ptr idt; /* 279 10 */ + u16 ldt; /* 289 2 */ + u16 tss; /* 291 2 */ + long unsigned int tr; /* 293 8 */ + long unsigned int safety; /* 301 8 */ + long unsigned int return_address; /* 309 8 */ + + /* size: 317, cachelines: 5, members: 25 */ + /* last cacheline: 61 bytes */ + } __attribute__((__packed__)); + +Move misc_enable_saved to the end of the struct declaration so that +saved_msrs fits in before the cacheline 4 boundary. + +The comment above the saved_context declaration says to fix wakeup_64.S +file and __save/__restore_processor_state() if the struct is modified: +it looks like all the accesses in wakeup_64.S are done through offsets +which are computed at build-time. Update that comment accordingly. + +At the end, the false positive kmemleak report is due to a limitation +from kmemleak but it is always good to avoid unaligned members for +optimisation purposes. + +Please note that it looks like this issue is not new, e.g. + + https://lore.kernel.org/all/9f1bb619-c4ee-21c4-a251-870bd4db04fa@lwfinger.net/ + https://lore.kernel.org/all/94e48fcd-1dbd-ebd2-4c91-f39941735909@molgen.mpg.de/ + + [ bp: Massage + cleanup commit message. ] + +Fixes: 7a9c2dd08ead ("x86/pm: Introduce quirk framework to save/restore extra MSR registers around suspend/resume") +Suggested-by: Mat Martineau +Signed-off-by: Matthieu Baerts +Signed-off-by: Borislav Petkov +Reviewed-by: Rafael J. Wysocki +Link: https://lore.kernel.org/r/20220426202138.498310-1-matthieu.baerts@tessares.net +Signed-off-by: Sasha Levin +--- + arch/x86/include/asm/suspend_32.h | 2 +- + arch/x86/include/asm/suspend_64.h | 12 ++++++++---- + 2 files changed, 9 insertions(+), 5 deletions(-) + +diff --git a/arch/x86/include/asm/suspend_32.h b/arch/x86/include/asm/suspend_32.h +index 5cc2ce4ab8a3..4cb2a435dc85 100644 +--- a/arch/x86/include/asm/suspend_32.h ++++ b/arch/x86/include/asm/suspend_32.h +@@ -20,7 +20,6 @@ struct saved_context { + #endif + unsigned long cr0, cr2, cr3, cr4; + u64 misc_enable; +- bool misc_enable_saved; + struct saved_msrs saved_msrs; + struct desc_ptr gdt_desc; + struct desc_ptr idt; +@@ -29,6 +28,7 @@ struct saved_context { + unsigned long tr; + unsigned long safety; + unsigned long return_address; ++ bool misc_enable_saved; + } __attribute__((packed)); + + #endif /* _ASM_X86_SUSPEND_32_H */ +diff --git a/arch/x86/include/asm/suspend_64.h b/arch/x86/include/asm/suspend_64.h +index 701751918921..a235dd7983f0 100644 +--- a/arch/x86/include/asm/suspend_64.h ++++ b/arch/x86/include/asm/suspend_64.h +@@ -13,9 +13,13 @@ + * Image of the saved processor state, used by the low level ACPI suspend to + * RAM code and by the low level hibernation code. + * +- * If you modify it, fix arch/x86/kernel/acpi/wakeup_64.S and make sure that +- * __save/__restore_processor_state(), defined in arch/x86/kernel/suspend_64.c, +- * still work as required. ++ * If you modify it, check how it is used in arch/x86/kernel/acpi/wakeup_64.S ++ * and make sure that __save/__restore_processor_state(), defined in ++ * arch/x86/power/cpu.c, still work as required. ++ * ++ * Because the structure is packed, make sure to avoid unaligned members. For ++ * optimisation purposes but also because tools like kmemleak only search for ++ * pointers that are aligned. + */ + struct saved_context { + struct pt_regs regs; +@@ -35,7 +39,6 @@ struct saved_context { + + unsigned long cr0, cr2, cr3, cr4, cr8; + u64 misc_enable; +- bool misc_enable_saved; + struct saved_msrs saved_msrs; + unsigned long efer; + u16 gdt_pad; /* Unused */ +@@ -47,6 +50,7 @@ struct saved_context { + unsigned long tr; + unsigned long safety; + unsigned long return_address; ++ bool misc_enable_saved; + } __attribute__((packed)); + + #define loaddebug(thread,register) \ +-- +2.35.1 + -- 2.47.3