All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Avi Weiss <thnkslprpt@gmail.com>
Cc: richardcochran@gmail.com, netdev@vger.kernel.org,
	horms@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	arnd@arndb.de, john.stultz@linaro.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] ptp: Report clock removal to poll waiters
Date: Thu, 12 Nov 2026 16:40:04 +0000	[thread overview]
Message-ID: <179450160478.52552.8310562765355263034.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261108064928.1931917-2-thnkslprpt@gmail.com>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Sun,  8 Nov 2026 08:49:29 +0200 you wrote:
> ptp_clock_unregister() marks the clock defunct and wakes timestamp
> waiters before posix_clock_unregister() marks it a zombie. A poll
> waiter can consume the removal wakeup while the event queue is empty,
> return no events, and remain blocked until timeout after device
> removal.
> 
> Using netdevsim's mock PTP clock in an x86_64 QEMU/KVM guest,
> the unpatched kernel missed all eight epoll removal notifications.
> The four poll waits returned POLLERR only at timeout. With this
> patch, all 12 poll and epoll waits reported clock removal promptly.
> 
> [...]

Here is the summary with links:
  - [net,v2] ptp: Report clock removal to poll waiters
    https://git.kernel.org/netdev/net-next/c/92be25a17ed6

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-11-12 16:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-08  6:49 [PATCH net v2] ptp: Report clock removal to poll waiters Avi Weiss
2026-11-08  6:52 ` netdev-bot+sinfo
2026-11-09  6:50 ` netdev-bot+sashiko
2026-11-12 16:40 ` patchwork-bot+netdevbpf [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=179450160478.52552.8310562765355263034.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=john.stultz@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=richardcochran@gmail.com \
    --cc=thnkslprpt@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.