linux-kernel - Re: RFC: time_namespaces(7) manual page

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]

Date:   Tue, 07 Apr 2020 16:19:12 +0200
From:   Thomas Gleixner <tglx@...utronix.de>
To:     "Michael Kerrisk \(man-pages\)" <mtk.manpages@...il.com>,
        Andrei Vagin <avagin@...il.com>
Cc:     mtk.manpages@...il.com, Andrei Vagin <avagin@...nvz.org>,
        Dmitry Safonov <dima@...sta.com>,
        linux-man <linux-man@...r.kernel.org>,
        Vincenzo Frascino <vincenzo.frascino@....com>,
        Linux API <linux-api@...r.kernel.org>,
        Containers <containers@...ts.linux-foundation.org>,
        Dmitry Safonov <0x7f454c46@...il.com>,
        lkml <linux-kernel@...r.kernel.org>,
        Cyrill Gorcunov <gorcunov@...il.com>,
        "Eric W. Biederman" <ebiederm@...ssion.com>,
        Andy Lutomirski <luto@...nel.org>,
        Adrian Reber <adrian@...as.de>
Subject: Re: RFC: time_namespaces(7) manual page

"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com> writes:
> I've tried to capture this info, as well some other relevant errors
> in the following text. Does it look okay?
>
>        Writes  to  the  timens_offsets  file  can fail with the following
>        errors:
>
>        EINVAL An offset-nanosecs value is greater than 999,999,999.
>
>        EINVAL A clock-id value is not valid.
>
>        EPERM  The caller does not have the the CAP_SYS_TIME capability.
>
>        ERANGE An offset-secs value is out of range.  In particular;
>
>               · offset-secs can't be set to a value which would make  the
>                 current time on the corresponding clock inside the names‐
>                 pace a negative value; and
>
>               · offset-secs can't be set to a value such that the time on
>                 the corresponding clock inside the namespace would exceed
>                 half of the value of the  kernel  constant  KTIME_SEC_MAX
>                 (this  limits  the  clock  value to a maximum of approxi‐
>                 mately 146 years).

Yes.

Thanks,

        tglx