]> git.ipfire.org Git - thirdparty/kernel/stable-queue.git/commitdiff
Fixes for 5.4
authorSasha Levin <sashal@kernel.org>
Mon, 17 Feb 2025 16:47:43 +0000 (11:47 -0500)
committerSasha Levin <sashal@kernel.org>
Mon, 17 Feb 2025 16:47:43 +0000 (11:47 -0500)
Signed-off-by: Sasha Levin <sashal@kernel.org>
16 files changed:
queue-5.4/arm64-cacheinfo-avoid-out-of-bounds-write-to-cachein.patch [new file with mode: 0644]
queue-5.4/asoc-intel-bytcr_rt5640-add-dmi-quirk-for-vexia-edu-.patch [new file with mode: 0644]
queue-5.4/gpio-bcm-kona-add-missing-newline-to-dev_err-format-.patch [new file with mode: 0644]
queue-5.4/gpio-bcm-kona-fix-gpio-lock-unlock-for-banks-above-b.patch [new file with mode: 0644]
queue-5.4/gpio-bcm-kona-make-sure-gpio-bits-are-unlocked-when-.patch [new file with mode: 0644]
queue-5.4/grab-mm-lock-before-grabbing-pt-lock.patch [new file with mode: 0644]
queue-5.4/hid-multitouch-add-null-check-in-mt_input_configured.patch [new file with mode: 0644]
queue-5.4/media-cxd2841er-fix-64-bit-division-on-gcc-9.patch [new file with mode: 0644]
queue-5.4/ndisc-ndisc_send_redirect-must-use-dev_get_by_index_.patch [new file with mode: 0644]
queue-5.4/orangefs-fix-a-oob-in-orangefs_debug_write.patch [new file with mode: 0644]
queue-5.4/series
queue-5.4/team-better-team_option_type_string-validation.patch [new file with mode: 0644]
queue-5.4/vfio-pci-enable-iowrite64-and-ioread64-for-vfio-pci.patch [new file with mode: 0644]
queue-5.4/vrf-use-rcu-protection-in-l3mdev_l3_out.patch [new file with mode: 0644]
queue-5.4/x86-xen-allow-larger-contiguous-memory-regions-in-pv.patch [new file with mode: 0644]
queue-5.4/xen-remove-a-confusing-comment-on-auto-translated-gu.patch [new file with mode: 0644]

