linux-kernel - Re: [PATCH 0/8] kernel/fork: Move thread stack free otu of the scheduler path.

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20211203162211.qvcnvbj4cdsa5g3a@linutronix.de>
Date:   Fri, 3 Dec 2021 17:22:11 +0100
From:   Sebastian Andrzej Siewior <bigeasy@...utronix.de>
To:     linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org,
        tglx@...utronix.de
Cc:     Ingo Molnar <mingo@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Andy Lutomirski <luto@...nel.org>,
        Juri Lelli <juri.lelli@...hat.com>,
        Vincent Guittot <vincent.guittot@...aro.org>,
        Dietmar Eggemann <dietmar.eggemann@....com>,
        Steven Rostedt <rostedt@...dmis.org>,
        Ben Segall <bsegall@...gle.com>,
        Daniel Bristot de Oliveira <bristot@...hat.com>
Subject: Re: [PATCH 0/8] kernel/fork: Move thread stack free otu of the
 scheduler path.

On 2021-11-18 15:38:50 [+0100], To linux-kernel@...r.kernel.org wrote:
> + tglx.
> 
> It starts at
>    https://lore.kernel.org/all/20211118143452.136421-1-bigeasy@linutronix.de/
> 
> On 2021-11-18 15:34:44 [+0100], To linux-kernel@...r.kernel.org wrote:
> > 
> > This is a follup-up on the patch
> >     sched: Delay task stack freeing on RT 
> >     https://lkml.kernel.org/r/20210928122411.593486363@linutronix.de
> > 
> > It addresses the review feedback:
> > - Decouple stack accounting from its free invocation. The accounting
> >   happens in do_exit(), the final free call happens later.
> > 
> > - Add put_task_stack_sched() to finish_task_switch(). Here the VMAP
> >   stack is cached only. If it fails, or in the !VMAP case then the final
> >   free happens in delayed_put_task_struct(). This is also an oportunity
> >   to cache the stack.

ping ;)

Sebastian