Paul Jackson wrote: > Andi wrote: >> In this case it's libnuma internally which doesn't check and even if it >> did couldn't do anything because these calls cannot error out. > > Ouch. > > From a quick scan of the libnuma that is in numactl v2.0.1, > it looks to me like libnuma can just exit, without recourse, > in the event of the following errors: I already fixed all of those in the patchkit (in "fix error handling in libnuma"). These were all new in 2.0.0 btw, 1.0.x didn't have them. Only for allocation failure did I add an exit() because that's not really recoverable currently. -Andi -- To unsubscribe from this list: send the line "unsubscribe linux-numa" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
