From owner-freebsd-alpha Sat Jun 24 23:50:43 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from cara.sonn.com (cara.sonn.com [206.79.239.6]) by hub.freebsd.org (Postfix) with ESMTP id 25DED37B5D2 for ; Sat, 24 Jun 2000 23:50:41 -0700 (PDT) (envelope-from gersh@cara.sonn.com) Received: from localhost (gersh@localhost) by cara.sonn.com (8.9.3/8.9.3) with ESMTP id XAA05661; Sat, 24 Jun 2000 23:38:30 -0700 (PDT) Date: Sat, 24 Jun 2000 23:38:30 -0700 (PDT) From: Gerry Bash To: Matthew Jacob Cc: freebsd-alpha@FreeBSD.ORG Subject: Re: Alpha memory managment fault questions In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Oh good point. I changed it to use a copyinstr and all works fine, Thanks alot. On Sat, 24 Jun 2000, Matthew Jacob wrote: > > What makes you think uap->fname is in the kernel's address space? > The pointer uap points to arguments that are in user space. > > Coincidentally on some platforms or implementations you can refer to them > directly in the part of the kernel that is in a direct call path from a > syscall. But this is not guaranteed. In fact, the PDP-11/{45,70} > implementation of Unix had user and kernel in completely different address > spaces that required the use of special instructions to copy bytes between > them (e.g., MFPD (move from previous data space)). > > If you want to print fname in the kernel, what function do you want to use > to assist in printing it? > > [ hint- you should follow the call path to namei from execve ] > > -matt > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message