6.1.38-rc2 review

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

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.

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.

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

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 <[email protected]>

     Linux 6.1.38-rc2

Linus Torvalds <[email protected]>
gup: avoid stack expansion warning for known-good case

Rodrigo Siqueira <[email protected]>
drm/amd/display: Ensure vmin and vmax adjust for DCE

Bas Nieuwenhuizen <[email protected]>
drm/amdgpu: Validate VM ioctl flags.

Ahmed S. Darwish <[email protected]>
docs: Set minimal gtags / GNU GLOBAL version to 6.6.5

Ahmed S. Darwish <[email protected]>
scripts/tags.sh: Resolve gtags empty index generation

Krister Johansen <[email protected]>
perf symbols: Symbol lookup with kcore can fail if multiple segments match stext

Finn Thain <[email protected]>
nubus: Partially revert proc_create_single_data() conversion

Linus Torvalds <[email protected]>
execve: always mark stack as growing down during early stack setup

Mario Limonciello <[email protected]>
PCI/ACPI: Call _REG when transitioning D-states

Bjorn Helgaas <[email protected]>
PCI/ACPI: Validate acpi_pci_set_power_state() parameter

Aric Cyr <[email protected]>
drm/amd/display: Do not update DRR while BW optimizations pending

Alvin Lee <[email protected]>
drm/amd/display: Remove optimization for VRR updates

Max Filippov <[email protected]>
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(-)

Quoted 24 lines · Greg Kroah-Hartman

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 <[email protected]>

     Linux 6.1.38-rc2

Quoted 3 lines

Linus Torvalds <[email protected]>
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 ?

Quoted 29 lines · Guenter Roeck

Quoted 27 lines · Greg Kroah-Hartman

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 <[email protected]>

      Linux 6.1.38-rc2

Linus Torvalds <[email protected]>
gup: avoid stack expansion warning for known-good case

Quoted 4 lines

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?

Quoted 35 lines · Greg Kroah-Hartman

Quoted 33 lines · Guenter Roeck

Quoted 18 lines · Greg Kroah-Hartman

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

Quoted 9 lines

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <[email protected]>

      Linux 6.1.38-rc2

Linus Torvalds <[email protected]>
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 ?

Quoted 2 lines

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.

Quoted 36 lines · Guenter Roeck

Quoted 35 lines · Greg Kroah-Hartman

Quoted 33 lines · Guenter Roeck

Quoted 18 lines · Greg Kroah-Hartman

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

Quoted 9 lines

-------------
Pseudo-Shortlog of commits:

Greg Kroah-Hartman <[email protected]>

      Linux 6.1.38-rc2

Linus Torvalds <[email protected]>
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 ?

Quoted 6 lines

Quoted 2 lines

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.

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.

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.

From: Greg Kroah-Hartman <[email protected]>
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.

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