From: Salvatore Bonaccorso <carnil@debian.org>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Borislav Petkov <bp@alien8.de>,
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,
conor@kernel.org, Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 6.1 000/194] 6.1.47-rc1 review
Date: Tue, 22 Aug 2023 17:27:02 +0200 [thread overview]
Message-ID: <ZOTTxsW5IGhOO8IW@eldamar.lan> (raw)
In-Reply-To: <CA+G9fYvkBSb-i_6unB3bRLwRibVtZ3snYDe_gG+bsZehu3Hv3w@mail.gmail.com>
Hi,
[Adding Peter Zijlstra to CC]
On Tue, Aug 22, 2023 at 04:25:22PM +0530, Naresh Kamboju wrote:
> On Tue, 22 Aug 2023 at 01:21, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> >
> > This is the start of the stable review cycle for the 6.1.47 release.
> > There are 194 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 Wed, 23 Aug 2023 19:40:45 +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.1.47-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-6.1.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:
> Kernel warnings noticed on x86_64 while booting the kernel.
> Paul E. McKenney reported this last week [1] and discussions email
> thread provided here.
>
> [1] https://lore.kernel.org/lkml/4dc3d0ec-b827-4bce-8927-cfa5d837fd03@paulmck-laptop/T/
Seeing the same warning for the 6.1.47-rc1, which is missing
4ae68b26c3ab ("objtool/x86: Fix SRSO mess"). Unfortunately the commit
will not apply cleanly to 6.1.y.
I guess we need at least as well dbcdbdfdf137 ("objtool: Rework
instruction -> symbol mapping"), but not sure this is enough.
Peter, is this correct?
Regards,
Salvatore
next prev parent reply other threads:[~2023-08-22 15:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 19:39 [PATCH 6.1 000/194] 6.1.47-rc1 review Greg Kroah-Hartman
2023-08-21 22:58 ` Joel Fernandes
2023-08-22 15:41 ` Joel Fernandes
2023-08-21 23:35 ` Takeshi Ogasawara
2023-08-22 3:00 ` Bagas Sanjaya
2023-08-22 10:55 ` Naresh Kamboju
2023-08-22 15:27 ` Salvatore Bonaccorso [this message]
2023-08-22 15:51 ` Greg Kroah-Hartman
2023-08-22 17:27 ` Greg Kroah-Hartman
2023-08-22 11:01 ` SeongJae Park
2023-08-22 14:08 ` Shuah Khan
2023-08-22 20:23 ` Florian Fainelli
2023-08-22 23:55 ` Ron Economos
2023-08-23 0:49 ` Guenter Roeck
2023-08-23 7:03 ` Greg Kroah-Hartman
2023-08-23 8:17 ` Naresh Kamboju
2023-08-23 8:27 ` Greg Kroah-Hartman
2023-08-23 13:30 ` Guenter Roeck
2023-08-23 15:50 ` Greg Kroah-Hartman
2023-08-24 13:35 ` Greg Kroah-Hartman
2023-08-24 15:08 ` Guenter Roeck
2023-08-24 15:15 ` Greg Kroah-Hartman
2023-08-24 15:58 ` Guenter Roeck
2023-08-24 16:40 ` Greg Kroah-Hartman
2023-08-23 13:28 ` Guenter Roeck
2023-08-23 8:54 ` Sudip Mukherjee (Codethink)
2023-08-23 9:26 ` Greg Kroah-Hartman
2023-08-23 10:32 ` Naresh Kamboju
2023-08-23 13:30 ` Guenter Roeck
2023-08-23 14:37 ` Sudip Mukherjee
2023-08-23 9:35 ` Conor Dooley
2023-08-23 13:37 ` Guenter Roeck
2023-08-23 15:24 ` 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=ZOTTxsW5IGhOO8IW@eldamar.lan \
--to=carnil@debian.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--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=naresh.kamboju@linaro.org \
--cc=patches@kernelci.org \
--cc=patches@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=pavel@denx.de \
--cc=peterz@infradead.org \
--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