Re: [PATCH v9 0/7] sched: Persistent user requested affinity

[Waiman Long]

On 9/22/22 04:45, Peter Zijlstra wrote:
> On Fri, Sep 16, 2022 at 02:32:10PM -0400, Waiman Long wrote:
>
> > Waiman Long (7):
> >    sched: Add __releases annotations to affine_move_task()
> >    sched: Use user_cpus_ptr for saving user provided cpumask in
> >      sched_setaffinity()
> >    sched: Enforce user requested affinity
> >    sched: Introduce affinity_context structure
> >    sched: Handle set_cpus_allowed_ptr() & sched_setaffinity() race
> >    sched: Fix sched_setaffinity() and fork/clone() race
> >    sched: Always clear user_cpus_ptr in do_set_cpus_allowed()
> I still think this is ordered all wrong. Esp. with that affinity context
> doing the right thing isn't onerous at all.
>
> So please, re-order this and fold all fixes back in so that it becomes
> a sane series. Basically patches 5 and 6 shouldn't exist, they fix
> issues created by the earlier patches.
Thanks for the suggestion. Will rework the series as suggested.

Cheers,
Longman