All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hyunwoo Kim <imv4bel@gmail.com>
To: Sultan Alsawaf <sultan@kerneltoast.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, horms@kernel.org, kerneljasonxing@gmail.com,
	kuniyu@google.com, mhal@rbox.co, jiayuan.chen@linux.dev,
	steffen.klassert@secunet.com, ben@decadent.org.uk,
	herbert@gondor.apana.org.au, dsahern@kernel.org,
	sd@queasysnail.net, netdev@vger.kernel.org,
	stable@vger.kernel.org, imv4bel@gmail.com
Subject: Re: [PATCH net v4] net: skbuff: propagate shared-frag marker through frag-transfer helpers
Date: Sat, 16 May 2026 00:11:39 +0900	[thread overview]
Message-ID: <agc3q4sVMIu_0btE@v4bel> (raw)
In-Reply-To: <aga_C6fXL0dZdDzb@v4bel>

On Fri, May 15, 2026 at 03:36:59PM +0900, Hyunwoo Kim wrote:
> On Thu, May 14, 2026 at 11:26:28PM -0700, Sultan Alsawaf wrote:
> > On Fri, May 15, 2026 at 02:55:35PM +0900, Hyunwoo Kim wrote:
> > > Changes in v4:
> > > - Include the tcp_clone_payload() propagation suggested by Sabrina.
> > > - Drop the skb_try_coalesce() change; addressed by commit f84eca581739.
> > > - v3: https://lore.kernel.org/all/agW4vC0r8QOUKtRT@v4bel/
> > > 
> > > Changes in v3:
> > > - Include the skb_gro_receive() audit patch suggested by Sultan
> > > - v2: https://lore.kernel.org/all/agToIEDI4TaTNLRb@v4bel/
> > > 
> > > Changes in v2:
> > > - Also propagate SHARED_FRAG in skb_try_coalesce() and skb_shift()
> > > - v1: https://lore.kernel.org/all/agRfuVOeMI5pbHhY@v4bel/
> > 
> > Hi Hyunwoo,
> > 
> > Per your ask to me to use AI for exploring relevant paths [1], I've attached my
> > findings from a pretty thorough day of hunting for these with Claude.
> > 
> > None of the findings appear to be currently exploitable.
> > 
> > Please let me know if you have any questions, and I hope you find this helpful.
> > 
> > [1] https://lore.kernel.org/all/agWUdie1xBvBu22I@v4bel/
> > 
> > Thanks,
> > Sultan
> 
> Thank you so much. This is a really useful report; I'll take it and dig 
> further from there.
> 
> Thanks again!
> 
> 
> Best regards,
> Hyunwoo Kim

After analyzing the call paths, I also could not find any other user 
page write path triggerable on current mainline.

Unless there are additional review comments, I plan to finalize the 
v4 patch. Thank you.


Best regards,
Hyunwoo Kim

  reply	other threads:[~2026-05-15 15:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-15  5:55 [PATCH net v4] net: skbuff: propagate shared-frag marker through frag-transfer helpers Hyunwoo Kim
2026-05-15  6:07 ` Hyunwoo Kim
2026-05-15  6:26 ` Sultan Alsawaf
2026-05-15  6:36   ` Hyunwoo Kim
2026-05-15 15:11     ` Hyunwoo Kim [this message]
2026-05-15 16:41 ` Aaron Esau
2026-05-15 20:22   ` Hyunwoo Kim
2026-05-15 21:36     ` Hyunwoo Kim
2026-05-16  0:08       ` Jakub Kicinski

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=agc3q4sVMIu_0btE@v4bel \
    --to=imv4bel@gmail.com \
    --cc=ben@decadent.org.uk \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=horms@kernel.org \
    --cc=jiayuan.chen@linux.dev \
    --cc=kerneljasonxing@gmail.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=mhal@rbox.co \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sd@queasysnail.net \
    --cc=stable@vger.kernel.org \
    --cc=steffen.klassert@secunet.com \
    --cc=sultan@kerneltoast.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.