diff --git a/queue-5.4/arm64-cacheinfo-avoid-out-of-bounds-write-to-cachein.patch b/queue-5.4/arm64-cacheinfo-avoid-out-of-bounds-write-to-cachein.patch
new file mode 100644 (file)
index 0000000..c1e3da2
--- /dev/null
@@ -0,0 +1,55 @@
+From 033ecb53f85bd1477001816736f49558eb351733 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Thu, 6 Feb 2025 12:44:20 -0500
+Subject: arm64: cacheinfo: Avoid out-of-bounds write to cacheinfo array
+
+From: Radu Rendec <rrendec@redhat.com>
+
+[ Upstream commit 875d742cf5327c93cba1f11e12b08d3cce7a88d2 ]
+
+The loop that detects/populates cache information already has a bounds
+check on the array size but does not account for cache levels with
+separate data/instructions cache. Fix this by incrementing the index
+for any populated leaf (instead of any populated level).
+
+Fixes: 5d425c186537 ("arm64: kernel: add support for cpu cache information")
+
+Signed-off-by: Radu Rendec <rrendec@redhat.com>
+Link: https://lore.kernel.org/r/20250206174420.2178724-1-rrendec@redhat.com
+Signed-off-by: Will Deacon <will@kernel.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ arch/arm64/kernel/cacheinfo.c | 12 +++++++-----
+ 1 file changed, 7 insertions(+), 5 deletions(-)
+
+diff --git a/arch/arm64/kernel/cacheinfo.c b/arch/arm64/kernel/cacheinfo.c
+index 97c42be71338a..1510f457b6154 100644
+--- a/arch/arm64/kernel/cacheinfo.c
++++ b/arch/arm64/kernel/cacheinfo.c
+@@ -87,16 +87,18 @@ int populate_cache_leaves(unsigned int cpu)
+       unsigned int level, idx;
+       enum cache_type type;
+       struct cpu_cacheinfo *this_cpu_ci = get_cpu_cacheinfo(cpu);
+-      struct cacheinfo *this_leaf = this_cpu_ci->info_list;
++      struct cacheinfo *infos = this_cpu_ci->info_list;
+       for (idx = 0, level = 1; level <= this_cpu_ci->num_levels &&
+-           idx < this_cpu_ci->num_leaves; idx++, level++) {
++           idx < this_cpu_ci->num_leaves; level++) {
+               type = get_cache_type(level);
+               if (type == CACHE_TYPE_SEPARATE) {
+-                      ci_leaf_init(this_leaf++, CACHE_TYPE_DATA, level);
+-                      ci_leaf_init(this_leaf++, CACHE_TYPE_INST, level);
++                      if (idx + 1 >= this_cpu_ci->num_leaves)
++                              break;
++                      ci_leaf_init(&infos[idx++], CACHE_TYPE_DATA, level);
++                      ci_leaf_init(&infos[idx++], CACHE_TYPE_INST, level);
+               } else {
+-                      ci_leaf_init(this_leaf++, type, level);
++                      ci_leaf_init(&infos[idx++], type, level);
+               }
+       }
+       return 0;
+-- 
+2.39.5
+
diff --git a/queue-5.4/asoc-intel-bytcr_rt5640-add-dmi-quirk-for-vexia-edu-.patch b/queue-5.4/asoc-intel-bytcr_rt5640-add-dmi-quirk-for-vexia-edu-.patch
new file mode 100644 (file)
index 0000000..99f7091
--- /dev/null
@@ -0,0 +1,60 @@
+From c79d677857944fa5e41d701edb70d5218a52badc Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Thu, 23 Jan 2025 14:25:07 +0100
+Subject: ASoC: Intel: bytcr_rt5640: Add DMI quirk for Vexia Edu Atla 10 tablet
+ 5V
+
+From: Hans de Goede <hdegoede@redhat.com>
+
+[ Upstream commit 6917192378c1ce17ba31df51c4e0d8b1c97a453b ]
+
+The Vexia EDU ATLA 10 tablet comes in 2 different versions with
+significantly different mainboards. The only outward difference is that
+the charging barrel on one is marked 5V and the other is marked 9V.
+
+The 5V version mostly works with the BYTCR defaults, except that it is
+missing a CHAN package in its ACPI tables and the default of using
+SSP0-AIF2 is wrong, instead SSP0-AIF1 must be used. That and its jack
+detect signal is not inverted as it usually is.
+
+Add a DMI quirk for the 5V version to fix sound not working.
+
+Signed-off-by: Hans de Goede <hdegoede@redhat.com>
+Link: https://patch.msgid.link/20250123132507.18434-1-hdegoede@redhat.com
+Signed-off-by: Mark Brown <broonie@kernel.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ sound/soc/intel/boards/bytcr_rt5640.c | 17 ++++++++++++++++-
+ 1 file changed, 16 insertions(+), 1 deletion(-)
+
+diff --git a/sound/soc/intel/boards/bytcr_rt5640.c b/sound/soc/intel/boards/bytcr_rt5640.c
+index 53a15be38b56f..104cfb56d225f 100644
+--- a/sound/soc/intel/boards/bytcr_rt5640.c
++++ b/sound/soc/intel/boards/bytcr_rt5640.c
+@@ -909,7 +909,22 @@ static const struct dmi_system_id byt_rt5640_quirk_table[] = {
+                                       BYT_RT5640_SSP0_AIF2 |
+                                       BYT_RT5640_MCLK_EN),
+       },
+-      {       /* Vexia Edu Atla 10 tablet */
++      {
++              /* Vexia Edu Atla 10 tablet 5V version */
++              .matches = {
++                      /* Having all 3 of these not set is somewhat unique */
++                      DMI_MATCH(DMI_SYS_VENDOR, "To be filled by O.E.M."),
++                      DMI_MATCH(DMI_PRODUCT_NAME, "To be filled by O.E.M."),
++                      DMI_MATCH(DMI_BOARD_NAME, "To be filled by O.E.M."),
++                      /* Above strings are too generic, also match on BIOS date */
++                      DMI_MATCH(DMI_BIOS_DATE, "05/14/2015"),
++              },
++              .driver_data = (void *)(BYTCR_INPUT_DEFAULTS |
++                                      BYT_RT5640_JD_NOT_INV |
++                                      BYT_RT5640_SSP0_AIF1 |
++                                      BYT_RT5640_MCLK_EN),
++      },
++      {       /* Vexia Edu Atla 10 tablet 9V version */
+               .matches = {
+                       DMI_MATCH(DMI_BOARD_VENDOR, "AMI Corporation"),
+                       DMI_MATCH(DMI_BOARD_NAME, "Aptio CRB"),
+-- 
+2.39.5
+
diff --git a/queue-5.4/gpio-bcm-kona-add-missing-newline-to-dev_err-format-.patch b/queue-5.4/gpio-bcm-kona-add-missing-newline-to-dev_err-format-.patch
new file mode 100644 (file)
index 0000000..afdefd4
--- /dev/null
@@ -0,0 +1,40 @@
+From 33bf883bb39e2f6077d664ac727c57e71463e664 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Thu, 6 Feb 2025 18:46:02 +0100
+Subject: gpio: bcm-kona: Add missing newline to dev_err format string
+
+From: Artur Weber <aweber.kernel@gmail.com>
+
+[ Upstream commit 615279db222c3ac56d5c93716efd72b843295c1f ]
+
+Add a missing newline to the format string of the "Couldn't get IRQ
+for bank..." error message.
+
+Fixes: 757651e3d60e ("gpio: bcm281xx: Add GPIO driver")
+Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
+Reviewed-by: Markus Mayer <mmayer@broadcom.com>
+Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
+Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
+Link: https://lore.kernel.org/r/20250206-kona-gpio-fixes-v2-3-409135eab780@gmail.com
+Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/gpio/gpio-bcm-kona.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/drivers/gpio/gpio-bcm-kona.c b/drivers/gpio/gpio-bcm-kona.c
+index aad1d5af6382b..35bf2ecc71b49 100644
+--- a/drivers/gpio/gpio-bcm-kona.c
++++ b/drivers/gpio/gpio-bcm-kona.c
+@@ -674,7 +674,7 @@ static int bcm_kona_gpio_probe(struct platform_device *pdev)
+               bank->irq = platform_get_irq(pdev, i);
+               bank->kona_gpio = kona_gpio;
+               if (bank->irq < 0) {
+-                      dev_err(dev, "Couldn't get IRQ for bank %d", i);
++                      dev_err(dev, "Couldn't get IRQ for bank %d\n", i);
+                       ret = -ENOENT;
+                       goto err_irq_domain;
+               }
+-- 
+2.39.5
+
diff --git a/queue-5.4/gpio-bcm-kona-fix-gpio-lock-unlock-for-banks-above-b.patch b/queue-5.4/gpio-bcm-kona-fix-gpio-lock-unlock-for-banks-above-b.patch
new file mode 100644 (file)
index 0000000..7c4647f
--- /dev/null
@@ -0,0 +1,64 @@
+From e228ae7b3b0e2076312a7be89d00603e452f9473 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Thu, 6 Feb 2025 18:46:00 +0100
+Subject: gpio: bcm-kona: Fix GPIO lock/unlock for banks above bank 0
+
+From: Artur Weber <aweber.kernel@gmail.com>
+
+[ Upstream commit de1d0d160f64ee76df1d364d521b2faf465a091c ]
+
+The GPIO lock/unlock functions clear/write a bit to the relevant
+register for each bank. However, due to an oversight the bit that
+was being written was based on the total GPIO number, not the index
+of the GPIO within the relevant bank, causing it to fail for any
+GPIO above 32 (thus any GPIO for banks above bank 0).
+
+Fix lock/unlock for these banks by using the correct bit.
+
+Fixes: bdb93c03c550 ("gpio: bcm281xx: Centralize register locking")
+Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
+Reviewed-by: Markus Mayer <mmayer@broadcom.com>
+Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
+Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
+Link: https://lore.kernel.org/r/20250206-kona-gpio-fixes-v2-1-409135eab780@gmail.com
+Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/gpio/gpio-bcm-kona.c | 6 ++++--
+ 1 file changed, 4 insertions(+), 2 deletions(-)
+
+diff --git a/drivers/gpio/gpio-bcm-kona.c b/drivers/gpio/gpio-bcm-kona.c
+index 100575973e1fd..840a4b7e6c4d1 100644
+--- a/drivers/gpio/gpio-bcm-kona.c
++++ b/drivers/gpio/gpio-bcm-kona.c
+@@ -94,11 +94,12 @@ static void bcm_kona_gpio_lock_gpio(struct bcm_kona_gpio *kona_gpio,
+       u32 val;
+       unsigned long flags;
+       int bank_id = GPIO_BANK(gpio);
++      int bit = GPIO_BIT(gpio);
+       raw_spin_lock_irqsave(&kona_gpio->lock, flags);
+       val = readl(kona_gpio->reg_base + GPIO_PWD_STATUS(bank_id));
+-      val |= BIT(gpio);
++      val |= BIT(bit);
+       bcm_kona_gpio_write_lock_regs(kona_gpio->reg_base, bank_id, val);
+       raw_spin_unlock_irqrestore(&kona_gpio->lock, flags);
+@@ -110,11 +111,12 @@ static void bcm_kona_gpio_unlock_gpio(struct bcm_kona_gpio *kona_gpio,
+       u32 val;
+       unsigned long flags;
+       int bank_id = GPIO_BANK(gpio);
++      int bit = GPIO_BIT(gpio);
+       raw_spin_lock_irqsave(&kona_gpio->lock, flags);
+       val = readl(kona_gpio->reg_base + GPIO_PWD_STATUS(bank_id));
+-      val &= ~BIT(gpio);
++      val &= ~BIT(bit);
+       bcm_kona_gpio_write_lock_regs(kona_gpio->reg_base, bank_id, val);
+       raw_spin_unlock_irqrestore(&kona_gpio->lock, flags);
+-- 
+2.39.5
+
diff --git a/queue-5.4/gpio-bcm-kona-make-sure-gpio-bits-are-unlocked-when-.patch b/queue-5.4/gpio-bcm-kona-make-sure-gpio-bits-are-unlocked-when-.patch
new file mode 100644 (file)
index 0000000..90fd4e4
--- /dev/null
@@ -0,0 +1,160 @@
+From da27f04f26d02dfb4f99090db82119f39f7fe67b Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Thu, 6 Feb 2025 18:46:01 +0100
+Subject: gpio: bcm-kona: Make sure GPIO bits are unlocked when requesting IRQ
+
+From: Artur Weber <aweber.kernel@gmail.com>
+
+[ Upstream commit 57f5db77a915cc29461a679a6bcae7097967be1a ]
+
+The settings for all GPIOs are locked by default in bcm_kona_gpio_reset.
+The settings for a GPIO are unlocked when requesting it as a GPIO, but
+not when requesting it as an interrupt, causing the IRQ settings to not
+get applied.
+
+Fix this by making sure to unlock the right bits when an IRQ is requested.
+To avoid a situation where an IRQ being released causes a lock despite
+the same GPIO being used by a GPIO request or vice versa, add an unlock
+counter and only lock if it reaches 0.
+
+Fixes: 757651e3d60e ("gpio: bcm281xx: Add GPIO driver")
+Reviewed-by: Florian Fainelli <florian.fainelli@broadcom.com>
+Reviewed-by: Markus Mayer <mmayer@broadcom.com>
+Signed-off-by: Artur Weber <aweber.kernel@gmail.com>
+Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
+Link: https://lore.kernel.org/r/20250206-kona-gpio-fixes-v2-2-409135eab780@gmail.com
+Signed-off-by: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/gpio/gpio-bcm-kona.c | 67 +++++++++++++++++++++++++++++-------
+ 1 file changed, 55 insertions(+), 12 deletions(-)
+
+diff --git a/drivers/gpio/gpio-bcm-kona.c b/drivers/gpio/gpio-bcm-kona.c
+index 840a4b7e6c4d1..aad1d5af6382b 100644
+--- a/drivers/gpio/gpio-bcm-kona.c
++++ b/drivers/gpio/gpio-bcm-kona.c
+@@ -77,6 +77,22 @@ struct bcm_kona_gpio {
+ struct bcm_kona_gpio_bank {
+       int id;
+       int irq;
++      /*
++       * Used to keep track of lock/unlock operations for each GPIO in the
++       * bank.
++       *
++       * All GPIOs are locked by default (see bcm_kona_gpio_reset), and the
++       * unlock count for all GPIOs is 0 by default. Each unlock increments
++       * the counter, and each lock decrements the counter.
++       *
++       * The lock function only locks the GPIO once its unlock counter is
++       * down to 0. This is necessary because the GPIO is unlocked in two
++       * places in this driver: once for requested GPIOs, and once for
++       * requested IRQs. Since it is possible for a GPIO to be requested
++       * as both a GPIO and an IRQ, we need to ensure that we don't lock it
++       * too early.
++       */
++      u8 gpio_unlock_count[GPIO_PER_BANK];
+       /* Used in the interrupt handler */
+       struct bcm_kona_gpio *kona_gpio;
+ };
+@@ -95,14 +111,23 @@ static void bcm_kona_gpio_lock_gpio(struct bcm_kona_gpio *kona_gpio,
+       unsigned long flags;
+       int bank_id = GPIO_BANK(gpio);
+       int bit = GPIO_BIT(gpio);
++      struct bcm_kona_gpio_bank *bank = &kona_gpio->banks[bank_id];
+-      raw_spin_lock_irqsave(&kona_gpio->lock, flags);
++      if (bank->gpio_unlock_count[bit] == 0) {
++              dev_err(kona_gpio->gpio_chip.parent,
++                      "Unbalanced locks for GPIO %u\n", gpio);
++              return;
++      }
+-      val = readl(kona_gpio->reg_base + GPIO_PWD_STATUS(bank_id));
+-      val |= BIT(bit);
+-      bcm_kona_gpio_write_lock_regs(kona_gpio->reg_base, bank_id, val);
++      if (--bank->gpio_unlock_count[bit] == 0) {
++              raw_spin_lock_irqsave(&kona_gpio->lock, flags);
+-      raw_spin_unlock_irqrestore(&kona_gpio->lock, flags);
++              val = readl(kona_gpio->reg_base + GPIO_PWD_STATUS(bank_id));
++              val |= BIT(bit);
++              bcm_kona_gpio_write_lock_regs(kona_gpio->reg_base, bank_id, val);
++
++              raw_spin_unlock_irqrestore(&kona_gpio->lock, flags);
++      }
+ }
+ static void bcm_kona_gpio_unlock_gpio(struct bcm_kona_gpio *kona_gpio,
+@@ -112,14 +137,19 @@ static void bcm_kona_gpio_unlock_gpio(struct bcm_kona_gpio *kona_gpio,
+       unsigned long flags;
+       int bank_id = GPIO_BANK(gpio);
+       int bit = GPIO_BIT(gpio);
++      struct bcm_kona_gpio_bank *bank = &kona_gpio->banks[bank_id];
+-      raw_spin_lock_irqsave(&kona_gpio->lock, flags);
++      if (bank->gpio_unlock_count[bit] == 0) {
++              raw_spin_lock_irqsave(&kona_gpio->lock, flags);
+-      val = readl(kona_gpio->reg_base + GPIO_PWD_STATUS(bank_id));
+-      val &= ~BIT(bit);
+-      bcm_kona_gpio_write_lock_regs(kona_gpio->reg_base, bank_id, val);
++              val = readl(kona_gpio->reg_base + GPIO_PWD_STATUS(bank_id));
++              val &= ~BIT(bit);
++              bcm_kona_gpio_write_lock_regs(kona_gpio->reg_base, bank_id, val);
+-      raw_spin_unlock_irqrestore(&kona_gpio->lock, flags);
++              raw_spin_unlock_irqrestore(&kona_gpio->lock, flags);
++      }
++
++      ++bank->gpio_unlock_count[bit];
+ }
+ static int bcm_kona_gpio_get_dir(struct gpio_chip *chip, unsigned gpio)
+@@ -370,6 +400,7 @@ static void bcm_kona_gpio_irq_mask(struct irq_data *d)
+       kona_gpio = irq_data_get_irq_chip_data(d);
+       reg_base = kona_gpio->reg_base;
++
+       raw_spin_lock_irqsave(&kona_gpio->lock, flags);
+       val = readl(reg_base + GPIO_INT_MASK(bank_id));
+@@ -392,6 +423,7 @@ static void bcm_kona_gpio_irq_unmask(struct irq_data *d)
+       kona_gpio = irq_data_get_irq_chip_data(d);
+       reg_base = kona_gpio->reg_base;
++
+       raw_spin_lock_irqsave(&kona_gpio->lock, flags);
+       val = readl(reg_base + GPIO_INT_MSKCLR(bank_id));
+@@ -489,15 +521,26 @@ static void bcm_kona_gpio_irq_handler(struct irq_desc *desc)
+ static int bcm_kona_gpio_irq_reqres(struct irq_data *d)
+ {
+       struct bcm_kona_gpio *kona_gpio = irq_data_get_irq_chip_data(d);
++      unsigned int gpio = d->hwirq;
++
++      /*
++       * We need to unlock the GPIO before any other operations are performed
++       * on the relevant GPIO configuration registers
++       */
++      bcm_kona_gpio_unlock_gpio(kona_gpio, gpio);
+-      return gpiochip_reqres_irq(&kona_gpio->gpio_chip, d->hwirq);
++      return gpiochip_reqres_irq(&kona_gpio->gpio_chip, gpio);
+ }
+ static void bcm_kona_gpio_irq_relres(struct irq_data *d)
+ {
+       struct bcm_kona_gpio *kona_gpio = irq_data_get_irq_chip_data(d);
++      unsigned int gpio = d->hwirq;
++
++      /* Once we no longer use it, lock the GPIO again */
++      bcm_kona_gpio_lock_gpio(kona_gpio, gpio);
+-      gpiochip_relres_irq(&kona_gpio->gpio_chip, d->hwirq);
++      gpiochip_relres_irq(&kona_gpio->gpio_chip, gpio);
+ }
+ static struct irq_chip bcm_gpio_irq_chip = {
+-- 
+2.39.5
+
diff --git a/queue-5.4/grab-mm-lock-before-grabbing-pt-lock.patch b/queue-5.4/grab-mm-lock-before-grabbing-pt-lock.patch
new file mode 100644 (file)
index 0000000..229ec75
--- /dev/null
@@ -0,0 +1,156 @@
+From 14bb26aa6bf5e3394c76a5f2cc075220c57f9319 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Wed, 4 Dec 2024 11:35:15 +0100
+Subject: Grab mm lock before grabbing pt lock
+
+From: Maksym Planeta <maksym@exostellar.io>
+
+[ Upstream commit 6d002348789bc16e9203e9818b7a3688787e3b29 ]
+
+Function xen_pin_page calls xen_pte_lock, which in turn grab page
+table lock (ptlock). When locking, xen_pte_lock expect mm->page_table_lock
+to be held before grabbing ptlock, but this does not happen when pinning
+is caused by xen_mm_pin_all.
+
+This commit addresses lockdep warning below, which shows up when
+suspending a Xen VM.
+
+[ 3680.658422] Freezing user space processes
+[ 3680.660156] Freezing user space processes completed (elapsed 0.001 seconds)
+[ 3680.660182] OOM killer disabled.
+[ 3680.660192] Freezing remaining freezable tasks
+[ 3680.661485] Freezing remaining freezable tasks completed (elapsed 0.001 seconds)
+[ 3680.685254]
+[ 3680.685265] ==================================
+[ 3680.685269] WARNING: Nested lock was not taken
+[ 3680.685274] 6.12.0+ #16 Tainted: G        W
+[ 3680.685279] ----------------------------------
+[ 3680.685283] migration/0/19 is trying to lock:
+[ 3680.685288] ffff88800bac33c0 (ptlock_ptr(ptdesc)#2){+.+.}-{3:3}, at: xen_pin_page+0x175/0x1d0
+[ 3680.685303]
+[ 3680.685303] but this task is not holding:
+[ 3680.685308] init_mm.page_table_lock
+[ 3680.685311]
+[ 3680.685311] stack backtrace:
+[ 3680.685316] CPU: 0 UID: 0 PID: 19 Comm: migration/0 Tainted: G        W          6.12.0+ #16
+[ 3680.685324] Tainted: [W]=WARN
+[ 3680.685328] Stopper: multi_cpu_stop+0x0/0x120 <- __stop_cpus.constprop.0+0x8c/0xd0
+[ 3680.685339] Call Trace:
+[ 3680.685344]  <TASK>
+[ 3680.685347]  dump_stack_lvl+0x77/0xb0
+[ 3680.685356]  __lock_acquire+0x917/0x2310
+[ 3680.685364]  lock_acquire+0xce/0x2c0
+[ 3680.685369]  ? xen_pin_page+0x175/0x1d0
+[ 3680.685373]  _raw_spin_lock_nest_lock+0x2f/0x70
+[ 3680.685381]  ? xen_pin_page+0x175/0x1d0
+[ 3680.685386]  xen_pin_page+0x175/0x1d0
+[ 3680.685390]  ? __pfx_xen_pin_page+0x10/0x10
+[ 3680.685394]  __xen_pgd_walk+0x233/0x2c0
+[ 3680.685401]  ? stop_one_cpu+0x91/0x100
+[ 3680.685405]  __xen_pgd_pin+0x5d/0x250
+[ 3680.685410]  xen_mm_pin_all+0x70/0xa0
+[ 3680.685415]  xen_pv_pre_suspend+0xf/0x280
+[ 3680.685420]  xen_suspend+0x57/0x1a0
+[ 3680.685428]  multi_cpu_stop+0x6b/0x120
+[ 3680.685432]  ? update_cpumasks_hier+0x7c/0xa60
+[ 3680.685439]  ? __pfx_multi_cpu_stop+0x10/0x10
+[ 3680.685443]  cpu_stopper_thread+0x8c/0x140
+[ 3680.685448]  ? smpboot_thread_fn+0x20/0x1f0
+[ 3680.685454]  ? __pfx_smpboot_thread_fn+0x10/0x10
+[ 3680.685458]  smpboot_thread_fn+0xed/0x1f0
+[ 3680.685462]  kthread+0xde/0x110
+[ 3680.685467]  ? __pfx_kthread+0x10/0x10
+[ 3680.685471]  ret_from_fork+0x2f/0x50
+[ 3680.685478]  ? __pfx_kthread+0x10/0x10
+[ 3680.685482]  ret_from_fork_asm+0x1a/0x30
+[ 3680.685489]  </TASK>
+[ 3680.685491]
+[ 3680.685491] other info that might help us debug this:
+[ 3680.685497] 1 lock held by migration/0/19:
+[ 3680.685500]  #0: ffffffff8284df38 (pgd_lock){+.+.}-{3:3}, at: xen_mm_pin_all+0x14/0xa0
+[ 3680.685512]
+[ 3680.685512] stack backtrace:
+[ 3680.685518] CPU: 0 UID: 0 PID: 19 Comm: migration/0 Tainted: G        W          6.12.0+ #16
+[ 3680.685528] Tainted: [W]=WARN
+[ 3680.685531] Stopper: multi_cpu_stop+0x0/0x120 <- __stop_cpus.constprop.0+0x8c/0xd0
+[ 3680.685538] Call Trace:
+[ 3680.685541]  <TASK>
+[ 3680.685544]  dump_stack_lvl+0x77/0xb0
+[ 3680.685549]  __lock_acquire+0x93c/0x2310
+[ 3680.685554]  lock_acquire+0xce/0x2c0
+[ 3680.685558]  ? xen_pin_page+0x175/0x1d0
+[ 3680.685562]  _raw_spin_lock_nest_lock+0x2f/0x70
+[ 3680.685568]  ? xen_pin_page+0x175/0x1d0
+[ 3680.685572]  xen_pin_page+0x175/0x1d0
+[ 3680.685578]  ? __pfx_xen_pin_page+0x10/0x10
+[ 3680.685582]  __xen_pgd_walk+0x233/0x2c0
+[ 3680.685588]  ? stop_one_cpu+0x91/0x100
+[ 3680.685592]  __xen_pgd_pin+0x5d/0x250
+[ 3680.685596]  xen_mm_pin_all+0x70/0xa0
+[ 3680.685600]  xen_pv_pre_suspend+0xf/0x280
+[ 3680.685607]  xen_suspend+0x57/0x1a0
+[ 3680.685611]  multi_cpu_stop+0x6b/0x120
+[ 3680.685615]  ? update_cpumasks_hier+0x7c/0xa60
+[ 3680.685620]  ? __pfx_multi_cpu_stop+0x10/0x10
+[ 3680.685625]  cpu_stopper_thread+0x8c/0x140
+[ 3680.685629]  ? smpboot_thread_fn+0x20/0x1f0
+[ 3680.685634]  ? __pfx_smpboot_thread_fn+0x10/0x10
+[ 3680.685638]  smpboot_thread_fn+0xed/0x1f0
+[ 3680.685642]  kthread+0xde/0x110
+[ 3680.685645]  ? __pfx_kthread+0x10/0x10
+[ 3680.685649]  ret_from_fork+0x2f/0x50
+[ 3680.685654]  ? __pfx_kthread+0x10/0x10
+[ 3680.685657]  ret_from_fork_asm+0x1a/0x30
+[ 3680.685662]  </TASK>
+[ 3680.685267] xen:grant_table: Grant tables using version 1 layout
+[ 3680.685921] OOM killer enabled.
+[ 3680.685934] Restarting tasks ... done.
+
+Signed-off-by: Maksym Planeta <maksym@exostellar.io>
+Reviewed-by: Juergen Gross <jgross@suse.com>
+Message-ID: <20241204103516.3309112-1-maksym@exostellar.io>
+Signed-off-by: Juergen Gross <jgross@suse.com>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ arch/x86/xen/mmu_pv.c | 4 ++++
+ 1 file changed, 4 insertions(+)
+
+diff --git a/arch/x86/xen/mmu_pv.c b/arch/x86/xen/mmu_pv.c
+index 57fa2dbf3f7a9..d61e40466d786 100644
+--- a/arch/x86/xen/mmu_pv.c
++++ b/arch/x86/xen/mmu_pv.c
+@@ -887,6 +887,7 @@ void xen_mm_pin_all(void)
+ {
+       struct page *page;
++      spin_lock(&init_mm.page_table_lock);
+       spin_lock(&pgd_lock);
+       list_for_each_entry(page, &pgd_list, lru) {
+@@ -897,6 +898,7 @@ void xen_mm_pin_all(void)
+       }
+       spin_unlock(&pgd_lock);
++      spin_unlock(&init_mm.page_table_lock);
+ }
+ static int __init xen_mark_pinned(struct mm_struct *mm, struct page *page,
+@@ -1009,6 +1011,7 @@ void xen_mm_unpin_all(void)
+ {
+       struct page *page;
++      spin_lock(&init_mm.page_table_lock);
+       spin_lock(&pgd_lock);
+       list_for_each_entry(page, &pgd_list, lru) {
+@@ -1020,6 +1023,7 @@ void xen_mm_unpin_all(void)
+       }
+       spin_unlock(&pgd_lock);
++      spin_unlock(&init_mm.page_table_lock);
+ }
+ static void xen_activate_mm(struct mm_struct *prev, struct mm_struct *next)
+-- 
+2.39.5
+
diff --git a/queue-5.4/hid-multitouch-add-null-check-in-mt_input_configured.patch b/queue-5.4/hid-multitouch-add-null-check-in-mt_input_configured.patch
new file mode 100644 (file)
index 0000000..94d978f
--- /dev/null
@@ -0,0 +1,43 @@
+From cbbf83f57fda89e28e8b5212063ea7185200a7a8 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Fri, 15 Nov 2024 14:26:21 +0800
+Subject: HID: multitouch: Add NULL check in mt_input_configured
+
+From: Charles Han <hanchunchao@inspur.com>
+
+[ Upstream commit 9b8e2220d3a052a690b1d1b23019673e612494c5 ]
+
+devm_kasprintf() can return a NULL pointer on failure,but this
+returned value in mt_input_configured() is not checked.
+Add NULL check in mt_input_configured(), to handle kernel NULL
+pointer dereference error.
+
+Fixes: 479439463529 ("HID: multitouch: Correct devm device reference for hidinput input_dev name")
+Signed-off-by: Charles Han <hanchunchao@inspur.com>
+Signed-off-by: Jiri Kosina <jkosina@suse.com>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/hid/hid-multitouch.c | 5 ++++-
+ 1 file changed, 4 insertions(+), 1 deletion(-)
+
+diff --git a/drivers/hid/hid-multitouch.c b/drivers/hid/hid-multitouch.c
+index 5994e7d1b82d9..cb0bbba5c1c95 100644
+--- a/drivers/hid/hid-multitouch.c
++++ b/drivers/hid/hid-multitouch.c
+@@ -1601,9 +1601,12 @@ static int mt_input_configured(struct hid_device *hdev, struct hid_input *hi)
+               break;
+       }
+-      if (suffix)
++      if (suffix) {
+               hi->input->name = devm_kasprintf(&hdev->dev, GFP_KERNEL,
+                                                "%s %s", hdev->name, suffix);
++              if (!hi->input->name)
++                      return -ENOMEM;
++      }
+       return 0;
+ }
+-- 
+2.39.5
+
diff --git a/queue-5.4/media-cxd2841er-fix-64-bit-division-on-gcc-9.patch b/queue-5.4/media-cxd2841er-fix-64-bit-division-on-gcc-9.patch
new file mode 100644 (file)
index 0000000..2505b47
--- /dev/null
@@ -0,0 +1,53 @@
+From d8fe5d0cee72ffdd364d8a5925798fdfbcaac84b Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Mon, 11 Nov 2024 11:41:42 +0100
+Subject: media: cxd2841er: fix 64-bit division on gcc-9
+
+From: Arnd Bergmann <arnd@arndb.de>
+
+[ Upstream commit 8d46603eeeb4c6abff1d2e49f2a6ae289dac765e ]
+
+It appears that do_div() once more gets confused by a complex
+expression that ends up not quite being constant despite
+__builtin_constant_p() thinking it is:
+
+ERROR: modpost: "__aeabi_uldivmod" [drivers/media/dvb-frontends/cxd2841er.ko] undefined!
+
+Use div_u64() instead, forcing the expression to be evaluated
+first, and making it a bit more readable.
+
+Cc: Dan Carpenter <dan.carpenter@linaro.org>
+Reported-by: Naresh Kamboju <naresh.kamboju@linaro.org>
+Closes: https://lore.kernel.org/linux-media/CA+G9fYvvNm-aYodLaAwwTjEGtX0YxR-1R14FOA5aHKt0sSVsYg@mail.gmail.com/
+Reported-by: Linux Kernel Functional Testing <lkft@linaro.org>
+Closes: https://lore.kernel.org/linux-media/CA+G9fYvvNm-aYodLaAwwTjEGtX0YxR-1R14FOA5aHKt0sSVsYg@mail.gmail.com/
+Signed-off-by: Arnd Bergmann <arnd@arndb.de>
+Signed-off-by: Hans Verkuil <hverkuil@xs4all.nl>
+[hverkuil: added Closes tags]
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/media/dvb-frontends/cxd2841er.c | 8 ++------
+ 1 file changed, 2 insertions(+), 6 deletions(-)
+
+diff --git a/drivers/media/dvb-frontends/cxd2841er.c b/drivers/media/dvb-frontends/cxd2841er.c
+index 6b495fc36fd0c..51e890554457d 100644
+--- a/drivers/media/dvb-frontends/cxd2841er.c
++++ b/drivers/media/dvb-frontends/cxd2841er.c
+@@ -310,12 +310,8 @@ static int cxd2841er_set_reg_bits(struct cxd2841er_priv *priv,
+ static u32 cxd2841er_calc_iffreq_xtal(enum cxd2841er_xtal xtal, u32 ifhz)
+ {
+-      u64 tmp;
+-
+-      tmp = (u64) ifhz * 16777216;
+-      do_div(tmp, ((xtal == SONY_XTAL_24000) ? 48000000 : 41000000));
+-
+-      return (u32) tmp;
++      return div_u64(ifhz * 16777216ull,
++                     (xtal == SONY_XTAL_24000) ? 48000000 : 41000000);
+ }
+ static u32 cxd2841er_calc_iffreq(u32 ifhz)
+-- 
+2.39.5
+
diff --git a/queue-5.4/ndisc-ndisc_send_redirect-must-use-dev_get_by_index_.patch b/queue-5.4/ndisc-ndisc_send_redirect-must-use-dev_get_by_index_.patch
new file mode 100644 (file)
index 0000000..1a601a6
--- /dev/null
@@ -0,0 +1,41 @@
+From 7c84ac9a43d3ecfc5d5d1e16534c8d7265713c0c Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Fri, 7 Feb 2025 13:58:33 +0000
+Subject: ndisc: ndisc_send_redirect() must use dev_get_by_index_rcu()
+
+From: Eric Dumazet <edumazet@google.com>
+
+[ Upstream commit 48145a57d4bbe3496e8e4880b23ea6b511e6e519 ]
+
+ndisc_send_redirect() is called under RCU protection, not RTNL.
+
+It must use dev_get_by_index_rcu() instead of __dev_get_by_index()
+
+Fixes: 2f17becfbea5 ("vrf: check the original netdevice for generating redirect")
+Signed-off-by: Eric Dumazet <edumazet@google.com>
+Cc: Stephen Suryaputra <ssuryaextr@gmail.com>
+Reviewed-by: David Ahern <dsahern@kernel.org>
+Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
+Link: https://patch.msgid.link/20250207135841.1948589-2-edumazet@google.com
+Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ net/ipv6/ndisc.c | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/net/ipv6/ndisc.c b/net/ipv6/ndisc.c
+index 64729e7e6a866..3096807caecab 100644
+--- a/net/ipv6/ndisc.c
++++ b/net/ipv6/ndisc.c
+@@ -1597,7 +1597,7 @@ void ndisc_send_redirect(struct sk_buff *skb, const struct in6_addr *target)
+       bool ret;
+       if (netif_is_l3_master(skb->dev)) {
+-              dev = __dev_get_by_index(dev_net(skb->dev), IPCB(skb)->iif);
++              dev = dev_get_by_index_rcu(dev_net(skb->dev), IPCB(skb)->iif);
+               if (!dev)
+                       return;
+       }
+-- 
+2.39.5
+
diff --git a/queue-5.4/orangefs-fix-a-oob-in-orangefs_debug_write.patch b/queue-5.4/orangefs-fix-a-oob-in-orangefs_debug_write.patch
new file mode 100644 (file)
index 0000000..58d38f9
--- /dev/null
@@ -0,0 +1,39 @@
+From b48a4bc92a50ce92e2bd87325761d0532c2323b0 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Wed, 8 Jan 2025 14:21:08 -0500
+Subject: orangefs: fix a oob in orangefs_debug_write
+
+From: Mike Marshall <hubcap@omnibond.com>
+
+[ Upstream commit f7c848431632598ff9bce57a659db6af60d75b39 ]
+
+I got a syzbot report: slab-out-of-bounds Read in
+orangefs_debug_write... several people suggested fixes,
+I tested Al Viro's suggestion and made this patch.
+
+Signed-off-by: Mike Marshall <hubcap@omnibond.com>
+Reported-by: syzbot+fc519d7875f2d9186c1f@syzkaller.appspotmail.com
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ fs/orangefs/orangefs-debugfs.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/fs/orangefs/orangefs-debugfs.c b/fs/orangefs/orangefs-debugfs.c
+index 1b508f5433846..fa41db0884880 100644
+--- a/fs/orangefs/orangefs-debugfs.c
++++ b/fs/orangefs/orangefs-debugfs.c
+@@ -393,9 +393,9 @@ static ssize_t orangefs_debug_write(struct file *file,
+        * Thwart users who try to jamb a ridiculous number
+        * of bytes into the debug file...
+        */
+-      if (count > ORANGEFS_MAX_DEBUG_STRING_LEN + 1) {
++      if (count > ORANGEFS_MAX_DEBUG_STRING_LEN) {
+               silly = count;
+-              count = ORANGEFS_MAX_DEBUG_STRING_LEN + 1;
++              count = ORANGEFS_MAX_DEBUG_STRING_LEN;
+       }
+       buf = kzalloc(ORANGEFS_MAX_DEBUG_STRING_LEN, GFP_KERNEL);
+-- 
+2.39.5
+
index 4097b028e6dece210647f2d8cc93e2c7685cc5f9..da63270670f78a07ce6eafef780206d24cd3aa5c 100644 (file)
@@ -153,3 +153,18 @@ net-ncsi-wait-for-the-last-response-to-deselect-package-before-configuring-chann
 ptp-ensure-info-enable-callback-is-always-set.patch
 mips-ftrace-declare-ftrace_get_parent_ra_addr-as-static.patch
 ocfs2-check-dir-i_size-in-ocfs2_find_entry.patch
+hid-multitouch-add-null-check-in-mt_input_configured.patch
+ndisc-ndisc_send_redirect-must-use-dev_get_by_index_.patch
+vrf-use-rcu-protection-in-l3mdev_l3_out.patch
+team-better-team_option_type_string-validation.patch
+arm64-cacheinfo-avoid-out-of-bounds-write-to-cachein.patch
+gpio-bcm-kona-fix-gpio-lock-unlock-for-banks-above-b.patch
+gpio-bcm-kona-make-sure-gpio-bits-are-unlocked-when-.patch
+gpio-bcm-kona-add-missing-newline-to-dev_err-format-.patch
+xen-remove-a-confusing-comment-on-auto-translated-gu.patch
+x86-xen-allow-larger-contiguous-memory-regions-in-pv.patch
+media-cxd2841er-fix-64-bit-division-on-gcc-9.patch
+vfio-pci-enable-iowrite64-and-ioread64-for-vfio-pci.patch
+grab-mm-lock-before-grabbing-pt-lock.patch
+orangefs-fix-a-oob-in-orangefs_debug_write.patch
+asoc-intel-bytcr_rt5640-add-dmi-quirk-for-vexia-edu-.patch
diff --git a/queue-5.4/team-better-team_option_type_string-validation.patch b/queue-5.4/team-better-team_option_type_string-validation.patch
new file mode 100644 (file)
index 0000000..989786d
--- /dev/null
@@ -0,0 +1,76 @@
+From 8ee02383e137fabba4f1d35af25c157f9f0d4690 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Wed, 12 Feb 2025 13:49:28 +0000
+Subject: team: better TEAM_OPTION_TYPE_STRING validation
+
+From: Eric Dumazet <edumazet@google.com>
+
+[ Upstream commit 5bef3ac184b5626ea62385d6b82a1992b89d7940 ]
+
+syzbot reported following splat [1]
+
+Make sure user-provided data contains one nul byte.
+
+[1]
+ BUG: KMSAN: uninit-value in string_nocheck lib/vsprintf.c:633 [inline]
+ BUG: KMSAN: uninit-value in string+0x3ec/0x5f0 lib/vsprintf.c:714
+  string_nocheck lib/vsprintf.c:633 [inline]
+  string+0x3ec/0x5f0 lib/vsprintf.c:714
+  vsnprintf+0xa5d/0x1960 lib/vsprintf.c:2843
+  __request_module+0x252/0x9f0 kernel/module/kmod.c:149
+  team_mode_get drivers/net/team/team_core.c:480 [inline]
+  team_change_mode drivers/net/team/team_core.c:607 [inline]
+  team_mode_option_set+0x437/0x970 drivers/net/team/team_core.c:1401
+  team_option_set drivers/net/team/team_core.c:375 [inline]
+  team_nl_options_set_doit+0x1339/0x1f90 drivers/net/team/team_core.c:2662
+  genl_family_rcv_msg_doit net/netlink/genetlink.c:1115 [inline]
+  genl_family_rcv_msg net/netlink/genetlink.c:1195 [inline]
+  genl_rcv_msg+0x1214/0x12c0 net/netlink/genetlink.c:1210
+  netlink_rcv_skb+0x375/0x650 net/netlink/af_netlink.c:2543
+  genl_rcv+0x40/0x60 net/netlink/genetlink.c:1219
+  netlink_unicast_kernel net/netlink/af_netlink.c:1322 [inline]
+  netlink_unicast+0xf52/0x1260 net/netlink/af_netlink.c:1348
+  netlink_sendmsg+0x10da/0x11e0 net/netlink/af_netlink.c:1892
+  sock_sendmsg_nosec net/socket.c:718 [inline]
+  __sock_sendmsg+0x30f/0x380 net/socket.c:733
+  ____sys_sendmsg+0x877/0xb60 net/socket.c:2573
+  ___sys_sendmsg+0x28d/0x3c0 net/socket.c:2627
+  __sys_sendmsg net/socket.c:2659 [inline]
+  __do_sys_sendmsg net/socket.c:2664 [inline]
+  __se_sys_sendmsg net/socket.c:2662 [inline]
+  __x64_sys_sendmsg+0x212/0x3c0 net/socket.c:2662
+  x64_sys_call+0x2ed6/0x3c30 arch/x86/include/generated/asm/syscalls_64.h:47
+  do_syscall_x64 arch/x86/entry/common.c:52 [inline]
+  do_syscall_64+0xcd/0x1e0 arch/x86/entry/common.c:83
+ entry_SYSCALL_64_after_hwframe+0x77/0x7f
+
+Fixes: 3d249d4ca7d0 ("net: introduce ethernet teaming device")
+Reported-by: syzbot+1fcd957a82e3a1baa94d@syzkaller.appspotmail.com
+Closes: https://syzkaller.appspot.com/bug?extid=1fcd957a82e3a1baa94d
+Signed-off-by: Eric Dumazet <edumazet@google.com>
+Reviewed-by: Jiri Pirko <jiri@nvidia.com>
+Link: https://patch.msgid.link/20250212134928.1541609-1-edumazet@google.com
+Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/net/team/team.c | 4 +++-
+ 1 file changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/drivers/net/team/team.c b/drivers/net/team/team.c
+index b0a9dd33a0196..197aea66b30dd 100644
+--- a/drivers/net/team/team.c
++++ b/drivers/net/team/team.c
+@@ -2663,7 +2663,9 @@ static int team_nl_cmd_options_set(struct sk_buff *skb, struct genl_info *info)
+                               ctx.data.u32_val = nla_get_u32(attr_data);
+                               break;
+                       case TEAM_OPTION_TYPE_STRING:
+-                              if (nla_len(attr_data) > TEAM_STRING_MAX_LEN) {
++                              if (nla_len(attr_data) > TEAM_STRING_MAX_LEN ||
++                                  !memchr(nla_data(attr_data), '\0',
++                                          nla_len(attr_data))) {
+                                       err = -EINVAL;
+                                       goto team_put;
+                               }
+-- 
+2.39.5
+
diff --git a/queue-5.4/vfio-pci-enable-iowrite64-and-ioread64-for-vfio-pci.patch b/queue-5.4/vfio-pci-enable-iowrite64-and-ioread64-for-vfio-pci.patch
new file mode 100644 (file)
index 0000000..44a0076
--- /dev/null
@@ -0,0 +1,49 @@
+From 9b5e6f7a01498d2cd11d29d582f278dac756f248 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Tue, 10 Dec 2024 05:19:37 -0800
+Subject: vfio/pci: Enable iowrite64 and ioread64 for vfio pci
+
+From: Ramesh Thomas <ramesh.thomas@intel.com>
+
+[ Upstream commit 2b938e3db335e3670475e31a722c2bee34748c5a ]
+
+Definitions of ioread64 and iowrite64 macros in asm/io.h called by vfio
+pci implementations are enclosed inside check for CONFIG_GENERIC_IOMAP.
+They don't get defined if CONFIG_GENERIC_IOMAP is defined. Include
+linux/io-64-nonatomic-lo-hi.h to define iowrite64 and ioread64 macros
+when they are not defined. io-64-nonatomic-lo-hi.h maps the macros to
+generic implementation in lib/iomap.c. The generic implementation does
+64 bit rw if readq/writeq is defined for the architecture, otherwise it
+would do 32 bit back to back rw.
+
+Note that there are two versions of the generic implementation that
+differs in the order the 32 bit words are written if 64 bit support is
+not present. This is not the little/big endian ordering, which is
+handled separately. This patch uses the lo followed by hi word ordering
+which is consistent with current back to back implementation in the
+vfio/pci code.
+
+Signed-off-by: Ramesh Thomas <ramesh.thomas@intel.com>
+Reviewed-by: Jason Gunthorpe <jgg@nvidia.com>
+Link: https://lore.kernel.org/r/20241210131938.303500-2-ramesh.thomas@intel.com
+Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ drivers/vfio/pci/vfio_pci_rdwr.c | 1 +
+ 1 file changed, 1 insertion(+)
+
+diff --git a/drivers/vfio/pci/vfio_pci_rdwr.c b/drivers/vfio/pci/vfio_pci_rdwr.c
+index 83f81d24df78e..94e3fb9f42243 100644
+--- a/drivers/vfio/pci/vfio_pci_rdwr.c
++++ b/drivers/vfio/pci/vfio_pci_rdwr.c
+@@ -16,6 +16,7 @@
+ #include <linux/io.h>
+ #include <linux/vfio.h>
+ #include <linux/vgaarb.h>
++#include <linux/io-64-nonatomic-lo-hi.h>
+ #include "vfio_pci_private.h"
+-- 
+2.39.5
+
diff --git a/queue-5.4/vrf-use-rcu-protection-in-l3mdev_l3_out.patch b/queue-5.4/vrf-use-rcu-protection-in-l3mdev_l3_out.patch
new file mode 100644 (file)
index 0000000..a40c80d
--- /dev/null
@@ -0,0 +1,52 @@
+From ce70a73b43bbab4324a1c0db480e9692275e6460 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Fri, 7 Feb 2025 13:58:38 +0000
+Subject: vrf: use RCU protection in l3mdev_l3_out()
+
+From: Eric Dumazet <edumazet@google.com>
+
+[ Upstream commit 6d0ce46a93135d96b7fa075a94a88fe0da8e8773 ]
+
+l3mdev_l3_out() can be called without RCU being held:
+
+raw_sendmsg()
+ ip_push_pending_frames()
+  ip_send_skb()
+   ip_local_out()
+    __ip_local_out()
+     l3mdev_ip_out()
+
+Add rcu_read_lock() / rcu_read_unlock() pair to avoid
+a potential UAF.
+
+Fixes: a8e3e1a9f020 ("net: l3mdev: Add hook to output path")
+Signed-off-by: Eric Dumazet <edumazet@google.com>
+Reviewed-by: David Ahern <dsahern@kernel.org>
+Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>
+Link: https://patch.msgid.link/20250207135841.1948589-7-edumazet@google.com
+Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ include/net/l3mdev.h | 2 ++
+ 1 file changed, 2 insertions(+)
+
+diff --git a/include/net/l3mdev.h b/include/net/l3mdev.h
+index e942372b077b5..062da1588be05 100644
+--- a/include/net/l3mdev.h
++++ b/include/net/l3mdev.h
+@@ -179,10 +179,12 @@ struct sk_buff *l3mdev_l3_out(struct sock *sk, struct sk_buff *skb, u16 proto)
+       if (netif_is_l3_slave(dev)) {
+               struct net_device *master;
++              rcu_read_lock();
+               master = netdev_master_upper_dev_get_rcu(dev);
+               if (master && master->l3mdev_ops->l3mdev_l3_out)
+                       skb = master->l3mdev_ops->l3mdev_l3_out(master, sk,
+                                                               skb, proto);
++              rcu_read_unlock();
+       }
+       return skb;
+-- 
+2.39.5
+
diff --git a/queue-5.4/x86-xen-allow-larger-contiguous-memory-regions-in-pv.patch b/queue-5.4/x86-xen-allow-larger-contiguous-memory-regions-in-pv.patch
new file mode 100644 (file)
index 0000000..b1442aa
--- /dev/null
@@ -0,0 +1,171 @@
+From 61f84fdc9f6440415d758197965973e84f08aefb Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Tue, 11 Feb 2025 11:16:28 +0100
+Subject: x86/xen: allow larger contiguous memory regions in PV guests
+
+From: Juergen Gross <jgross@suse.com>
+
+[ Upstream commit e93ec87286bd1fd30b7389e7a387cfb259f297e3 ]
+
+Today a PV guest (including dom0) can create 2MB contiguous memory
+regions for DMA buffers at max. This has led to problems at least
+with the megaraid_sas driver, which wants to allocate a 2.3MB DMA
+buffer.
+
+The limiting factor is the frame array used to do the hypercall for
+making the memory contiguous, which has 512 entries and is just a
+static array in mmu_pv.c.
+
+In order to not waste memory for non-PV guests, put the initial
+frame array into .init.data section and dynamically allocate an array
+from the .init_after_bootmem hook of PV guests.
+
+In case a contiguous memory area larger than the initially supported
+2MB is requested, allocate a larger buffer for the frame list. Note
+that such an allocation is tried only after memory management has been
+initialized properly, which is tested via a flag being set in the
+.init_after_bootmem hook.
+
+Fixes: 9f40ec84a797 ("xen/swiotlb: add alignment check for dma buffers")
+Signed-off-by: Juergen Gross <jgross@suse.com>
+Tested-by: Alan Robinson <Alan.Robinson@fujitsu.com>
+Reviewed-by: Jan Beulich <jbeulich@suse.com>
+Signed-off-by: Juergen Gross <jgross@suse.com>
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ arch/x86/xen/mmu_pv.c | 71 +++++++++++++++++++++++++++++++++++++------
+ 1 file changed, 62 insertions(+), 9 deletions(-)
+
+diff --git a/arch/x86/xen/mmu_pv.c b/arch/x86/xen/mmu_pv.c
+index 5d54a75eb8781..57fa2dbf3f7a9 100644
+--- a/arch/x86/xen/mmu_pv.c
++++ b/arch/x86/xen/mmu_pv.c
+@@ -106,6 +106,51 @@ static pud_t level3_user_vsyscall[PTRS_PER_PUD] __page_aligned_bss;
+  */
+ static DEFINE_SPINLOCK(xen_reservation_lock);
++/* Protected by xen_reservation_lock. */
++#define MIN_CONTIG_ORDER 9 /* 2MB */
++static unsigned int discontig_frames_order = MIN_CONTIG_ORDER;
++static unsigned long discontig_frames_early[1UL << MIN_CONTIG_ORDER] __initdata;
++static unsigned long *discontig_frames __refdata = discontig_frames_early;
++static bool discontig_frames_dyn;
++
++static int alloc_discontig_frames(unsigned int order)
++{
++      unsigned long *new_array, *old_array;
++      unsigned int old_order;
++      unsigned long flags;
++
++      BUG_ON(order < MIN_CONTIG_ORDER);
++      BUILD_BUG_ON(sizeof(discontig_frames_early) != PAGE_SIZE);
++
++      new_array = (unsigned long *)__get_free_pages(GFP_KERNEL,
++                                                    order - MIN_CONTIG_ORDER);
++      if (!new_array)
++              return -ENOMEM;
++
++      spin_lock_irqsave(&xen_reservation_lock, flags);
++
++      old_order = discontig_frames_order;
++
++      if (order > discontig_frames_order || !discontig_frames_dyn) {
++              if (!discontig_frames_dyn)
++                      old_array = NULL;
++              else
++                      old_array = discontig_frames;
++
++              discontig_frames = new_array;
++              discontig_frames_order = order;
++              discontig_frames_dyn = true;
++      } else {
++              old_array = new_array;
++      }
++
++      spin_unlock_irqrestore(&xen_reservation_lock, flags);
++
++      free_pages((unsigned long)old_array, old_order - MIN_CONTIG_ORDER);
++
++      return 0;
++}
++
+ /*
+  * Note about cr3 (pagetable base) values:
+  *
+@@ -874,6 +919,9 @@ static void __init xen_after_bootmem(void)
+       SetPagePinned(virt_to_page(level3_user_vsyscall));
+ #endif
+       xen_pgd_walk(&init_mm, xen_mark_pinned, FIXADDR_TOP);
++
++      if (alloc_discontig_frames(MIN_CONTIG_ORDER))
++              BUG();
+ }
+ static int xen_unpin_page(struct mm_struct *mm, struct page *page,
+@@ -2467,10 +2515,6 @@ void __init xen_init_mmu_ops(void)
+       memset(dummy_mapping, 0xff, PAGE_SIZE);
+ }
+-/* Protected by xen_reservation_lock. */
+-#define MAX_CONTIG_ORDER 9 /* 2MB */
+-static unsigned long discontig_frames[1<<MAX_CONTIG_ORDER];
+-
+ #define VOID_PTE (mfn_pte(0, __pgprot(0)))
+ static void xen_zap_pfn_range(unsigned long vaddr, unsigned int order,
+                               unsigned long *in_frames,
+@@ -2587,18 +2631,25 @@ int xen_create_contiguous_region(phys_addr_t pstart, unsigned int order,
+                                unsigned int address_bits,
+                                dma_addr_t *dma_handle)
+ {
+-      unsigned long *in_frames = discontig_frames, out_frame;
++      unsigned long *in_frames, out_frame;
+       unsigned long  flags;
+       int            success;
+       unsigned long vstart = (unsigned long)phys_to_virt(pstart);
+-      if (unlikely(order > MAX_CONTIG_ORDER))
+-              return -ENOMEM;
++      if (unlikely(order > discontig_frames_order)) {
++              if (!discontig_frames_dyn)
++                      return -ENOMEM;
++
++              if (alloc_discontig_frames(order))
++                      return -ENOMEM;
++      }
+       memset((void *) vstart, 0, PAGE_SIZE << order);
+       spin_lock_irqsave(&xen_reservation_lock, flags);
++      in_frames = discontig_frames;
++
+       /* 1. Zap current PTEs, remembering MFNs. */
+       xen_zap_pfn_range(vstart, order, in_frames, NULL);
+@@ -2622,12 +2673,12 @@ int xen_create_contiguous_region(phys_addr_t pstart, unsigned int order,
+ void xen_destroy_contiguous_region(phys_addr_t pstart, unsigned int order)
+ {
+-      unsigned long *out_frames = discontig_frames, in_frame;
++      unsigned long *out_frames, in_frame;
+       unsigned long  flags;
+       int success;
+       unsigned long vstart;
+-      if (unlikely(order > MAX_CONTIG_ORDER))
++      if (unlikely(order > discontig_frames_order))
+               return;
+       vstart = (unsigned long)phys_to_virt(pstart);
+@@ -2635,6 +2686,8 @@ void xen_destroy_contiguous_region(phys_addr_t pstart, unsigned int order)
+       spin_lock_irqsave(&xen_reservation_lock, flags);
++      out_frames = discontig_frames;
++
+       /* 1. Find start MFN of contiguous extent. */
+       in_frame = virt_to_mfn(vstart);
+-- 
+2.39.5
+
diff --git a/queue-5.4/xen-remove-a-confusing-comment-on-auto-translated-gu.patch b/queue-5.4/xen-remove-a-confusing-comment-on-auto-translated-gu.patch
new file mode 100644 (file)
index 0000000..aa9779e
--- /dev/null
@@ -0,0 +1,44 @@
+From 5cb7967b5c902ea3115071b3a4ffa68b306995f5 Mon Sep 17 00:00:00 2001
+From: Sasha Levin <sashal@kernel.org>
+Date: Wed, 2 Aug 2023 18:31:51 +0200
+Subject: xen: remove a confusing comment on auto-translated guest I/O
+
+From: Petr Tesarik <petr.tesarik.ext@huawei.com>
+
+[ Upstream commit d826c9e61c99120f8996f8fed6417167e32eb922 ]
+
+After removing the conditional return from xen_create_contiguous_region(),
+the accompanying comment was left in place, but it now precedes an
+unrelated conditional and confuses readers.
+
+Fixes: 989513a735f5 ("xen: cleanup pvh leftovers from pv-only sources")
+Signed-off-by: Petr Tesarik <petr.tesarik.ext@huawei.com>
+Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
+Link: https://lore.kernel.org/r/20230802163151.1486-1-petrtesarik@huaweicloud.com
+Signed-off-by: Juergen Gross <jgross@suse.com>
+Stable-dep-of: e93ec87286bd ("x86/xen: allow larger contiguous memory regions in PV guests")
+Signed-off-by: Sasha Levin <sashal@kernel.org>
+---
+ arch/x86/xen/mmu_pv.c | 6 ------
+ 1 file changed, 6 deletions(-)
+
+diff --git a/arch/x86/xen/mmu_pv.c b/arch/x86/xen/mmu_pv.c
+index c8dbee62ec2ab..5d54a75eb8781 100644
+--- a/arch/x86/xen/mmu_pv.c
++++ b/arch/x86/xen/mmu_pv.c
+@@ -2592,12 +2592,6 @@ int xen_create_contiguous_region(phys_addr_t pstart, unsigned int order,
+       int            success;
+       unsigned long vstart = (unsigned long)phys_to_virt(pstart);
+-      /*
+-       * Currently an auto-translated guest will not perform I/O, nor will
+-       * it require PAE page directories below 4GB. Therefore any calls to
+-       * this function are redundant and can be ignored.
+-       */
+-
+       if (unlikely(order > MAX_CONTIG_ORDER))
+               return -ENOMEM;
+-- 
+2.39.5
+