Netdev List
 help / color / mirror / Atom feed
From: luoxuanqiang <xuanqiang.luo@linux.dev>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: linux-renesas-soc@vger.kernel.org, netdev@vger.kernel.org,
	paul@pbarker.dev, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
	richardcochran@gmail.com, masaru.nagai.vx@renesas.com,
	sergei.shtylyov@cogentembedded.com,
	Xuanqiang Luo <luoxuanqiang@kylinos.cn>,
	stable@vger.kernel.org
Subject: Re: [PATCH net v1] net: ravb: fix use-after-free in ravb_get_ts_info
Date: Sun, 2 Aug 2026 17:21:53 +0800	[thread overview]
Message-ID: <ea65462f-deb1-4088-bec6-ec52a18996a7@linux.dev> (raw)
In-Reply-To: <20260801093532.GC3091634@ragnatech.se>


在 2026/8/1 17:35, Niklas Söderlund 写道:
> Ahh, yes you are correct. Clearing priv->ptp.clock after the clock have
> been unregistered, and checking it before use, is not introduced in that
> series. And as you do here that should be fixed.
>
> I have no strong opinion if this is done before or after the PTP rework
> series. If you want to send a v2 and have it go in before I will rebase
> on top of your work. Else adding this on-top of the rework is trivial as
> the locations where it needs to be checked are abstracted out to
> callbacks.
>
Hello Niklas,

Thanks for confirming. I have sent v2 separately.

Best regards,
Xuanqiang


      reply	other threads:[~2026-08-02  9:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-31  6:32 [PATCH net v1] net: ravb: fix use-after-free in ravb_get_ts_info xuanqiang.luo
2026-07-31 18:25 ` Niklas Söderlund
2026-08-01  1:56   ` luoxuanqiang
2026-08-01  9:35     ` Niklas Söderlund
2026-08-02  9:21       ` luoxuanqiang [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=ea65462f-deb1-4088-bec6-ec52a18996a7@linux.dev \
    --to=xuanqiang.luo@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=kuba@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=luoxuanqiang@kylinos.cn \
    --cc=masaru.nagai.vx@renesas.com \
    --cc=netdev@vger.kernel.org \
    --cc=niklas.soderlund@ragnatech.se \
    --cc=pabeni@redhat.com \
    --cc=paul@pbarker.dev \
    --cc=richardcochran@gmail.com \
    --cc=sergei.shtylyov@cogentembedded.com \
    --cc=stable@vger.kernel.org \
    /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