linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Michal Hocko <mhocko@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
	Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH] mm,fs: Split dump_mapping() out from dump_page()
Date: Mon, 22 Nov 2021 13:36:06 +0000	[thread overview]
Message-ID: <YZucxp+6g7fRhcgS@casper.infradead.org> (raw)
In-Reply-To: <YZtCpK2ZsV0qLm6+@dhcp22.suse.cz>

On Mon, Nov 22, 2021 at 08:11:32AM +0100, Michal Hocko wrote:
> On Sun 21-11-21 12:10:56, Matthew Wilcox wrote:
> > dump_mapping() is a big chunk of dump_page(), and it'd be handy to be
> > able to call it when we don't have a struct page.  Split it out and move
> > it to fs/inode.c.  Take the opportunity to simplify some of the debug
> > messages a little.
> 
> Makes sense. I haven't checked the head files inclusion side of this but
> I suspect mm heads do include uaccess.h. Not sure inode.c does as well.

It does ... convolutedly:

linux/fs.h
linux/percpu-rwsem.h
linux/rcuwait.h
linux/sched/signal.h
linux/sched/task.h
linux/uaccess.h

There may be shorter paths to including that file, but that's the
one that's actually used according to cpp.  fs/inode.c includes linux/mm.h,
so it also gets it through

linux/pgtable.h
x86/include/asm/pgtable.h
x86/include/asm/pkru.h
x86/include/asm/fpu/xstate.h

which is probably not how you think the mm files get uaccess.h, but
again, that's the first way that cpp tells me it gets pulled in.  Our
header files remain a mess.

> > Signed-off-by: Matthew Wilcox (Oracle) <willy@infradead.org>
> 
> Acked-by: Michal Hocko <mhocko@suse.com>

Thanks!


  reply	other threads:[~2021-11-22 13:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-21 12:10 [PATCH] mm,fs: Split dump_mapping() out from dump_page() Matthew Wilcox (Oracle)
2021-11-22  7:11 ` Michal Hocko
2021-11-22 13:36   ` Matthew Wilcox [this message]
2021-12-23  5:12 ` William Kucharski

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=YZucxp+6g7fRhcgS@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    /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).