From: James Morris <jmorris@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
<linux-kernel@vger.kernel.org>, <linux-ia64@vger.kernel.org>,
<sds@epoch.ncsc.mil>
Subject: Re: selinux build failure
Date: Mon, 25 Aug 2003 01:25:48 +1000 (EST) [thread overview]
Message-ID: <Mutt.LNX.4.44.0308250124380.22060-100000@excalibur.intercode.com.au> (raw)
In-Reply-To: <20030824160245.A18526@infradead.org>
On Sun, 24 Aug 2003, Christoph Hellwig wrote:
> Argg, this is b0rked. {asm,linux}/compat.h are for the 32bit compatiblity
> code. 64bit arches don't have fcntl64 - see the #if BITS_PER_LONG == 32
> around sys_fcntl64 in fcntl.c..
Indeed. How about this?
- James
--
James Morris
<jmorris@redhat.com>
diff -urN -X dontdiff linux-2.6.0-test4.orig/security/selinux/hooks.c linux-2.6.0-test4.w1/security/selinux/hooks.c
--- linux-2.6.0-test4.orig/security/selinux/hooks.c 2003-08-23 11:53:14.000000000 +1000
+++ linux-2.6.0-test4.w1/security/selinux/hooks.c 2003-08-25 01:23:11.690432168 +1000
@@ -2057,9 +2057,11 @@
case F_GETLK:
case F_SETLK:
case F_SETLKW:
+#if BITS_PER_LONG == 32
case F_GETLK64:
case F_SETLK64:
case F_SETLKW64:
+#endif
if (!file->f_dentry || !file->f_dentry->d_inode) {
err = -EINVAL;
break;
next prev parent reply other threads:[~2003-08-24 15:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-23 4:27 Randy.Dunlap
2003-08-24 14:49 ` James Morris
2003-08-24 15:02 ` Christoph Hellwig
2003-08-24 15:25 ` James Morris [this message]
[not found] <o4Fj.1rw.9@gated-at.bofh.it>
[not found] ` <o4YO.1Fl.21@gated-at.bofh.it>
2003-08-24 0:21 ` Arnd Bergmann
2003-08-25 16:50 ` Randy.Dunlap
2003-08-26 0:12 ` James Morris
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=Mutt.LNX.4.44.0308250124380.22060-100000@excalibur.intercode.com.au \
--to=jmorris@redhat.com \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=sds@epoch.ncsc.mil \
/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®