linux-kernel - Re: the different effect of system call fork()

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: <1239196128.5031.3.camel@spike.firmix.at>
Date:	Wed, 08 Apr 2009 15:08:48 +0200
From:	Bernd Petrovitsch <bernd@...mix.at>
To:	Sino <szj087@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: the different effect of system call fork()

Hi!

On Wed, 2009-04-08 at 20:53 +0800, Sino wrote:
[...]
> I don't know whether this is the right place for this email, but I

It's probably not.

> post it here since it concerns the system call of fork.
> here is my fwo source code.
> 
> //fork1.cc
[...]
>    if (pid_t pid = fork() < 0)

I don't think that this line does what you want it to do.
Hint: Using a "pid_t" for the boolean result for a comparison seems
strange at best.

	Bernd
-- 
Firmix Software GmbH                   http://www.firmix.at/
mobil: +43 664 4416156                 fax: +43 1 7890849-55
          Embedded Linux Development and Services


--
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/