linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>, Andrei Vagin <avagin@gmail.com>
Cc: mtk.manpages@gmail.com, Andrei Vagin <avagin@openvz.org>,
	Dmitry Safonov <dima@arista.com>,
	linux-man <linux-man@vger.kernel.org>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Linux API <linux-api@vger.kernel.org>,
	Containers <containers@lists.linux-foundation.org>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	lkml <linux-kernel@vger.kernel.org>,
	Cyrill Gorcunov <gorcunov@gmail.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andy Lutomirski <luto@kernel.org>, Adrian Reber <adrian@lisas.de>
Subject: Re: RFC: time_namespaces(7) manual page
Date: Tue, 7 Apr 2020 17:32:15 +0200	[thread overview]
Message-ID: <445b53ec-df68-1edf-dfd9-2882b3607e55@gmail.com> (raw)
In-Reply-To: <87lfn7js4f.fsf@nanos.tec.linutronix.de>

On 4/7/20 4:19 PM, Thomas Gleixner wrote:
> "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.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!

Cheers,

Michael


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  reply	other threads:[~2020-04-07 15:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-04 11:08 RFC: time_namespaces(7) manual page Michael Kerrisk (man-pages)
2020-04-06  7:38 ` Andrey Vagin
2020-04-06 11:50 ` Dmitry Safonov
2020-04-07 12:12   ` Michael Kerrisk (man-pages)
2020-04-07  3:23 ` Andrei Vagin
2020-04-07 10:30   ` Thomas Gleixner
2020-04-07 13:06     ` Michael Kerrisk (man-pages)
2020-04-07 14:19       ` Thomas Gleixner
2020-04-07 15:32         ` Michael Kerrisk (man-pages) [this message]
2020-04-07 12:53   ` Michael Kerrisk (man-pages)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=445b53ec-df68-1edf-dfd9-2882b3607e55@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=0x7f454c46@gmail.com \
    --cc=adrian@lisas.de \
    --cc=avagin@gmail.com \
    --cc=avagin@openvz.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dima@arista.com \
    --cc=ebiederm@xmission.com \
    --cc=gorcunov@gmail.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vincenzo.frascino@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).