[PATCH AUTOSEL 5.11 03/22] KVM: arm64: Hide system instruction access to Trace registers

From: Suzuki K Poulose [ Upstream commit 1d676673d665fd2162e7e466dcfbe5373bfdb73e ] Currently we advertise the ID_AA6DFR0_EL1.TRACEVER for the guest, when the trace register accesses are trapped (CPTR_EL2.TTA == 1). So, the guest will get an undefined instruction, if trusts the ID registers and

[PATCH AUTOSEL 5.11 04/22] KVM: arm64: Disable guest access to trace filter controls

From: Suzuki K Poulose [ Upstream commit a354a64d91eec3e0f8ef0eed575b480fd75b999c ] Disable guest access to the Trace Filter control registers. We do not advertise the Trace filter feature to the guest (ID_AA64DFR0_EL1: TRACE_FILT is cleared) already, but the guest can still access the TRFCR_EL1

[PATCH AUTOSEL 5.11 01/22] interconnect: core: fix error return code of icc_link_destroy()

From: Jia-Ju Bai [ Upstream commit 715ea61532e731c62392221238906704e63d75b6 ] When krealloc() fails and new is NULL, no error return code of icc_link_destroy() is assigned. To fix this bug, ret is assigned with -ENOMEM hen new is NULL. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai Link: h

[PATCH AUTOSEL 5.11 02/22] gfs2: Flag a withdraw if init_threads() fails

From: Andrew Price [ Upstream commit 62dd0f98a0e5668424270b47a0c2e973795faba7 ] Interrupting mount with ^C quickly enough can cause the kthread_run() calls in gfs2's init_threads() to fail and the error path leads to a deadlock on the s_umount rwsem. The abridged chain of events is: [mount pa

[PATCH AUTOSEL 5.11 05/22] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 5.11 07/22] scsi: iscsi: Fix race condition between login and sync thread

From: Gulam Mohamed [ Upstream commit 9e67600ed6b8565da4b85698ec659b5879a6c1c6 ] A kernel panic was observed due to a timing issue between the sync thread and the initiator processing a login response from the target. The session reopen can be invoked both from the session sync thread when iscsi

[PATCH AUTOSEL 5.11 06/22] gfs2: report "already frozen/thawed" errors

From: Bob Peterson [ Upstream commit ff132c5f93c06bd4432bbab5c369e468653bdec4 ] Before this patch, gfs2's freeze function failed to report an error when the target file system was already frozen as it should (and as generic vfs function freeze_super does. Similarly, gfs2's thaw function failed t

[PATCH AUTOSEL 5.11 10/22] drm/tegra: dc: Don't set PLL clock to 0Hz

From: Dmitry Osipenko [ Upstream commit f8fb97c915954fc6de6513cdf277103b5c6df7b3 ] RGB output doesn't allow to change parent clock rate of the display and PCLK rate is set to 0Hz in this case. The tegra_dc_commit_state() shall not set the display clock to 0Hz since this change propagates to the

[PATCH AUTOSEL 5.11 08/22] ftrace: Check if pages were allocated before calling free_pages()

From: "Steven Rostedt (VMware)" [ Upstream commit 59300b36f85f254260c81d9dd09195fa49eb0f98 ] It is possible that on error pg->size can be zero when getting its order, which would return a -1 value. It is dangerous to pass in an order of -1 to free_pages(). Check if order is greater than or equal

[PATCH AUTOSEL 5.11 12/22] XArray: Fix splitting to non-zero orders

From: "Matthew Wilcox (Oracle)" [ Upstream commit 3012110d71f41410932924e1d188f9eb57f1f824 ] Splitting an order-4 entry into order-2 entries would leave the array containing pointers to 40008000c000 instead of . This is a one-character fix, but enhance the test suite to check

[PATCH AUTOSEL 5.11 09/22] tools/kvm_stat: Add restart delay

From: Stefan Raspl [ Upstream commit 75f94ecbd0dfd2ac4e671f165f5ae864b7301422 ] If this service is enabled and the system rebooted, Systemd's initial attempt to start this unit file may fail in case the kvm module is not loaded. Since we did not specify a delay for the retries, Systemd restarts

[PATCH AUTOSEL 5.11 13/22] radix tree test suite: Fix compilation

From: "Matthew Wilcox (Oracle)" [ Upstream commit 7487de534dcbe143e6f41da751dd3ffcf93b00ee ] Commit 4bba4c4bb09a added tools/include/linux/compiler_types.h which includes linux/compiler-gcc.h. Unfortunately, we had our own (empty) compiler_types.h which overrode the one added by that commit, an

[PATCH AUTOSEL 5.11 15/22] radix tree test suite: Register the main thread with the RCU library

From: "Matthew Wilcox (Oracle)" [ Upstream commit 1bb4bd266cf39fd2fa711f2d265c558b92df1119 ] Several test runners register individual worker threads with the RCU library, but neglect to register the main thread, which can lead to objects being freed while the main thread is in what appears to be

