Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1460663

Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier() just before freeing

From Tejun Heo <tj@kernel.org>
Newsgroups linux.kernel
Subject Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier() just before freeing
Date 2016-08-11 18:30 +0200
Message-ID <s511N-6al-69@gated-at.bofh.it> (permalink)
References <s4HPt-16w-45@gated-at.bofh.it> <s4JRf-2Dd-7@gated-at.bofh.it> <s4U9X-1Pt-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hello, Roman.

On Thu, Aug 11, 2016 at 11:07:14AM +0200, Roman Penyaev wrote:
> Yes, exactly, this is an illegal operation.  But it is not more illegal
> than calling kill() twice or reinit() when counter is not yet zero.
> And those illegals are covered with warnings, which can be observed
> for example with this freeze/unfreeze blk-mq bug.

I have no objections about adding warnings for these conditions;
however, adding rcu barrier to mask illegal usages is a very different
thing.  That adds a lot of unnecessary latency to the exit function
and makes it unusable from non-sleepable contexts.

Thanks.

-- 
tejun

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier()  just before freeing Tejun Heo <tj@kernel.org> - 2016-08-11 00:10 +0200
  Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier()  just before freeing Roman Penyaev <roman.penyaev@profitbricks.com> - 2016-08-11 11:10 +0200
    Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier()  just before freeing Tejun Heo <tj@kernel.org> - 2016-08-11 18:30 +0200
      Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier()  just before freeing Roman Penyaev <roman.penyaev@profitbricks.com> - 2016-08-11 19:40 +0200

csiph-web