From: Michal Hocko <mhocko@kernel.org>
To: Oscar Salvador <osalvador@suse.de>
Cc: akpm@linux-foundation.org, anshuman.khandual@arm.com,
william.kucharski@oracle.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Jan Kara <jack@suse.cz>,
Hugh Dickins <hughd@google.com>
Subject: Re: [PATCH] mm: Fix __dump_page when mapping->host is not set
Date: Sat, 16 Mar 2019 09:23:54 +0100 [thread overview]
Message-ID: <20190316082354.GF15672@dhcp22.suse.cz> (raw)
In-Reply-To: <20190315143304.pkuvj4qwtlzgm7iq@d104.suse.de>
On Fri 15-03-19 15:33:07, Oscar Salvador wrote:
> On Fri, Mar 15, 2019 at 01:47:33PM +0100, Michal Hocko wrote:
> > diff --git a/mm/debug.c b/mm/debug.c
> > index 1611cf00a137..499c26d5ebe5 100644
> > --- a/mm/debug.c
> > +++ b/mm/debug.c
> > @@ -78,6 +78,9 @@ void __dump_page(struct page *page, const char *reason)
> > else if (PageKsm(page))
> > pr_warn("ksm ");
> > else if (mapping) {
> > + if (PageSwapCache(page))
> > + mapping = page_swap_info(page)->swap_file->f_mapping;
> > +
> > pr_warn("%ps ", mapping->a_ops);
> > if (mapping->host->i_dentry.first) {
> > struct dentry *dentry;
>
> This looks like a much nicer fix, indeed.
If we go this way then we should swap the order and print the mapping
before we alter it.
> I gave it a spin and it works.
Thanks for testing!
> Since the mapping is set during the swapon, I would assume that this should
> always work for swap.
> Although I am not sure if once you start playing with e.g zswap the picture can
> change.
>
> Let us wait for Hugh and Jan.
Yes, I really cannot tell this is really safe. Maybe we want to do the
check for host anyway. Just to be sure.
--
Michal Hocko
SUSE Labs
prev parent reply other threads:[~2019-03-16 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-15 12:18 [PATCH] mm: Fix __dump_page when mapping->host is not set Oscar Salvador
2019-03-15 12:47 ` Michal Hocko
2019-03-15 14:33 ` Oscar Salvador
2019-03-15 17:21 ` Hugh Dickins
2019-03-16 8:34 ` Michal Hocko
2019-03-16 8:23 ` 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=20190316082354.GF15672@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=william.kucharski@oracle.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