From: patchwork-bot+netdevbpf@kernel.org
To: Wei Fang (OSS) <wei.fang@oss.nxp.com>
Cc: xiaoning.wang@nxp.com, richardcochran@gmail.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, Frank.Li@nxp.com,
wei.fang@nxp.com, imx@lists.linux.dev, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] ptp: netc: skip PEROUT disable if channel is not enabled
Date: Mon, 17 Aug 2026 20:00:16 +0000 [thread overview]
Message-ID: <178699681614.1714062.8810905823945131454.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260811083614.3589967-1-wei.fang@oss.nxp.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 11 Aug 2026 16:36:14 +0800 you wrote:
> From: Wei Fang <wei.fang@nxp.com>
>
> When userspace calls ioctl(PTP_PEROUT_REQUEST) with period = 0 to disable
> a PEROUT channel that is not enabled, the driver incorrectly enters the
> disable path. Since the channel's struct netc_pp was previously zeroed,
> pp->alarm_id evaluates to 0, causing priv->fs_alarm_bitmap &= ~BIT(0) to
> silently revoke the alarm 0 allocation from whichever channel is actively
> using it. This can cause two channels conflict over the same hardware
> alarm configuration and corrupt their periodic output signals.
>
> [...]
Here is the summary with links:
- [net] ptp: netc: skip PEROUT disable if channel is not enabled
https://git.kernel.org/netdev/net/c/273480bb836e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-17 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 8:36 [PATCH net] ptp: netc: skip PEROUT disable if channel is not enabled wei.fang
2026-08-17 20:00 ` 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=178699681614.1714062.8810905823945131454.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=wei.fang@nxp.com \
--cc=wei.fang@oss.nxp.com \
--cc=xiaoning.wang@nxp.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.