[PATCH AUTOSEL 5.11 11/22] gpu: host1x: Use different lock classes for each client

From: Mikko Perttunen [ Upstream commit a24f98176d1efae2c37d3438c57a624d530d9c33 ] To avoid false lockdep warnings, give each client lock a different lock class, passed from the initialization site by macro. Signed-off-by: Mikko Perttunen Signed-off-by: Thierry Reding Signed-off-by: Sasha Lev

[PATCH AUTOSEL 5.11 17/22] idr test suite: Create anchor before launching throbber

From: "Matthew Wilcox (Oracle)" [ Upstream commit 094ffbd1d8eaa27ed426feb8530cb1456348b018 ] The throbber could race with creation of the anchor entry and cause the IDR to have zero entries in it, which would cause the test to fail. Signed-off-by: Matthew Wilcox (Oracle) Signed-off-by: Sasha L

[PATCH AUTOSEL 5.11 14/22] block: only update parent bi_status when bio fail

From: Yufen Yu [ Upstream commit 3edf5346e4f2ce2fa0c94651a90a8dda169565ee ] For multiple split bios, if one of the bio is fail, the whole should return error to application. But we found there is a race between bio_integrity_verify_fn and bio complete, which return io success to application afte

[PATCH AUTOSEL 5.11 19/22] io_uring: don't mark S_ISBLK async work as unbounded

From: Jens Axboe [ Upstream commit 4b982bd0f383db9132e892c0c5144117359a6289 ] S_ISBLK is marked as unbounded work for async preparation, because it doesn't match S_ISREG. That is incorrect, as any read/write to a block device is also a bounded operation. Fix it up and ensure that S_ISBLK isn't m

[PATCH AUTOSEL 5.11 16/22] idr test suite: Take RCU read lock in idr_find_test_1

From: "Matthew Wilcox (Oracle)" [ Upstream commit 703586410da69eb40062e64d413ca33bd735917a ] When run on a single CPU, this test would frequently access already-freed memory. Due to timing, this bug never showed up on multi-CPU tests. Reported-by: Chris von Recklinghausen Signed-off-by: Matth

[PATCH AUTOSEL 5.11 21/22] riscv,entry: fix misaligned base for excp_vect_table

From: Zihao Yu [ Upstream commit ac8d0b901f0033b783156ab2dc1a0e73ec42409b ] In RV64, the size of each entry in excp_vect_table is 8 bytes. If the base of the table is not 8-byte aligned, loading an entry in the table will raise a misaligned exception. Although such exception will be handled by o

[PATCH AUTOSEL 5.11 18/22] null_blk: fix command timeout completion handling

From: Damien Le Moal [ Upstream commit de3510e52b0a398261271455562458003b8eea62 ] Memory backed or zoned null block devices may generate actual request timeout errors due to the submission path being blocked on memory allocation or zone locking. Unlike fake timeouts or injected timeouts, the req

[PATCH AUTOSEL 5.11 22/22] block: don't ignore REQ_NOWAIT for direct IO

From: Pavel Begunkov [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocki

[PATCH AUTOSEL 5.10 01/22] interconnect: core: fix error return code of icc_link_destroy()

From: Jia-Ju Bai [ Upstream commit 715ea61532e731c62392221238906704e63d75b6 ] When krealloc() fails and new is NULL, no error return code of icc_link_destroy() is assigned. To fix this bug, ret is assigned with -ENOMEM hen new is NULL. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai Link: h

[PATCH AUTOSEL 5.10 03/22] KVM: arm64: Hide system instruction access to Trace registers

From: Suzuki K Poulose [ Upstream commit 1d676673d665fd2162e7e466dcfbe5373bfdb73e ] Currently we advertise the ID_AA6DFR0_EL1.TRACEVER for the guest, when the trace register accesses are trapped (CPTR_EL2.TTA == 1). So, the guest will get an undefined instruction, if trusts the ID registers and

[PATCH AUTOSEL 5.11 20/22] riscv: evaluate put_user() arg before enabling user access

From: Ben Dooks [ Upstream commit 285a76bb2cf51b0c74c634f2aaccdb93e1f2a359 ] The header has a problem with put_user(a, ptr) if the 'a' is not a simple variable, such as a function. This can lead to the compiler producing code as so: 1: enable_user_access() 2: evaluate 'a' into regist

[PATCH AUTOSEL 5.10 09/22] tools/kvm_stat: Add restart delay

From: Stefan Raspl [ Upstream commit 75f94ecbd0dfd2ac4e671f165f5ae864b7301422 ] If this service is enabled and the system rebooted, Systemd's initial attempt to start this unit file may fail in case the kvm module is not loaded. Since we did not specify a delay for the retries, Systemd restarts

[PATCH AUTOSEL 5.10 08/22] ftrace: Check if pages were allocated before calling free_pages()

From: "Steven Rostedt (VMware)" [ Upstream commit 59300b36f85f254260c81d9dd09195fa49eb0f98 ] It is possible that on error pg->size can be zero when getting its order, which would return a -1 value. It is dangerous to pass in an order of -1 to free_pages(). Check if order is greater than or equal

[PATCH AUTOSEL 5.10 10/22] drm/tegra: dc: Don't set PLL clock to 0Hz

From: Dmitry Osipenko [ Upstream commit f8fb97c915954fc6de6513cdf277103b5c6df7b3 ] RGB output doesn't allow to change parent clock rate of the display and PCLK rate is set to 0Hz in this case. The tegra_dc_commit_state() shall not set the display clock to 0Hz since this change propagates to the

[PATCH AUTOSEL 5.10 07/22] scsi: iscsi: Fix race condition between login and sync thread

From: Gulam Mohamed [ Upstream commit 9e67600ed6b8565da4b85698ec659b5879a6c1c6 ] A kernel panic was observed due to a timing issue between the sync thread and the initiator processing a login response from the target. The session reopen can be invoked both from the session sync thread when iscsi

[PATCH AUTOSEL 5.10 05/22] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 5.10 04/22] KVM: arm64: Disable guest access to trace filter controls

