2020-06-05 14:19:01

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 00/14] 5.7.1-rc1 review

This is the start of the stable review cycle for the 5.7.1 release.
There are 14 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.

Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
Anything received after that time might be too late.

The whole patch series can be found in one patch at:
https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
or in the git tree and branch at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
and the diffstat can be found below.

thanks,

greg k-h

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <[email protected]>
Linux 5.7.1-rc1

Dan Carpenter <[email protected]>
airo: Fix read overflows sending packets

DENG Qingfang <[email protected]>
net: dsa: mt7530: set CPU port to fallback mode

Sakari Ailus <[email protected]>
media: staging: ipu3-imgu: Move alignment attribute to field

Sakari Ailus <[email protected]>
media: Revert "staging: imgu: Address a compiler warning on alignment"

Jérôme Pouiller <[email protected]>
mmc: fix compilation of user API

Daniel Axtens <[email protected]>
kernel/relay.c: handle alloc_percpu returning NULL in relay_open

Herbert Xu <[email protected]>
crypto: api - Fix use-after-free and race in crypto_spawn_alg

Matthew Garrett <[email protected]>
mt76: mt76x02u: Add support for newer versions of the XBox One wifi adapter

Giuseppe Marco Randazzo <[email protected]>
p54usb: add AirVasT USB stick device-id

Julian Sax <[email protected]>
HID: i2c-hid: add Schneider SCL142ALM to descriptor override

Benjamin Tissoires <[email protected]>
HID: multitouch: enable multi-input as a quirk for some devices

Scott Shumate <[email protected]>
HID: sony: Fix for broken buttons on DS3 USB dongles

Fan Yang <[email protected]>
mm: Fix mremap not considering huge pmd devmap

Brad Love <[email protected]>
media: dvbdev: Fix tuner->demod media controller link


-------------

Diffstat:

Makefile | 4 ++--
arch/x86/include/asm/pgtable.h | 1 +
crypto/algapi.c | 22 +++++++++++++++------
crypto/api.c | 3 ++-
crypto/internal.h | 1 +
drivers/hid/hid-multitouch.c | 26 +++++++++++++++++++++++++
drivers/hid/hid-sony.c | 17 ++++++++++++++++
drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c | 8 ++++++++
drivers/media/dvb-core/dvbdev.c | 5 +++--
drivers/net/dsa/mt7530.c | 11 ++++++++---
drivers/net/dsa/mt7530.h | 6 ++++++
drivers/net/wireless/cisco/airo.c | 12 ++++++++++++
drivers/net/wireless/intersil/p54/p54usb.c | 1 +
drivers/net/wireless/mediatek/mt76/mt76x02.h | 1 +
drivers/net/wireless/mediatek/mt76/mt76x2/usb.c | 1 +
drivers/staging/media/ipu3/include/intel-ipu3.h | 7 ++++---
include/uapi/linux/mmc/ioctl.h | 1 +
kernel/relay.c | 5 +++++
mm/mremap.c | 2 +-
19 files changed, 116 insertions(+), 18 deletions(-)



2020-06-05 14:19:01

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 07/14] mt76: mt76x02u: Add support for newer versions of the XBox One wifi adapter

From: Matthew Garrett <[email protected]>

commit b2934279c3e9719145ff4090d4ab951e340df17e upstream.

The current version has a new USB ID and reports as an 0x7632 device.
Adding the IDs results in it working out of the box.

Signed-off-by: Matthew Garrett <[email protected]>
Signed-off-by: Felix Fietkau <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
drivers/net/wireless/mediatek/mt76/mt76x02.h | 1 +
drivers/net/wireless/mediatek/mt76/mt76x2/usb.c | 1 +
2 files changed, 2 insertions(+)

