Re: [PATCH -next 00/15] sysctl: move sysctls from vm_table into its own files

yukaixiong <[email protected]>
Newsgroups gmane.linux.kernel.lsm,gmane.linux.ports.sh.devel,gmane.linux.kernel,gmane.linux.file-systems,gmane.linux.kernel.mm,gmane.linux.nfs,gmane.linux.network
Message-ID <[email protected]>

On 2024/9/2 15:17, Joel Granados wrote:
> On Mon, Aug 26, 2024 at 08:04:34PM +0800, Kaixiong Yu wrote:
>> This patch series moves sysctls of vm_table in kernel/sysctl.c to
>> places where they actually belong, and do some related code clean-ups.
>> After this patch series, all sysctls in vm_table have been moved into its
>> own files, meanwhile, delete vm_table.
>>
>> All the modifications of this patch series base on
>> linux-next(tags/next-20240823). To test this patch series, the code was
>> compiled with both the CONFIG_SYSCTL enabled and disabled on arm64 and
>> x86_64 architectures. After this patch series is applied, all files
>> under /proc/sys/vm can be read or written normally.
>>
>> Kaixiong Yu (15):
>>    mm: vmstat: move sysctls to its own files
>>    mm: filemap: move sysctl to its own file
>>    mm: swap: move sysctl to its own file
>>    mm: vmscan: move vmscan sysctls to its own file
>>    mm: util: move sysctls into it own files
>>    mm: mmap: move sysctl into its own file
>>    security: min_addr: move sysctl into its own file
>>    mm: nommu: move sysctl to its own file
>>    fs: fs-writeback: move sysctl to its own file
>>    fs: drop_caches: move sysctl to its own file
>>    sunrpc: use vfs_pressure_ratio() helper
>>    fs: dcache: move the sysctl into its own file
>>    x86: vdso: move the sysctl into its own file
>>    sh: vdso: move the sysctl into its own file
>>    sysctl: remove unneeded include
>>
> Thx for this.
>
> I passed this through 0-day testing and it return some errors. Please
> address those build errors/regrssions before you send V2.
>
> Best

ok,I will fix those  errors/warnings in v2
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.