From: Suzuki K Poulose [ Upstream commit a354a64d91eec3e0f8ef0eed575b480fd75b999c ] Disable guest access to the Trace Filter control registers. We do not advertise the Trace filter feature to the guest (ID_AA64DFR0_EL1: TRACE_FILT is cleared) already, but the guest can still access the TRFCR_EL1

[PATCH AUTOSEL 5.10 02/22] gfs2: Flag a withdraw if init_threads() fails

From: Andrew Price [ Upstream commit 62dd0f98a0e5668424270b47a0c2e973795faba7 ] Interrupting mount with ^C quickly enough can cause the kthread_run() calls in gfs2's init_threads() to fail and the error path leads to a deadlock on the s_umount rwsem. The abridged chain of events is: [mount pa

[PATCH AUTOSEL 5.10 06/22] gfs2: report "already frozen/thawed" errors

From: Bob Peterson [ Upstream commit ff132c5f93c06bd4432bbab5c369e468653bdec4 ] Before this patch, gfs2's freeze function failed to report an error when the target file system was already frozen as it should (and as generic vfs function freeze_super does. Similarly, gfs2's thaw function failed t

[PATCH AUTOSEL 5.10 15/22] radix tree test suite: Register the main thread with the RCU library

From: "Matthew Wilcox (Oracle)" [ Upstream commit 1bb4bd266cf39fd2fa711f2d265c558b92df1119 ] Several test runners register individual worker threads with the RCU library, but neglect to register the main thread, which can lead to objects being freed while the main thread is in what appears to be

[PATCH AUTOSEL 5.10 12/22] XArray: Fix splitting to non-zero orders

From: "Matthew Wilcox (Oracle)" [ Upstream commit 3012110d71f41410932924e1d188f9eb57f1f824 ] Splitting an order-4 entry into order-2 entries would leave the array containing pointers to 40008000c000 instead of . This is a one-character fix, but enhance the test suite to check

[PATCH AUTOSEL 5.10 20/22] riscv: evaluate put_user() arg before enabling user access

From: Ben Dooks [ Upstream commit 285a76bb2cf51b0c74c634f2aaccdb93e1f2a359 ] The header has a problem with put_user(a, ptr) if the 'a' is not a simple variable, such as a function. This can lead to the compiler producing code as so: 1: enable_user_access() 2: evaluate 'a' into regist

[PATCH AUTOSEL 5.10 17/22] idr test suite: Create anchor before launching throbber

From: "Matthew Wilcox (Oracle)" [ Upstream commit 094ffbd1d8eaa27ed426feb8530cb1456348b018 ] The throbber could race with creation of the anchor entry and cause the IDR to have zero entries in it, which would cause the test to fail. Signed-off-by: Matthew Wilcox (Oracle) Signed-off-by: Sasha L

[PATCH AUTOSEL 5.10 16/22] idr test suite: Take RCU read lock in idr_find_test_1

From: "Matthew Wilcox (Oracle)" [ Upstream commit 703586410da69eb40062e64d413ca33bd735917a ] When run on a single CPU, this test would frequently access already-freed memory. Due to timing, this bug never showed up on multi-CPU tests. Reported-by: Chris von Recklinghausen Signed-off-by: Matth

[PATCH AUTOSEL 5.10 19/22] io_uring: don't mark S_ISBLK async work as unbounded

From: Jens Axboe [ Upstream commit 4b982bd0f383db9132e892c0c5144117359a6289 ] S_ISBLK is marked as unbounded work for async preparation, because it doesn't match S_ISREG. That is incorrect, as any read/write to a block device is also a bounded operation. Fix it up and ensure that S_ISBLK isn't m

[PATCH AUTOSEL 5.10 22/22] block: don't ignore REQ_NOWAIT for direct IO

