Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp2153171imm; Tue, 2 Oct 2018 22:26:56 -0700 (PDT) X-Google-Smtp-Source: ACcGV60FbR51iFaRZUM5DizVYlSG5jn3VspJb+UnT/FOQQRIh6h/ZU0r5uqOIpPCdcO9d6fdGZKF X-Received: by 2002:a62:5f46:: with SMTP id t67-v6mr3874780pfb.223.1538544416416; Tue, 02 Oct 2018 22:26:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1538544416; cv=none; d=google.com; s=arc-20160816; b=G7i+VrjNF2e5e7mRDlbCW6XkRf6DhdSFRJ+4esFjbAAdOk51+BLgwW7DNTQJygzaS6 sVMhyCCGpBghFnxrPS9woIOjh3tu29QVfIi4QIA837FRyOFhL2VUkLQjt6gjw4Ey70zu a85/QAoI8HKyRjIjbNFCEuqXIdsYQdIuzVxwqdSd8coK5SMBP5bDLCwUvqip+pv9J/x3 UKLYlou12svw2J2DGbubCXhqzBn4aqTsaFK+/+/4yz6KuUoCKYKkEhSgjxg1EtpYXBPo iFbw8gDoAk+gkM9RiPdMOBSEWOnfL/M2PlmleAiOgdUeCVVyphpKLmGYoGhFPr57KQI4 KB5w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=FeboVOazhwZlIR6G7PtBqqquFNzq/yVoHSqotk+6YU8=; b=nkCqG92qiu9kpwCzf5jcIotoKZ0qtZZoiI2vA9jIlwabqgecyvBuPpexULuAmW125a KTs/NGIbilakg8j4fLg7iOwGBoWaDj0NLl6kovCe56vxCZRmCN31mv4l+Dk13jU3rqls dHY44MFBLLXY2M2uRmcKIWgIKb1rs9OUoTLa+oDD9Ma5g6DmVnF15L3BnThyQ455KmG3 wwfuIx+TUjF5meJOExI1W7zd30a3s9NCrPNQSFfILDpVkaXQgJOKN9q4QPjIdhM1T1yo fiLNLCwKrDhhdZT9dsJV+dmM20RdNFHt6Bh7dU5umehqUGr5K/5l9QPNDoN38AEZz3fG reRw== 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 j189-v6si248714pgd.476.2018.10.02.22.26.41; Tue, 02 Oct 2018 22:26:56 -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 S1726775AbeJCMNB (ORCPT + 99 others); Wed, 3 Oct 2018 08:13:01 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:33026 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726510AbeJCMNA (ORCPT ); Wed, 3 Oct 2018 08:13:00 -0400 Received: from p5492e4c1.dip0.t-ipconnect.de ([84.146.228.193] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1g7ZfE-0006tq-6X; Wed, 03 Oct 2018 07:25:36 +0200 Date: Wed, 3 Oct 2018 07:25:35 +0200 (CEST) From: Thomas Gleixner To: "Eric W. Biederman" cc: Arnd Bergmann , avagin@virtuozzo.com, dima@arista.com, Linux Kernel Mailing List , 0x7f454c46@gmail.com, adrian@lisas.de, Andy Lutomirski , Christian Brauner , gorcunov@openvz.org, "H. Peter Anvin" , Ingo Molnar , Jeff Dike , Oleg Nesterov , xemul@virtuozzo.com, Shuah Khan , containers@lists.linux-foundation.org, criu@openvz.org, Linux API , the arch/x86 maintainers , Alexey Dobriyan , linux-kselftest@vger.kernel.org Subject: Re: Setting monotonic time? In-Reply-To: <87in2jskew.fsf@xmission.com> Message-ID: References: <20180919205037.9574-1-dima@arista.com> <874lej6nny.fsf@xmission.com> <20180924205119.GA14833@outlook.office365.com> <874leezh8n.fsf@xmission.com> <20180925014150.GA6302@outlook.office365.com> <87zhw4rwiq.fsf@xmission.com> <87mus1ftb9.fsf@xmission.com> <877ej2xc23.fsf_-_@xmission.com> <87in2jskew.fsf@xmission.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 3 Oct 2018, Eric W. Biederman wrote: > Direct access to hardware/drivers and not through an abstraction like > the vfs (an abstraction over block devices) can legitimately be handled > by hotplug events. I unplug one keyboard I plug in another. > > I don't know if the input layer is more of a general abstraction > or more of a hardware device. I have not dug into it but my guess > is abstraction from what I have heard. > > The scary difficulty here is if after restart input is reporting times > in CLOCK_MONOTONIC and the applications in the namespace are talking > about times in CLOCK_MONOTONIC_SYNC. Then there is an issue. As even > with a fixed offset the times don't match up. > > So a time namespace absolutely needs to do is figure out how to deal > with all of the kernel interfaces reporting times and figure out how to > report them in the current time namespace. So you want to talk to Arnd who is leading the y2038 effort. He knowns how many and which interfaces are involved aside of the obvious core timer ones. It's quite an amount and the problem is that you really need to do that at the interface level, because many of those time stamps are taken in contexts which are completely oblivious of name spaces. Ditto for timeouts and similar things which are handed in through these interfaces. Thanks, tglx