Re: copy to suer space

["Luís Henriques" <lhenriques@criticalsoftware.com>]

> There is a time window in which it might get paged out in the mean time but
> it's admittedly a very small window. But that is irrelevant as copy_to_user
> would take care of the page out case by faulting the page back in (that is
> at least my understanding of it).
>
> But that is not the problem I was talking about: Imagine you do
> successfully modify the user space code and AFTER THAT the kernel pages out
> the code and pages it back in later. Your change is then lost without
> trace.
>
> That can easily crash your program depending on what modifications you do
> to it...
>
> Anton

I don't understand... this means that the paging does not save the a code 
segment in memory? (sorry, this question is being done by a newbie...) When a 
page is back to memory, what happens? Is read again from the binary file 
(executable)?

Well... I don't think this will have much impact in my module because what it 
does is:

 - change the code in a process
 - return to the process
 - next time the process is scheduled, the code will be stored again in the CS

So, I don't think that the paging will really became a problem as this shall 
be quiet fast! The idea of changing the code is just to insert a delay in a 
process, but leaving the process «burning» CPU time...

The point is: I'm not changing the code because of an obscure (to me...) 
reason. You told me that the code segment may be protected and I'm 
investigating on that but I would like to be sure that the kernel has no 
acess to a user CS...

-- 
Luís Henriques