netdev - Re: PTP_PEROUT_REQUEST and clock stepping

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20140910172619.GB5944@localhost.localdomain>
Date:	Wed, 10 Sep 2014 19:26:20 +0200
From:	Richard Cochran <richardcochran@...il.com>
To:	Daniel Glöckner <dg@...ix.com>
Cc:	netdev@...r.kernel.org
Subject: Re: PTP_PEROUT_REQUEST and clock stepping

On Wed, Sep 10, 2014 at 06:16:37PM +0200, Daniel Glöckner wrote:
> Hi,
> I was wondering how periodic output is supposed to behave if the clock
> is stepped from a time after ptp_perout_request.start to a time before
> ptp_perout_request.start.

I would say the result is undefined.

User space should first stop the periodic output, then reprogram the
clock, then restart the periodic output. Anything else makes no sense
at all.

Thanks,
Richard
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html