public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: [PATCH] setrlimit/getrlimit
Date: Wed, 15 Dec 1999 08:04:00 -0000	[thread overview]
Message-ID: <19991215170722.M822@mff.cuni.cz> (raw)
In-Reply-To: <19991215164633.A30703@Wotan.suse.de>

> Jakub, I changed the sparc/bits/resouces.h file as you suggested,
> sparc32 uses signed long, sparc64 unsigned long. Could you please
> look at the patch ?

I'll wait until we get to consensus with Davem and I do the kernel side.

> I have one problem with this: What happens if somebody compiles
> his sparc64 binaries with the new header files and runs for example
> linux 2.2.5 ? This kernel doesn't reject negative rlimit values.

No problem. He will not do it. sparc64 userland will be officially supported
with 2.3.latest and later. E.g. up to 2.3.18 or when was it any 64bit task
can set its page tables as it wants because it can access its VPTE area, so
enabling BINFMT_ELF on those kernels is a security issue. Also, several
other bugs have been fixed in 2.3, so 64bit userland would not be usable
anyway.

Cheers,
    Jakub
___________________________________________________________________
Jakub Jelinek | jakub@redhat.com | http://sunsite.mff.cuni.cz/~jj
Linux version 2.3.26 on a sparc64 machine (1343.49 BogoMips)
___________________________________________________________________

      reply	other threads:[~1999-12-15  8:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-15  7:46 Thorsten Kukuk
1999-12-15  8:04 ` Jakub Jelinek [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=19991215170722.M822@mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=kukuk@suse.de \
    --cc=libc-hacker@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).