linux-kernel - Re: [PATCH 10/19] OpenRISC: System calls

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BANLkTiniGVKrCJXcjBGdmQdqsbfOZ_-agw@mail.gmail.com>
Date:	Sun, 19 Jun 2011 17:09:54 +0200
From:	richard -rw- weinberger <richard.weinberger@...il.com>
To:	Jonas Bonn <jonas@...thpole.se>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 10/19] OpenRISC: System calls

On Sun, Jun 19, 2011 at 1:43 PM, Jonas Bonn <jonas@...thpole.se> wrote:
> +asmlinkage int _sys_vfork(struct pt_regs *regs)
> +{
> +       /* This doesn't seem to work */
> +//        return do_fork(CLONE_VFORK | CLONE_VM | SIGCHLD, regs->sp, regs, 0, NULL, NULL);

Just being curious, why does that not work?

> +       /* This works */
> +        return do_fork(SIGCHLD, regs->sp, regs, 0, NULL, NULL);

This looks very odd.

> +}

-- 
Thanks,
//richard
--
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/