Re: [PATCH 6.1 00/13] 6.1.38-rc2 review

Guenter Roeck
2023-07-05T16:14:06Z

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