From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Georg Müller" <georgmueller@gmx.net>
Cc: stable@vger.kernel.org, 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
Subject: Re: [PATCH 6.0 000/177] 6.0.18-rc1 review
Date: Fri, 6 Jan 2023 15:34:15 +0100 [thread overview]
Message-ID: <Y7gxZ201DOi7nyZZ@kroah.com> (raw)
In-Reply-To: <53f19c0a-412d-ba8e-57bb-b626ba5b7672@gmx.net>
On Fri, Jan 06, 2023 at 03:27:58PM +0100, Georg Müller wrote:
> Hi Greg,
>
> Am 04.01.23 um 17:04 schrieb Greg Kroah-Hartman:
> > This is the start of the stable review cycle for the 6.0.18 release.
> > There are 177 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 Fri, 06 Jan 2023 16:04:29 +0000.
> > Anything received after that time might be too late.
>
> There is an easy-to-trigger kernel panic in cifs which was introduced in 6.0.16 and could be fixed by backporting the following commit:
>
> 9ee2afe5207b ("cifs: prevent copying past input buffer boundaries")
>
> Please see https://bugzilla.kernel.org/show_bug.cgi?id=216895 for the details
>
> Could this commit be added as well to 6.0.18?
It is too late for this release, we can add it to the next one. Or you
can move to 6.1.y which you should be doing anyway as 6.0.y is about to
go end-of-life in a few days.
thanks,
greg k-h
next prev parent reply other threads:[~2023-01-06 14:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 16:04 [PATCH 6.0 000/177] 6.0.18-rc1 review Greg Kroah-Hartman
2023-01-04 20:08 ` Florian Fainelli
2023-01-04 21:48 ` Allen Pais
2023-01-04 22:18 ` Shuah Khan
2023-01-04 22:33 ` Guenter Roeck
2023-01-05 7:02 ` Jon Hunter
2023-01-05 7:20 ` Bagas Sanjaya
2023-01-05 9:03 ` Naresh Kamboju
2023-01-05 11:14 ` Sudip Mukherjee (Codethink)
2023-01-05 14:44 ` Justin Forbes
2023-01-05 22:33 ` Ron Economos
2023-01-06 14:27 ` Georg Müller
2023-01-06 14:34 ` Greg Kroah-Hartman [this message]
2023-01-07 9:25 ` Greg Kroah-Hartman
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=Y7gxZ201DOi7nyZZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=f.fainelli@gmail.com \
--cc=georgmueller@gmx.net \
--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