From: Dave Chinner <david@fromorbit.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
hch@infradead.org, darrick.wong@oracle.com,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] xfs: handle register_shrinker error
Date: Fri, 24 Nov 2017 09:00:46 +1100 [thread overview]
Message-ID: <20171123220045.GV5858@dastard> (raw)
In-Reply-To: <20171123161137.ncjqskbvdm6dgb3z@dhcp22.suse.cz>
On Thu, Nov 23, 2017 at 05:11:37PM +0100, Michal Hocko wrote:
> On Fri 24-11-17 01:01:10, Tetsuo Handa wrote:
> > Michal Hocko wrote:
> > > On Thu 23-11-17 05:26:33, Christoph Hellwig wrote:
> > > > Looks good,
> > > >
> > > > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > >
> > > Thanks!
> > >
> > > > I can take a stab at the quota one.
> > >
> > > That would be really great!
> > >
> > Again, it does not look good. Since kmem_free() does only kvfree(),
> > nothing will release memory allocated by list_lru_init().
>
> Hmm, you are right. I have (blindly) followed the current code flow
> which is wrong as well. The following should do the trick. Should I
> split that into two patches?
One is fine by me - if we're need to backport one fix, then we need
to backport both :/
> ---
> diff --git a/fs/xfs/xfs_buf.c b/fs/xfs/xfs_buf.c
> index dd0e18af990c..4c6e86d861fd 100644
> --- a/fs/xfs/xfs_buf.c
> +++ b/fs/xfs/xfs_buf.c
> @@ -1815,25 +1815,27 @@ xfs_alloc_buftarg(
> btp->bt_daxdev = dax_dev;
>
> if (xfs_setsize_buftarg_early(btp, bdev))
> - goto error;
> + goto error_free;
>
> if (list_lru_init(&btp->bt_lru))
> - goto error;
> + goto error_free;
>
> if (percpu_counter_init(&btp->bt_io_count, 0, GFP_KERNEL))
> - goto error;
> + goto error_lru;
>
> btp->bt_shrinker.count_objects = xfs_buftarg_shrink_count;
> btp->bt_shrinker.scan_objects = xfs_buftarg_shrink_scan;
> btp->bt_shrinker.seeks = DEFAULT_SEEKS;
> btp->bt_shrinker.flags = SHRINKER_NUMA_AWARE;
> - if (register_shrinker(&btp->bt_shrinker)) {
> - percpu_counter_destroy(&btp->bt_io_count);
> - goto error;
> - }
> + if (register_shrinker(&btp->bt_shrinker))
> + goto error_pcpu;
> return btp;
>
> -error:
> +error_pcpu:
> + percpu_counter_destroy(&btp->bt_io_count);
> +error_lru:
> + list_lru_destroy(&btp->bt_lru);
> +error_free:
> kmem_free(btp);
> return NULL;
That should do the trick.
Acked-by: Dave Chinner <dchinner@redhat.com>
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2017-11-23 22:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 12:08 [PATCH] xfs: handle register_shrinker error Michal Hocko
2017-11-23 13:26 ` Christoph Hellwig
2017-11-23 13:41 ` Michal Hocko
2017-11-23 16:01 ` Tetsuo Handa
2017-11-23 16:11 ` Michal Hocko
2017-11-23 16:17 ` Tetsuo Handa
2017-11-23 16:31 ` Michal Hocko
2017-11-23 22:00 ` Dave Chinner [this message]
2017-11-24 7:39 ` [PATCH v2] " Michal Hocko
2017-11-24 12:03 ` Tetsuo Handa
2017-11-24 12:09 ` Michal Hocko
2017-11-25 23:34 ` Dave Chinner
2017-11-26 2:14 ` Tetsuo Handa
2017-11-27 8:05 ` Michal Hocko
2017-11-27 17:44 ` Darrick J. Wong
2017-11-28 9:35 ` Michal Hocko
2017-11-28 16:39 ` Darrick J. Wong
2017-11-28 19:40 ` Michal Hocko
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=20171123220045.GV5858@dastard \
--to=david@fromorbit.com \
--cc=darrick.wong@oracle.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
/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).