Received: by 2002:a25:868d:0:0:0:0:0 with SMTP id z13csp2414612ybk; Sun, 17 May 2020 21:06:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz2AwgT0zPcnhaNcVBIE7UM6szYcFJhB8p17+LoQccNO5Vg5sDtV45twk9Tg8nJ8fAm6LxO X-Received: by 2002:a50:b082:: with SMTP id j2mr5710112edd.201.1589774764879; Sun, 17 May 2020 21:06:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1589774764; cv=none; d=google.com; s=arc-20160816; b=AuJgtaD/LY8d1YfEpatwg2OjuG+VNtlfo8ASaDhmAKcfaavATBZn/0BmpFwgRT2brn tVVt0Kt+YXvI47FdK/SkImUHwBHwzkKoz+ftQ6RwGZrCBdQnQmIJbsuIKoxRD6K1shjk ykwkXorjE8k9+PPxZYGPlXa/DoerCdsR78Iac6A4xz/CN6e2qCCxO2GE4C8e92l5owDR ASsZja5gIRtCGp/MjalF9j8Ck8nmR11pHMmWjo842y0g3YjrdnNbns8B+VjPFgf2Tckw Rbd5PIN5w+Fc9REWIhWL4ebR/GlDowe7Ji8AQtd8I9WJ2HkrOQeTUEonOfahofI8O2lO tVkg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:message-id:date:subject:cc :to:from; bh=JqV+Mjpx+Mt6dWIWbkBK8wXs0qGUaD0jTQ4q35Ghdow=; b=vwAYjYFpLFM1htWGrqvCDGkt6hwCuBQNHnhY4B7eS3v1vmGsLQihAiGeUGnRgiM098 16+1I9SKJWt2aLt08K6oY2KtdHnp76pTzRzJkSbFVHRvIRc9BaEc6s78g6s62xmAMCA9 PDhRq1eRM+YQUKepPU1Hf3eApH/csL6y+5Sxb9T6cE0en5bXULVxVqPoMjg6Xn1Wmleo b119+RKiZ3HxmCAUP7ogQfQRibvnM5MSR3WN4bUodBxygsWcCnxkYXqGrucwycI+MGSo Iq+w9jszjywU7RbX9BqvJJ8ZrKG+/p98zMAZGRlLrahr+NxRJXLOhVULa05jFv/3VZkf 9Idg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c22si6501805edx.33.2020.05.17.21.05.41; Sun, 17 May 2020 21:06:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726358AbgEREAM (ORCPT + 99 others); Mon, 18 May 2020 00:00:12 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:58192 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726040AbgEREAL (ORCPT ); Mon, 18 May 2020 00:00:11 -0400 Received: from DGGEMS412-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id 9C8696BCAAAF13898985; Mon, 18 May 2020 12:00:09 +0800 (CST) Received: from use12-sp2.huawei.com (10.67.189.174) by DGGEMS412-HUB.china.huawei.com (10.3.19.212) with Microsoft SMTP Server id 14.3.487.0; Mon, 18 May 2020 11:59:59 +0800 From: Xiaoming Ni To: , , , , , , , , , , , , , , CC: , , Subject: [PATCH v3 0/4] cleaning up the sysctls table (hung_task watchdog) Date: Mon, 18 May 2020 11:59:53 +0800 Message-ID: <1589774397-42485-1-git-send-email-nixiaoming@huawei.com> X-Mailer: git-send-email 1.8.5.6 MIME-Version: 1.0 Content-Type: text/plain X-Originating-IP: [10.67.189.174] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Kernel/sysctl.c contains more than 190 interface files, and there are a large number of config macro controls. When modifying the sysctl interface directly in kernel/sysctl.c, conflicts are very easy to occur. E.g: https://lkml.org/lkml/2020/5/10/413. Use register_sysctl() to register the sysctl interface to avoid merge conflicts when different features modify sysctl.c at the same time. So consider cleaning up the sysctls table, details are in: https://kernelnewbies.org/KernelProjects/proc https://lkml.org/lkml/2020/5/13/990 The current patch set extracts register_sysctl_init and some sysctl_vals variables, and clears the interface of hung_task and watchdog in sysctl.c. The current patch set is based on commit b9bbe6ed63b2b9 ("Linux 5.7-rc6"), which conflicts with the latest branch of linux-next: 9b4caf6941fc41d ("kernel / hung_task.c: introduce sysctl to print all traces when a hung task is detected") Should I modify to make patch based on the "linux-next" branch to avoid conflicts, or other branches? changes in v3: 1. make hung_task_timeout_max to be const 2. fix build warning: kernel/watchdog.c:779:14: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] .extra2 = &sixty, ^ V2: https://lkml.org/lkml/2020/5/16/81 changes in v2: 1. Adjusted the order of patches, first do public function extraction, then do feature code movement 2. Move hung_task sysctl to hung_task.c instead of adding new file 3. Extract multiple common variables instead of only neg_one, and keep the order of member values in sysctl_vals 4. Add const modification to the variable sixty in watchdog sysctl V1: https://lkml.org/lkml/2020/5/15/17 Xiaoming Ni (4): sysctl: Add register_sysctl_init() interface sysctl: Move some boundary constants form sysctl.c to sysctl_vals hung_task: Move hung_task sysctl interface to hung_task.c watchdog: move watchdog sysctl interface to watchdog.c fs/proc/proc_sysctl.c | 2 +- include/linux/sched/sysctl.h | 8 +- include/linux/sysctl.h | 13 ++- kernel/hung_task.c | 63 +++++++++++++- kernel/sysctl.c | 202 ++++++++----------------------------------- kernel/watchdog.c | 101 ++++++++++++++++++++++ 6 files changed, 210 insertions(+), 179 deletions(-) -- 1.8.5.6