public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH] gfs2: Put bitmap buffers in put_super
Date: Fri, 23 Nov 2018 14:18:24 -0500	[thread overview]
Message-ID: <20181123191824.GF1917@sasha-vm> (raw)
In-Reply-To: <20181119162232.15253-1-agruenba@redhat.com>

On Mon, Nov 19, 2018 at 05:22:32PM +0100, Andreas Gruenbacher wrote:
>commit 10283ea525d30f2e99828978fd04d8427876a7ad upstream.
>
>gfs2_put_super calls gfs2_clear_rgrpd to destroy the gfs2_rgrpd objects
>attached to the resource group glocks.  That function should release the
>buffers attached to the gfs2_bitmap objects (bi_bh), but the call to
>gfs2_rgrp_brelse for doing that is missing.
>
>When gfs2_releasepage later runs across these buffers which are still
>referenced, it refuses to free them.  This causes the pages the buffers
>are attached to to remain referenced as well.  With enough mount/unmount
>cycles, the system will eventually run out of memory.
>
>Fix this by adding the missing call to gfs2_rgrp_brelse in
>gfs2_clear_rgrpd.
>
>(Also fix a gfs2_rgrp_relse -> gfs2_rgrp_brelse typo in a comment.)
>
>Fixes: 39b0f1e92908 ("GFS2: Don't brelse rgrp buffer_heads every allocation")
>Cc: stable@vger.kernel.org # v4.9
>Signed-off-by: Andreas Gruenbacher <agruenba@redhat.com>

I've queued both patches to their appropriate branches, thank you.

--
Thanks,
Sasha

  reply	other threads:[~2018-11-24  6:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-19 16:22 [PATCH] gfs2: Put bitmap buffers in put_super Andreas Gruenbacher
2018-11-23 19:18 ` Sasha Levin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-11-19 16:24 Andreas Gruenbacher

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=20181123191824.GF1917@sasha-vm \
    --to=sashal@kernel.org \
    --cc=agruenba@redhat.com \
    --cc=stable@vger.kernel.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