All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Andy Whitcroft <apw@canonical.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Christoph Hellwig <hch@lst.de>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/1] x86: should 32 bit processes be PER_LINUX32
Date: Tue, 14 Sep 2010 22:31:42 +0400	[thread overview]
Message-ID: <4C8FBF8E.3060503@msgid.tls.msk.ru> (raw)
In-Reply-To: <4C8FBCCA.6060001@zytor.com>

14.09.2010 22:19, H. Peter Anvin wrote:
> On 09/14/2010 09:00 AM, Andy Whitcroft wrote:
>> While testing an x86 64 bit kernel on 32 bit userspace I noticed that I
[...]

Folks, while we're at it, can we also fix the ADDR_LIMIT_3GB personality?
With all current kernels it just does not work, returning EINVAL to the
second execve() call.  It never worked from within a 32bit process, but
that at least can be worked around by introducing a small 64bit helper.
Now that helper does not work too.

Or just remove it altogether, to stop confusing people... :)

(We finally moved our legacy application from oracle8 (which only exist
in 32bit for linux) to oracle10, so this problem has no relevance for
us anymore.  Before it were quite problematic...)

Thanks!

/mjt

      reply	other threads:[~2010-09-14 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-14 16:00 [PATCH 0/1] x86: should 32 bit processes be PER_LINUX32 Andy Whitcroft
2010-09-14 16:00 ` [PATCH 1/1] x86: ensure we correctly advertise 32 bit processes in a 64 bit kernel Andy Whitcroft
2010-09-14 18:19 ` [PATCH 0/1] x86: should 32 bit processes be PER_LINUX32 H. Peter Anvin
2010-09-14 18:31   ` Michael Tokarev [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4C8FBF8E.3060503@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=apw@canonical.com \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.