Sorry, I perhaps didn't said clearly.
As I knwon, if we remove vma from vma tree of task, the SIGSEGV must be got!
but I am not removed them , I just unmapped them. and the SIGSEGV occurs
some times,
not alway.
I doublt on it.
Any clearly idea?
many thanks.
liyu@WAN wrote:
It seem that code in other place jump here to enter kernel. this
is in a anonymous
code area.
At first time, I think this SIGSEGV will trigger by anonymous code
that is swapped,
but I wrote one specical condition check to filte out this sort of
code, IOW, I do
not swap out it. but I still get SIGSEGV.
May be, we can not be release the vma that include code? or, Is
there have some errors
in my words for page fault?
That's right, you cannot release the VMA if the application still
expects to use memory in that area. The page fault handler will
see that no VMA exists in that region and raise a SIGSEGV.
See arch/i386/mm/fault.c:do_page_fault
Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
|
|