From: Chuck Lever III <chuck.lever@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-stable <stable@vger.kernel.org>,
"patches@lists.linux.dev" <patches@lists.linux.dev>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
"shuah@kernel.org" <shuah@kernel.org>,
"patches@kernelci.org" <patches@kernelci.org>,
"lkft-triage@lists.linaro.org" <lkft-triage@lists.linaro.org>,
"pavel@denx.de" <pavel@denx.de>,
"jonathanh@nvidia.com" <jonathanh@nvidia.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"sudipm.mukherjee@gmail.com" <sudipm.mukherjee@gmail.com>,
"srw@sladewatkins.net" <srw@sladewatkins.net>,
"rwarsow@gmx.de" <rwarsow@gmx.de>,
"conor@kernel.org" <conor@kernel.org>,
"allen.lkml@gmail.com" <allen.lkml@gmail.com>,
"broonie@kernel.org" <broonie@kernel.org>
Subject: Re: [PATCH 5.10 000/770] 5.10.220-rc1 review
Date: Tue, 25 Jun 2024 19:08:56 +0000 [thread overview]
Message-ID: <B5D1D979-253A-4339-AF15-5DB3B8503698@oracle.com> (raw)
In-Reply-To: <cf232ba1-a3f3-4931-8775-254d42e261e5@roeck-us.net>
> On Jun 25, 2024, at 12:29 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>
> On 6/25/24 08:13, Chuck Lever III wrote:
>> Hi -
>>> On Jun 25, 2024, at 11:04 AM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>>>
>>> On Tue, Jun 25, 2024 at 07:48:00AM -0700, Guenter Roeck wrote:
>>>> On 6/18/24 05:27, Greg Kroah-Hartman wrote:
>>>>> This is the start of the stable review cycle for the 5.10.220 release.
>>>>> There are 770 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, 20 Jun 2024 12:32:00 +0000.
>>>>> Anything received after that time might be too late.
>>>>>
>>>>
>>>> [ ... ]
>>>>> Chuck Lever <chuck.lever@oracle.com>
>>>>> SUNRPC: Prepare for xdr_stream-style decoding on the server-side
>>>>>
>>>> The ChromeOS patches robot reports a number of fixes for the patches
>>>> applied in 5.5.220. This is one example, later fixed with commit
>>>> 90bfc37b5ab9 ("SUNRPC: Fix svcxdr_init_decode's end-of-buffer
>>>> calculation"), but there are more. Are those fixes going to be
>>>> applied in a subsequent release of v5.10.y, was there a reason to
>>>> not include them, or did they get lost ?
>>>
>>> I saw this as well, but when I tried to apply a few, they didn't, so I
>>> was guessing that Chuck had merged them together into the series.
>>>
>>> I'll defer to Chuck on this, this release was all his :)
>> I did this port months ago, I've been waiting for the dust to
>> settle on the 6.1 and 5.15 NFSD backports, so I've all but
>> forgotten the status of individual patches.
>> If you (Greg or Guenter) send me a list of what you believe is
>> missing, I can have a look at the individual cases and then
>> run the finished result through our NFSD CI gauntlet.
>
> This is what the robot reported so far:
>
> 1242a87da0d8 SUNRPC: Fix svcxdr_init_encode's buflen calculation
> Fixes: bddfdbcddbe2 ("NFSD: Extract the svcxdr_init_encode() helper")
> 90bfc37b5ab9 SUNRPC: Fix svcxdr_init_decode's end-of-buffer calculation
> Fixes: 5191955d6fc6 ("SUNRPC: Prepare for xdr_stream-style decoding on the server-side")
> 10396f4df8b7 nfsd: hold a lighter-weight client reference over CB_RECALL_ANY
> Fixes: 44df6f439a17 ("NFSD: add delegation reaper to react to low memory condition")
My naive search found:
Checking commit 44df6f439a17 ...
upstream fix 10396f4df8b75ff6ab0aa2cd74296565466f2c8d not found
10396f4df8b75ff6ab0aa2cd74296565466f2c8d nfsd: hold a lighter-weight client reference over CB_RECALL_ANY
upstream fix f385f7d244134246f984975ed34cd75f77de479f is already applied
Checking commit a2071573d634 ...
upstream fix f1aa2eb5ea05ccd1fd92d235346e60e90a1ed949 not found
f1aa2eb5ea05ccd1fd92d235346e60e90a1ed949 sysctl: fix proc_dobool() usability
Checking commit bddfdbcddbe2 ...
upstream fix 1242a87da0d8cd2a428e96ca68e7ea899b0f4624 not found
1242a87da0d8cd2a428e96ca68e7ea899b0f4624 SUNRPC: Fix svcxdr_init_encode's buflen calculation
Checking commit 9fe61450972d ... upstream fix 2111c3c0124f7432fe908c036a50abe8733dbf38 not found
2111c3c0124f7432fe908c036a50abe8733dbf38 namei: fix kernel-doc for struct renamedata and more
Checking commit 013c1667cf78 ... upstream fix 2c0f0f3639562d6e38ee9705303c6457c4936eac not found
2c0f0f3639562d6e38ee9705303c6457c4936eac module: correctly exit module_kallsyms_on_each_symbol when fn() != 0
upstream fix 1e80d9cb579ed7edd121753eeccce82ff82521b4 not found
1e80d9cb579ed7edd121753eeccce82ff82521b4 module: potential uninitialized return in module_kallsyms_on_each_symbol()
Checking commit 89ff87494c6e ...
upstream fix 5c11720767f70d34357d00a15ba5a0ad052c40fe not found
5c11720767f70d34357d00a15ba5a0ad052c40fe SUNRPC: Fix a NULL pointer deref in trace_svc_stats_latency()
Checking commit 5191955d6fc6 ...
upstream fix 90bfc37b5ab91c1a6165e3e5cfc49bf04571b762 not found
90bfc37b5ab91c1a6165e3e5cfc49bf04571b762 SUNRPC: Fix svcxdr_init_decode's end-of-buffer calculation
upstream fix b9f83ffaa0c096b4c832a43964fe6bff3acffe10 not found
b9f83ffaa0c096b4c832a43964fe6bff3acffe10 SUNRPC: Fix null pointer dereference in svc_rqst_free()
I'll look into backporting the missing NFSD and SUNRPC patches.
--
Chuck Lever
next prev parent reply other threads:[~2024-06-25 19:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 12:27 Greg Kroah-Hartman
2024-06-18 12:27 ` [PATCH 5.10 004/770] nfsd/nfs3: remove unused macro nfsd3_fhandleres Greg Kroah-Hartman
2024-06-18 21:01 ` [PATCH 5.10 000/770] 5.10.220-rc1 review Jon Hunter
2024-06-19 8:51 ` Pavel Machek
2024-06-19 9:04 ` Dominique Martinet
2024-06-19 10:16 ` Florian Fainelli
2024-06-19 11:10 ` Naresh Kamboju
2024-06-25 14:48 ` Guenter Roeck
2024-06-25 15:04 ` Greg Kroah-Hartman
2024-06-25 15:13 ` Chuck Lever III
2024-06-25 16:29 ` Guenter Roeck
2024-06-25 19:08 ` Chuck Lever III [this message]
2024-06-25 19:35 ` Guenter Roeck
2024-06-25 19:40 ` Chuck Lever III
2024-06-25 19:49 ` Chuck Lever III
2024-06-25 20:43 ` Guenter Roeck
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=B5D1D979-253A-4339-AF15-5DB3B8503698@oracle.com \
--to=chuck.lever@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--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=lkft-triage@lists.linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=pavel@denx.de \
--cc=rwarsow@gmx.de \
--cc=shuah@kernel.org \
--cc=srw@sladewatkins.net \
--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®