mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@ns.caldera.de>
To: joerg@hydrops.han.de (Joerg Ahrens)
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] sys_modify_ldt extension (default_ldt)
Date: Mon, 11 Jun 2001 14:19:18 +0200	[thread overview]
Message-ID: <200106111219.f5BCJI430936@ns.caldera.de> (raw)
In-Reply-To: <m158sRu-0009RiC@hydrops.han.de>

Hi Joerg,

In article <m158sRu-0009RiC@hydrops.han.de> you wrote:
> Hi,
>
> I am trying to integrate binfmt_xout.c into kernel 2.4 as part of the 
> linux-abi project (formerly known as iBCS). For old Xenix 286 binaries the 
> lcall7 gate needs to part of the LDT.
>
> In kernels 2.0 sys_modify_ldt(0,...) used to return the default_ldt (with 
> lcall7 gate) if there were no segments set up. This behaviour changed in 
> kernels 2.2 . As a result of a discussion with Linus, David Bruce wrote a 
> patch for binfmt_xout.c tweaking with gdt and current->tss.ldt to get the
> address of default_ldt. This patch does not work any more with kernels 2.4
> as tss vanished from task_struct. 
>
> I do see 4 ways to cope with this problem:
>
> a) extend sys_modify_ldt with a function to retrieve the default_ldt. I did 
>    this for testing (see attached diff for arch/i386/kernel/ldt.c ).

Looks sane to me.

> b) do some work an Davids patch but this is kind of magic for me :-)
>    (see attached default_ldt patch)
>
> c) loose the option to compile binfmt_xout (and the rest of linux-abi) as 
>    module and simply use the symbol default_ldt. I dint't try that.

As the linux-abi maintainer I do not think that's a good idea..

> d) Forget about those old fashioned 286 binaries. This option will make some
>    linux users feel sad, as they run these progs for their daily business.

If possible at all I'll vote for having 286 support.

I'll integrate the patch into the linux-abi tree if you also send me the
other changes (mostly binfmt_xout.c changes I suppose).

	Christoph

-- 
Of course it doesn't work. We've performed a software upgrade.

      reply	other threads:[~2001-06-11 12:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-09 23:47 Joerg Ahrens
2001-06-11 12:19 ` Christoph Hellwig [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=200106111219.f5BCJI430936@ns.caldera.de \
    --to=hch@ns.caldera.de \
    --cc=joerg@hydrops.han.de \
    --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 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®