Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4428918ybb; Tue, 7 Apr 2020 07:21:50 -0700 (PDT) X-Google-Smtp-Source: APiQypJc3ZlKP2cs7UE1raQvjrnPO8G1jFdZnwMPtosujDJqTkk+SoYLPnpPsbbgopggqqY/r6xq X-Received: by 2002:a9d:5e0d:: with SMTP id d13mr1824626oti.162.1586269310265; Tue, 07 Apr 2020 07:21:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586269310; cv=none; d=google.com; s=arc-20160816; b=QLy14PJLY+b9Yh0IjiCUIsaaOdJasrwGm6Sthjbqh8g0mMKgxlCoCHQ45m3bPtsbbX 6V1fLz6ZQdXXos9mLyrxN28UbyTNjrQFDkSxaCDzvlV+QXnexlvCpYi12CA5HR6zIma2 jZBTCzqmo6d5afWBxo01e1JfPkvfp9qQK9m0WoWCMKkoJEhL+BGTrbmEHh0XsHaF4VUA 8ZX802itU4BFp+dCYvd+r+xljiVkx6YEgzIysCO8/mIApss7C7NJVBVqcgvX8gLKNqmG R8qgzd1NHGuJoZ7YIVasonZ+obhWQh+RghotIH2BK3CszaysR5pX1ByjYXEmnSr5XBmP 62UA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :message-id:date:references:in-reply-to:subject:cc:to:from; bh=3+1+hCQtSXvuEx3T5f/Lc9l2TNBfGFhinALlyzb380I=; b=AOtg++KGWHEN+mYx3LuTmi2JRAj+DqaCWPhgavqVw58pXkFEOaE3Zc6tByspN4dANW 7FolexV1uQ0d33X2/Ctz+4P5tKBOnRh29dodTgu+QCb9q0qvSBA6rwnQShIY+o+2lx5+ Nh1A/ibRg6/6gwig4eFSC2MT5QPv513btsk6OtuR5gTBHc31UcaXtVz84NTBS1BcbRM/ q3w1ElF9tmZy3QI/SWnnbQwhbL51D3FIxeEIkcUHxUqJk2JR31cN1lghKMhZH2xwosko 0QdUopzwr/466eOMnI+CfxRnX688YH42vxlQ6ay79Y1H7ZddcksbDlquilUi6fv9aQCs L88Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id 7si1312171ooy.80.2020.04.07.07.21.29; Tue, 07 Apr 2020 07:21:50 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729023AbgDGOTX convert rfc822-to-8bit (ORCPT + 99 others); Tue, 7 Apr 2020 10:19:23 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:47543 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728737AbgDGOTW (ORCPT ); Tue, 7 Apr 2020 10:19:22 -0400 Received: from [5.158.153.52] (helo=nanos.tec.linutronix.de) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1jLp4K-000768-PN; Tue, 07 Apr 2020 16:19:12 +0200 Received: by nanos.tec.linutronix.de (Postfix, from userid 1000) id 64BBF101303; Tue, 7 Apr 2020 16:19:12 +0200 (CEST) From: Thomas Gleixner To: "Michael Kerrisk \(man-pages\)" , Andrei Vagin Cc: mtk.manpages@gmail.com, Andrei Vagin , Dmitry Safonov , linux-man , Vincenzo Frascino , Linux API , Containers , Dmitry Safonov <0x7f454c46@gmail.com>, lkml , Cyrill Gorcunov , "Eric W. Biederman" , Andy Lutomirski , Adrian Reber Subject: Re: RFC: time_namespaces(7) manual page In-Reply-To: References: <7221df0a-435b-f8bc-ff91-c188af535e73@gmail.com> <20200407032318.GA494464@gmail.com> <87r1wzk2p5.fsf@nanos.tec.linutronix.de> Date: Tue, 07 Apr 2020 16:19:12 +0200 Message-ID: <87lfn7js4f.fsf@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org "Michael Kerrisk (man-pages)" 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