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;
Date:   Sun, 20 Feb 2022 12:05:35 -0500
From:   Steven Rostedt <rostedt@goodmis.org>
To:     tangmeng <tangmeng@uniontech.com>
Cc:     mingo@redhat.com, mcgrof@kernel.org, keescook@chromium.org,
        yzaikin@google.com, linux-kernel@vger.kernel.org,
        linux-fsdevel@vger.kernel.org, nizhen@uniontech.com,
        zhanglianjie@uniontech.com, nixiaoming@huawei.com
Subject: Re: [PATCH 02/11] kernel/trace: move stack_tracer_enabled sysctl to
 its own file
Message-ID: <20220220120535.50380537@gandalf.local.home>
In-Reply-To: <20220220060017.13285-1-tangmeng@uniontech.com>
References: <20220220060017.13285-1-tangmeng@uniontech.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Sun, 20 Feb 2022 14:00:17 +0800
tangmeng <tangmeng@uniontech.com> wrote:

> kernel/sysctl.c is a kitchen sink where everyone leaves their dirty
> dishes, this makes it very difficult to maintain.
> 
> To help with this maintenance let's start by moving sysctls to places
> where they actually belong.  The proc sysctl maintainers do not want to
> know what sysctl knobs you wish to add for your own piece of code, we
> just care about the core logic.
> 
> All filesystem syctls now get reviewed by fs folks. This commit
> follows the commit of fs, move the stack_tracer_enabled sysctl to its
> own file, kernel/trace/trace_stack.c.
> 
> Signed-off-by: tangmeng <tangmeng@uniontech.com>

Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>

-- Steve