Linux-Next discussions
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Pekka Enberg <penberg@cs.helsinki.fi>,
	Christoph Lameter <cl@linux-foundation.org>
Cc: linux-next@vger.kernel.org, Alexey Dobriyan <adobriyan@gmail.com>
Subject: linux-next: manual merge of the slab tree
Date: Mon, 3 Nov 2008 15:07:50 +1100	[thread overview]
Message-ID: <20081103150750.87fe762d.sfr@canb.auug.org.au> (raw)

Hi all,

Today's linux-next merge of the slab tree got a conflict in
fs/proc/inode.c between commit 5bcd7ff9e1690dbdbccb2a1cb3c2ea8b8381c435
("proc: proc_init_inodecache() can't fail") from Linus' tree and commit
f7f650b4b85ad364072936db9e6beddcb2ca33b8 ("Filesystem: /proc filesystem
support for slab defrag") from the slab tree.

It is just a context change. I fixed it up (see below) and will carry the
fix for a couple of days (during which time it will hopefully be fixed in
your tree).
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc fs/proc/inode.c
index 2543fd0,54f8137..0000000
--- a/fs/proc/inode.c
+++ b/fs/proc/inode.c
@@@ -106,13 -106,22 +106,21 @@@ static void init_once(void *foo
  	inode_init_once(&ei->vfs_inode);
  }
  
+ static void *proc_get_inodes(struct kmem_cache *s, int nr, void **v)
+ {
+ 	return fs_get_inodes(s, nr, v,
+ 		offsetof(struct proc_inode, vfs_inode));
+ };
+ 
 -int __init proc_init_inodecache(void)
 +void __init proc_init_inodecache(void)
  {
  	proc_inode_cachep = kmem_cache_create("proc_inode_cache",
  					     sizeof(struct proc_inode),
  					     0, (SLAB_RECLAIM_ACCOUNT|
  						SLAB_MEM_SPREAD|SLAB_PANIC),
  					     init_once);
+ 	kmem_cache_setup_defrag(proc_inode_cachep,
+ 				proc_get_inodes, kick_inodes);
 -	return 0;
  }
  
  static const struct super_operations proc_sops = {

             reply	other threads:[~2008-11-03  4:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03  4:07 Stephen Rothwell [this message]
2008-11-03  9:38 ` linux-next: manual merge of the slab tree Pekka Enberg
  -- strict thread matches above, loose matches on Subject: below --
2008-11-03  4:26 Stephen Rothwell
2008-11-03  9:39 ` Pekka Enberg
2008-11-03  4:19 Stephen Rothwell
2008-11-03  4:52 ` KOSAKI Motohiro
2008-11-03  9:39 ` Pekka Enberg
2008-10-21  4:55 Stephen Rothwell
2008-08-13  4:57 Stephen Rothwell
2008-08-13  6:19 ` Pekka Enberg
2008-08-13  7:11   ` Stephen Rothwell
2008-08-13  7:10     ` Pekka Enberg
2008-08-13  7:36       ` Stephen Rothwell
2008-08-13  7:21 ` Pekka Enberg
2008-08-13  7:40   ` Stephen Rothwell

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=20081103150750.87fe762d.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=adobriyan@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=linux-next@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    /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