[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1f974f16-c46d-4e9b-b0ed-c15b5d5c45cd@cloudflare.com>
Date: Mon, 20 Oct 2025 15:02:11 -0700
From: Jesse Brandeburg <jbrandeburg@...udflare.com>
To: "Nitka, Grzegorz" <grzegorz.nitka@...el.com>,
Frederick Lawler <fred@...udflare.com>,
"Nguyen, Anthony L" <anthony.l.nguyen@...el.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@...el.com>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
AndrewLunn <andrew+netdev@...n.ch>, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>,
Paolo Abeni <pabeni@...hat.com>,
"kernel-team@...udflare.com" <kernel-team@...udflare.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [Intel-wired-lan] ice: General protection fault in
ptp_clock_index
On 7/31/25 4:01 AM, Nitka, Grzegorz wrote:
>> Hi Intel team, anyone have an idea on this? Looks like maybe removal of
>> device 0 that had originally registered PTP clock isn't handled well?
>>
>
> Hi All,
>
> Thank you for your message. We're looking into this.
> Yes, at first sight it seems to be a race condition hit while removing PF which is PTP
> owner (and responsible for removing PTP clock).
Hi Intel team, any progress on this issue?
BR,
Jesse
Powered by blists - more mailing lists