On Wed, 2006-05-10 at 16:42 -0700, Christoph Lameter wrote:
> Seems that the code is not modifying x86 code but all code.
Right. It's definitely broken in that regard. I sent it out in this
condition so the patch was small, easy to review, and my approach would
be easy to see.
> An app should be getting an out of memory error and not a SIGBUS when
> running out of memory.
>
> I thought we fixed the SIGBUS problems and were now reporting out of
> memory? If there still is an issue then we better fix out of memory
> handling. Provide a way for the app to trap OOM conditions?
Yes, the SIGBUS issues are "fixed". Now the application is killed
directly via VM_FAULT_OOM so it is not possible to handle the fault from
userspace. For my libhugetlbfs-based fallback approach, I needed to
patch the kernel so that SIGBUS was delivered to the process like in the
days of old.
--
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center
-
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]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