From: Pavel Begunkov [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocki

[PATCH AUTOSEL 5.4 02/13] KVM: arm64: Hide system instruction access to Trace registers

From: Suzuki K Poulose [ Upstream commit 1d676673d665fd2162e7e466dcfbe5373bfdb73e ] Currently we advertise the ID_AA6DFR0_EL1.TRACEVER for the guest, when the trace register accesses are trapped (CPTR_EL2.TTA == 1). So, the guest will get an undefined instruction, if trusts the ID registers and

[PATCH AUTOSEL 5.10 13/22] radix tree test suite: Fix compilation

From: "Matthew Wilcox (Oracle)" [ Upstream commit 7487de534dcbe143e6f41da751dd3ffcf93b00ee ] Commit 4bba4c4bb09a added tools/include/linux/compiler_types.h which includes linux/compiler-gcc.h. Unfortunately, we had our own (empty) compiler_types.h which overrode the one added by that commit, an

[PATCH AUTOSEL 5.10 18/22] null_blk: fix command timeout completion handling

From: Damien Le Moal [ Upstream commit de3510e52b0a398261271455562458003b8eea62 ] Memory backed or zoned null block devices may generate actual request timeout errors due to the submission path being blocked on memory allocation or zone locking. Unlike fake timeouts or injected timeouts, the req

[PATCH AUTOSEL 5.10 21/22] riscv,entry: fix misaligned base for excp_vect_table

From: Zihao Yu [ Upstream commit ac8d0b901f0033b783156ab2dc1a0e73ec42409b ] In RV64, the size of each entry in excp_vect_table is 8 bytes. If the base of the table is not 8-byte aligned, loading an entry in the table will raise a misaligned exception. Although such exception will be handled by o

[PATCH AUTOSEL 5.10 11/22] gpu: host1x: Use different lock classes for each client

From: Mikko Perttunen [ Upstream commit a24f98176d1efae2c37d3438c57a624d530d9c33 ] To avoid false lockdep warnings, give each client lock a different lock class, passed from the initialization site by macro. Signed-off-by: Mikko Perttunen Signed-off-by: Thierry Reding Signed-off-by: Sasha Lev

[PATCH AUTOSEL 5.10 14/22] block: only update parent bi_status when bio fail

From: Yufen Yu [ Upstream commit 3edf5346e4f2ce2fa0c94651a90a8dda169565ee ] For multiple split bios, if one of the bio is fail, the whole should return error to application. But we found there is a race between bio_integrity_verify_fn and bio complete, which return io success to application afte

[PATCH AUTOSEL 4.19 4/8] gfs2: report "already frozen/thawed" errors

From: Bob Peterson [ Upstream commit ff132c5f93c06bd4432bbab5c369e468653bdec4 ] Before this patch, gfs2's freeze function failed to report an error when the target file system was already frozen as it should (and as generic vfs function freeze_super does. Similarly, gfs2's thaw function failed t

[PATCH AUTOSEL 4.19 1/8] KVM: arm64: Hide system instruction access to Trace registers

From: Suzuki K Poulose [ Upstream commit 1d676673d665fd2162e7e466dcfbe5373bfdb73e ] Currently we advertise the ID_AA6DFR0_EL1.TRACEVER for the guest, when the trace register accesses are trapped (CPTR_EL2.TTA == 1). So, the guest will get an undefined instruction, if trusts the ID registers and

[PATCH AUTOSEL 4.19 5/8] drm/tegra: dc: Don't set PLL clock to 0Hz

From: Dmitry Osipenko [ Upstream commit f8fb97c915954fc6de6513cdf277103b5c6df7b3 ] RGB output doesn't allow to change parent clock rate of the display and PCLK rate is set to 0Hz in this case. The tegra_dc_commit_state() shall not set the display clock to 0Hz since this change propagates to the

[PATCH AUTOSEL 5.4 07/13] radix tree test suite: Fix compilation

From: "Matthew Wilcox (Oracle)" [ Upstream commit dd841a749d1ded8e2e5facc4242ee0b6779fc0cb ] Introducing local_lock broke compilation; fix it all up. Signed-off-by: Matthew Wilcox (Oracle) Signed-off-by: Sasha Levin --- tools/testing/radix-tree/linux/compiler_types.h | 0 1 file changed, 0 i

[PATCH AUTOSEL 5.4 06/13] drm/tegra: dc: Don't set PLL clock to 0Hz

From: Dmitry Osipenko [ Upstream commit f8fb97c915954fc6de6513cdf277103b5c6df7b3 ] RGB output doesn't allow to change parent clock rate of the display and PCLK rate is set to 0Hz in this case. The tegra_dc_commit_state() shall not set the display clock to 0Hz since this change propagates to the

[PATCH AUTOSEL 4.14 3/5] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 4.14 2/5] KVM: arm64: Disable guest access to trace filter controls

From: Suzuki K Poulose [ Upstream commit a354a64d91eec3e0f8ef0eed575b480fd75b999c ] Disable guest access to the Trace Filter control registers. We do not advertise the Trace filter feature to the guest (ID_AA64DFR0_EL1: TRACE_FILT is cleared) already, but the guest can still access the TRFCR_EL1

