Please apply 736b380e28d0 and eca856950f7c down to 6.1.y

Please apply 736b380e28d0 and eca856950f7c down to 6.1.y

[Wongi Lee]

Hi,

Could the following upstream commits be queued for the active stable
trees?

  commit 736b380e28d0480c7bc3e022f1950f31fe53a7c5
  ("ipv6: account for fraggap on the paged allocation path")

  commit eca856950f7cb1a221e02b99d758409f2c5cec42
  ("ipv4: account for fraggap on the paged allocation path")

These fix incorrect fraggap accounting in the paged allocation path.
This can write past skb->end into skb_shared_info when MSG_MORE is 
used together with MSG_SPLICE_PAGES.

Please apply these to 6.1.y, 6.6.y, 6.12.y, 6.18.y, 7.0.y and 7.1.y.

I checked that the IPv6 upstream commit cherry-picks cleanly onto the
following stable branches:

linux-7.0.y
linux-6.18.y
linux-6.12.y
linux-6.6.y
linux-6.1.y

I checked that the IPv4 upstream commit cherry-picks cleanly onto the
following stable branches:

linux-7.0.y
linux-6.18.y

The IPv4 commit needs a small context-only backport for:

linux-6.12.y
linux-6.6.y
linux-6.1.y

Thanks,
Wongi

Re: Please apply 736b380e28d0 and eca856950f7c down to 6.1.y

[Greg Kroah-Hartman]

On Wed, Jun 24, 2026 at 05:14:38PM +0900, Wongi Lee wrote:
> Hi,
> 
> Could the following upstream commits be queued for the active stable
> trees?
> 
>   commit 736b380e28d0480c7bc3e022f1950f31fe53a7c5
>   ("ipv6: account for fraggap on the paged allocation path")

I do not see that commit id in Linus's tree, are you sure it is correct?

>   commit eca856950f7cb1a221e02b99d758409f2c5cec42
>   ("ipv4: account for fraggap on the paged allocation path")

Same here, no id of that one in Linus's tree that I can see.

thanks,

greg k-h