From: Matthew Wilcox <willy@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Yoshinori Sato <ysato@users.sourceforge.jp>,
Rich Felker <dalias@libc.org>,
Linux-sh list <linux-sh@vger.kernel.org>,
Rob Landley <rob@landley.net>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH] sh: remove unneeded constructor.
Date: Sat, 4 Aug 2018 03:51:49 -0700 [thread overview]
Message-ID: <20180804105149.GB3183@bombadil.infradead.org> (raw)
In-Reply-To: <CAMuHMdXsz-+zsxouaLP5tTKA46G34iAACSce+RXrD8AiiQc2+A@mail.gmail.com>
On Sat, Aug 04, 2018 at 12:47:08PM +0200, Geert Uytterhoeven wrote:
> You do want to readd the __GFP_ZERO flag to the second user of PGALLOC_GFP,
> don't you?
I missed that! Probably only relevant for SH-64. But yes ... probably better
to make this explicit then:
+++ b/arch/sh/mm/pgtable.c
@@ -2,8 +2,6 @@
#include <linux/mm.h>
#include <linux/slab.h>
-#define PGALLOC_GFP GFP_KERNEL | __GFP_ZERO
-
static struct kmem_cache *pgd_cachep;
#if PAGETABLE_LEVELS > 2
static struct kmem_cache *pmd_cachep;
@@ -13,6 +11,7 @@ void pgd_ctor(void *x)
{
pgd_t *pgd = x;
+ memset(pgd, 0, USER_PTRS_PER_PGD * sizeof(pgd_t));
memcpy(pgd + USER_PTRS_PER_PGD,
swapper_pg_dir + USER_PTRS_PER_PGD,
(PTRS_PER_PGD - USER_PTRS_PER_PGD) * sizeof(pgd_t));
@@ -32,7 +31,7 @@ void pgtable_cache_init(void)
pgd_t *pgd_alloc(struct mm_struct *mm)
{
- return kmem_cache_alloc(pgd_cachep, PGALLOC_GFP);
+ return kmem_cache_alloc(pgd_cachep, GFP_KERNEL);
}
void pgd_free(struct mm_struct *mm, pgd_t *pgd)
@@ -48,7 +47,7 @@ void pud_populate(struct mm_struct *mm, pud_t *pud, pmd_t *pmd)
pmd_t *pmd_alloc_one(struct mm_struct *mm, unsigned long address)
{
- return kmem_cache_alloc(pmd_cachep, PGALLOC_GFP);
+ return kmem_cache_alloc(pmd_cachep, GFP_KERNEL | __GFP_ZERO);
}
void pmd_free(struct mm_struct *mm, pmd_t *pmd)
next prev parent reply other threads:[~2018-08-04 12:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180731051519.101249-1-ysato@users.sourceforge.jp>
2018-08-01 7:42 ` [PATCH] sh: remove unneeded constructor Geert Uytterhoeven
2018-08-01 11:13 ` Yoshinori Sato
2018-08-04 10:35 ` Matthew Wilcox
2018-08-04 10:47 ` Geert Uytterhoeven
2018-08-04 10:51 ` Matthew Wilcox [this message]
2018-08-05 15:54 ` Rob Landley
2018-08-05 16:32 ` Rich Felker
2018-08-05 22:48 ` Rob Landley
2018-08-05 23:33 ` Rich Felker
2018-08-06 6:57 ` Geert Uytterhoeven
2018-08-06 8:53 ` Arnd Bergmann
2018-08-10 18:18 ` Rob Landley
2020-06-06 16:32 ` Rich Felker
2020-06-06 16:32 ` Rich Felker
2020-06-08 13:01 ` Matthew Wilcox
2020-06-08 13:01 ` Matthew Wilcox
2018-08-01 11:20 ` Matthew Wilcox
2018-08-01 23:02 ` Rich Felker
2018-08-02 2:47 ` Matthew Wilcox
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=20180804105149.GB3183@bombadil.infradead.org \
--to=willy@infradead.org \
--cc=dalias@libc.org \
--cc=geert@linux-m68k.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
--cc=ysato@users.sourceforge.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).