[PATCH AUTOSEL 4.14 1/5] KVM: arm64: Hide system instruction access to Trace registers

From: Suzuki K Poulose [ Upstream commit 1d676673d665fd2162e7e466dcfbe5373bfdb73e ] Currently we advertise the ID_AA6DFR0_EL1.TRACEVER for the guest, when the trace register accesses are trapped (CPTR_EL2.TTA == 1). So, the guest will get an undefined instruction, if trusts the ID registers and

[PATCH AUTOSEL 4.19 7/8] block: only update parent bi_status when bio fail

From: Yufen Yu [ Upstream commit 3edf5346e4f2ce2fa0c94651a90a8dda169565ee ] For multiple split bios, if one of the bio is fail, the whole should return error to application. But we found there is a race between bio_integrity_verify_fn and bio complete, which return io success to application afte

[PATCH AUTOSEL 5.4 03/13] KVM: arm64: Disable guest access to trace filter controls

From: Suzuki K Poulose [ Upstream commit a354a64d91eec3e0f8ef0eed575b480fd75b999c ] Disable guest access to the Trace Filter control registers. We do not advertise the Trace filter feature to the guest (ID_AA64DFR0_EL1: TRACE_FILT is cleared) already, but the guest can still access the TRFCR_EL1

[PATCH AUTOSEL 5.4 01/13] interconnect: core: fix error return code of icc_link_destroy()

From: Jia-Ju Bai [ Upstream commit 715ea61532e731c62392221238906704e63d75b6 ] When krealloc() fails and new is NULL, no error return code of icc_link_destroy() is assigned. To fix this bug, ret is assigned with -ENOMEM hen new is NULL. Reported-by: TOTE Robot Signed-off-by: Jia-Ju Bai Link: h

[PATCH AUTOSEL 4.19 6/8] radix tree test suite: Fix compilation

From: "Matthew Wilcox (Oracle)" [ Upstream commit dd841a749d1ded8e2e5facc4242ee0b6779fc0cb ] Introducing local_lock broke compilation; fix it all up. Signed-off-by: Matthew Wilcox (Oracle) Signed-off-by: Sasha Levin --- tools/testing/radix-tree/linux/compiler_types.h | 0 1 file changed, 0 i

[PATCH AUTOSEL 4.19 8/8] riscv,entry: fix misaligned base for excp_vect_table

From: Zihao Yu [ Upstream commit ac8d0b901f0033b783156ab2dc1a0e73ec42409b ] In RV64, the size of each entry in excp_vect_table is 8 bytes. If the base of the table is not 8-byte aligned, loading an entry in the table will raise a misaligned exception. Although such exception will be handled by o

[PATCH AUTOSEL 5.4 04/13] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 4.19 3/8] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 4.19 2/8] KVM: arm64: Disable guest access to trace filter controls

From: Suzuki K Poulose [ Upstream commit a354a64d91eec3e0f8ef0eed575b480fd75b999c ] Disable guest access to the Trace Filter control registers. We do not advertise the Trace filter feature to the guest (ID_AA64DFR0_EL1: TRACE_FILT is cleared) already, but the guest can still access the TRFCR_EL1

[PATCH AUTOSEL 5.4 12/13] riscv,entry: fix misaligned base for excp_vect_table

From: Zihao Yu [ Upstream commit ac8d0b901f0033b783156ab2dc1a0e73ec42409b ] In RV64, the size of each entry in excp_vect_table is 8 bytes. If the base of the table is not 8-byte aligned, loading an entry in the table will raise a misaligned exception. Although such exception will be handled by o

[PATCH AUTOSEL 4.14 4/5] gfs2: report "already frozen/thawed" errors

From: Bob Peterson [ Upstream commit ff132c5f93c06bd4432bbab5c369e468653bdec4 ] Before this patch, gfs2's freeze function failed to report an error when the target file system was already frozen as it should (and as generic vfs function freeze_super does. Similarly, gfs2's thaw function failed t

[PATCH AUTOSEL 5.4 11/13] idr test suite: Create anchor before launching throbber

From: "Matthew Wilcox (Oracle)" [ Upstream commit 094ffbd1d8eaa27ed426feb8530cb1456348b018 ] The throbber could race with creation of the anchor entry and cause the IDR to have zero entries in it, which would cause the test to fail. Signed-off-by: Matthew Wilcox (Oracle) Signed-off-by: Sasha L

[PATCH AUTOSEL 5.4 10/13] idr test suite: Take RCU read lock in idr_find_test_1

From: "Matthew Wilcox (Oracle)" [ Upstream commit 703586410da69eb40062e64d413ca33bd735917a ] When run on a single CPU, this test would frequently access already-freed memory. Due to timing, this bug never showed up on multi-CPU tests. Reported-by: Chris von Recklinghausen Signed-off-by: Matth

[PATCH AUTOSEL 5.4 13/13] block: don't ignore REQ_NOWAIT for direct IO

