From: Richard Palethorpe <rpalethorpe@suse.de>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
open list <linux-kernel@vger.kernel.org>,
Shuah Khan <shuah@kernel.org>,
Florian Fainelli <f.fainelli@gmail.com>,
patches@kernelci.org, lkft-triage@lists.linaro.org,
Jon Hunter <jonathanh@nvidia.com>,
linux-stable <stable@vger.kernel.org>,
Pavel Machek <pavel@denx.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Guenter Roeck <linux@roeck-us.net>, LTP List <ltp@lists.linux.it>,
Cyril Hrubis <chrubis@suse.cz>, Li Wang <liwang@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
mkoutny@suse.cz
Subject: Re: [PATCH 4.19 00/12] 4.19.210-rc1 review
Date: Mon, 11 Oct 2021 08:28:31 +0100 [thread overview]
Message-ID: <875yu4au4n.fsf@suse.de> (raw)
In-Reply-To: <CA+G9fYvOK+5qPEU7RMfD1O5O3EwTfThoh3Le9Rx8GDhY3nY1Ww@mail.gmail.com>
Hello Naresh,
Naresh Kamboju <naresh.kamboju@linaro.org> writes:
> On Fri, 8 Oct 2021 at 17:00, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> 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 <lkft@linaro.org>
>
> 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.
next prev parent reply other threads:[~2021-10-11 7:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 11:27 [PATCH 4.19 00/12] 4.19.210-rc1 review Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 01/12] net: mdio: introduce a shutdown method to mdio device drivers Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 02/12] xen-netback: correct success/error reporting for the SKB-with-fraglist case Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 03/12] sparc64: fix pci_iounmap() when CONFIG_PCI is not set Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 04/12] ext2: fix sleeping in atomic bugs on error Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 05/12] scsi: sd: Free scsi_disk device via put_device() Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 06/12] usb: testusb: Fix for showing the connection speed Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 07/12] usb: dwc2: check return value after calling platform_get_resource() Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 08/12] selftests: be sure to make khdr before other targets Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 09/12] scsi: ses: Retry failed Send/Receive Diagnostic commands Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 10/12] tools/vm/page-types: remove dependency on opt_file for idle page tracking Greg Kroah-Hartman
2021-10-08 11:27 ` [PATCH 4.19 11/12] libata: Add ATA_HORKAGE_NO_NCQ_ON_ATI for Samsung 860 and 870 SSD Greg Kroah-Hartman
2021-10-08 11:28 ` [PATCH 4.19 12/12] lib/timerqueue: Rely on rbtree semantics for next timer Greg Kroah-Hartman
2021-10-08 15:43 ` [PATCH 4.19 00/12] 4.19.210-rc1 review Jon Hunter
2021-10-08 20:47 ` Pavel Machek
2021-10-08 20:48 ` Shuah Khan
2021-10-08 21:03 ` Guenter Roeck
2021-10-09 17:41 ` Naresh Kamboju
2021-10-11 7:28 ` Richard Palethorpe [this message]
2021-10-11 1:37 ` Samuel Zou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875yu4au4n.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chrubis@suse.cz \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=liwang@redhat.com \
--cc=lkft-triage@lists.linaro.org \
--cc=ltp@lists.linux.it \
--cc=mkoutny@suse.cz \
--cc=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=pavel@denx.de \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vincent.guittot@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).