From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Paolo Valente <paolo.valente@linaro.org>
Cc: Jens Axboe <axboe@kernel.dk>, Tejun Heo <tj@kernel.org>,
Li Zefan <lizefan@huawei.com>,
Angelo Ruocco <angeloruocco90@gmail.com>,
Dennis Zhou <dennis@kernel.org>,
Josef Bacik <josef@toxicpanda.com>,
Liu Bo <bo.liu@linux.alibaba.com>,
Bart Van Assche <bvanassche@acm.org>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-block <linux-block@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Mark Brown <broonie@kernel.org>,
bfq-iosched@googlegroups.com, oleksandr@natalenko.name,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH 01/12] kernfs: add function to find kernfs_node without increasing ref counter
Date: Tue, 13 Nov 2018 11:35:38 -0800 [thread overview]
Message-ID: <20181113193538.GA5096@kroah.com> (raw)
In-Reply-To: <07A5F685-9D7D-42A7-9A10-73C658F47435@linaro.org>
On Tue, Nov 13, 2018 at 06:53:59PM +0100, Paolo Valente wrote:
>
>
> > Il giorno 12 nov 2018, alle ore 13:28, Greg Kroah-Hartman <gregkh@linuxfoundation.org> ha scritto:
> >
> > On Mon, Nov 12, 2018 at 10:56:21AM +0100, Paolo Valente wrote:
> >> From: Angelo Ruocco <angeloruocco90@gmail.com>
> >>
> >> The kernfs pseudo file system doesn't export any function to only find
> >> a node by name, without also getting a reference on it.
> >> But in some cases it is useful to just locate a kernfs node, while
> >> using it or not depends on some other condition.
> >>
> >> This commit adds a function to just look for a node, without getting
> >> a reference on it.
> >
> > Eeek, that sounds really bad. So you save off a pointer to something,
> > and have no idea if that pointer now really is valid or not? It can
> > instantly disappear right afterwards.
> >
>
> Hi Greg,
> that function is invoked only in functions executed with cgroup_mutex
> held. This guarantees that nothing disappears or becomes
> inconsistent. That's why we decided to go for this optimization,
> instead of doing useless gets&puts pairs. Still, I'm not expert
> enough to state whether it is impossible that, once we have defined
> that function, it may then get used in some unsafe way.
I can guarantee once you define that function, it will be used in an
unsafe way :(
So just don't create it, use the put calls, it's fast and should never
be a performance issue.
> So, I seem to see two options:
> 1) Add a comment on the function, saying that cgroup_mutex must be
> held while invoking it (I guess you won't like this one).
Nope, do not create it.
> 2) Do not define such a new function, and, in the other patches, use
> the already-available find_and_get.
Yes, please do that.
thanks,
greg k-h
next prev parent reply other threads:[~2018-11-13 19:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 9:56 [PATCH 00/12] unify the interface of the proportional-share policy in blkio/io Paolo Valente
2018-11-12 9:56 ` [PATCH 01/12] kernfs: add function to find kernfs_node without increasing ref counter Paolo Valente
2018-11-12 12:28 ` Greg Kroah-Hartman
2018-11-13 1:56 ` Matthew Wilcox
2018-11-13 17:53 ` Paolo Valente
2018-11-13 19:35 ` Greg Kroah-Hartman [this message]
2018-11-12 9:56 ` [PATCH 02/12] cgroup: add hook seq_show_cft with also the owning cftype as parameter Paolo Valente
2018-11-12 9:56 ` [PATCH 03/12] block, cgroup: pass cftype to functions that need to use it Paolo Valente
2018-11-12 9:56 ` [PATCH 04/12] cgroup: link cftypes of the same subsystem with the same name Paolo Valente
2018-11-12 9:56 ` [PATCH 05/12] cgroup: add owner name to cftypes Paolo Valente
2018-11-12 9:56 ` [PATCH 06/12] block, bfq: align min and default weights with cfq Paolo Valente
2018-11-12 9:56 ` [PATCH 07/12] cgroup: make all functions of all cftypes be invoked Paolo Valente
2018-11-12 9:56 ` [PATCH 08/12] block, cfq: allow cgroup files to be shared Paolo Valente
2018-11-12 9:56 ` [PATCH 09/12] block, bfq: use standard file names for the proportional-share policy Paolo Valente
2018-11-12 9:56 ` [PATCH 10/12] block, throttle: allow sharing cgroup statistic files Paolo Valente
2018-11-12 9:56 ` [PATCH 11/12] doc, bfq-iosched: fix a few clerical errors Paolo Valente
2018-11-12 9:56 ` [PATCH 12/12] doc, bfq-iosched: make it consistent with the new cgroup interface Paolo Valente
2018-11-12 9:58 ` [PATCH 00/12] unify the interface of the proportional-share policy in blkio/io Paolo Valente
2018-11-12 10:00 ` Oleksandr Natalenko
2018-11-12 10:14 ` Oleksandr Natalenko
2018-11-12 10:17 ` Paolo Valente
2018-11-12 15:35 ` Jens Axboe
2018-11-12 15:45 ` Paolo Valente
2018-11-12 15:48 ` Jens Axboe
2018-11-12 15:54 ` Josef Bacik
2018-11-12 16:05 ` Jens Axboe
2018-11-15 11:54 ` Angelo Ruocco
[not found] ` <CADiTV-3tSpEMG7EHz3XGvfekNdtN8k_KQiDMtyykgOb81cvO0g@mail.gmail.com>
2018-11-15 15:42 ` Oleksandr Natalenko
2018-11-15 16:30 ` Jens Axboe
2018-11-19 9:46 ` Angelo Ruocco
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=20181113193538.GA5096@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=angeloruocco90@gmail.com \
--cc=axboe@kernel.dk \
--cc=bfq-iosched@googlegroups.com \
--cc=bo.liu@linux.alibaba.com \
--cc=broonie@kernel.org \
--cc=bvanassche@acm.org \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dennis@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=josef@toxicpanda.com \
--cc=linus.walleij@linaro.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=oleksandr@natalenko.name \
--cc=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--cc=ulf.hansson@linaro.org \
/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