From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, bob.liu@oracle.com,
sjenning@linux.vnet.ibm.com
Subject: + zbud-add-to-mm-init-under_reclaim.patch added to -mm tree
Date: Thu, 13 Jun 2013 12:25:03 -0700 [thread overview]
Message-ID: <51ba1c8f.EesvsSQ4XHYyea6m%akpm@linux-foundation.org> (raw)
Subject: + zbud-add-to-mm-init-under_reclaim.patch added to -mm tree
To: sjenning@linux.vnet.ibm.com,bob.liu@oracle.com
From: akpm@linux-foundation.org
Date: Thu, 13 Jun 2013 12:25:03 -0700
The patch titled
Subject: zswap: init under_reclaim
has been added to the -mm tree. Its filename is
zbud-add-to-mm-init-under_reclaim.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
The -mm tree is included into linux-next and is updated
there every 3-4 working days
------------------------------------------------------
From: Seth Jennings <sjenning@linux.vnet.ibm.com>
Subject: zswap: init under_reclaim
Bob Liu reported a memory leak in zswap. This was due to the
under_reclaim field in the zbud header not being initialized
to 0, which resulted in zbud_free() not freeing the page
under the false assumption that the page was undergoing
zbud reclaim.
This patch properly initializes the under_reclaim field.
Signed-off-by: Seth Jennings <sjenning@linux.vnet.ibm.com>
Reported-by: Bob Liu <bob.liu@oracle.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/zbud.c | 1 +
1 file changed, 1 insertion(+)
diff -puN mm/zbud.c~zbud-add-to-mm-init-under_reclaim mm/zbud.c
--- a/mm/zbud.c~zbud-add-to-mm-init-under_reclaim
+++ a/mm/zbud.c
@@ -138,6 +138,7 @@ static struct zbud_header *init_zbud_pag
zhdr->last_chunks = 0;
INIT_LIST_HEAD(&zhdr->buddy);
INIT_LIST_HEAD(&zhdr->lru);
+ zhdr->under_reclaim = 0;
return zhdr;
}
_
Patches currently in -mm which might be from sjenning@linux.vnet.ibm.com are
linux-next.patch
mm-remove-compressed-copy-from-zram-in-memory.patch
mm-remove-compressed-copy-from-zram-in-memory-fix.patch
mm-remove-compressed-copy-from-zram-in-memory-fix-2.patch
mm-remove-compressed-copy-from-zram-in-memory-fix-2-fix.patch
zbud-add-to-mm.patch
zbud-add-to-mm-init-under_reclaim.patch
zswap-add-to-mm.patch
zswap-add-documentation.patch
reply other threads:[~2013-06-13 19:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=51ba1c8f.EesvsSQ4XHYyea6m%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bob.liu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=sjenning@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).