From: Andi Kleen <ak@muc.de>
To: Andrea Arcangeli <andrea@cpushare.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: lcall disappeared? kernel CVS destabilized?
Date: Fri, 14 Jan 2005 02:30:54 +0100 [thread overview]
Message-ID: <m1llawajap.fsf@muc.de> (raw)
In-Reply-To: <20050114010132.GJ5949@dualathlon.random> (Andrea Arcangeli's message of "Fri, 14 Jan 2005 02:01:32 +0100")
Andrea Arcangeli <andrea@cpushare.com> writes:
> I'm porting the seccomp patch to 2.6.10, do you have an idea where lcall
> (i.e. call gates for binary compatibility with other OS) went? I can't
> find it anywhere. Looks like it was dropped but I must be sure of that,
> and especially I must be sure that you don't add it again without me
> noticing that I had to patch it ;). Is lcall definitely dead code that I
> can forget about or am I missing something? Thanks.
hch removed it some time ago because nobody used it anymore (Linux ABI
is not supported on 2.6) and it showed some potential security issues
-Andi
prev parent reply other threads:[~2005-01-14 1:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 1:01 lcall disappeared? kernel CVS destabilized? Andrea Arcangeli
2005-01-14 1:26 ` Andrew Morton
2005-01-14 1:49 ` Andrea Arcangeli
2005-01-14 1:30 ` Andi Kleen [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=m1llawajap.fsf@muc.de \
--to=ak@muc.de \
--cc=andrea@cpushare.com \
--cc=linux-kernel@vger.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.