From: Tejun Heo <tj@kernel.org>
To: Roman Penyaev <roman.penyaev@profitbricks.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] percpu-refcount: do not forget to rcu_barrier() just before freeing
Date: Thu, 11 Aug 2016 12:29:01 -0400 [thread overview]
Message-ID: <20160811162901.GC2695@mtj.duckdns.org> (raw)
In-Reply-To: <CAJrWOzCjXQ8D=OprqHCH7NXn81-rVqZyjbz6+8mAP=GHgV3_vg@mail.gmail.com>
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
next prev parent reply other threads:[~2016-08-11 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 19:55 Roman Pen
2016-08-10 22:09 ` Tejun Heo
2016-08-11 9:07 ` Roman Penyaev
2016-08-11 16:29 ` Tejun Heo [this message]
2016-08-11 17:29 ` Roman Penyaev
2016-08-15 4:34 ` [lkp] [percpu] e1bd8275fa: xfstests.generic.323.fail kernel test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160811162901.GC2695@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.penyaev@profitbricks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®