linux-kernel - Re: [PATCH RFC V1 net-next 3/4] net: Let the active time stamping layer be selectable.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 05 Apr 2022 11:01:11 +0200
From:   Kurt Kanzenbach <kurt@...utronix.de>
To:     Michael Walle <michael@...le.cc>, Andrew Lunn <andrew@...n.ch>
Cc:     richardcochran@...il.com, davem@...emloft.net,
        grygorii.strashko@...com, kuba@...nel.org,
        linux-kernel@...r.kernel.org, linux@...linux.org.uk,
        mlichvar@...hat.com, netdev@...r.kernel.org,
        qiangqing.zhang@....com, vladimir.oltean@....com
Subject: Re: [PATCH RFC V1 net-next 3/4] net: Let the active time stamping
 layer be selectable.

On Mon Apr 04 2022, Michael Walle wrote:
> That would make sense. I guess what bothers me with the current
> mechanism is that a feature addition to the PHY in the *future* (the
> timestamping support) might break a board - or at least changes the
> behavior by suddenly using PHY timestamping.

Currently PHY timestamping is hidden behind a configuration option
(NETWORK_PHY_TIMESTAMPING). By disabling this option the default
behavior should stay at MAC timestamping even if additional features
are added on top of the PHY drivers at later stages. Or not?

Thanks,
Kurt

Download attachment "signature.asc" of type "application/pgp-signature" (862 bytes)