From: Pavel Begunkov [ Upstream commit f8b78caf21d5bc3fcfc40c18898f9d52ed1451a5 ] If IOCB_NOWAIT is set on submission, then that needs to get propagated to REQ_NOWAIT on the block side. Otherwise we completely lose this information, and any issuer of IOCB_NOWAIT IO will potentially end up blocki

[PATCH AUTOSEL 5.4 09/13] radix tree test suite: Register the main thread with the RCU library

From: "Matthew Wilcox (Oracle)" [ Upstream commit 1bb4bd266cf39fd2fa711f2d265c558b92df1119 ] Several test runners register individual worker threads with the RCU library, but neglect to register the main thread, which can lead to objects being freed while the main thread is in what appears to be

[PATCH AUTOSEL 4.14 5/5] block: only update parent bi_status when bio fail

From: Yufen Yu [ Upstream commit 3edf5346e4f2ce2fa0c94651a90a8dda169565ee ] For multiple split bios, if one of the bio is fail, the whole should return error to application. But we found there is a race between bio_integrity_verify_fn and bio complete, which return io success to application afte

[PATCH AUTOSEL 4.4] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 4.9 2/2] gfs2: report "already frozen/thawed" errors

From: Bob Peterson [ Upstream commit ff132c5f93c06bd4432bbab5c369e468653bdec4 ] Before this patch, gfs2's freeze function failed to report an error when the target file system was already frozen as it should (and as generic vfs function freeze_super does. Similarly, gfs2's thaw function failed t

[PATCH AUTOSEL 4.9 1/2] drm/imx: imx-ldb: fix out of bounds array access warning

From: Arnd Bergmann [ Upstream commit 33ce7f2f95cabb5834cf0906308a5cb6103976da ] When CONFIG_OF is disabled, building with 'make W=1' produces warnings about out of bounds array access: drivers/gpu/drm/imx/imx-ldb.c: In function 'imx_ldb_set_clock.constprop': drivers/gpu/drm/imx/imx-ldb.c:186:8

[PATCH AUTOSEL 5.4 08/13] block: only update parent bi_status when bio fail

From: Yufen Yu [ Upstream commit 3edf5346e4f2ce2fa0c94651a90a8dda169565ee ] For multiple split bios, if one of the bio is fail, the whole should return error to application. But we found there is a race between bio_integrity_verify_fn and bio complete, which return io success to application afte

[PATCH AUTOSEL 5.4 05/13] gfs2: report "already frozen/thawed" errors

From: Bob Peterson [ Upstream commit ff132c5f93c06bd4432bbab5c369e468653bdec4 ] Before this patch, gfs2's freeze function failed to report an error when the target file system was already frozen as it should (and as generic vfs function freeze_super does. Similarly, gfs2's thaw function failed t

Re: [PATCH v2 1/2] power: supply: bq25980 Apply datasheet revision changes

Hi, On Thu, Feb 11, 2021 at 08:36:03AM +0100, Krzysztof Kozlowski wrote: > On Wed, Feb 10, 2021 at 04:56:45PM -0600, Ricardo Rivera-Matos wrote: > > The latest datasheet revision for BQ25980, BQ25975, and BQ25960 changed > > > > various register step sizes and offset values. > > > > This patch

Re: [PATCH 5.10 039/126] can: dev: move driver related infrastructure into separate subdir

On Mon, Apr 05, 2021 at 05:30:29PM +0200, Pavel Machek wrote: > Hi! > > > From: Marc Kleine-Budde > > > > [ Upstream commit 3e77f70e734584e0ad1038e459ed3fd2400f873a ] > > > > This patch moves the CAN driver related infrastructure into a separate > > subdir. > > It will be split into more files

Re: [PATCH v2 2/2] power: supply: bq25980: Move props from battery node

Hi, On Thu, Feb 11, 2021 at 08:38:07AM +0100, Krzysztof Kozlowski wrote: > On Wed, Feb 10, 2021 at 04:56:46PM -0600, Ricardo Rivera-Matos wrote: > > Currently POWER_SUPPLY_PROP_CONSTANT_CHARGE_CURRENT and > > POWER_SUPPLY_PROP_CONSTANT_CHARGE_VOLTAGE are exposed on the battery node > > and this is

[PATCH rdma-next 8/8] net/rds: Move to client_supported callback

On Apr 4, 2021, at 10:50 PM, Leon Romanovsky wrote: > > From: Parav Pandit > > Use newly introduced client_supported() callback to avoid client > additional if the RDMA device is not of IB type or if it doesn't > support device memory extensions. > > Signed-off-by: Parav Pandit > Signed-off-b

Re: [PATCH v4 3/4] locking/qspinlock: Add ARCH_USE_QUEUED_SPINLOCKS_XCHG32

Hi Paul, Thx for the explanation, here is my comment. On Wed, Mar 31, 2021 at 1:33 PM Paul Campbell wrote: > > On Wednesday, 31 March 2021 5:18:56 PM NZDT Guo Ren wrote: > > > > [1] > > > > https://github.com/c-sky/csky-linux/commit/e837aad23148542771794d8a2fcc > > > > 52afd0fcbf88> > > > > > >

