mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Ron Economos <re@w6rz.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, linux@roeck-us.net, shuah@kernel.org,
	patches@kernelci.org, lkft-triage@lists.linaro.org,
	pavel@denx.de, f.fainelli@gmail.com, sudipm.mukherjee@gmail.com,
	slade@sladewatkins.com,
	"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH 5.10 00/11] 5.10.123-rc1 review
Date: Thu, 16 Jun 2022 11:11:25 +0100	[thread overview]
Message-ID: <51786b52-a33c-96c3-583b-2fd2d158ad5d@nvidia.com> (raw)
In-Reply-To: <a05678bb-29f8-23ea-9260-cc1cece3f480@w6rz.net>



On 16/06/2022 10:46, Ron Economos wrote:
> On 6/16/22 1:48 AM, Jon Hunter wrote:
>>
>> On 14/06/2022 19:40, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 5.10.123 release.
>>> There are 11 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 Thu, 16 Jun 2022 18:37:02 +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.10.123-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.10.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>
>> No new regressions for Tegra. I am seeing the following kernel warning 
>> that is causing a boot test to fail, but this has been happening for a 
>> few releases now (I would have reported it earlier but we have been 
>> having some infrastructure issues) ...
>>
>>  WARNING KERN urandom_read_iter: 82 callbacks suppressed
>>
>> This appears to be introduced by commit "random: convert to using 
>> fops->read_iter()" [0]. Interestingly, I am not seeing this in the 
>> mainline as far as I can tell and so I am not sure if there is 
>> something else that is missing?
>>
> I'm also seeing this on RISC-V. 5.15 and 5.17, but not 5.18.
> 


That's good to know. I don't see this on 5.18 either, just 5.10, 5.15 
and 5.17.

Jon

-- 
nvpublic

  reply	other threads:[~2022-06-16 10:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 18:40 Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 01/11] Documentation: Add documentation for Processor MMIO Stale Data Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 02/11] x86/speculation/mmio: Enumerate Processor MMIO Stale Data bug Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 03/11] x86/speculation: Add a common function for MD_CLEAR mitigation update Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 04/11] x86/speculation/mmio: Add mitigation for Processor MMIO Stale Data Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 05/11] x86/bugs: Group MDS, TAA & Processor MMIO Stale Data mitigations Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 06/11] x86/speculation/mmio: Enable CPU Fill buffer clearing on idle Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 07/11] x86/speculation/mmio: Add sysfs reporting for Processor MMIO Stale Data Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 08/11] x86/speculation/srbds: Update SRBDS mitigation selection Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 09/11] x86/speculation/mmio: Reuse SRBDS mitigation for SBDS Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 10/11] KVM: x86/speculation: Disable Fill buffer clear within guests Greg Kroah-Hartman
2022-06-14 18:40 ` [PATCH 5.10 11/11] x86/speculation/mmio: Print SMT warning Greg Kroah-Hartman
2022-06-14 21:46 ` [PATCH 5.10 00/11] 5.10.123-rc1 review Florian Fainelli
2022-06-15  2:46 ` Shuah Khan
2022-06-15  5:00 ` Fox Chen
2022-06-15  9:20 ` Sudip Mukherjee
2022-06-15 17:57 ` Naresh Kamboju
2022-06-15 22:03 ` Guenter Roeck
2022-06-16  1:56 ` Samuel Zou
2022-06-16  3:28 ` Tyler Hicks
2022-06-16  8:48 ` Jon Hunter
2022-06-16  9:46   ` Ron Economos
2022-06-16 10:11     ` Jon Hunter [this message]
2022-06-16 13:16       ` Jason A. Donenfeld
2022-06-16 13:11   ` Jason A. Donenfeld
2022-06-16 13:17     ` Jon Hunter
2022-06-16 13:20       ` [PATCH] random: quiet urandom warning ratelimit suppression message Jason A. Donenfeld
2022-06-17  2:10         ` Ron Economos
2022-06-16 11:08 ` [PATCH 5.10 00/11] 5.10.123-rc1 review Pavel Machek

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=51786b52-a33c-96c3-583b-2fd2d158ad5d@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=pavel@denx.de \
    --cc=re@w6rz.net \
    --cc=shuah@kernel.org \
    --cc=slade@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®