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: Windows password security audit tool. GUI, reports in PDF.

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

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

On Sun, 2011-06-19 at 17:09 +0200, richard -rw- weinberger wrote:
> 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?

Something about the CLONE_VM flag is breaking things... not sure what,
at this point.  I'm not sure how concerned to be about this... this
syscall is deprecated, so the code isn't really used anyway -- then
again, the fact that it causes userspace code to crash may be an
indication of an issue elsewhere.

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

vfork is replaced by fork (in libc) when the syscall doesn't exist so it
seemed reasonable to make vfork look like fork even when the syscall's
there.  It's worked for us up until now...

/Jonas

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