linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: bring back /sys/kernel/mm
Date: Sun, 26 Jan 2014 21:02:44 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.1401262053510.1002@eggly.anvils> (raw)
In-Reply-To: <20140127040330.GA17584@windriver.com>

On Sun, 26 Jan 2014, Paul Gortmaker wrote:
> [[PATCH] mm: bring back /sys/kernel/mm] On 26/01/2014 (Sun 18:52) Hugh Dickins wrote:
> 
> > Commit da29bd36224b ("mm/mm_init.c: make creation of the mm_kobj happen
> > earlier than device_initcall") changed to pure_initcall(mm_sysfs_init).
> > 
> > That's too early: mm_sysfs_init() depends on core_initcall(ksysfs_init)
> > to have made the kernel_kobj directory "kernel" in which to create "mm".
> > 
> > Make it postcore_initcall(mm_sysfs_init).  We could use core_initcall(),
> > and depend upon Makefile link order kernel/ mm/ fs/ ipc/ security/ ...
> > as core_initcall(debugfs_init) and core_initcall(securityfs_init) do;
> > but better not.
> 
> Agreed, N+1 is better than link order.  I guess it silently fails then,
> with /sys/kernel/mm missing as the symptom?  I'd booted i386 and ppc
> and didn't spot this, unfortunately...  wondering now if there was a
> hint in dmesg that I simply failed to notice.

No, nothing in dmesg at all: both mm_sysfs_init() and ksm_init()
(it was /sys/kernel/mm/ksm/run that I was looking for) thought
they had succeeded.

Ah, I get it: it's normal to pass NULL parent to kobject_create_and_add(),
that just means create at the root.  And when I look at an unfixed box,
yes, there's /sys/mm with all the right contents.

Given /sys/block and /sys/fs and /sys/kernel, I think /sys/mm is a better
location; but we're a few years too late to be making that change now ;)

Hugh

> 
> > 
> > Signed-off-by: Hugh Dickins <hughd@google.com>
> 
> Acked-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> 
> Thanks,
> Paul.
> 
> > ---
> > 
> >  mm/mm_init.c |    2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > --- 3.13.0+/mm/mm_init.c	2014-01-23 21:51:26.004001378 -0800
> > +++ linux/mm/mm_init.c	2014-01-26 18:06:40.488488209 -0800
> > @@ -202,4 +202,4 @@ static int __init mm_sysfs_init(void)
> >  
> >  	return 0;
> >  }
> > -pure_initcall(mm_sysfs_init);
> > +postcore_initcall(mm_sysfs_init);

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2014-01-27  5:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27  2:52 Hugh Dickins
2014-01-27  4:03 ` Paul Gortmaker
2014-01-27  5:02   ` Hugh Dickins [this message]
2014-01-27  5:29     ` Paul Gortmaker

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=alpine.LSU.2.11.1401262053510.1002@eggly.anvils \
    --to=hughd@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=torvalds@linux-foundation.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