public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	jsipek@cs.sunysb.edu
Cc: Eric Whitney <eric.whitney@hp.com>
Subject: [PATCH 2.6.21-mm1]  remove unionfs reference to SLAB_CTOR_VERIFY
Date: Mon, 07 May 2007 11:22:32 -0400	[thread overview]
Message-ID: <1178551352.5079.25.camel@localhost> (raw)

With unionfs included as a module, 2.6.21-mm1 build broke with:

fs/unionfs/super.c: In function ‘init_once’:
fs/unionfs/super.c:822: error: ‘SLAB_CTOR_VERIFY’ undeclared (first use in this function)
fs/unionfs/super.c:822: error: (Each undeclared identifier is reported only oncefs/unionfs/super.c:822: error: for each function it appears in.)

Looks like it missed the removal of SLAB_CTOR_VERIFY.  

This patch matches how the situation was addressed elsewhere
throughout the kernel.  Fixes the problem for me...

Signed-off-by:  Lee Schermerhorn <lee.schermerhorn@hp.com>

 fs/unionfs/super.c |    3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

Index: Linux/fs/unionfs/super.c
===================================================================
--- Linux.orig/fs/unionfs/super.c	2007-05-07 10:00:21.000000000 -0400
+++ Linux/fs/unionfs/super.c	2007-05-07 10:40:51.000000000 -0400
@@ -819,8 +819,7 @@ static void init_once(void *v, struct km
 {
 	struct unionfs_inode_info *i = v;
 
-	if ((flags & (SLAB_CTOR_VERIFY | SLAB_CTOR_CONSTRUCTOR)) ==
-	    SLAB_CTOR_CONSTRUCTOR)
+	if (flags & SLAB_CTOR_CONSTRUCTOR)
 		inode_init_once(&i->vfs_inode);
 }
 



             reply	other threads:[~2007-05-07 15:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 15:22 Lee Schermerhorn [this message]
2007-05-07 17:16 ` [PATCH 2.6.21-mm1] remove unionfs reference to SLAB_CTOR_VERIFY Josef Sipek
2007-05-07 17:27   ` Lee Schermerhorn

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=1178551352.5079.25.camel@localhost \
    --to=lee.schermerhorn@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric.whitney@hp.com \
    --cc=jsipek@cs.sunysb.edu \
    --cc=linux-kernel@vger.kernel.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