[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130726160853.81f244ba08368e8cecab0c3b@linux-foundation.org>
Date: Fri, 26 Jul 2013 16:08:53 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: monstr@...str.eu
Cc: Rich Felker <dalias@...ifal.cx>,
Michal Simek <michal.simek@...inx.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
James Hogan <james.hogan@...tec.com>,
Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
Frederic Weisbecker <fweisbec@...il.com>,
Rusty Russell <rusty@...tcorp.com.au>,
linux-kernel@...r.kernel.org, Oleg Nesterov <oleg@...hat.com>,
dholsgrove@...inx.com, Al Viro <viro@...IV.linux.org.uk>,
microblaze-uclinux@...e.uq.edu.au,
Thomas Gleixner <tglx@...utronix.de>,
Kees Cook <keescook@...omium.org>
Subject: Re: [microblaze-linux] [RESEND PATCH] microblaze: Fix clone syscall
On Wed, 24 Jul 2013 08:48:27 +0200 Michal Simek <monstr@...str.eu> wrote:
> On 07/24/2013 07:55 AM, Rich Felker wrote:
> > On Wed, Jul 24, 2013 at 07:34:07AM +0200, Michal Simek wrote:
> >> Microblaze was assign to CLONE_BACKWARDS type where
> >> parent tid was passed via 3rd argument.
> >> Microblaze glibc is using 4th argument for it.
> >>
> >> Create new CLONE_BACKWARDS3 type where stack_size is passed
> >> via 3rd argument, parent thread id pointer via 4th,
> >> child thread id pointer via 5th and tls value as 6th
> >> argument
> >
> > I believe this also affects us in musl. What is the motivation for
> > making a configure option that results in there being two incompatible
> > syscall ABIs for the same arch?
> > This sounds like a really bad idea...
>
> This patch fixes bug which was introduced by Al's patch where he moved
> clone implementation from microblaze folder to generic location.
That's important information which was omitted from the changelog.
Please identify the patch which casused this regression (SHA hash and
title), thanks.
--
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