--- a/drivers/net/wireless/mediatek/mt76/mt76x02.h
+++ b/drivers/net/wireless/mediatek/mt76/mt76x02.h
@@ -216,6 +216,7 @@ static inline bool is_mt76x0(struct mt76
static inline bool is_mt76x2(struct mt76x02_dev *dev)
{
return mt76_chip(&dev->mt76) == 0x7612 ||
+ mt76_chip(&dev->mt76) == 0x7632 ||
mt76_chip(&dev->mt76) == 0x7662 ||
mt76_chip(&dev->mt76) == 0x7602;
}
--- a/drivers/net/wireless/mediatek/mt76/mt76x2/usb.c
+++ b/drivers/net/wireless/mediatek/mt76/mt76x2/usb.c
@@ -18,6 +18,7 @@ static const struct usb_device_id mt76x2
{ USB_DEVICE(0x7392, 0xb711) }, /* Edimax EW 7722 UAC */
{ USB_DEVICE(0x0846, 0x9053) }, /* Netgear A6210 */
{ USB_DEVICE(0x045e, 0x02e6) }, /* XBox One Wireless Adapter */
+ { USB_DEVICE(0x045e, 0x02fe) }, /* XBox One Wireless Adapter */
{ },
};



2020-06-05 14:19:25

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 14/14] airo: Fix read overflows sending packets

From: Dan Carpenter <[email protected]>

commit 11e7a91994c29da96d847f676be023da6a2c1359 upstream.

The problem is that we always copy a minimum of ETH_ZLEN (60) bytes from
skb->data even when skb->len is less than ETH_ZLEN so it leads to a read
overflow.

The fix is to pad skb->data to at least ETH_ZLEN bytes.

Cc: <[email protected]>
Reported-by: Hu Jiahui <[email protected]>
Signed-off-by: Dan Carpenter <[email protected]>
Reviewed-by: Eric Dumazet <[email protected]>
Signed-off-by: Kalle Valo <[email protected]>
Link: https://lore.kernel.org/r/20200527184830.GA1164846@mwanda
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
drivers/net/wireless/cisco/airo.c | 12 ++++++++++++
1 file changed, 12 insertions(+)

--- a/drivers/net/wireless/cisco/airo.c
+++ b/drivers/net/wireless/cisco/airo.c
@@ -1925,6 +1925,10 @@ static netdev_tx_t mpi_start_xmit(struct
airo_print_err(dev->name, "%s: skb == NULL!",__func__);
return NETDEV_TX_OK;
}
+ if (skb_padto(skb, ETH_ZLEN)) {
+ dev->stats.tx_dropped++;
+ return NETDEV_TX_OK;
+ }
npacks = skb_queue_len (&ai->txq);

if (npacks >= MAXTXQ - 1) {
@@ -2127,6 +2131,10 @@ static netdev_tx_t airo_start_xmit(struc
airo_print_err(dev->name, "%s: skb == NULL!", __func__);
return NETDEV_TX_OK;
}
+ if (skb_padto(skb, ETH_ZLEN)) {
+ dev->stats.tx_dropped++;
+ return NETDEV_TX_OK;
+ }

/* Find a vacant FID */
for( i = 0; i < MAX_FIDS / 2 && (fids[i] & 0xffff0000); i++ );
@@ -2201,6 +2209,10 @@ static netdev_tx_t airo_start_xmit11(str
airo_print_err(dev->name, "%s: skb == NULL!", __func__);
return NETDEV_TX_OK;
}
+ if (skb_padto(skb, ETH_ZLEN)) {
+ dev->stats.tx_dropped++;
+ return NETDEV_TX_OK;
+ }

/* Find a vacant FID */
for( i = MAX_FIDS / 2; i < MAX_FIDS && (fids[i] & 0xffff0000); i++ );


2020-06-05 14:19:26

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 08/14] crypto: api - Fix use-after-free and race in crypto_spawn_alg

From: Herbert Xu <[email protected]>

commit 6603523bf5e432c7c8490fb500793bb15d4e5f61 upstream.

There are two problems in crypto_spawn_alg. First of all it may
return spawn->alg even if spawn->dead is set. This results in a
double-free as detected by syzbot.

Secondly the setting of the DYING flag is racy because we hold
the read-lock instead of the write-lock. We should instead call
crypto_shoot_alg in a safe manner by gaining a refcount, dropping
the lock, and then releasing the refcount.

This patch fixes both problems.

