Re: [PATCH] broken TASK_SIZE for ia32_aout

[Al Viro]

On Sun, May 06, 2012 at 11:48:15AM -0700, H. Peter Anvin wrote:
> Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote:
> >Umm...  Let me restate that question: is there ever a case when it
> >would
> >_not_ be a syscall property?  I.e. when both 64bit and 32bit syscalls
> >are
> >possible for a given process *and* callers of is_compat_task() care
> >about
> >the kind of process and not the kind of syscall?
> >
> >Is e.g. sparc behaviour ("what kind of process it is, regardless of
> >whether
> >we are issuing a 32bit or a 64bit syscall") correct?
> >
> >Sure, on a platform where the possible kind of syscall is a function of
> >process' personality, a thread property can be a used to tell which
> >kind of syscall we are in.

> I would argue Sparc is not correct here but I am not a Sparc expert.

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