lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Fri, 11 Feb 2022 10:23:42 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Peter Zijlstra <peterz@...radead.org>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     Zhen Ni <nizhen@...ontech.com>, mingo@...hat.com,
        juri.lelli@...hat.com, vincent.guittot@...aro.org,
        keescook@...omium.org, linux-kernel@...r.kernel.org,
        linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH] sched: move rr_timeslice sysctls to rt.c

Cc'ing Andrew for coordination on merging these sorts of patches.

On Fri, Feb 11, 2022 at 12:51:14PM +0100, Peter Zijlstra wrote:
> So I've dropped the whole lot I had:
> 
> patches/zhen_ni-sched-move_energy_aware_sysctls_to_topology_c.patch
> patches/zhen_ni-sched-move_cfs_bandwidth_slice_sysctls_to_fair_c.patch
> patches/zhen_ni-sched-move_uclamp_util_sysctls_to_core_c.patch
> patches/zhen_ni-sched-move_schedstats_sysctls_to_core_c.patch
> patches/zhen_ni-sched-move_deadline_period_sysctls_to_deadline_c.patch
> patches/zhen_ni-sched-move_rt_period_runtime_sysctls_to_rt_c.patch
> patches/zhen_ni-sched-move_rr_timeslice_sysctls_to_rt_c.patch
> 
> And I expect a single coherent series or I'll forgo all this.

I suspect Zhen will follow up accordingly.

So Andrew had merged tons of initial cleanups for kernel/sysctl.c. Now
that some of the initial grunt work and sysctls for fs are out of
kernel/sysctl.c, I'm seeing the next target seems to be the scheduler. I
don't think these *need* to go through Andrew's tree since the fs
changes are already on Linus' tree. So figured I'd drop this note to
just remind ourselves that if accumulate a few of these patches for one
subsystem there is a greater risk of a conflict later with another
subsystem doing some similar cleanup. So for the next release I think it
makes sense to keep this localized somehow if we can. Maybe we just deal
with these on Peter's tree?

  Luis

Powered by blists - more mailing lists