From: Sanghyun Park <sanghyun.park.cnu@gmail.com>
To: fw@strlen.de
Cc: Sanghyun Park <sanghyun.park.cnu@gmail.com>,
steffen.klassert@secunet.com, herbert@gondor.apana.org.au,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfrm: policy: Fix use-after-free on inexact bin in xfrm_policy_bysel_ctx()
Date: Tue, 2 Jun 2026 15:23:46 +0900 [thread overview]
Message-ID: <20260602062348.1995083-1-sanghyun.park.cnu@gmail.com> (raw)
In-Reply-To: <ahmGAgwpJx0OFKe7@strlen.de>
Thank you for the review. I apologize for the several mistakes I've made.
> There is no such commit, neither ID nor subject.
You are right, I apologize. The correct one is:
Fixes: 6be3b0db6db8 ("xfrm: policy: add inexact policy search tree infrastructure")
> Looks like this patch is whitespace-damaged.
Will use git send-email for v2.
> Could you also say in changelog why you added the 3rd criterion?
> Became (bin && ret && delete).
The extra ret check was only meant to avoid pruning the inexact bin when
the lookup did not actually find and unlink a policy. Pruning in that
case is harmless but unnecessary. It is sort of an optimization fix
rather than security-related one.
After looking at it again, I will drop the extra ret check in v2 and keep
the original condition as bin && delete to make the patch minimal.
I will send a v2 with these fixes in a concise version.
Thank you,
Sanghyun
prev parent reply other threads:[~2026-06-02 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 8:06 Sanghyun Park
2026-05-29 12:26 ` Florian Westphal
2026-06-02 6:23 ` Sanghyun Park [this message]
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=20260602062348.1995083-1-sanghyun.park.cnu@gmail.com \
--to=sanghyun.park.cnu@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=steffen.klassert@secunet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®