mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wright <chris@wirex.com>
To: Frank Davis <fdavis@si.rr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.50 : fs/hugetlbfs/inode.c error
Date: Wed, 27 Nov 2002 16:08:52 -0800	[thread overview]
Message-ID: <20021127160852.A320@figure1.int.wirex.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0211271845410.4018-100000@linux-dev>; from fdavis@si.rr.com on Wed, Nov 27, 2002 at 06:47:23PM -0500

* Frank Davis (fdavis@si.rr.com) wrote:
> 
> fs/hugetlbfs/inode.c: In function `hugetlbfs_delete_inode':
> fs/hugetlbfs/inode.c:212: `security_ops' undeclared (first use in this function)
> fs/hugetlbfs/inode.c:212: (Each undeclared identifier is reported only once
> fs/hugetlbfs/inode.c:212: for each function it appears in.)
> fs/hugetlbfs/inode.c: In function `hugetlbfs_setattr':
> fs/hugetlbfs/inode.c:336: `security_ops' undeclared (first use in this function)

Yup, GregKH missed this one and posted a patch to Linus just as 2.5.50 was
released.  The following patch from GregKH will fix this error.  This is
already in 2.5-bk.

-chris

===== fs/hugetlbfs/inode.c 1.4 vs 1.5 =====
--- 1.4/fs/hugetlbfs/inode.c	Wed Nov 20 03:19:02 2002
+++ 1.5/fs/hugetlbfs/inode.c	Wed Nov 27 15:09:41 2002
@@ -209,7 +209,7 @@
 	if (inode->i_data.nrpages)
 		truncate_hugepages(&inode->i_data, 0);
 
-	security_ops->inode_delete(inode);
+	security_inode_delete(inode);
 
 	clear_inode(inode);
 	destroy_inode(inode);
@@ -333,7 +333,7 @@
 	if (error)
 		goto out;
 
-	error = security_ops->inode_setattr(dentry, attr);
+	error = security_inode_setattr(dentry, attr);
 	if (error)
 		goto out;
 



      reply	other threads:[~2002-11-28  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-27 23:47 Frank Davis
2002-11-28  0:08 ` Chris Wright [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=20021127160852.A320@figure1.int.wirex.com \
    --to=chris@wirex.com \
    --cc=fdavis@si.rr.com \
    --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

all inboxes | Powered by JetHome®