Reported-by: [email protected]
Fixes: 4f87ee118d16 ("crypto: api - Do not zap spawn->alg")
Fixes: 73669cc55646 ("crypto: api - Fix race condition in...")
Cc: <[email protected]>
Signed-off-by: Herbert Xu <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
crypto/algapi.c | 22 ++++++++++++++++------
crypto/api.c | 3 ++-
crypto/internal.h | 1 +
3 files changed, 19 insertions(+), 7 deletions(-)

--- a/crypto/algapi.c
+++ b/crypto/algapi.c
@@ -716,17 +716,27 @@ EXPORT_SYMBOL_GPL(crypto_drop_spawn);

static struct crypto_alg *crypto_spawn_alg(struct crypto_spawn *spawn)
{
- struct crypto_alg *alg;
+ struct crypto_alg *alg = ERR_PTR(-EAGAIN);
+ struct crypto_alg *target;
+ bool shoot = false;

down_read(&crypto_alg_sem);
- alg = spawn->alg;
- if (!spawn->dead && !crypto_mod_get(alg)) {
- alg->cra_flags |= CRYPTO_ALG_DYING;
- alg = NULL;
+ if (!spawn->dead) {
+ alg = spawn->alg;
+ if (!crypto_mod_get(alg)) {
+ target = crypto_alg_get(alg);
+ shoot = true;
+ alg = ERR_PTR(-EAGAIN);
+ }
}
up_read(&crypto_alg_sem);

- return alg ?: ERR_PTR(-EAGAIN);
+ if (shoot) {
+ crypto_shoot_alg(target);
+ crypto_alg_put(target);
+ }
+
+ return alg;
}

struct crypto_tfm *crypto_spawn_tfm(struct crypto_spawn *spawn, u32 type,
--- a/crypto/api.c
+++ b/crypto/api.c
@@ -333,12 +333,13 @@ static unsigned int crypto_ctxsize(struc
return len;
}

-static void crypto_shoot_alg(struct crypto_alg *alg)
+void crypto_shoot_alg(struct crypto_alg *alg)
{
down_write(&crypto_alg_sem);
alg->cra_flags |= CRYPTO_ALG_DYING;
up_write(&crypto_alg_sem);
}
+EXPORT_SYMBOL_GPL(crypto_shoot_alg);

struct crypto_tfm *__crypto_alloc_tfm(struct crypto_alg *alg, u32 type,
u32 mask)
--- a/crypto/internal.h
+++ b/crypto/internal.h
@@ -65,6 +65,7 @@ void crypto_alg_tested(const char *name,
void crypto_remove_spawns(struct crypto_alg *alg, struct list_head *list,
struct crypto_alg *nalg);
void crypto_remove_final(struct list_head *list);
+void crypto_shoot_alg(struct crypto_alg *alg);
struct crypto_tfm *__crypto_alloc_tfm(struct crypto_alg *alg, u32 type,
u32 mask);
void *crypto_create_tfm(struct crypto_alg *alg,


2020-06-05 14:20:19

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 13/14] net: dsa: mt7530: set CPU port to fallback mode

From: DENG Qingfang <[email protected]>

commit 38152ea37d8bdaffa22603e0a5b5b86cfa8714c9 upstream.

Currently, setting a bridge's self PVID to other value and deleting
the default VID 1 renders untagged ports of that VLAN unable to talk to
the CPU port:

bridge vlan add dev br0 vid 2 pvid untagged self
bridge vlan del dev br0 vid 1 self
bridge vlan add dev sw0p0 vid 2 pvid untagged
bridge vlan del dev sw0p0 vid 1
# br0 cannot send untagged frames out of sw0p0 anymore

That is because the CPU port is set to security mode and its PVID is
still 1, and untagged frames are dropped due to VLAN member violation.

Set the CPU port to fallback mode so untagged frames can pass through.

Fixes: 83163f7dca56 ("net: dsa: mediatek: add VLAN support for MT7530")
Signed-off-by: DENG Qingfang <[email protected]>
Reviewed-by: Florian Fainelli <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
drivers/net/dsa/mt7530.c | 11 ++++++++---
drivers/net/dsa/mt7530.h | 6 ++++++
2 files changed, 14 insertions(+), 3 deletions(-)

--- a/drivers/net/dsa/mt7530.c
+++ b/drivers/net/dsa/mt7530.c
@@ -807,10 +807,15 @@ mt7530_port_set_vlan_aware(struct dsa_sw
PCR_MATRIX_MASK, PCR_MATRIX(MT7530_ALL_MEMBERS));

/* Trapped into security mode allows packet forwarding through VLAN
- * table lookup.
+ * table lookup. CPU port is set to fallback mode to let untagged
+ * frames pass through.
*/
- mt7530_rmw(priv, MT7530_PCR_P(port), PCR_PORT_VLAN_MASK,
- MT7530_PORT_SECURITY_MODE);
+ if (dsa_is_cpu_port(ds, port))
+ mt7530_rmw(priv, MT7530_PCR_P(port), PCR_PORT_VLAN_MASK,
+ MT7530_PORT_FALLBACK_MODE);
+ else
+ mt7530_rmw(priv, MT7530_PCR_P(port), PCR_PORT_VLAN_MASK,
+ MT7530_PORT_SECURITY_MODE);

/* Set the port as a user port which is to be able to recognize VID
* from incoming packets before fetching entry within the VLAN table.
--- a/drivers/net/dsa/mt7530.h
+++ b/drivers/net/dsa/mt7530.h
@@ -153,6 +153,12 @@ enum mt7530_port_mode {
/* Port Matrix Mode: Frames are forwarded by the PCR_MATRIX members. */
MT7530_PORT_MATRIX_MODE = PORT_VLAN(0),

+ /* Fallback Mode: Forward received frames with ingress ports that do
+ * not belong to the VLAN member. Frames whose VID is not listed on
+ * the VLAN table are forwarded by the PCR_MATRIX members.
+ */
+ MT7530_PORT_FALLBACK_MODE = PORT_VLAN(1),
+
/* Security Mode: Discard any frame due to ingress membership
* violation or VID missed on the VLAN table.
*/


2020-06-05 14:30:47

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 05/14] HID: i2c-hid: add Schneider SCL142ALM to descriptor override

From: Julian Sax <[email protected]>

commit 6507ef10660efdfee93f0f3b9fac24b5e4d83e56 upstream.

This device uses the SIPODEV SP1064 touchpad, which does not
supply descriptors, so it has to be added to the override list.

Cc: [email protected]
Signed-off-by: Julian Sax <[email protected]>
Signed-off-by: Jiri Kosina <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c | 8 ++++++++
1 file changed, 8 insertions(+)

--- a/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c
+++ b/drivers/hid/i2c-hid/i2c-hid-dmi-quirks.c
@@ -389,6 +389,14 @@ static const struct dmi_system_id i2c_hi
},
.driver_data = (void *)&sipodev_desc
},
+ {
+ .ident = "Schneider SCL142ALM",
+ .matches = {
+ DMI_EXACT_MATCH(DMI_SYS_VENDOR, "SCHNEIDER"),
+ DMI_EXACT_MATCH(DMI_PRODUCT_NAME, "SCL142ALM"),
+ },
+ .driver_data = (void *)&sipodev_desc
+ },
{ } /* Terminate list */
};



