From: "H. Peter Anvin" <hpa@zytor.com>
To: David Miller <davem@davemloft.net>
Cc: viro@ZenIV.linux.org.uk, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, ralf@linux-mips.org
Subject: Re: [PATCH] broken TASK_SIZE for ia32_aout
Date: Sun, 06 May 2012 13:51:30 -0700 [thread overview]
Message-ID: <af01067e-5a22-44a8-acb1-368e45dbb06c@email.android.com> (raw)
In-Reply-To: <20120506.163243.1653904376439925642.davem@davemloft.net>
No. The input layer exports pointers in structures on the read/write paths, and bitmasks encoded in ASCII strings which depend on sizeof(long). The stupid... it burns...
David Miller <davem@davemloft.net> wrote:
>From: "H. Peter Anvin" <hpa@zytor.com>
>Date: Sun, 06 May 2012 11:48:15 -0700
>
>> I would argue Sparc is not correct here but I am not a Sparc expert.
>
>I can easily make sparc take on the x86 behavior if things like the
>input layer really need it.
>
>However, isn't the input layer case a case where compat==native
>on anything other than x86 because it's a u64 alignment issue?
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2012-05-06 20:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 16:20 [PATCH] broken TASK_SIZE for ia32_aout Al Viro
2012-05-06 17:16 ` Linus Torvalds
2012-05-06 17:37 ` H. Peter Anvin
2012-05-06 17:54 ` Al Viro
2012-05-06 17:56 ` Al Viro
2012-05-06 17:58 ` H. Peter Anvin
2012-05-06 18:46 ` Al Viro
2012-05-06 18:48 ` H. Peter Anvin
2012-05-06 19:58 ` Al Viro
2012-05-06 20:32 ` David Miller
2012-05-06 20:51 ` H. Peter Anvin [this message]
2012-05-06 23:40 ` David Miller
2012-05-06 23:48 ` H. Peter Anvin
2012-05-07 2:56 ` David Miller
2012-05-07 3:05 ` H. Peter Anvin
2012-05-06 23:32 ` Al Viro
2012-05-06 23:38 ` David Miller
2012-05-07 0:13 ` Al Viro
2012-05-07 0:24 ` Al Viro
2012-05-06 17:23 ` [tip:x86/urgent] x86, compat: Correct broken TASK_SIZE for ia32 a. out binaries tip-bot for Al Viro
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=af01067e-5a22-44a8-acb1-368e45dbb06c@email.android.com \
--to=hpa@zytor.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@ZenIV.linux.org.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox