From: sashiko-bot@kernel.org
To: "Ivan Vecera" <ivecera@redhat.com>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [PATCH net-next 04/10] dpll: take domain locks around driver callbacks
Date: Sat, 07 Nov 2026 12:11:35 +0000 [thread overview]
Message-ID: <sashiko-outbox-202876@kernel.org> (raw)
In-Reply-To: <20261106121005.1327603-5-ivecera@redhat.com>
Thank you for your contribution! Sashiko AI review found no new issues
in this patch, but noticed 1 related pre-existing issue it does not
introduce:
- [Medium] dpll: broken NLM_F_ECHO in dpll_pin_event_send() [1]
--
commit 1d6bef1472d6edb1fb63ca2b725c77cbbc70a8da
Author: Ivan Vecera <ivecera@redhat.com>
dpll: take domain locks around driver callbacks
This commit acquires the object's domain lock around driver callbacks in
netlink requests, dumps, and notifications.
> diff --git a/drivers/dpll/dpll_netlink.c b/drivers/dpll/dpll_netlink.c
> index e5380d95f238b..1b4e3a0166a74 100644
> --- a/drivers/dpll/dpll_netlink.c
> +++ b/drivers/dpll/dpll_netlink.c
[ ... ]
> @@ -941,27 +955,39 @@ dpll_pin_event_send(enum dpll_cmd event, struct dpll_pin *pin)
>
> int dpll_pin_create_ntf(struct dpll_pin *pin, u64 src_clock_id)
> {
> + int ret;
> +
> + mutex_lock(&pin->domain->lock);
> dpll_pin_notify(pin, src_clock_id, DPLL_PIN_CREATED);
> - return dpll_pin_event_send(DPLL_CMD_PIN_CREATE_NTF, pin);
> + ret = dpll_pin_event_send(DPLL_CMD_PIN_CREATE_NTF, pin);
> + mutex_unlock(&pin->domain->lock);
> +
> + return ret;
> }
[Severity: Medium]
This problem wasn't introduced by this patch, but does dpll_pin_event_send()
break NLM_F_ECHO on pin SET requests [1]?
drivers/dpll/dpll_netlink.c:dpll_pin_event_send() {
...
hdr = genlmsg_put(msg, 0, 0, &dpll_nl_family, 0, event);
...
genlmsg_end(msg, hdr);
genlmsg_multicast(&dpll_nl_family, msg, 0, 0, GFP_KERNEL);
...
}
When a user-space SET request triggers a pin change notification,
dpll_pin_event_send() is called without the request's genl_info context.
Passing a portid of 0 to genlmsg_put() and calling genlmsg_multicast()
instead of genl_notify() drops the originating socket information, so user
space never receives the requested NLM_F_ECHO notification.
[1] https://sashiko.dev/#/bug/linux-14884b2c-eeea-47fd-87fe-40bc535d32cc
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106121005.1327603-1-ivecera@redhat.com?part=4
next prev parent reply other threads:[~2026-11-07 12:11 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 12:09 [PATCH net-next 00/10] dpll: do not serialize driver callbacks under global dpll_lock Ivan Vecera
2026-11-06 12:09 ` [PATCH net-next 01/10] ice: dpll: notify TSPLL lock status from the periodic work only Ivan Vecera
2026-11-10 12:20 ` Petr Oros
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 10:55 ` Ivan Vecera
2026-11-06 12:09 ` [PATCH net-next 02/10] ice: dpll: serialize changes of the SyncE CGU registers Ivan Vecera
2026-11-07 12:11 ` sashiko-bot
2026-11-10 9:45 ` Ivan Vecera
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 10:56 ` Ivan Vecera
2026-11-06 12:09 ` [PATCH net-next 03/10] dpll: add domain object Ivan Vecera
2026-11-10 12:23 ` Petr Oros
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 10:58 ` Ivan Vecera
2026-11-06 12:09 ` [PATCH net-next 04/10] dpll: take domain locks around driver callbacks Ivan Vecera
2026-11-07 12:11 ` sashiko-bot [this message]
2026-11-09 14:27 ` Ivan Vecera
2026-11-10 12:23 ` Petr Oros
2026-11-06 12:10 ` [PATCH net-next 05/10] dpll: convert dpll_lock to rwsem Ivan Vecera
2026-11-10 12:24 ` Petr Oros
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 11:01 ` Ivan Vecera
2026-11-06 12:10 ` [PATCH net-next 06/10] dpll: add KUnit tests for core locking Ivan Vecera
2026-11-07 12:11 ` sashiko-bot
2026-11-10 9:45 ` Ivan Vecera
2026-11-10 12:24 ` Petr Oros
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 10:53 ` Ivan Vecera
2026-11-06 12:10 ` [PATCH net-next 07/10] dpll: reject measured_freq_get for foreign and on-pin registrations Ivan Vecera
2026-11-10 12:24 ` Petr Oros
2026-11-06 12:10 ` [PATCH net-next 08/10] dpll: zl3073x: update locking comments Ivan Vecera
2026-11-10 12:24 ` Petr Oros
2026-11-06 12:10 ` [PATCH net-next 09/10] ice: dpll: " Ivan Vecera
2026-11-10 15:31 ` Petr Oros
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 11:03 ` Ivan Vecera
2026-11-06 12:10 ` [PATCH net-next 10/10] dpll: document locking rules Ivan Vecera
2026-11-10 12:25 ` Petr Oros
2026-11-10 17:53 ` netdev-bot+sashiko
2026-11-11 11:07 ` Ivan Vecera
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=sashiko-outbox-202876@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=sashiko-reviews@lists.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