2020-06-05 14:30:56

by Greg Kroah-Hartman

[permalink] [raw]
Subject: [PATCH 5.7 10/14] mmc: fix compilation of user API

From: Jérôme Pouiller <[email protected]>

commit 83fc5dd57f86c3ec7d6d22565a6ff6c948853b64 upstream.

The definitions of MMC_IOC_CMD and of MMC_IOC_MULTI_CMD rely on
MMC_BLOCK_MAJOR:

#define MMC_IOC_CMD _IOWR(MMC_BLOCK_MAJOR, 0, struct mmc_ioc_cmd)
#define MMC_IOC_MULTI_CMD _IOWR(MMC_BLOCK_MAJOR, 1, struct mmc_ioc_multi_cmd)

However, MMC_BLOCK_MAJOR is defined in linux/major.h and
linux/mmc/ioctl.h did not include it.

Signed-off-by: Jérôme Pouiller <[email protected]>
Cc: [email protected]
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Ulf Hansson <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
include/uapi/linux/mmc/ioctl.h | 1 +
1 file changed, 1 insertion(+)

--- a/include/uapi/linux/mmc/ioctl.h
+++ b/include/uapi/linux/mmc/ioctl.h
@@ -3,6 +3,7 @@
#define LINUX_MMC_IOCTL_H

