Date: Fri, 28 Jan 2005 20:23:55 -0800
From: Om <okuttan@netd.com>
To: Rock Gordon <rockgordon@yahoo.com>
Cc: Jan Hudec <bulb@ucw.cz>, linux-kernel@vger.kernel.org,
       kernelnewbies@nl.linux.org, Bernd Petrovitsch <bernd@firmix.at>
Subject: Re: userspace vs. kernelspace address
Message-ID: <20050129042355.GA5527@netd.com>
Reply-To: Om <okuttan@netd.com>
References: <20050128075209.GA14153@vagabond> <20050128214051.34768.qmail@web41411.mail.yahoo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20050128214051.34768.qmail@web41411.mail.yahoo.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 891
Lines: 22

On Fri, Jan 28, 2005 at 01:40:51PM -0800, Rock Gordon wrote:
> Hi everbody,
> 
> Thanks for your replies.
> 
> However I think my copy_to_user and copy_from_user are
> failing since the kernel-mode thread is copying data
> into another process's address space, and I am not
> sure how to do this. Do the get_fs() and set_fs()
> combinations let you do that? If not, then how do I do
My idea is on kernel thread is limited. But I think it is not possible to
any userspace address from any kernel thread because they do not have access
to it. Their proc_struct->mm field is empty.
I am not sure whether set_fs and get_fs help in this case.

HTH,
Om
-
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/