DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=IaJ1bVm6zYbujavaB+6JrkuXcbkVsCEKos1kmZ6wEjJ9vTXcAF9KftreHt/foCZTj0+ITk5WGYjA+siRQ1ssTWh1ibBRoSQOizTKiEQbhqs1LbFCDNeakxgZUD24pQ/YfdjE+a3gWKoEEB8IOj3Ms21yBFHgCBtFcg74cKTMpdM=
Message-ID: <a36005b50602071123r8179c7di8e95bf0a336f1b0c@mail.gmail.com>
Date: Tue, 7 Feb 2006 11:23:42 -0800
From: Ulrich Drepper <drepper@gmail.com>
To: Jeff Dike <jdike@addtoit.com>
Subject: Re: [PATCH 2/8] UML - Define jmpbuf access constants
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
       user-mode-linux-devel@lists.sourceforge.net
In-Reply-To: <20060207185707.GB6841@ccure.user-mode-linux.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <200602070223.k172NpJa009654@ccure.user-mode-linux.org>
	 <a36005b50602070937h60e35294q1dbef2c21f2fb50d@mail.gmail.com>
	 <20060207185707.GB6841@ccure.user-mode-linux.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 904
Lines: 25

On 2/7/06, Jeff Dike <jdike@addtoit.com> wrote:
> Nope, that would be the next step if this turned out to be untenable,
> which I guess it is.

You have to do it if you want to keep using the setjmp interface.


> You're actually encrypting them somehow?  How?  And why?

For security reasons.


> Is there a reason there can't be an API for looking at the contents of
> a jmp_buf?

It's not needed.  There is no reason to look at the content of the
struct except if you do something which isn't guaranteed by the spec. 
I'll definitely not add such an interface.  If you need this
functionality, implement it yourself.  setjmp is most likely overkill
anyway.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/