Re: [PATCH percpu/for-3.11 1/2] percpu-refcount: add __must_check topercpu_ref_init() and don't use ACCESS_ONCE() in percpu_ref_kill_rcu()
From: Tejun Heo
Date: Wed Jun 19 2013 - 22:23:26 EST
On Thu, Jun 20, 2013 at 10:29:51AM +0930, Rusty Russell wrote:
> Now seems to get abused by lazy coders who blame users for their own
> broken APIs. And Ubuntu, who turn it on by default in their gcc when
> optimizing. Yeah, it's a sore point :)
How is the API broken? It is a function which either succeeds or
fails and, if it fails during boot, like any other allocation failures
during boot, the boot fails. It's not different from kmalloc()
returning NULL on failure.
> if (system(command))
It *does* matter.
> Sorry, I was unclear. If you fail the percpu allocation, you have a
> counter which is always in atomic mode.
> This saves everyone a headache. init doesn't fail, no poorly-tested
> failure paths, no whining Rusty.
How does that save a headache? It *should* fail if allocation fails.
Having untraceable persistent slow down after heavy memory pressure is
no fun to track down. If you're worried about not being able to
detect bugs in error path, the right thing to do would be inducing
allocation failures regularly so that those paths can be tested, which
we already do.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/