Received: by 2002:ac0:bc90:0:0:0:0:0 with SMTP id a16csp71230img; Wed, 27 Mar 2019 17:11:57 -0700 (PDT) X-Google-Smtp-Source: APXvYqydd3QQzLOYdEMs5BrxhHAKwnXGQt4/Jlj4prMBlbw1Ifo5fD3Gfx2SuqL6QIC0Og5dEoH0 X-Received: by 2002:a17:902:8d89:: with SMTP id v9mr22474417plo.230.1553731917352; Wed, 27 Mar 2019 17:11:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1553731917; cv=none; d=google.com; s=arc-20160816; b=idF3APKb9UmPQMM1LZfEyvFgd3RMB+USUiXlLyR0WNiLUtna+gyb1sNt+y1wVjJPDi R4Wj96E6tqETZ+8wj1FRTTYb6uajz6xxhvOFtW6Ye0r6xJErSWJ+qJjfGhI08L7uP+ow Hgkdq+kGnf0jcYrnFicvPfCH04lDVKGeGd/tQTm+EGysHcFK22ZXvWHuqOoyU8QM5kca 8XHsdnZ8SVXcXyEEDprkvyYCpvxvN6YOv9hXsBbHtf3NXXTNZuxRU+FMuvxzkWDyNB0k LeLTTEvS4iVSF/eZwiQR3f+/qJgQQP+D2bqds/RCXwPPGy1oJ6jPhTiowqXMzn+Vj1hl 9j9w== 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=DDTN+i6u6LJgLof/q6cD8Dc7v3l0mvCbOVaqVteftpo=; b=dHvAyletoWmzDm448UXkDwTV4elylZ48pQZ3MgFyWwfuRaypIlvsoY4waGNy1KAp2i zwAWTtFk3PQoyGsgMJ9ydo6J9kZUJZ6vRs7fcZbKvguYqYdpLaMD1CdCAzp36h26IkjI d+kvopNbj0+tY2akXqP19utJh231MCFw/roxO99TPQnrvJCS9XRtlYp+9G5V9nUbXmvq OhPCmz+BJSSSTzGfwJsk6fN6oOoJtHrpaGlh3y98autA+NJ0PzhCBKRyp2NipePEwlir z/qybePDseUSAZS8LbKS349lQw5FFpVgj6d145NiHbg+DJFFvUPao4M57FQrHlfXHc9+ 9jaw== 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 f1si20583408pld.32.2019.03.27.17.11.39; Wed, 27 Mar 2019 17:11:57 -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 S1727799AbfC1AKx (ORCPT + 99 others); Wed, 27 Mar 2019 20:10:53 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:51979 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727202AbfC1AKx (ORCPT ); Wed, 27 Mar 2019 20:10:53 -0400 Received: from p5492e2fc.dip0.t-ipconnect.de ([84.146.226.252] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1h9Id8-0005nc-Ud; Thu, 28 Mar 2019 01:10:51 +0100 Date: Thu, 28 Mar 2019 01:10:50 +0100 (CET) From: Thomas Gleixner To: Ondrej Mosnacek cc: linux-audit@redhat.com, Paul Moore , Richard Guy Briggs , Steve Grubb , Miroslav Lichvar , John Stultz , Stephen Boyd , LKML , Clark Williams Subject: Re: [RFC PATCH ghak10 v6 1/2] timekeeping: Audit clock adjustments In-Reply-To: Message-ID: References: <20190307123254.348-1-omosnace@redhat.com> <20190307123254.348-2-omosnace@redhat.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 Thu, 28 Mar 2019, Thomas Gleixner wrote: > On Thu, 7 Mar 2019, Ondrej Mosnacek wrote: > > --- a/kernel/auditsc.c > > +++ b/kernel/auditsc.c > > @@ -2512,6 +2512,14 @@ void __audit_fanotify(unsigned int response) > > AUDIT_FANOTIFY, "resp=%u", response); > > } > > > > +/* We need to allocate with GFP_ATOMIC here, since these two functions will be > > + * called while holding the timekeeping lock: */ > > Audit is no justification for doing ATOMIC allocations just because it's > convenient in the middle of code which blocks every concurrent reader. Aside of that you might talk to your colleagues working on Preempt-RT about this. I'm pretty sure they are going to have opinions simply because you cannot do ATOMIC allocations in those contexts on RT. Logging needs to be unintrusive and allocations are definitely not. Thanks, tglx