Re: [PATCH rdma-next 00/10] Enable relaxed ordering for ULPs

> On Apr 5, 2021, at 7:08 AM, Leon Romanovsky wrote: > > On Mon, Apr 05, 2021 at 03:41:15PM +0200, Christoph Hellwig wrote: >> On Mon, Apr 05, 2021 at 08:23:54AM +0300, Leon Romanovsky wrote: >>> From: Leon Romanovsky >>> From Avihai, >>> >>> Relaxed Ordering is a PCIe mechanism that rel

Re: [PATCH 5.4 03/74] module: merge repetitive strings in module_sig_check()

On Mon, Apr 05, 2021 at 05:11:13PM +0300, Sergey Shtylyov wrote: On 4/5/21 4:40 PM, Greg Kroah-Hartman wrote: [...] [ Upstream commit 705e9195187d85249fbb0eaa844b1604a98fbc9a ] The 'reason' variable in module_sig_check() points to 3 strings across the *switch* statement, all needlessly startin

Re: [GIT PULL] Immutable branch between MFD and Power due for the v5.13 merge window

Hi, On Tue, Mar 23, 2021 at 10:11:18AM +0100, Linus Walleij wrote: > On Tue, Mar 23, 2021 at 9:57 AM Lee Jones wrote: > > > git://git.kernel.org/pub/scm/linux/kernel/git/lee/mfd.git > > ib-mfd-power-v5.13 > > Thanks so much for fixing this Lee! > > Sebastian: if you decide to pull this in I

Re: [syzbot] WARNING in mntput_no_expire (2)

On Mon, Apr 05, 2021 at 01:44:37PM +0200, Christian Brauner wrote: > On Sun, Apr 04, 2021 at 08:17:21PM +, Al Viro wrote: > > On Sun, Apr 04, 2021 at 06:50:10PM +, Al Viro wrote: > > > > > > Yeah, I have at least namei.o > > > > > > > > https://drive.google.com/file/d/1AvO1St0YltIrA86DXjp

RE: [PATCH net 1/2] net: hns3: Remove the left over redundant check & assignment

> From: Leon Romanovsky [mailto:l...@kernel.org] > Sent: Monday, April 5, 2021 1:43 PM > To: Salil Mehta > Cc: da...@davemloft.net; k...@kernel.org; net...@vger.kernel.org; > linux-kernel@vger.kernel.org; Linuxarm ; > linux...@openeuler.org > Subject: Re: [PATCH net 1/2] net: hns3: Remove the left

Re: [PATCH 2/5] crypto: ccp: Reject SEV commands with mismatching command buffer

On 4/2/21 6:36 PM, Sean Christopherson wrote: > WARN on and reject SEV commands that provide a valid data pointer, but do > not have a known, non-zero length. And conversely, reject commands that > take a command buffer but none is provided. > > Aside from sanity checking intput, disallowing a no

Re: KCSAN: data-race in ext4_fc_commit / ext4_fc_commit

Thanks for the report Hao! I think following lines in fast_commit.c are the culprit: if (likely(sbi->s_fc_avg_commit_time)) sbi->s_fc_avg_commit_time = (commit_time + sbi->s_fc_avg_commit_time * 3) / 4; else sbi->s_fc_

Re: [PATCH][next] iio: hrtimer-trigger: Fix potential integer overflow in iio_hrtimer_store_sampling_frequency

On Mon, 29 Mar 2021 15:58:17 -0500 "Gustavo A. R. Silva" wrote: > Add suffix ULL to constant 1000 in order to avoid a potential integer > overflow and give the compiler complete information about the proper > arithmetic to use. Notice that this constant is being used in a context > that expects a

Re: [PATCH v5 7/8] KVM: arm64: vgic-v3: Expose GICR_TYPER.Last for userspace

Hi Marc, On 4/5/21 12:10 PM, Marc Zyngier wrote: > On Sun, 04 Apr 2021 18:22:42 +0100, > Eric Auger wrote: >> >> Commit 23bde34771f1 ("KVM: arm64: vgic-v3: Drop the >> reporting of GICR_TYPER.Last for userspace") temporarily fixed >> a bug identified when attempting to access the GICR_TYPER >> re

Re: [PATCH v5 0/8] KVM/ARM: Some vgic fixes and init sequence KVM selftests

Hi Marc, On 4/5/21 12:12 PM, Marc Zyngier wrote: > Hi Eric, > > On Sun, 04 Apr 2021 18:22:35 +0100, > Eric Auger wrote: >> >> While writting vgic v3 init sequence KVM selftests I noticed some >> relatively minor issues. This was also the opportunity to try to >> fix the issue laterly reported by

Re: [PATCH v2] powerpc: iommu: fix build when neither PCI or IBMVIO is set

On 4/5/21 2:04 AM, Christophe Leroy wrote: > > > Le 04/04/2021 à 21:26, Randy Dunlap a écrit : >> When neither CONFIG_PCI nor CONFIG_IBMVIO is set/enabled, iommu.c has a >> build error. The fault injection code is not useful in that kernel config, >> so make the FAIL_IOMMU option depend on PCI ||

