Re: [bug-libsigsegv] Re: sigsegv on s390 only giving start address of page in segv handler

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Christian Borntraeger wrote:
> I even think that this cannot be fully solved by looking at the instruction, 
> e.g. you cannot tell which access triggered the fault for instruction with
> two memory accesses (mvc) in the same page.

Sure you can. If it's a "read" fault (i.e. the page has no readable mapping),
you can claim the source address operand is the fault address. Otherwise,
i.e. if it's a "write" fault, the destination address operand is the fault
address.

Bruno
--
To unsubscribe from this list: send the line "unsubscribe linux-s390" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Kernel Development]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite Info]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Linux Media]     [Device Mapper]

  Powered by Linux