Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 May 2009 17:58:11 +0100
From:      Ray Kinsella <raykinsella78@gmail.com>
To:        Ryan Stone <rysto32@gmail.com>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: contigmalloc & access protection failure
Message-ID:  <584ec6bb0905100958m1a0ee883h76eaa41eb566e033@mail.gmail.com>
In-Reply-To: <bc2d970905100922s4722d339mc807d210d6d13b86@mail.gmail.com>
References:  <584ec6bb0905100532n36ae97b1rc5e6e31c23bdb44b@mail.gmail.com> <bc2d970905100922s4722d339mc807d210d6d13b86@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 <rysto32@gmail.com> wrote:
> Oh, and you're passing VM_PROT_ALL -- that says "map this
> read/write/execute".=A0 You want VM_PROT_READ
>
> Ryan Stone
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?584ec6bb0905100958m1a0ee883h76eaa41eb566e033>