Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp2814736pxb; Thu, 3 Feb 2022 15:20:32 -0800 (PST) X-Google-Smtp-Source: ABdhPJyz/UxpEJAhesLVnX5MQFuaUzeUKOIdyK3tYsf+Z/ZrUdYQdBu1uMduOOYzA88f3FwBoalR X-Received: by 2002:a05:6402:1ca4:: with SMTP id cz4mr500375edb.28.1643930432157; Thu, 03 Feb 2022 15:20:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643930432; cv=none; d=google.com; s=arc-20160816; b=vV+m+FbE5fa49c1F8w9wDwWbpmVCUxRBCMUeq6EuLrf+BtLjCy25u4uH4ohS+DaHQa oMtwel5P9RN6vUD2QIqWeAUsQhLiNG5EKNDy0qaf2LTItKoophUjkKSzzB6D8WN4qNUj rOA3IbIlCfyC0cNk2cSrh1m329SxFO9rvMER4TDUuGvB2H0LXKZCIAoo35hWQS0cKr6y 0EJ57Ls/6p8Wah+HrkudnJ/gBNQVlJ6LYDXSdMorLgMLLurMMFcCc1KjkZ72D5rMoW2O Vkb3R6QR5KMneDjQ6uk7o0LCU39QGOac2PaqE4EUdAJ8H2uvfW66fnk7FRHH1cQHZKBx 6qYA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=U4C4OCa1Nvs01R45W3Ay9R6lIjYfrb4U7/RUPw787LQ=; b=QIoPWU4Z7c8DCP954lbIbCdp+uUbA6A9pcntwaGRdQlZqu8zjsN7JiP3l2Ey1Q/iFG lWkhIRIOWP/fAHM04EeOZ8+8rxtfnVpLF3ieK6rRSnBzqS9B1XJAIETRLYbVGxtoTodV +xRT46OtakVKtd7r7sI90EctUc5hLciJ3ULv7XW5L/EsAw5a98AhDMKlv6Yo/kl9DfE3 AaCczzt8KmPjMKpyd/7k/i/47pgvY5IyBycWamMfE03sZm7rUuj9Mj2TCQXzEe4H7xUc wOur/3FEQKTBBltLWUoO3RJsKvUpiAS+ifMiJsAB19tV30x5KZDzsFoeC0dY4H+zPkpV P4UA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=3L3r68S4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h12si140808edb.140.2022.02.03.15.20.05; Thu, 03 Feb 2022 15:20:32 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@infradead.org header.s=bombadil.20210309 header.b=3L3r68S4; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1353877AbiBCTxp (ORCPT + 99 others); Thu, 3 Feb 2022 14:53:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49022 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233153AbiBCTxp (ORCPT ); Thu, 3 Feb 2022 14:53:45 -0500 Received: from bombadil.infradead.org (bombadil.infradead.org [IPv6:2607:7c80:54:e::133]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2BA69C061714; Thu, 3 Feb 2022 11:53:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20210309; h=Sender:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=U4C4OCa1Nvs01R45W3Ay9R6lIjYfrb4U7/RUPw787LQ=; b=3L3r68S46ebKK9cqWNZF8HkI54 J8mtXyCYmYNlqaERNHO5V1F29b+IU8JPO4OgbpQDQSUVZXoAw2dAMkUBoa9XyXol+ivw4/4XVfKJn XiBn8mxCoN9vC87Sh2qzN/ikL3VP+ahD3YA+4cSBe3rR57wfXAlYK9CrRARUTS7ciL77+0ZjZKhOO FJzSgm4EXqP6C9vEDj1QifOmMqIEzkclS9YfowjfchaY5zWe+fvWsolVY9NbXQo6wp3Mss2bw3dfb +49iFDJVMH0PZDwbThqWOvc2y8eavytlwbUBp6zUA0htlPJW5DZmbQcSfPRGWBlXVwskwgdX3Hct7 ITvV0tIg==; Received: from mcgrof by bombadil.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1nFiAd-002eDE-49; Thu, 03 Feb 2022 19:53:31 +0000 Date: Thu, 3 Feb 2022 11:53:31 -0800 From: Luis Chamberlain To: Thomas Gleixner Cc: "Eric W. Biederman" , tangmeng , keescook@chromium.org, yzaikin@google.com, john.stultz@linaro.org, sboyd@kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, Greg Kroah-Hartman Subject: Re: [PATCH v5] kernel/time: move timer sysctls to its own file Message-ID: References: <20220131102214.2284-1-tangmeng@uniontech.com> <87wnicssth.ffs@tglx> <87r18ks379.ffs@tglx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87r18ks379.ffs@tglx> Sender: Luis Chamberlain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Feb 03, 2022 at 10:35:06AM +0100, Thomas Gleixner wrote: > On Wed, Feb 02 2022 at 17:17, Luis Chamberlain wrote: > > On Thu, Feb 03, 2022 at 01:21:46AM +0100, Thomas Gleixner wrote: > > *Today* all filesystem syctls now get reviewed by fs folks. They are > > all tidied up there. > > > > In the future x86 folks can review their sysctls. But for no reason > > should I have to review every single knob. That's not scalable. > > Fair enough, but can we please have a changelog which explains the > rationale to the people who have not been part of that discussion and > decision. Sure thing, tangmeng please update the commit log a bit better. > >> That aside, I'm tired of this because this is now at V5 and you still > >> failed to fix the fallout reported by the 0-day infrastructure vs. this > >> part of the patch: > >> > >> > +static int __init timer_sysctl_init(void) > >> > +{ > >> > + register_sysctl_init("kernel", timer_sysctl); > >> > + return 0; > >> > +} > >> > >> kernel/time/timer.c: In function 'timer_sysctl_init': > >> >> kernel/time/timer.c:284:9: error: implicit declaration of function 'register_sysctl_init'; did you mean 'timer_sysctl_init'? [-Werror=implicit-function-declaration] > >> 284 | register_sysctl_init("kernel", timer_sysctl); > >> | ^~~~~~~~~~~~~~~~~~~~ > >> > > > > That's an issue with the patch being tested on a tree where that > > routine is not present? > > From the report: > > ... > [also build test ERROR on linus/master > > Linus tree has this interface. So that's not the problem. > > Hint #1: The interfaxce is not available unconditionally > > Hint #2: The 0-day reports provide the config file which exposes the > fail tangmeng, please fix. Luis