Re: [PATCH 2/5] crypto: ccp: Reject SEV commands with mismatching command buffer

On Mon, Apr 05, 2021, Tom Lendacky wrote: > On 4/2/21 6:36 PM, Sean Christopherson wrote: > > diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c > > index 6556d220713b..4c513318f16a 100644 > > --- a/drivers/crypto/ccp/sev-dev.c > > +++ b/drivers/crypto/ccp/sev-dev.c > > @@ -14

[PATCH net-next] net: intel: Enable SERDES PHY rx clk for PSE

EHL PSE SGMII mode requires to ungate the SERDES PHY rx clk for power up sequence and vice versa. Signed-off-by: Voon Weifeng --- drivers/net/ethernet/stmicro/stmmac/dwmac-intel.c | 10 ++ drivers/net/ethernet/stmicro/stmmac/dwmac-intel.h | 1 + 2 files changed, 11 insertions(+) diff -

Re: [PATCH] rtlwifi: Simplify locking of a skb list accesses

On 4/5/21 2:57 AM, Christophe JAILLET wrote: The 'c2hcmd_lock' spinlock is only used to protect some __skb_queue_tail() and __skb_dequeue() calls. Use the lock provided in the skb itself and call skb_queue_tail() and skb_dequeue(). These functions already include the correct locking. Signed-off-

Re: [PATCH 2/5] crypto: ccp: Reject SEV commands with mismatching command buffer

On 4/5/21 11:33 AM, Sean Christopherson wrote: > On Mon, Apr 05, 2021, Tom Lendacky wrote: >> On 4/2/21 6:36 PM, Sean Christopherson wrote: >>> diff --git a/drivers/crypto/ccp/sev-dev.c b/drivers/crypto/ccp/sev-dev.c >>> index 6556d220713b..4c513318f16a 100644 >>> --- a/drivers/crypto/ccp/sev-de

[PATCH v6 0/9] KVM/ARM: Some vgic fixes and init sequence KVM selftests

While writting vgic v3 init sequence KVM selftests I noticed some relatively minor issues. This was also the opportunity to try to fix the issue laterly reported by Zenghui, related to the RDIST_TYPER last bit emulation. The final patch is a first batch of VGIC init sequence selftests. Of course th

[PATCH v6 1/9] KVM: arm64: vgic-v3: Fix some error codes when setting RDIST base

KVM_DEV_ARM_VGIC_GRP_ADDR group doc says we should return -EEXIST in case the base address of the redist is already set. We currently return -EINVAL. However we need to return -EINVAL in case a legacy REDIST address is attempted to be set while REDIST_REGIONS were set. This case is discriminated b

[PATCH v6 4/9] KVM: arm/arm64: vgic: Reset base address on kvm_vgic_dist_destroy()

On vgic_dist_destroy(), the addresses are not reset. However for kvm selftest purpose this would allow to continue the test execution even after a failure when running KVM_RUN. So let's reset the base addresses. Signed-off-by: Eric Auger --- v1 -> v2: - use dist-> in the else and add braces ---

[PATCH v6 2/9] KVM: arm64: Fix KVM_VGIC_V3_ADDR_TYPE_REDIST_REGION read

The doc says: "The characteristics of a specific redistributor region can be read by presetting the index field in the attr data. Only valid for KVM_DEV_TYPE_ARM_VGIC_V3" Unfortunately the existing code fails to read the input attr data. Fixes: 04c110932225 ("KVM: arm/arm64: Implement KVM_VGIC

[PATCH v6 3/9] KVM: arm64: vgic-v3: Fix error handling in vgic_v3_set_redist_base()

vgic_v3_insert_redist_region() may succeed while vgic_register_all_redist_iodevs fails. For example this happens while adding a redistributor region overlapping a dist region. The failure only is detected on vgic_register_all_redist_iodevs when vgic_v3_check_base() gets called in vgic_register_redi

[PATCH v6 7/9] kvm: arm64: vgic-v3: Introduce vgic_v3_free_redist_region()

To improve the readability, we introduce the new vgic_v3_free_redist_region helper and also rename vgic_v3_insert_redist_region into vgic_v3_alloc_redist_region Signed-off-by: Eric Auger --- arch/arm64/kvm/vgic/vgic-init.c| 6 ++ arch/arm64/kvm/vgic/vgic-mmio-v3.c | 17 +++--

[PATCH v6 5/9] docs: kvm: devices/arm-vgic-v3: enhance KVM_DEV_ARM_VGIC_CTRL_INIT doc

kvm_arch_vcpu_precreate() returns -EBUSY if the vgic is already initialized. So let's document that KVM_DEV_ARM_VGIC_CTRL_INIT must be called after all vcpu creations. Signed-off-by: Eric Auger --- v1 -> v2: - Must be called after all vcpu creations -> Must be called after all VCPUs have been

<    4   5   6   7   8   9   10   11   12   13   >