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>] [day] [month] [year] [list]
Message-ID: <CAO6QMdwwJBR8GnpHZo=viA4qj8HN6QOS4+pBQwvHu28E-POnTg@mail.gmail.com>
Date:   Fri, 1 Nov 2019 20:07:20 -0700
From:   Srinivas Murthy <the.srinivas.murthy@...il.com>
To:     linux-kernel@...r.kernel.org
Subject: how to find thread that fork'd the current

>From the current thread (in kernel) is there a way to tell which
thread fork'd it?

systemd -> proc1 --fork--> thread2

thread2 detaches; thread2's parent set to systemd; thread2's tgid set
to its pid;

I see that the detached threads have their tgid set to its own pid and
its parent/real_parent set to the parent systemd

Is there a way to reliably tell the parent proc/thread (proc1) from
thread2's current (task_infostruct)?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