#include <linux/types.h>
+#include <linux/major.h>

struct mmc_ioc_cmd {
/*


2020-06-05 22:14:39

by Shuah Khan

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On 6/5/20 8:14 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.7.1 release.
> There are 14 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>

Compiled and booted on my test system. No dmesg regressions.

thanks,
-- Shuah

2020-06-06 06:32:17

by Jon Hunter

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review


On 05/06/2020 15:14, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.7.1 release.
> There are 14 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h


All tests are passing for Tegra ...

Test results for stable-5.7:
11 builds: 11 pass, 0 fail
26 boots: 26 pass, 0 fail
50 tests: 50 pass, 0 fail

Linux version: 5.7.1-rc1-g3defbfe4b0cc
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra20-ventana,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04

Cheers
Jon

--
nvpublic

2020-06-06 13:37:18

by Guenter Roeck

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On 6/5/20 7:14 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.7.1 release.
> There are 14 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> Anything received after that time might be too late.
>


Build results:
total: 155 pass: 155 fail: 0
Qemu test results:
total: 431 pass: 431 fail: 0

Guenter

2020-06-06 15:53:04

by Naresh Kamboju

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On Fri, 5 Jun 2020 at 19:46, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 5.7.1 release.
> There are 14 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> Anything received after that time might be too late.
>
> The whole patch series can be found in one patch at:
> https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
> or in the git tree and branch at:
> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h

Results from Linaro’s test farm.

While running kselftest memfd_test case the kernel panic noticed on i386
which started with kernel BUG and followed by kernel panic.

steps to reproduce: (Not always reproducible)
- cd /opt/kselftests/mainline/memfd/
- ./run_fuse_test.sh || true
- ./run_hugetlbfs_test.sh || true

[ 417.473220] run_hugetlbfs_t (10826): drop_caches: 3
[ 417.491120] audit: type=1701 audit(1591388532.357:87503):
auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=10829
comm=\"memfd_test\" exe=\"/opt/kselftests/mainline/memfd/memfd_test\"
sig=6 res=1
[ 417.511294] BUG: kernel NULL pointer dereference, address: 00000043
[ 417.517569] #PF: supervisor read access in kernel mode
[ 417.522699] #PF: error_code(0x0000) - not-present page
[ 417.527830] *pde = 00000000
[ 417.530707] Oops: 0000 [#2] SMP
[ 417.533846] CPU: 3 PID: 10829 Comm: memfd_test Tainted: G D W
5.7.1-rc1 #1
[ 417.541845] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.0b 07/27/2017
[ 417.549327] EIP: kmem_cache_alloc_trace+0x81/0x2b0
<>
[ 931.776242] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x00000009
[ 931.783933] Kernel Offset: 0x1ce00000 from 0xc1000000 (relocation
range: 0xc0000000-0xf77fdfff)
[ 931.792627] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x00000009 ]---


software_node_release bug on stable-rc 5.7 noticed which is a known
issue on Linus's tree.
[ 400.320910] BUG: kernel NULL pointer dereference, address: 0000000000000000
[ 400.328959] #PF: supervisor read access in kernel mode
[ 400.334097] #PF: error_code(0x0000) - not-present page
[ 400.339226] PGD 800000022880d067 P4D 800000022880d067 PUD 21f410067 PMD 0
[ 400.346093] Oops: 0000 [#1] SMP PTI
[ 400.349586] CPU: 2 PID: 8865 Comm: modprobe Tainted: G W
5.7.1-rc1 #1
[ 400.357322] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.2 05/23/2018
[ 400.364711] RIP: 0010:ida_free+0x76/0x140

Full test log link,
https://lkft.validation.linaro.org/scheduler/job/1477323#L11575


Kernel BUG on arm64 dragonboard 410c which is reported upstream but
did not get reply.
BUG: spinlock bad magic on CPU#1, swapper/0/1
lock: msm_uart_ports
Upstream issue reported link,
https://lore.kernel.org/lkml/CA+G9fYsDgghO+4zMY-AF2RgUmAfjZyA+tjeg5m5F1rEgEtw5fg@mail.gmail.com/

--
Linaro LKFT
https://lkft.linaro.org

2020-06-07 11:20:32

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On Fri, Jun 05, 2020 at 04:11:49PM -0600, Shuah Khan wrote:
> On 6/5/20 8:14 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.7.1 release.
> > There are 14 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
>
> Compiled and booted on my test system. No dmesg regressions.

Thanks for testing all of these and letting me know.

greg k-h

2020-06-07 11:22:04

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On Sat, Jun 06, 2020 at 06:34:48AM -0700, Guenter Roeck wrote:
> On 6/5/20 7:14 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.7.1 release.
> > There are 14 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> > Anything received after that time might be too late.
> >
>
>
> Build results:
> total: 155 pass: 155 fail: 0
> Qemu test results:
> total: 431 pass: 431 fail: 0

Great, thanks for testing all of these and letting me know.

greg k-h

2020-06-07 11:25:09

by Greg Kroah-Hartman

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On Sat, Jun 06, 2020 at 09:19:53PM +0530, Naresh Kamboju wrote:
> On Fri, 5 Jun 2020 at 19:46, Greg Kroah-Hartman
> <[email protected]> wrote:
> >
> > This is the start of the stable review cycle for the 5.7.1 release.
> > There are 14 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with these being applied, please
> > let me know.
> >
> > Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> > Anything received after that time might be too late.
> >
> > The whole patch series can be found in one patch at:
> > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
> > or in the git tree and branch at:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
>
> Results from Linaro’s test farm.
>
> While running kselftest memfd_test case the kernel panic noticed on i386
> which started with kernel BUG and followed by kernel panic.
>
> steps to reproduce: (Not always reproducible)
> - cd /opt/kselftests/mainline/memfd/
> - ./run_fuse_test.sh || true
> - ./run_hugetlbfs_test.sh || true
>
> [ 417.473220] run_hugetlbfs_t (10826): drop_caches: 3
> [ 417.491120] audit: type=1701 audit(1591388532.357:87503):
> auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=10829
> comm=\"memfd_test\" exe=\"/opt/kselftests/mainline/memfd/memfd_test\"
> sig=6 res=1
> [ 417.511294] BUG: kernel NULL pointer dereference, address: 00000043
> [ 417.517569] #PF: supervisor read access in kernel mode
> [ 417.522699] #PF: error_code(0x0000) - not-present page
> [ 417.527830] *pde = 00000000
> [ 417.530707] Oops: 0000 [#2] SMP
> [ 417.533846] CPU: 3 PID: 10829 Comm: memfd_test Tainted: G D W
> 5.7.1-rc1 #1
> [ 417.541845] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> 2.0b 07/27/2017
> [ 417.549327] EIP: kmem_cache_alloc_trace+0x81/0x2b0
> <>
> [ 931.776242] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x00000009
> [ 931.783933] Kernel Offset: 0x1ce00000 from 0xc1000000 (relocation
> range: 0xc0000000-0xf77fdfff)
> [ 931.792627] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x00000009 ]---

Did you see this on Linus's tree too?

Is it a regression from 5.7.0?

> software_node_release bug on stable-rc 5.7 noticed which is a known
> issue on Linus's tree.
> [ 400.320910] BUG: kernel NULL pointer dereference, address: 0000000000000000
> [ 400.328959] #PF: supervisor read access in kernel mode
> [ 400.334097] #PF: error_code(0x0000) - not-present page
> [ 400.339226] PGD 800000022880d067 P4D 800000022880d067 PUD 21f410067 PMD 0
> [ 400.346093] Oops: 0000 [#1] SMP PTI
> [ 400.349586] CPU: 2 PID: 8865 Comm: modprobe Tainted: G W
> 5.7.1-rc1 #1
> [ 400.357322] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> 2.2 05/23/2018
> [ 400.364711] RIP: 0010:ida_free+0x76/0x140
>
> Full test log link,
> https://lkft.validation.linaro.org/scheduler/job/1477323#L11575
>
>
> Kernel BUG on arm64 dragonboard 410c which is reported upstream but
> did not get reply.
> BUG: spinlock bad magic on CPU#1, swapper/0/1
> lock: msm_uart_ports
> Upstream issue reported link,
> https://lore.kernel.org/lkml/CA+G9fYsDgghO+4zMY-AF2RgUmAfjZyA+tjeg5m5F1rEgEtw5fg@mail.gmail.com/


Thanks for testing all of these.

greg k-h

2020-06-07 20:26:02

by Naresh Kamboju

[permalink] [raw]
Subject: Re: [PATCH 5.7 00/14] 5.7.1-rc1 review

On Sun, 7 Jun 2020 at 16:50, Greg Kroah-Hartman
<[email protected]> wrote:
>
> On Sat, Jun 06, 2020 at 09:19:53PM +0530, Naresh Kamboju wrote:
> > On Fri, 5 Jun 2020 at 19:46, Greg Kroah-Hartman
> > <[email protected]> wrote:
> > >
> > > This is the start of the stable review cycle for the 5.7.1 release.
> > > There are 14 patches in this series, all will be posted as a response
> > > to this one. If anyone has any issues with these being applied, please
> > > let me know.
> > >
> > > Responses should be made by Sun, 07 Jun 2020 13:54:56 +0000.
> > > Anything received after that time might be too late.
> > >
> > > The whole patch series can be found in one patch at:
> > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.7.1-rc1.gz
> > > or in the git tree and branch at:
> > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-5.7.y
> > > and the diffstat can be found below.
> > >
> > > thanks,
> > >
> > > greg k-h
> >
> > Results from Linaro’s test farm.
> >
> > While running kselftest memfd_test case the kernel panic noticed on i386
> > which started with kernel BUG and followed by kernel panic.
> >
> > steps to reproduce: (Not always reproducible)
> > - cd /opt/kselftests/mainline/memfd/
> > - ./run_fuse_test.sh || true
> > - ./run_hugetlbfs_test.sh || true
> >
> > [ 417.473220] run_hugetlbfs_t (10826): drop_caches: 3
> > [ 417.491120] audit: type=1701 audit(1591388532.357:87503):
> > auid=4294967295 uid=0 gid=0 ses=4294967295 subj=kernel pid=10829
> > comm=\"memfd_test\" exe=\"/opt/kselftests/mainline/memfd/memfd_test\"
> > sig=6 res=1
> > [ 417.511294] BUG: kernel NULL pointer dereference, address: 00000043
> > [ 417.517569] #PF: supervisor read access in kernel mode
> > [ 417.522699] #PF: error_code(0x0000) - not-present page
> > [ 417.527830] *pde = 00000000
> > [ 417.530707] Oops: 0000 [#2] SMP
> > [ 417.533846] CPU: 3 PID: 10829 Comm: memfd_test Tainted: G D W
> > 5.7.1-rc1 #1
> > [ 417.541845] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
> > 2.0b 07/27/2017
> > [ 417.549327] EIP: kmem_cache_alloc_trace+0x81/0x2b0
> > <>
> > [ 931.776242] Kernel panic - not syncing: Attempted to kill init!
> > exitcode=0x00000009
> > [ 931.783933] Kernel Offset: 0x1ce00000 from 0xc1000000 (relocation
> > range: 0xc0000000-0xf77fdfff)
> > [ 931.792627] ---[ end Kernel panic - not syncing: Attempted to kill
> > init! exitcode=0x00000009 ]---
>
> Did you see this on Linus's tree too?

Yes.
I have noticed 4 out of 10 kselftest full runs.

>
> Is it a regression from 5.7.0?

It is a regression on Linus 's tree and the same problem was noticed on
stable-rc 5.7 branch.

- Naresh