On Thu, 24 Jan 2002, Shlomi Fish wrote: > We noticed our kernel module OOPSified kernels that used the new VM by > Andrea Archanageli, and we assumed it was still buggy, so we sticked with > the older one (which is by Rik van Riel IIRC). Now, in the last IGLU > meeting I had a talk with Moshe Bar who said, that it was not supposed to > work. > > The reason is that we used kmalloc and if we don't touch the buffer we > allocated for a long time, and then tried to access a pointer to a 5th or > greater page after its start, it is not guaranteed to succeed.
that sounds completely bogus. i presume there was a misunderstanding somewhere. > <rant> > kmalloc is supposed to be similar to the malloc() userland function, which > gives you a dynamically allocated buffer for life. Why does not kmalloc > behaves that way in the new VM? Would it not break compatibility with many > third-party modules, like our own? > </rant> i dont believe it acts this way. fwiw, are you allcoating memory *only* using kmalloc? where does your code oops? > Can anybody clarify this situation? sure, but probably not on this list. you might want to try either kernelnewbies or the linux kernl maling list. -- mulix http://vipe.technion.ac.il/~mulix/ http://syscalltrack.sf.net/ ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
