netdev - Re: What is SOF_TIMESTAMPING_RX

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] [day] [month] [year] [list]

Message-ID: <CALCETrWZ8kBFDMmUAjKrwndLWEo70OQv3rFSTXdLOyMGy-095Q@mail.gmail.com>
Date:	Tue, 4 Mar 2014 09:45:08 -0800
From:	Andy Lutomirski <luto@...capital.net>
To:	Richard Cochran <richardcochran@...il.com>
Cc:	Network Development <netdev@...r.kernel.org>
Subject: Re: What is SOF_TIMESTAMPING_RX_HARDWARE?

On Tue, Mar 4, 2014 at 9:42 AM, Richard Cochran
<richardcochran@...il.com> wrote:
> On Tue, Mar 04, 2014 at 09:21:47AM -0800, Andy Lutomirski wrote:
>>
>> In theory, the driver could stop reporting timestamps if
>> SOF_TIMESTAMPING_RAW_HARDWARE: and SOF_TIMESTAMPING_SYS_HARDWARE
>> aren't set.  I don't see why SOF_TIMESTAMPING_RX_HARDWARE would make
>> any sense in this context.
>
> AFAICT, the intent was that the former are handled by the stack, while
> the latter is handled by the driver.

I suspect that any attempt to implement this will break userspace --
there must be programs my now (like mine!) that set
SOF_TIMESTAMPING_SYS_HARDWARE but not SOF_TIMESTAMPING_RX_HARDWARE.

I'll write a documentation patch.

--Andy
--
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