linux-kernel - Re: RFC: documentation of the autogroup feature

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]

Date:   Wed, 23 Nov 2016 18:11:15 +0100
From:   Mike Galbraith <efault@....de>
To:     "Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>
Cc:     Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Ingo Molnar <mingo@...nel.org>,
        linux-man <linux-man@...r.kernel.org>,
        lkml <linux-kernel@...r.kernel.org>,
        Thomas Gleixner <tglx@...utronix.de>
Subject: Re: RFC: documentation of the autogroup feature

On Wed, 2016-11-23 at 17:04 +0100, Michael Kerrisk (man-pages) wrote:

> > > In what circumstances does a process get moved back to the root 
> > > task group?
> > 
> > Userspace actions, tool or human fingers.
> 
> Could you say a little more please. What Kernel-user-space 
> APIs/system calls/etc. cause this to happen?

Well, the system call would be write(), scribbling in the cgroups vfs
interface.. not all that helpful without ever more technical detail.

> > > Actually, can you define for me what the root task group is, and 
> > > why it exists? That may be worth some words in this man page.
> > 
> > I don't think we need group scheduling details, there's plenty of
> > documentation elsewhere for those who want theory.  
> 
> Well, you suggested above 
> 
>     Perhaps mention that moving a task back to the root task
>     group will result in the autogroup again taking effect.

Dang, evolution doesn't have an unsend button :)

	-Mike