Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp6370900imm; Mon, 27 Aug 2018 14:44:13 -0700 (PDT) X-Google-Smtp-Source: ANB0VdaEy5Sbro/McJEgQ3YkLgiln6MZsKoKsA/hkXJOL/xdVfdI90YqNBWRF5LeB8SwpJl0KxPK X-Received: by 2002:a62:4f0b:: with SMTP id d11-v6mr15801656pfb.132.1535406253301; Mon, 27 Aug 2018 14:44:13 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535406253; cv=none; d=google.com; s=arc-20160816; b=HkuTNIp87OO7VrbZnb10wtAg3cko1Q/7OipLkqlHFT8xG0ZaV/cHNnlOKzq6Knu8yB VpwvPa4qzZ1PNXKNrHC99Vjg0/dFohFIaxVwApNDAayUURPZWbeNTQW1dT10A0kNzUmz AdRkvxouVK+7d9Q/bjKzqgfcuv5Bf11ivcOXp6ICGPR+k7PT8rIFmYlEbq2ziWeF5sV4 Eq3jgKO+/w3pMdOkaVcMU7bI6i2YX4d3SzbS9ON8acezLIi1YH6AJDihePr7YhRtn8Iv kjytf4mlqMkvHWNbXaS+XcymsUP845duChHkzV17Cj+xQ5NzVnLDRX5wtzkXhcDdHsj7 e6wg== 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 :arc-authentication-results; bh=Psoy5PdvQC/0ekQIcQjnZPRcmVy0AICnpYokZE1geHk=; b=lSzFCSDXiukc46mlarrrP4uAmmDT/gqRkiqpQq/OzO7/2tzLoBa2Ts8rn3TnTz0Jud LW51MChYryP/4+MHknzKFIP8kdVMw+CGNsM+6QWnm4ir2SE+oWSpg/zcpzlsm6I2SJ6M sqvDsX+nj+XbQJd4hZ0ZGdLeiw0o7JYDLlpsRAWxGL0+M6328zjFp4RCJW+/srtuRF3r 4CREdu7P5c6AliRITTRXR5sGxmcd6zC/I0UpLG+oE/OUggDRJmsmnFTIrN9SEZXjI1CU z4HG3c8aQAdJPbi2VYxFcbSns7dkRkSqrUyseEBI3B7ekkeAlSfrbDBkQ/q4I9d/o36F 1UGA== 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 p14-v6si318920plo.357.2018.08.27.14.43.58; Mon, 27 Aug 2018 14:44:13 -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 S1727530AbeH1BbL (ORCPT + 99 others); Mon, 27 Aug 2018 21:31:11 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:43533 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726994AbeH1BbL (ORCPT ); Mon, 27 Aug 2018 21:31:11 -0400 Received: from p4fea45ac.dip0.t-ipconnect.de ([79.234.69.172] helo=[192.168.0.145]) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fuPHW-0001vq-1i; Mon, 27 Aug 2018 23:42:42 +0200 Date: Mon, 27 Aug 2018 23:42:38 +0200 (CEST) From: Thomas Gleixner To: Miroslav Lichvar cc: Ondrej Mosnacek , Richard Guy Briggs , Linux-Audit Mailing List , Linux kernel mailing list , Stephen Boyd , John Stultz Subject: Re: [PATCH ghak10 v5 2/2] timekeeping/ntp: Audit clock/NTP params adjustments In-Reply-To: <20180827114557.GN27091@localhost> Message-ID: References: <20180824120001.20771-1-omosnace@redhat.com> <20180824120001.20771-3-omosnace@redhat.com> <20180824194703.h3mbuhrxzixmna4e@madcap2.tricolour.ca> <20180827114557.GN27091@localhost> 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 Mon, 27 Aug 2018, Miroslav Lichvar wrote: > On Mon, Aug 27, 2018 at 01:35:09PM +0200, Ondrej Mosnacek wrote: > > On Fri, Aug 24, 2018 at 9:51 PM Richard Guy Briggs wrote: > > > It appears this time_tai use of "constant" is different than > > > time_constant, the former not mentioned by Miroslav Lichvar. What is it > > > and is it important to log for security? It sounds like it is > > > important. > > > The TAI offset is the offset of the clock from the International > > Atomic Time, so basically the time zone offset. I suppose it can't > > influence the audit timestamps, but changing timezones can still cause > > all sorts of confusion throughout the system, so intuitively I would > > say we should log it. > > It's not related to timezones. ADJ_TAI sets the offset of the system > TAI clock (CLOCK_TAI) relative to the standard UTC clock > (CLOCK_REALTIME). CLOCK_TAI is rarely used by applications. Setting > the TAI offset effectively injects a whole-second offset to the TAI > time. Rarely used today, but with TSN it's going to get more usage in not so distant future. Thanks, tglx