Hi Ryan,
One last thing, thanks for your help,
Can you recommend any articles or books on developing with the FreeBSD
virtually memory manager?
Thanks
Ray Kinsella
On Sun, May 10, 2009 at 5:22 PM, Ryan Stone wrote:
> Oh, and you're passing VM_PROT_ALL -- that says "map this
> read/write/execut
ah I specified VM_PROT_ALL because I though that was "protecting"
against reads/writes and executes.
I had it the wrong way around, it was that VM_PROT that confused me,
my kernel panic works perfectly now thanks.
Regards
Ray Kinsella
On Sun, May 10, 2009 at 5:22 PM, Ryan Stone wrote:
> Oh, and
Oh, and you're passing VM_PROT_ALL -- that says "map this
read/write/execute". You want VM_PROT_READ
Ryan Stone
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "free
You're loading this through kldload? Then I'd imagine that
curthread->td_proc->p_vmspace->vm_map
refers to the vm_map of the kldload process, not the kernel. Try using
kernel_map directly.
Ryan Stone
___
freebsd-hackers@freebsd.org mailing list
http://
Hi all,
I am trying to create a kernel panic with a memory access volition,
the memory I am allocating is physically contiguous and is 2 pages in size,
I then try to use vm_map_protect to set the access flags of the 2nd
page to disables writes,
vm_map_protect returns successful but when I write to
5 matches
Mail list logo
