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: <f22d86810910250349w6e1c93bai3447164cf700e657@mail.gmail.com>
Date:	Sun, 25 Oct 2009 16:19:10 +0530
From:	"Leonidas ." <leonidas137@...il.com>
To:	Clemens Ladisch <clemens@...isch.de>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: Process id recycling and status of tasks

> The obvious question which follows from above is what would be the correct
> way to determine whether a process is alive or not using pid_alive()? Using
> pid_task() does not seem correct and seemingly correct way looks unfeasible.
>

I guess, just checking task_struct->exit_state will be okay to do,
right? If exit
state is DEAD then the task is stale, might avoid using the reference counting
counterparts, right?

-Leo.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