From: Jiri Slaby <jirislaby@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>, stable@vger.kernel.org
Cc: patches@lists.linux.dev, linux-kernel@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,
jonathanh@nvidia.com, f.fainelli@gmail.com,
sudipm.mukherjee@gmail.com, srw@sladewatkins.net, rwarsow@gmx.de,
conor@kernel.org, allen.lkml@gmail.com, broonie@kernel.org,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
kerneljasonxing@gmail.com
Subject: Re: [PATCH 6.9 000/368] 6.9.4-rc2 review
Date: Tue, 11 Jun 2024 07:48:39 +0200 [thread overview]
Message-ID: <aee27b1f-5c8e-4060-a19e-42e198c1493f@kernel.org> (raw)
In-Reply-To: <95bb260e-bf31-46dc-b720-88ca6aa7e29c@kernel.org>
On 11. 06. 24, 7:45, Jiri Slaby wrote:
> On 09. 06. 24, 13:41, Greg Kroah-Hartman wrote:
>> This is the start of the stable review cycle for the 6.9.4 release.
>> There are 368 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 Tue, 11 Jun 2024 11:36:08 +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/v6.x/stable-review/patch-6.9.4-rc2.gz
>> or in the git tree and branch at:
>> git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-6.9.y
>> and the diffstat can be found below.
>
> Maybe it was noted somewhere already, but I was forced by our machinery
> to include this too:
> +Subject: tcp: reduce accepted window in NEW_SYN_RECV state
> +Git-commit: f4dca95fc0f6350918f2e6727e35b41f7f86fcce
> +Patch-mainline: 6.10-rc2
> +
> +Jason commit made checks against ACK sequence less strict
> +and can be exploited by attackers to establish spoofed flows
> +with less probes.
>
> which makes sense to me.
Forget about this, you dropped 378979e94e953c207 in -rc2 in:
commit f11c1a69cc6b202f454d5e585b6917ce2873bcc9
Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Date: Sun Jun 9 13:26:26 2024 +0200
drop more patches
All is good then.
> thanks,--
js
suse labs
prev parent reply other threads:[~2024-06-11 5:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 11:41 [PATCH 6.9 000/368] 6.9.4-rc2 review Greg Kroah-Hartman
2024-06-09 16:12 ` SeongJae Park
2024-06-10 1:28 ` Bagas Sanjaya
2024-06-10 14:08 ` Mark Brown
2024-06-10 15:54 ` Jon Hunter
2024-06-10 16:13 ` Naresh Kamboju
2024-06-11 3:59 ` Kelsey Steele
2024-06-11 5:45 ` Jiri Slaby
2024-06-11 5:48 ` Jiri Slaby [this message]
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=aee27b1f-5c8e-4060-a19e-42e198c1493f@kernel.org \
--to=jirislaby@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=allen.lkml@gmail.com \
--cc=broonie@kernel.org \
--cc=conor@kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jonathanh@nvidia.com \
--cc=kerneljasonxing@gmail.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).