From: sav@bcs.zp.ua (Andrew V. Samoilov)
To: k3ph@dxis.monroe.pa.us, linux-kernel@vger.kernel.org
Subject: iBCS with 2.2.19 kernel
Date: Wed, 11 Apr 2001 10:29:22 +0300 (EEST) [thread overview]
Message-ID: <200104110729.KAA02201@pif.bcs.zp.ua> (raw)
On 2001-03-27 08:39:32 PST Bob Schreibmaier k3ph@dxis.monroe.pa.us write
to comp.os.linux.misc
> I just compiled the 2.2.19 kernel with gcc 2.95.3.
> Compiles and runs just fine. I recompiled the
> iBCS 2.1 module and it compiles just fine, too.
> However, when I try to insmod iBCS it complains
> about variable strlen_user undefined.
>
> Everything works fine under 2.2.18.
>
> Anybody else see this? Anybody know how to fix this?
>
> TIA.
This night I also had same problem. But iBCS does not work for me from 2.2.18.
I write a patch, and it seems everithing works fine for me.
Can you test this patch ?
With best wishes,
Andrew.
diff -rup ibcs/iBCSemul/binfmt_lib.c ibcs-2219/iBCSemul/binfmt_lib.c
--- ibcs/iBCSemul/binfmt_lib.c Sat Jul 4 01:22:11 1998
+++ ibcs-2219/iBCSemul/binfmt_lib.c Wed Apr 11 02:08:12 2001
@@ -12,6 +12,9 @@
#include <asm/pgtable.h>
+#if LINUX_VERSION_CODE > 0x020212 /* > 2.2.18 */
+#define strlen_user(p) strnlen_user((p), LONG_MAX)
+#endif
unsigned long *
create_ibcs_tables(char *p, struct linux_binprm *bprm, int ibcs)
diff -rup ibcs/include/ibcs/ibcs.h ibcs-2219/include/ibcs/ibcs.h
--- ibcs/include/ibcs/ibcs.h Thu Nov 5 23:50:32 1998
+++ ibcs-2219/include/ibcs/ibcs.h Wed Apr 11 02:07:40 2001
@@ -43,9 +43,11 @@ do_revalidate(struct dentry *dentry)
return 0;
}
-
typedef int (*sysfun_p)();
+#if LINUX_VERSION_CODE > 0x020212 /* > 2.2.18 */
+#define strlen_user(p) strnlen_user ((p), LONG_MAX)
+#endif
extern sysfun_p sys_call_table[];
reply other threads:[~2001-04-11 7:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200104110729.KAA02201@pif.bcs.zp.ua \
--to=sav@bcs.zp.ua \
--cc=k3ph@dxis.monroe.pa.us \
--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®