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: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Thu, 11 Aug 2022 04:05:03 +0200
From:   Andrew Lunn <>
To:     Richard Cochran <>
Cc:     Csókás Bence <>,, Fugang Duan <>
Subject: Re: [PATCH] fec: Restart PPS after link state change

On Wed, Aug 10, 2022 at 06:37:19PM -0700, Richard Cochran wrote:
> On Thu, Aug 11, 2022 at 02:05:39AM +0200, Andrew Lunn wrote:
> > > Yes. We use PPS to synchronize devices on a common backplane. We use PTP to
> > > sync this PPS to a master clock. But if PTP sync drops out, we wouldn't want
> > > the backplane-level synchronization to fail. The PPS needs to stay on as
> > > long as userspace *explicitly* disables it, regardless of what happens to
> > > the link.
> > 
> > We need the PTP Maintainers view on that. I don't know if that is
> > normal or not.
> IMO the least surprising behavior is that once enabled, a feature
> stays on until explicitly disabled.

O.K, thanks for the response.

Your answer is a bit surprising to me. To me, an interface which is
administratively down is completely inactive. The action to down it
should disable everything.

So your answer also implies PPS can be used before the interface is
set administratively up?


Powered by blists - more mailing lists