From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
linux-mm@kvack.org, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH 3/6] bdi: Use refcount_t for reference counting instead atomic_t
Date: Tue, 17 Jul 2018 17:56:30 +0200 [thread overview]
Message-ID: <20180717155630.5propcebpubol6x3@linutronix.de> (raw)
In-Reply-To: <20180716155716.1f7ac43d211133a8cb476637@linux-foundation.org>
On 2018-07-16 15:57:16 [-0700], Andrew Morton wrote:
> > --- a/mm/backing-dev.c
> > +++ b/mm/backing-dev.c
> > @@ -438,10 +438,10 @@ wb_congested_get_create(struct backing_dev_info *bdi, int blkcg_id, gfp_t gfp)
> > if (new_congested) {
> > /* !found and storage for new one already allocated, insert */
> > congested = new_congested;
> > - new_congested = NULL;
> > rb_link_node(&congested->rb_node, parent, node);
> > rb_insert_color(&congested->rb_node, &bdi->cgwb_congested_tree);
> > - goto found;
> > + spin_unlock_irqrestore(&cgwb_lock, flags);
> > + return congested;
> > }
> >
> > spin_unlock_irqrestore(&cgwb_lock, flags);
> > @@ -451,13 +451,13 @@ wb_congested_get_create(struct backing_dev_info *bdi, int blkcg_id, gfp_t gfp)
> > if (!new_congested)
> > return NULL;
> >
> > - atomic_set(&new_congested->refcnt, 0);
> > + refcount_set(&new_congested->refcnt, 1);
> > new_congested->__bdi = bdi;
> > new_congested->blkcg_id = blkcg_id;
> > goto retry;
> >
> > found:
> > - atomic_inc(&congested->refcnt);
> > + refcount_inc(&congested->refcnt);
> > spin_unlock_irqrestore(&cgwb_lock, flags);
> > kfree(new_congested);
> > return congested;
> >
> > ...
> >
>
> I'm not sure that the restructuring of wb_congested_get_create() was
> desirable and it does make the patch harder to review. But it looks
> OK to me.
By `restructuring' you mean the addition of return statement instead
using the goto label in the first hunk? If so, then you would have
refcount_set(&new_congested->refcnt, 0);
refcount_inc(&congested->refcnt);
which is a 0 -> 1 transition and is forbidden by refcount_t. So I had to
avoid this one.
Thank you applying the patches!
You applied the bdi and userns switch from atomic_t to refcount_t.
There were also the patches
[PATCH 4/6] bdi: Use irqsave variant of refcount_dec_and_lock()
[PATCH 6/6] userns: Use irqsave variant of refcount_dec_and_lock()
in the series which make use the irqsave version of
refcount_dec_and_lock(). Did you miss them by chance or skipped them on
purpose?
Sebastian
next prev parent reply other threads:[~2018-07-17 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 20:01 [PATCH 0/6] use irqsafe variant of refcount_dec_and_lock() / atomic_dec_and_lock() Sebastian Andrzej Siewior
2018-07-03 20:01 ` [PATCH 3/6] bdi: Use refcount_t for reference counting instead atomic_t Sebastian Andrzej Siewior
2018-07-16 12:30 ` Sebastian Andrzej Siewior
2018-07-16 22:57 ` Andrew Morton
2018-07-17 15:56 ` Sebastian Andrzej Siewior [this message]
2018-07-03 20:01 ` [PATCH 4/6] bdi: Use irqsave variant of refcount_dec_and_lock() Sebastian Andrzej Siewior
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=20180717155630.5propcebpubol6x3@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).