From: Ian Kent <raven@themaw.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Miller <davem@davemloft.net>,
thomas@m3y3r.de, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: Linux 3.3-rc4
Date: Tue, 21 Feb 2012 12:52:39 +0800 [thread overview]
Message-ID: <1329799959.2226.32.camel@perseus.themaw.net> (raw)
In-Reply-To: <CA+55aFzVyr_U0-2Df2bqcX7G6DvkEGp=1N+ck4=EHuq=NY0Wkw@mail.gmail.com>
On Mon, 2012-02-20 at 20:17 -0800, Linus Torvalds wrote:
> On Mon, Feb 20, 2012 at 8:02 PM, Ian Kent <raven@themaw.net> wrote:
> >
> > It doesn't but changing it for exiting binaries will break existing
> > binaries that use a workaround.
>
> What existing binaries?
My bad, autofs for one, but obviously when running in compat mode.
And any other user space users, such as the auto_dir package, but I
don't know if that is maintained any more.
>
> > I'm proposing this because the systemd folks were happy to do it this
> > way. But if you would like any other existing user space users to change
> > to using a correctly sized packet then, yes, it isn't what you want to
> > happen.
>
> Existing binaries *do* use the correct size packet - it's the correct
> size for native x86-32!
>
> It's our x86-64 compat layer that is wrong. It's a clear bug. Nothing else.
>
> We don't start making up new interfaces because we have clear bugs: we
> fix the damn bugs.
>
> How could you even sanely do "workarounds"? A x86-32 binary shouldn't
> even be able to *tell* that the kernel is 64-bit. And if it does that
> somehow, we should fix that too!
Sure, not an acceptable excuse I know, but it was too late when I
realized my mistake.
So, as you say, let's fix the bug.
autofs is by far the biggest user and I can manage the change for it and
I can at least post to the auto_dir list (if it still exists) and Thomas
can feedback to the systemd folks.
Then there is the question of how it should be done.
I think the patch attached to your original post needs a little work if
that is to be used. Correct me if I'm wrong but AFAICT there are more
architectures that use 8-byte alignment than just x86-64, such as alpha,
ia64 and ppc64 and I believe they may also be used in a compat mode.
Is there a better way to do this change, anyone?
Ian
next prev parent reply other threads:[~2012-02-21 4:52 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-19 0:27 Linus Torvalds
2012-02-19 13:42 ` Thomas Meyer
2012-02-19 18:45 ` Linus Torvalds
2012-02-19 19:49 ` David Miller
2012-02-19 20:02 ` Linus Torvalds
2012-02-20 3:28 ` Ian Kent
2012-02-21 3:29 ` Ian Kent
2012-02-21 3:38 ` Linus Torvalds
2012-02-21 4:02 ` Ian Kent
2012-02-21 4:17 ` Linus Torvalds
2012-02-21 4:52 ` Ian Kent [this message]
2012-02-21 5:06 ` Linus Torvalds
2012-02-21 5:21 ` Linus Torvalds
2012-02-21 5:27 ` H. Peter Anvin
2012-02-21 5:28 ` H. Peter Anvin
2012-02-21 5:32 ` Linus Torvalds
2012-02-21 5:39 ` Ian Kent
2012-02-21 4:18 ` H. Peter Anvin
2012-02-21 4:22 ` H. Peter Anvin
2012-02-21 13:03 ` Alan Cox
2012-02-21 18:26 ` Use gcc to check exported files [Was: Linux 3.3-rc4] Sam Ravnborg
2012-02-21 18:58 ` Linux 3.3-rc4 Thomas Meyer
2012-02-21 22:07 ` Linus Torvalds
2012-02-21 22:43 ` Linus Torvalds
2012-02-21 23:10 ` Eric Dumazet
2012-02-21 23:19 ` Linus Torvalds
2012-02-24 10:39 ` Jiri Kosina
2012-02-24 16:52 ` Linus Torvalds
2012-02-24 18:01 ` Jiri Kosina
2012-02-24 18:21 ` Linus Torvalds
2012-02-29 8:38 ` Jiri Kosina
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=1329799959.2226.32.camel@perseus.themaw.net \
--to=raven@themaw.net \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®