From: Michal Hocko <mhocko@kernel.org>
To: kpark3469@gmail.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
dan.j.williams@intel.com, vinmenon@codeaurora.org, jack@suse.cz,
Sahara <keun-o.park@darkmatter.ae>
Subject: Re: [PATCH] mm: clean up page_is_poisoned in linux/mm.h
Date: Mon, 4 Jun 2018 08:46:04 +0200 [thread overview]
Message-ID: <20180604064604.GC19202@dhcp22.suse.cz> (raw)
In-Reply-To: <1528014138-27674-1-git-send-email-kpark3469@gmail.com>
On Sun 03-06-18 12:22:18, kpark3469@gmail.com wrote:
> From: Sahara <keun-o.park@darkmatter.ae>
>
> When bd33ef36("mm: enable page poisoning early at boot") got rid of
> the PAGE_EXT_DEBUG_POISON, page_is_poisoned in the header left
> behind. This patch cleans up the leftovers under the table.
Acked-by: Michal Hocko <mhocko@suse.com>
Btw. we tend to use abbrev = 12 for sha1 references.
> Signed-off-by: Sahara <keun-o.park@darkmatter.ae>
> ---
> include/linux/mm.h | 2 --
> 1 file changed, 2 deletions(-)
>
> diff --git a/include/linux/mm.h b/include/linux/mm.h
> index c6fa9a2..a53b0ad 100644
> --- a/include/linux/mm.h
> +++ b/include/linux/mm.h
> @@ -2522,12 +2522,10 @@ extern int apply_to_page_range(struct mm_struct *mm, unsigned long address,
> #ifdef CONFIG_PAGE_POISONING
> extern bool page_poisoning_enabled(void);
> extern void kernel_poison_pages(struct page *page, int numpages, int enable);
> -extern bool page_is_poisoned(struct page *page);
> #else
> static inline bool page_poisoning_enabled(void) { return false; }
> static inline void kernel_poison_pages(struct page *page, int numpages,
> int enable) { }
> -static inline bool page_is_poisoned(struct page *page) { return false; }
> #endif
>
> #ifdef CONFIG_DEBUG_PAGEALLOC
> --
> 2.7.4
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2018-06-04 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 8:22 [PATCH] mm: clean up page_is_poisoned in linux/mm.h kpark3469
2018-06-04 6:46 ` Michal Hocko [this message]
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=20180604064604.GC19202@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=keun-o.park@darkmatter.ae \
--cc=kpark3469@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vinmenon@codeaurora.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;
as well as URLs for NNTP newsgroup(s).