Documentation/process/changes.rst | 7 +++++ Makefile | 4 +-- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++ drivers/gpu/drm/amd/display/dc/core/dc.c | 50 +++++++++++++++++------------- drivers/nubus/proc.c | 22 ++++++++++--- drivers/pci/pci-acpi.c | 53 ++++++++++++++++++++++++-------- include/linux/mm.h | 4 ++- mm/memory.c | 4 +++ mm/nommu.c | 7 ++++- scripts/tags.sh | 9 +++++- tools/perf/util/symbol.c | 17 ++++++++-- 11 files changed, 135 insertions(+), 46 deletions(-)
This is the start of the stable review cycle for the 6.1.38 release.
There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Linux 6.1.38-rc2
Linus Torvalds <torvalds@linux-foundation.org>
gup: avoid stack expansion warning for known-good case
Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
drm/amd/display: Ensure vmin and vmax adjust for DCE
Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
drm/amdgpu: Validate VM ioctl flags.
Ahmed S. Darwish <darwi@linutronix.de>
docs: Set minimal gtags / GNU GLOBAL version to 6.6.5
Ahmed S. Darwish <darwi@linutronix.de>
scripts/tags.sh: Resolve gtags empty index generation
Krister Johansen <kjlx@templeofstupid.com>
perf symbols: Symbol lookup with kcore can fail if multiple segments match stext
Finn Thain <fthain@linux-m68k.org>
nubus: Partially revert proc_create_single_data() conversion
Linus Torvalds <torvalds@linux-foundation.org>
execve: always mark stack as growing down during early stack setup
Mario Limonciello <mario.limonciello@amd.com>
PCI/ACPI: Call _REG when transitioning D-states
Bjorn Helgaas <bhelgaas@google.com>
PCI/ACPI: Validate acpi_pci_set_power_state() parameter
Aric Cyr <aric.cyr@amd.com>
drm/amd/display: Do not update DRR while BW optimizations pending
Alvin Lee <Alvin.Lee2@amd.com>
drm/amd/display: Remove optimization for VRR updates
Max Filippov <jcmvbkbc@gmail.com>
xtensa: fix lock_mm_and_find_vma in case VMA not found
-------------
Diffstat:
Documentation/process/changes.rst | 7 +++++
Makefile | 4 +--
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++
drivers/gpu/drm/amd/display/dc/core/dc.c | 50 +++++++++++++++++-------------
drivers/nubus/proc.c | 22 ++++++++++---
drivers/pci/pci-acpi.c | 53 ++++++++++++++++++++++++--------
include/linux/mm.h | 4 ++-
mm/memory.c | 4 +++
mm/nommu.c | 7 ++++-
scripts/tags.sh | 9 +++++-
tools/perf/util/symbol.c | 17 ++++++++--
11 files changed, 135 insertions(+), 46 deletions(-)
Hi Greg On Tue, Jul 4, 2023 at 5:49 PM Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y > and the diffstat can be found below. > > thanks, > > greg k-h > 6.1.38-rc2 tested. Build successfully completed. Boot successfully completed. No dmesg regressions. Video output normal. Sound output normal. Lenovo ThinkPad X1 Carbon Gen10(Intel i7-1260P(x86_64), arch linux) Thanks Tested-by: Takeshi Ogasawara <takeshi.ogasawara@futuring-girl.com>
On Tue, Jul 04, 2023 at 09:48:32AM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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. > Successfully compiled and installed bindeb-pkgs on my computer (Acer Aspire E15, Intel Core i3 Haswell). No noticeable regressions. Tested-by: Bagas Sanjaya <bagasdotme@gmail.com> -- An old man doll... just what I always wanted! - Clara
On Tue, Jul 04, 2023 at 09:48:32AM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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. Tested-by: Conor Dooley <conor.dooley@microchip.com> Cheers, Conor.
On 7/4/23 1:48 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y > and the diffstat can be found below. > > thanks, > > greg k-h Built and booted successfully on RISC-V RV64 (HiFive Unmatched). Tested-by: Ron Economos <re@w6rz.net>
On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
>
> -------------
> Pseudo-Shortlog of commits:
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Linux 6.1.38-rc2
>
> Linus Torvalds <torvalds@linux-foundation.org>
> gup: avoid stack expansion warning for known-good case
>
I am a bit puzzled by this patch. It avoids a warning introduced with
upstream commit a425ac5365f6 ("gup: add warning if some caller would
seem to want stack expansion"), or at least it says so, but that patch
is not in v6.1.y. Why is this patch needed here ?
Thanks,
Guenter
> Rodrigo Siqueira <Rodrigo.Siqueira@amd.com>
> drm/amd/display: Ensure vmin and vmax adjust for DCE
>
> Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
> drm/amdgpu: Validate VM ioctl flags.
>
> Ahmed S. Darwish <darwi@linutronix.de>
> docs: Set minimal gtags / GNU GLOBAL version to 6.6.5
>
> Ahmed S. Darwish <darwi@linutronix.de>
> scripts/tags.sh: Resolve gtags empty index generation
>
> Krister Johansen <kjlx@templeofstupid.com>
> perf symbols: Symbol lookup with kcore can fail if multiple segments match stext
>
> Finn Thain <fthain@linux-m68k.org>
> nubus: Partially revert proc_create_single_data() conversion
>
> Linus Torvalds <torvalds@linux-foundation.org>
> execve: always mark stack as growing down during early stack setup
>
> Mario Limonciello <mario.limonciello@amd.com>
> PCI/ACPI: Call _REG when transitioning D-states
>
> Bjorn Helgaas <bhelgaas@google.com>
> PCI/ACPI: Validate acpi_pci_set_power_state() parameter
>
> Aric Cyr <aric.cyr@amd.com>
> drm/amd/display: Do not update DRR while BW optimizations pending
>
> Alvin Lee <Alvin.Lee2@amd.com>
> drm/amd/display: Remove optimization for VRR updates
>
> Max Filippov <jcmvbkbc@gmail.com>
> xtensa: fix lock_mm_and_find_vma in case VMA not found
>
>
> -------------
>
> Diffstat:
>
> Documentation/process/changes.rst | 7 +++++
> Makefile | 4 +--
> drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 4 +++
> drivers/gpu/drm/amd/display/dc/core/dc.c | 50 +++++++++++++++++-------------
> drivers/nubus/proc.c | 22 ++++++++++---
> drivers/pci/pci-acpi.c | 53 ++++++++++++++++++++++++--------
> include/linux/mm.h | 4 ++-
> mm/memory.c | 4 +++
> mm/nommu.c | 7 ++++-
> scripts/tags.sh | 9 +++++-
> tools/perf/util/symbol.c | 17 ++++++++--
> 11 files changed, 135 insertions(+), 46 deletions(-)
>
>
On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 6.1.38 release.
> > There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
> > and the diffstat can be found below.
> >
> > thanks,
> >
> > greg k-h
> >
> > -------------
> > Pseudo-Shortlog of commits:
> >
> > Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Linux 6.1.38-rc2
> >
> > Linus Torvalds <torvalds@linux-foundation.org>
> > gup: avoid stack expansion warning for known-good case
> >
>
> I am a bit puzzled by this patch. It avoids a warning introduced with
> upstream commit a425ac5365f6 ("gup: add warning if some caller would
> seem to want stack expansion"), or at least it says so, but that patch
> is not in v6.1.y. Why is this patch needed here ?
It isn't, and was dropped for -rc2, right?
thanks,
greg k-h
On 7/5/23 09:06, Greg Kroah-Hartman wrote:
> On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
>> On 7/4/23 01:48, Greg Kroah-Hartman wrote:
>>> This is the start of the stable review cycle for the 6.1.38 release.
>>> There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
>>> and the diffstat can be found below.
>>>
>>> thanks,
>>>
>>> greg k-h
>>>
>>> -------------
>>> Pseudo-Shortlog of commits:
>>>
>>> Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> Linux 6.1.38-rc2
>>>
>>> Linus Torvalds <torvalds@linux-foundation.org>
>>> gup: avoid stack expansion warning for known-good case
>>>
>>
>> I am a bit puzzled by this patch. It avoids a warning introduced with
>> upstream commit a425ac5365f6 ("gup: add warning if some caller would
>> seem to want stack expansion"), or at least it says so, but that patch
>> is not in v6.1.y. Why is this patch needed here ?
>
> It isn't, and was dropped for -rc2, right?
>
The above is from the -rc2 log so, no, it was not dropped. I checked in the
repository to be sure. It is also in v6.3.12-rc2 and v6.4.2-rc2, but there
it makes sense because a425ac5365f6 was applied/backported to those branches.
Thanks,
Guenter
On Wed, Jul 05, 2023 at 09:13:58AM -0700, Guenter Roeck wrote:
> On 7/5/23 09:06, Greg Kroah-Hartman wrote:
> > On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> > > On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.38 release.
> > > > There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
> > > > and the diffstat can be found below.
> > > >
> > > > thanks,
> > > >
> > > > greg k-h
> > > >
> > > > -------------
> > > > Pseudo-Shortlog of commits:
> > > >
> > > > Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > Linux 6.1.38-rc2
> > > >
> > > > Linus Torvalds <torvalds@linux-foundation.org>
> > > > gup: avoid stack expansion warning for known-good case
> > > >
> > >
> > > I am a bit puzzled by this patch. It avoids a warning introduced with
> > > upstream commit a425ac5365f6 ("gup: add warning if some caller would
> > > seem to want stack expansion"), or at least it says so, but that patch
> > > is not in v6.1.y. Why is this patch needed here ?
> >
> > It isn't, and was dropped for -rc2, right?
> >
>
> The above is from the -rc2 log so, no, it was not dropped. I checked in the
> repository to be sure. It is also in v6.3.12-rc2 and v6.4.2-rc2, but there
> it makes sense because a425ac5365f6 was applied/backported to those branches.
Ah, I must have dropped it right after the -rc2 announcement, it's been
a long week already:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=a5847f7c495fdc9c0a7b63703237f2891a6b6ed1
but be sure, it's gone from all branches now.
thanks,
greg k-h
On Wed, Jul 05, 2023 at 05:25:24PM +0100, Greg Kroah-Hartman wrote:
> On Wed, Jul 05, 2023 at 09:13:58AM -0700, Guenter Roeck wrote:
> > On 7/5/23 09:06, Greg Kroah-Hartman wrote:
> > > On Wed, Jul 05, 2023 at 07:23:30AM -0700, Guenter Roeck wrote:
> > > > On 7/4/23 01:48, Greg Kroah-Hartman wrote:
> > > > > This is the start of the stable review cycle for the 6.1.38 release.
> > > > > There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
> > > > > and the diffstat can be found below.
> > > > >
> > > > > thanks,
> > > > >
> > > > > greg k-h
> > > > >
> > > > > -------------
> > > > > Pseudo-Shortlog of commits:
> > > > >
> > > > > Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > > > > Linux 6.1.38-rc2
> > > > >
> > > > > Linus Torvalds <torvalds@linux-foundation.org>
> > > > > gup: avoid stack expansion warning for known-good case
> > > > >
> > > >
> > > > I am a bit puzzled by this patch. It avoids a warning introduced with
> > > > upstream commit a425ac5365f6 ("gup: add warning if some caller would
> > > > seem to want stack expansion"), or at least it says so, but that patch
> > > > is not in v6.1.y. Why is this patch needed here ?
> > >
> > > It isn't, and was dropped for -rc2, right?
> > >
> >
> > The above is from the -rc2 log so, no, it was not dropped. I checked in the
> > repository to be sure. It is also in v6.3.12-rc2 and v6.4.2-rc2, but there
> > it makes sense because a425ac5365f6 was applied/backported to those branches.
>
> Ah, I must have dropped it right after the -rc2 announcement, it's been
> a long week already:
> https://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git/commit/?id=a5847f7c495fdc9c0a7b63703237f2891a6b6ed1
>
> but be sure, it's gone from all branches now.
>
Great, thanks!
Guenter
* Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote: > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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, 06 Jul 2023 08:46:01 +0000. > Anything received after that time might be too late. Hi Greg 6.1.38-rc2 compiles, boots and runs here on x86_64 (AMD Ryzen 5 PRO 4650G, Slackware64-15.0) Tested-by: Markus Reichelt <lkt+2023@mareichelt.com>
On Tue, Jul 04, 2023 at 09:48:32AM +0100, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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, 06 Jul 2023 08:46:01 +0000. > Anything received after that time might be too late. > Build results: total: 157 pass: 157 fail: 0 Qemu test results: total: 519 pass: 519 fail: 0 Tested-by: Guenter Roeck <linux@roeck-us.net> Guenter
Hello Greg, > From: Greg Kroah-Hartman <gregkh@linuxfoundation.org> > Sent: Tuesday, July 4, 2023 9:49 AM > > This is the start of the stable review cycle for the 6.1.38 release. > There are 13 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, 06 Jul 2023 08:46:01 +0000. > Anything received after that time might be too late. Thank you for the release! CIP configurations built and booted okay with Linux 6.1.38-rc2 (185484ee4c4f): https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines/920271897/ https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/commits/linux-6.1.y Tested-by: Chris Paterson (CIP) <chris.paterson2@renesas.com> Kind regards, Chris
On Tue, 04 Jul 2023 09:48:32 +0100, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 6.1.38 release.
> There are 13 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, 06 Jul 2023 08:46:01 +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.38-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.1.y
> and the diffstat can be found below.
>
> thanks,
>
> greg k-h
All tests passing for Tegra ...
Test results for stable-v6.1:
7 builds: 7 pass, 0 fail
22 boots: 22 pass, 0 fail
104 tests: 104 pass, 0 fail
Linux version: 6.1.38-rc2-g185484ee4c4f
Boards tested: tegra124-jetson-tk1, tegra186-p2771-0000,
tegra194-p2972-0000, tegra194-p3509-0000+p3668-0000,
tegra210-p2371-2180, tegra210-p3450-0000,
tegra30-cardhu-a04
Tested-by: Jon Hunter <jonathanh@nvidia.com>
Jon
© 2016 - 2026 Red Hat, Inc.