From: Gerhard Engleder <gerhard@engleder-embedded.com>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
Richard Cochran <richardcochran@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net: tsnep: fix timestamping with a stacked DSA driver
Date: Fri, 16 May 2025 22:12:18 +0200 [thread overview]
Message-ID: <6eb6d8fc-3d3d-491f-9b57-a859d39dabb4@engleder-embedded.com> (raw)
In-Reply-To: <20250513200645.vxuevzz3hdtd56sc@skbuf>
On 13.05.25 22:06, Vladimir Oltean wrote:
> On Tue, May 13, 2025 at 08:34:17PM +0200, Gerhard Engleder wrote:
>> On 12.05.25 23:09, Vladimir Oltean wrote:
>>> On Mon, May 12, 2025 at 10:07:52PM +0200, Gerhard Engleder wrote:
>>>> On 12.05.25 15:24, Vladimir Oltean wrote:
>>>>> This driver seems susceptible to a form of the bug explained in commit
>>>>> c26a2c2ddc01 ("gianfar: Fix TX timestamping with a stacked DSA driver")
>>>>> and in Documentation/networking/timestamping.rst section "Other caveats
>>>>> for MAC drivers", specifically it timestamps any skb which has
>>>>> SKBTX_HW_TSTAMP, and does not consider adapter->hwtstamp_config.tx_type.
>>>>
>>>> Is it necessary in general to check adapter->hwtstamp_config.tx_type for
>>>> HWTSTAMP_TX_ON or only to fix this bug?
>>>
>>> I'll start with the problem description and work my way towards an answer.
>>
>> (...)
>>
>>>> I can take over this patch and test it when I understand more clearly
>>>> what needs to be done.
>>>>
>>>> Gerhard
>>>
>>> It would be great if you could take over this patch. After the net ->
>>> net-next merge I can then submit the ndo_hwtstamp_get()/ndo_hwtstamp_set()
>>> conversion patch for tsnep, the one which initially prompted me to look
>>> into how this driver uses the provided configuration.
>>
>> I will post a new patch version in the next days. You can send me the
>> ndo_hwtstamp_get()/ndo_hwtstamp_set() conversion patch for testing. I
>> have it on my list, but nothing done so far, so I feel responsible
>> for that too.
>>
>> Gerhard
>
> See attached. It applies on top of this patch ("do_tstamp" is present in
> the context).
I tested the ndo_hwtstamp_get()/ndo_hwtstamp_set() conversion patch
successfully on top of the timestamping fix patch. Thank you for the
patch!
Reviewed-by: Gerhard Engleder <gerhard@engleder-embedded.com>
Tested-by: Gerhard Engleder <gerhard@engleder-embedded.com>
prev parent reply other threads:[~2025-05-16 21:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 13:24 [PATCH net] net: tsnep: fix timestamping with a stacked DSA driver Vladimir Oltean
2025-05-12 20:07 ` Gerhard Engleder
2025-05-12 21:09 ` Vladimir Oltean
2025-05-13 18:34 ` Gerhard Engleder
2025-05-13 20:06 ` Vladimir Oltean
2025-05-16 20:12 ` Gerhard Engleder [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=6eb6d8fc-3d3d-491f-9b57-a859d39dabb4@engleder-embedded.com \
--to=gerhard@engleder-embedded.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vadim.fedorenko@linux.dev \
--cc=vladimir.oltean@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox