Netdev List
 help / color / mirror / Atom feed
From: Grzegorz Nitka <grzegorz.nitka@intel.com>
To: netdev@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, intel-wired-lan@lists.osuosl.org,
	poros@redhat.com, richardcochran@gmail.com,
	andrew+netdev@lunn.ch, przemyslaw.kitszel@intel.com,
	anthony.l.nguyen@intel.com, Prathosh.Satish@microchip.com,
	ivecera@redhat.com, jiri@resnulli.us,
	arkadiusz.kubalewski@intel.com, vadim.fedorenko@linux.dev,
	donald.hunter@gmail.com, horms@kernel.org, pabeni@redhat.com,
	kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
	Grzegorz Nitka <grzegorz.nitka@intel.com>
Subject: [PATCH v14 net-next 04/13] dpll: send delete notification before unregister in on-pin rollback
Date: Sun,  7 Jun 2026 20:30:36 +0200	[thread overview]
Message-ID: <20260607183045.1213735-5-grzegorz.nitka@intel.com> (raw)
In-Reply-To: <20260607183045.1213735-1-grzegorz.nitka@intel.com>

The rollback path in dpll_pin_on_pin_register() called
__dpll_pin_unregister() before dpll_pin_delete_ntf(). When the
unregister dropped the pin's last DPLL reference it cleared the
DPLL_REGISTERED mark in dpll_pin_xa, so the subsequent
dpll_pin_event_send() failed dpll_pin_available() and aborted with
-ENODEV. As a result userspace was never notified of the rollback
deletion and remained out of sync with the kernel.

Send the delete notification first, matching the order used by
dpll_pin_unregister() and dpll_pin_on_pin_unregister().

Fixes: 9d71b54b65b1 ("dpll: netlink: Add DPLL framework base functions")
Signed-off-by: Grzegorz Nitka <grzegorz.nitka@intel.com>
---
 drivers/dpll/dpll_core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/dpll/dpll_core.c b/drivers/dpll/dpll_core.c
index cea7e2be2cbc..80195f3a84f3 100644
--- a/drivers/dpll/dpll_core.c
+++ b/drivers/dpll/dpll_core.c
@@ -1007,9 +1007,9 @@ int dpll_pin_on_pin_register(struct dpll_pin *parent, struct dpll_pin *pin,
 dpll_unregister:
 	xa_for_each(&parent->dpll_refs, i, ref)
 		if (i < stop) {
+			dpll_pin_delete_ntf(pin);
 			__dpll_pin_unregister(ref->dpll, pin, ops, priv,
 					      parent);
-			dpll_pin_delete_ntf(pin);
 		}
 	dpll_xa_ref_pin_del(&pin->parent_refs, parent, ops, priv, pin);
 unlock:
-- 
2.39.3


  parent reply	other threads:[~2026-06-07 18:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-07 18:30 [PATCH v14 net-next 00/13] dpll/ice: Add generic DPLL type and full TX reference clock control for E825 Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 01/13] dpll: add generic DPLL type Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 02/13] dpll: allow registering FW-identified pin with a different DPLL Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 03/13] dpll: fix stale iteration in dpll_pin_on_pin_unregister() Grzegorz Nitka
2026-06-08 16:51   ` Kubalewski, Arkadiusz
2026-06-09  6:50     ` Nitka, Grzegorz
2026-06-11  8:50   ` Paolo Abeni
2026-06-11 10:01     ` Nitka, Grzegorz
2026-06-11 14:41       ` Paolo Abeni
2026-06-11 17:41         ` Jakub Kicinski
2026-06-11 18:36           ` Nitka, Grzegorz
2026-06-07 18:30 ` Grzegorz Nitka [this message]
2026-06-08 16:45   ` [PATCH v14 net-next 04/13] dpll: send delete notification before unregister in on-pin rollback Kubalewski, Arkadiusz
2026-06-09  7:09     ` Nitka, Grzegorz
2026-06-10 19:42       ` Nitka, Grzegorz
2026-06-10 21:27         ` Nitka, Grzegorz
2026-06-07 18:30 ` [PATCH v14 net-next 05/13] dpll: emit per-dpll delete notifications in dpll_pin_on_pin_unregister() Grzegorz Nitka
2026-06-08 16:40   ` Kubalewski, Arkadiusz
2026-06-07 18:30 ` [PATCH v14 net-next 06/13] dpll: guard sync-pair removal on full pin unregister Grzegorz Nitka
2026-06-08 16:38   ` Kubalewski, Arkadiusz
2026-06-07 18:30 ` [PATCH v14 net-next 07/13] dpll: balance create/delete notifications in __dpll_pin_(un)register Grzegorz Nitka
2026-06-08 16:35   ` Kubalewski, Arkadiusz
2026-06-07 18:30 ` [PATCH v14 net-next 08/13] dpll: extend pin notifier with notification source ID Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 09/13] dpll: allow fwnode pins to attempt state change without capability bit Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 10/13] ice: introduce TXC DPLL device and TX ref clock pin framework for E825 Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 11/13] ice: implement CPI support for E825C Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 12/13] ice: add Tx reference clock index handling to AN restart command Grzegorz Nitka
2026-06-07 18:30 ` [PATCH v14 net-next 13/13] ice: implement E825 TX ref clock control and TXC hardware sync status Grzegorz Nitka

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=20260607183045.1213735-5-grzegorz.nitka@intel.com \
    --to=grzegorz.nitka@intel.com \
    --cc=Prathosh.Satish@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=ivecera@redhat.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=poros@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=richardcochran@gmail.com \
    --cc=vadim.fedorenko@linux.dev \
    /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