This is the start of the stable review cycle for the 4.19.210 release.
There are 12 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, 10 Oct 2021 11:27:07 +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/v4.x/stable-review/patch-4.19.210-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-4.19.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 4.19.210-rc1
Davidlohr Bueso <[email protected]>
lib/timerqueue: Rely on rbtree semantics for next timer
Kate Hsuan <[email protected]>
libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD.
Changbin Du <[email protected]>
tools/vm/page-types: remove dependency on opt_file for idle page tracking
Wen Xiong <[email protected]>
scsi: ses: Retry failed Send/Receive Diagnostic commands
Li Zhijian <[email protected]>
selftests: be sure to make khdr before other targets
Yang Yingliang <[email protected]>
usb: dwc2: check return value after calling platform_get_resource()
Faizel K B <[email protected]>
usb: testusb: Fix for showing the connection speed
Ming Lei <[email protected]>
scsi: sd: Free scsi_disk device via put_device()
Dan Carpenter <[email protected]>
ext2: fix sleeping in atomic bugs on error
Linus Torvalds <[email protected]>
sparc64: fix pci_iounmap() when CONFIG_PCI is not set
Jan Beulich <[email protected]>
xen-netback: correct success/error reporting for the SKB-with-fraglist case
Vladimir Oltean <[email protected]>
net: mdio: introduce a shutdown method to mdio device drivers
-------------
Diffstat:
Makefile | 4 ++--
arch/sparc/lib/iomap.c | 2 ++
drivers/ata/libata-core.c | 34 ++++++++++++++++++++++++++++++++--
drivers/net/phy/mdio_device.c | 11 +++++++++++
drivers/net/xen-netback/netback.c | 2 +-
drivers/scsi/sd.c | 9 +++++----
drivers/scsi/ses.c | 22 ++++++++++++++++++----
drivers/usb/dwc2/hcd.c | 4 ++++
fs/ext2/balloc.c | 14 ++++++--------
include/linux/libata.h | 1 +
include/linux/mdio.h | 3 +++
include/linux/timerqueue.h | 13 ++++++-------
lib/timerqueue.c | 30 ++++++++++++------------------
tools/testing/selftests/lib.mk | 1 +
tools/usb/testusb.c | 14 ++++++++------
tools/vm/page-types.c | 2 +-
16 files changed, 113 insertions(+), 53 deletions(-)
From: Jan Beulich <[email protected]>
[ Upstream commit 3ede7f84c7c21f93c5eac611d60eba3f2c765e0f ]
When re-entering the main loop of xenvif_tx_check_gop() a 2nd time, the
special considerations for the head of the SKB no longer apply. Don't
mistakenly report ERROR to the frontend for the first entry in the list,
even if - from all I can tell - this shouldn't matter much as the overall
transmit will need to be considered failed anyway.
Signed-off-by: Jan Beulich <[email protected]>
Reviewed-by: Paul Durrant <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/net/xen-netback/netback.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/xen-netback/netback.c b/drivers/net/xen-netback/netback.c
index 41bdfb684d46..4d0d5501ca56 100644
--- a/drivers/net/xen-netback/netback.c
+++ b/drivers/net/xen-netback/netback.c
@@ -492,7 +492,7 @@ check_frags:
* the header's copy failed, and they are
* sharing a slot, send an error
*/
- if (i == 0 && sharedslot)
+ if (i == 0 && !first_shinfo && sharedslot)
xenvif_idx_release(queue, pending_idx,
XEN_NETIF_RSP_ERROR);
else
--
2.33.0
From: Yang Yingliang <[email protected]>
[ Upstream commit 856e6e8e0f9300befa87dde09edb578555c99a82 ]
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.
Signed-off-by: Yang Yingliang <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
drivers/usb/dwc2/hcd.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/dwc2/hcd.c b/drivers/usb/dwc2/hcd.c
index 58e53e3d905b..22c4d554865e 100644
--- a/drivers/usb/dwc2/hcd.c
+++ b/drivers/usb/dwc2/hcd.c
@@ -5234,6 +5234,10 @@ int dwc2_hcd_init(struct dwc2_hsotg *hsotg)
hcd->has_tt = 1;
res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
+ if (!res) {
+ retval = -EINVAL;
+ goto error1;
+ }
hcd->rsrc_start = res->start;
hcd->rsrc_len = resource_size(res);
--
2.33.0
From: Linus Torvalds <[email protected]>
[ Upstream commit d8b1e10a2b8efaf71d151aa756052fbf2f3b6d57 ]
Guenter reported [1] that the pci_iounmap() changes remain problematic,
with sparc64 allnoconfig and tinyconfig still not building due to the
header file changes and confusion with the arch-specific pci_iounmap()
implementation.
I'm pretty convinced that sparc should just use GENERIC_IOMAP instead of
doing its own thing, since it turns out that the sparc64 version of
pci_iounmap() is somewhat buggy (see [2]). But in the meantime, this
just fixes the build by avoiding the trivial re-definition of the empty
case.
Link: https://lore.kernel.org/lkml/[email protected]/ [1]
Link: https://lore.kernel.org/lkml/CAHk-=wgheheFx9myQyy5osh79BAazvmvYURAtub2gQtMvLrhqQ@mail.gmail.com/ [2]
Reported-by: Guenter Roeck <[email protected]>
Cc: David Miller <[email protected]>
Signed-off-by: Linus Torvalds <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
arch/sparc/lib/iomap.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/sparc/lib/iomap.c b/arch/sparc/lib/iomap.c
index c9da9f139694..f3a8cd491ce0 100644
--- a/arch/sparc/lib/iomap.c
+++ b/arch/sparc/lib/iomap.c
@@ -19,8 +19,10 @@ void ioport_unmap(void __iomem *addr)
EXPORT_SYMBOL(ioport_map);
EXPORT_SYMBOL(ioport_unmap);
+#ifdef CONFIG_PCI
void pci_iounmap(struct pci_dev *dev, void __iomem * addr)
{
/* nothing to do */
}
EXPORT_SYMBOL(pci_iounmap);
+#endif
--
2.33.0
From: Faizel K B <[email protected]>
[ Upstream commit f81c08f897adafd2ed43f86f00207ff929f0b2eb ]
testusb' application which uses 'usbtest' driver reports 'unknown speed'
from the function 'find_testdev'. The variable 'entry->speed' was not
updated from the application. The IOCTL mentioned in the FIXME comment can
only report whether the connection is low speed or not. Speed is read using
the IOCTL USBDEVFS_GET_SPEED which reports the proper speed grade. The
call is implemented in the function 'handle_testdev' where the file
descriptor was availble locally. Sample output is given below where 'high
speed' is printed as the connected speed.
sudo ./testusb -a
high speed /dev/bus/usb/001/011 0
/dev/bus/usb/001/011 test 0, 0.000015 secs
/dev/bus/usb/001/011 test 1, 0.194208 secs
/dev/bus/usb/001/011 test 2, 0.077289 secs
/dev/bus/usb/001/011 test 3, 0.170604 secs
/dev/bus/usb/001/011 test 4, 0.108335 secs
/dev/bus/usb/001/011 test 5, 2.788076 secs
/dev/bus/usb/001/011 test 6, 2.594610 secs
/dev/bus/usb/001/011 test 7, 2.905459 secs
/dev/bus/usb/001/011 test 8, 2.795193 secs
/dev/bus/usb/001/011 test 9, 8.372651 secs
/dev/bus/usb/001/011 test 10, 6.919731 secs
/dev/bus/usb/001/011 test 11, 16.372687 secs
/dev/bus/usb/001/011 test 12, 16.375233 secs
/dev/bus/usb/001/011 test 13, 2.977457 secs
/dev/bus/usb/001/011 test 14 --> 22 (Invalid argument)
/dev/bus/usb/001/011 test 17, 0.148826 secs
/dev/bus/usb/001/011 test 18, 0.068718 secs
/dev/bus/usb/001/011 test 19, 0.125992 secs
/dev/bus/usb/001/011 test 20, 0.127477 secs
/dev/bus/usb/001/011 test 21 --> 22 (Invalid argument)
/dev/bus/usb/001/011 test 24, 4.133763 secs
/dev/bus/usb/001/011 test 27, 2.140066 secs
/dev/bus/usb/001/011 test 28, 2.120713 secs
/dev/bus/usb/001/011 test 29, 0.507762 secs
Signed-off-by: Faizel K B <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Greg Kroah-Hartman <[email protected]>
Signed-off-by: Sasha Levin <[email protected]>
---
tools/usb/testusb.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/tools/usb/testusb.c b/tools/usb/testusb.c
index 2d89b5f686b1..791aadef2d59 100644
--- a/tools/usb/testusb.c
+++ b/tools/usb/testusb.c
@@ -278,12 +278,6 @@ nomem:
}
entry->ifnum = ifnum;
-
- /* FIXME update USBDEVFS_CONNECTINFO so it tells about high speed etc */
-
- fprintf(stderr, "%s speed\t%s\t%u\n",
- speed(entry->speed), entry->name, entry->ifnum);
-
entry->next = testdevs;
testdevs = entry;
return 0;
@@ -312,6 +306,14 @@ static void *handle_testdev (void *arg)
return 0;
}
+ status = ioctl(fd, USBDEVFS_GET_SPEED, NULL);
+ if (status < 0)
+ fprintf(stderr, "USBDEVFS_GET_SPEED failed %d\n", status);
+ else
+ dev->speed = status;
+ fprintf(stderr, "%s speed\t%s\t%u\n",
+ speed(dev->speed), dev->name, dev->ifnum);
+
restart:
for (i = 0; i < TEST_CASES; i++) {
if (dev->test != -1 && dev->test != i)
--
2.33.0
On 10/8/21 5:27 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.210 release.
> There are 12 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, 10 Oct 2021 11:27:07 +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/v4.x/stable-review/patch-4.19.210-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-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Compiled and booted on my test system. No dmesg regressions.
Tested-by: Shuah Khan <[email protected]>
thanks,
-- Shuah
Hi!
> This is the start of the stable review cycle for the 4.19.210 release.
> There are 12 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.
CIP testing did not find any problems here:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-4.19.y
Tested-by: Pavel Machek (CIP) <[email protected]>
Best regards,
Pavel
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
On Fri, Oct 08, 2021 at 01:27:48PM +0200, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.210 release.
> There are 12 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, 10 Oct 2021 11:27:07 +0000.
> Anything received after that time might be too late.
>
Build results:
total: 155 pass: 155 fail: 0
Qemu test results:
total: 439 pass: 439 fail: 0
Tested-by: Guenter Roeck <[email protected]>
Guenter
On Fri, 8 Oct 2021 at 17:00, Greg Kroah-Hartman
<[email protected]> wrote:
>
> This is the start of the stable review cycle for the 4.19.210 release.
> There are 12 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, 10 Oct 2021 11:27:07 +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/v4.x/stable-review/patch-4.19.210-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-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
Results from Linaro’s test farm.
No regressions on arm64, arm, x86_64, and i386.
Tested-by: Linux Kernel Functional Testing <[email protected]>
NOTE:
LTP version upgrade to LTP 20210927.
The new case "cfs_bandwidth01" found the following warning.
Since it is a new test case that found this warning can not be considered as
regression.
This warning is only seen on stable rc 4.19
but not found on 4.14, 5.4, 5.10 and 5.14.
Test output log:
----------------
cfs_bandwidth01.c:57: TINFO: Set 'worker1/cpu.max' = '3000 10000'
cfs_bandwidth01.c:57: TINFO: Set 'worker2/cpu.max' = '2000 10000'
cfs_bandwidth01.c:57: TINFO: Set 'worker3/cpu.max' = '3000 10000'
cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained workers
cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
cfs_bandwidth01.c:130: TPASS: Workers exited
cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained workers
cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
cfs_bandwidth01.c:130: TPASS: Workers exited
cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained work[
56.624213] ------------[ cut here ]------------
[ 56.629421] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list
[ 56.629439] WARNING: CPU: 2 PID: 0 at kernel/sched/fair.c:375
unthrottle_cfs_rq+0x1f7/0x220
[ 56.643189] Modules linked in: x86_pkg_temp_thermal
[ 56.648073] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.19.210-rc1 #1
[ 56.654515] Hardware name: Supermicro SYS-5019S-ML/X11SSH-F, BIOS
2.2 05/23/2018
[ 56.661908] RIP: 0010:unthrottle_cfs_rq+0x1f7/0x220
[ 56.666779] Code: 87 b7 00 0f 0b e9 8a fe ff ff 80 3d c5 a5 7a 01
00 0f 85 4d ff ff ff 48 c7 c7 d0 1f 94 87 c6 05 b1 a5 7a 01 01 e8 26
87 b7 00 <0f> 0b 48 85 db 0f 84 70 ff ff ff e9 2a ff ff ff 31 db 80 3d
93 a5
[ 56.685515] RSP: 0018:ffff945e2f903e48 EFLAGS: 00010086
[ 56.690731] RAX: 0000000000000000 RBX: ffff945de35b0e00 RCX: 0000000000000000
[ 56.697855] RDX: 0000000000000000 RSI: ffffffff87fb8c8d RDI: ffffffff87fb908d
[ 56.704979] RBP: ffff945e2f903e70 R08: 0000000d2f6066af R09: ffff945e2f903de0
[ 56.712102] R10: 0000000000000000 R11: ffffffff87fb886d R12: ffff945e2df6b800
[ 56.719228] R13: ffff945e2f89fbc0 R14: 0000000000000001 R15: 0000000000000001
[ 56.726353] FS: 0000000000000000(0000) GS:ffff945e2f900000(0000)
knlGS:0000000000000000
[ 56.734429] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 56.740165] CR2: 00000000006333e8 CR3: 000000014a20a003 CR4: 00000000003606e0
[ 56.747290] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 56.754412] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 56.761536] Call Trace:
[ 56.763980] <IRQ>
[ 56.765992] distribute_cfs_runtime+0xd1/0x120
[ 56.770428] sched_cfs_period_timer+0xbb/0x210
[ 56.774868] __hrtimer_run_queues+0x131/0x2b0
[ 56.779216] ? sched_cfs_slack_timer+0xc0/0xc0
[ 56.783656] hrtimer_interrupt+0xfe/0x290
[ 56.787667] ? tick_irq_enter+0xab/0xd0
[ 56.791499] smp_apic_timer_interrupt+0x73/0x140
[ 56.796117] apic_timer_interrupt+0xf/0x20
[ 56.800206] </IRQ>
[ 56.802306] RIP: 0010:cpuidle_enter_state+0x119/0x2c0
[ 56.807349] Code: 77 ff 80 7d c7 00 74 12 9c 58 f6 c4 02 0f 85 8e
01 00 00 31 ff e8 c7 1d 7d ff e8 22 85 82 ff fb 48 ba cf f7 53 e3 a5
9b c4 20 <4c> 2b 7d c8 4c 89 f8 49 c1 ff 3f 48 f7 ea b8 ff ff ff 7f 48
c1 fa
[ 56.826086] RSP: 0018:ffffa81440cfbe50 EFLAGS: 00000286 ORIG_RAX:
ffffffffffffff13
[ 56.833642] RAX: ffffa81440cfbe90 RBX: ffff945e2e2ee800 RCX: 000000000000001f
[ 56.840780] RDX: 20c49ba5e353f7cf RSI: ffffffff86e286f7 RDI: ffffffff86e2850e
[ 56.847908] RBP: ffffa81440cfbe90 R08: 0000000d2f10ca02 R09: 00000000ffffffff
[ 56.855031] R10: 000000000000024a R11: ffff945e2f91ed08 R12: 0000000000000001
[ 56.862156] R13: ffffffff87cca620 R14: ffffffff87cca680 R15: 0000000d2f10ca02
[ 56.869279] ? cpuidle_enter+0x17/0x20
[ 56.873024] ? cpuidle_enter_state+0x10e/0x2c0
[ 56.877461] cpuidle_enter+0x17/0x20
[ 56.881029] call_cpuidle+0x23/0x40
[ 56.884515] do_idle+0x1b9/0x240
[ 56.887740] cpu_startup_entry+0x73/0x80
[ 56.891654] start_secondary+0x197/0x1e0
[ 56.895574] secondary_startup_64+0xa4/0xb0
[ 56.899751] ---[ end trace 20fd56519aa6c3c8 ]---
ers
cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
cfs_bandwidth01.c:130: TPASS: Workers exited
cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained workers
cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
cfs_bandwidth01.c:130: TPASS: Workers exited
cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained workers
cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
cfs_bandwidth01.c:130: TPASS: Workers exited
tst_test.c:1401: TFAIL: Kernel is now tainted.
HINT: You _MAY_ be missing kernel fixes, see:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=39f23ce07b93
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b34cb07dde7c
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fe61468b2cbc
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=5ab297bab984
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d4d22468dae
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=fdaba61ef8a2
URL:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.209-13-g0cf6c1babdb5/testrun/6034624/suite/linux-log-parser/test/check-kernel-warning-3690612/log
## Build
* kernel: 4.19.210-rc1
* git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
* git branch: linux-4.19.y
* git commit: 0cf6c1babdb51acc917475373133f5d05d584d35
* git describe: v4.19.209-13-g0cf6c1babdb5
* test details:
https://qa-reports.linaro.org/lkft/linux-stable-rc-linux-4.19.y/build/v4.19.209-13-g0cf6c1babdb5
## No regressions (compared to v4.19.209-13-g1c111a02b49d)
## No fixes (compared to v4.19.209-13-g1c111a02b49d)
## Test result summary
total: 80521, pass: 65633, fail: 663, skip: 12565, xfail: 1660
## Build Summary
* arm: 258 total, 258 passed, 0 failed
* arm64: 74 total, 74 passed, 0 failed
* dragonboard-410c: 1 total, 1 passed, 0 failed
* hi6220-hikey: 1 total, 1 passed, 0 failed
* i386: 35 total, 35 passed, 0 failed
* juno-r2: 1 total, 1 passed, 0 failed
* mips: 58 total, 58 passed, 0 failed
* s390: 24 total, 24 passed, 0 failed
* sparc: 24 total, 24 passed, 0 failed
* x15: 1 total, 1 passed, 0 failed
* x86: 1 total, 1 passed, 0 failed
* x86_64: 42 total, 42 passed, 0 failed
## Test suites summary
* fwts
* igt-gpu-tools
* kselftest-android
* kselftest-arm64
* kselftest-arm64/arm64.btitest.bti_c_func
* kselftest-arm64/arm64.btitest.bti_j_func
* kselftest-arm64/arm64.btitest.bti_jc_func
* kselftest-arm64/arm64.btitest.bti_none_func
* kselftest-arm64/arm64.btitest.nohint_func
* kselftest-arm64/arm64.btitest.paciasp_func
* kselftest-arm64/arm64.nobtitest.bti_c_func
* kselftest-arm64/arm64.nobtitest.bti_j_func
* kselftest-arm64/arm64.nobtitest.bti_jc_func
* kselftest-arm64/arm64.nobtitest.bti_none_func
* kselftest-arm64/arm64.nobtitest.nohint_func
* kselftest-arm64/arm64.nobtitest.paciasp_func
* kselftest-bpf
* kselftest-breakpoints
* kselftest-capabilities
* kselftest-cgroup
* kselftest-clone3
* kselftest-core
* kselftest-cpu-hotplug
* kselftest-cpufreq
* kselftest-drivers
* kselftest-efivarfs
* kselftest-filesystems
* kselftest-firmware
* kselftest-fpu
* kselftest-futex
* kselftest-gpio
* kselftest-intel_pstate
* kselftest-ipc
* kselftest-ir
* kselftest-kcmp
* kselftest-kexec
* kselftest-kvm
* kselftest-lib
* kselftest-livepatch
* kselftest-membarrier
* kselftest-memfd
* kselftest-memory-hotplug
* kselftest-mincore
* kselftest-mount
* kselftest-mqueue
* kselftest-net
* kselftest-netfilter
* kselftest-nsfs
* kselftest-openat2
* kselftest-pid_namespace
* kselftest-pidfd
* kselftest-proc
* kselftest-pstore
* kselftest-ptrace
* kselftest-rseq
* kselftest-rtc
* kselftest-seccomp
* kselftest-sigaltstack
* kselftest-size
* kselftest-splice
* kselftest-static_keys
* kselftest-sync
* kselftest-sysctl
* kselftest-tc-testing
* kselftest-timens
* kselftest-timers
* kselftest-tmpfs
* kselftest-tpm2
* kselftest-user
* kselftest-vm
* kselftest-x86
* kselftest-zram
* kvm-unit-tests
* libhugetlbfs
* linux-log-parser
* ltp-cap_bounds-tests
* ltp-commands-tests
* ltp-containers-tests
* ltp-controllers-tests
* ltp-cpuhotplug-tests
* ltp-crypto-tests
* ltp-cve-tests
* ltp-dio-tests
* ltp-fcntl-locktests-tests
* ltp-filecaps-tests
* ltp-fs-tests
* ltp-fs_bind-tests
* ltp-fs_perms_simple-tests
* ltp-fsx-tests
* ltp-hugetlb-tests
* ltp-io-tests
* ltp-ipc-tests
* ltp-math-tests
* ltp-mm-tests
* ltp-nptl-tests
* ltp-open-posix-tests
* ltp-pty-tests
* ltp-sched-tests
* ltp-securebits-tests
* ltp-syscalls-tests
* ltp-tracing-tests
* network-basic-tests
* packetdrill
* perf
* rcutorture
* ssuite
* v4l2-compliance
--
Linaro LKFT
https://lkft.linaro.org
On 2021/10/8 19:27, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.19.210 release.
> There are 12 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, 10 Oct 2021 11:27:07 +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/v4.x/stable-review/patch-4.19.210-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-4.19.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
Tested on arm64 and x86 for 4.19.210-rc1,
Kernel repo:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
Branch: linux-4.19.y
Version: 4.19.210-rc1
Commit: 0cf6c1babdb51acc917475373133f5d05d584d35
Compiler: gcc version 7.3.0 (GCC)
arm64:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8859
passed: 8859
failed: 0
timeout: 0
--------------------------------------------------------------------
x86:
--------------------------------------------------------------------
Testcase Result Summary:
total: 8859
passed: 8859
failed: 0
timeout: 0
--------------------------------------------------------------------
Tested-by: Hulk Robot <[email protected]>
Hello Naresh,
Naresh Kamboju <[email protected]> writes:
> On Fri, 8 Oct 2021 at 17:00, Greg Kroah-Hartman
> <[email protected]> wrote:
>>
>> This is the start of the stable review cycle for the 4.19.210 release.
>> There are 12 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, 10 Oct 2021 11:27:07 +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/v4.x/stable-review/patch-4.19.210-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-4.19.y
>> and the diffstat can be found below.
>>
>> thanks,
>>
>> greg k-h
>
> Results from Linaro’s test farm.
> No regressions on arm64, arm, x86_64, and i386.
>
> Tested-by: Linux Kernel Functional Testing <[email protected]>
>
> NOTE:
> LTP version upgrade to LTP 20210927.
> The new case "cfs_bandwidth01" found the following warning.
> Since it is a new test case that found this warning can not be considered as
> regression.
> This warning is only seen on stable rc 4.19
> but not found on 4.14, 5.4, 5.10 and 5.14.
>
> Test output log:
> ----------------
> cfs_bandwidth01.c:57: TINFO: Set 'worker1/cpu.max' = '3000 10000'
> cfs_bandwidth01.c:57: TINFO: Set 'worker2/cpu.max' = '2000 10000'
> cfs_bandwidth01.c:57: TINFO: Set 'worker3/cpu.max' = '3000 10000'
> cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained workers
> cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
> cfs_bandwidth01.c:130: TPASS: Workers exited
> cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained workers
> cfs_bandwidth01.c:57: TINFO: Set 'level2/cpu.max' = '5000 10000'
> cfs_bandwidth01.c:130: TPASS: Workers exited
> cfs_bandwidth01.c:118: TPASS: Scheduled bandwidth constrained work[
> 56.624213] ------------[ cut here ]------------
> [ 56.629421] rq->tmp_alone_branch != &rq->leaf_cfs_rq_list
FWIW this appears to be the bug the test is intended to
reproduce. Originally seen on a SUSE enterprise 4.12 kernel.
--
Thank you,
Richard.