From: J Sloan <jjs@toyota.com>
To: Cliff Albert <cliff@oisec.net>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Updated Linux kernel preemption patches
Date: Mon, 27 Aug 2001 12:31:57 -0700 [thread overview]
Message-ID: <3B8AA02D.6F7561AB@lexus.com> (raw)
In-Reply-To: <998877465.801.19.camel@phantasy> <20010827093835.A15153@oisec.net>
I get the same error -
RH 7.1 + updates and bits of rawhide -
Cliff Albert wrote:
> On Sun, Aug 26, 2001 at 09:57:43PM -0400, Robert Love wrote:
>
> > Available at:
> >
> > http://tech9.net/rml/linux/patch-rml-2.4.9-preempt-kernel-1
> > http://tech9.net/rml/linux/patch-rml-2.4.8-ac12-preempt-kernel-1
> >
> > for kernel 2.4.9 and 2.4.8-ac12, respectively.
> >
> > This is a straight update of Nigel Gamble's Linux kernel preemption
> > patch from http://kpreempt.sourceforge.net, updated for the above
> > kernels. Thus, this is Nigel's code -- I merely updated it.
> >
> > I am eager to see work done on the patch and to see what its future may
> > be. If you are in any way interested in application latency or
> > real-time support, I suggest you check this out. If you are just
> > curious, its an interesting patch none-the-less.
>
> Kernel won't compile when this patch is applied to 2.4.8-ac12
>
> kernel/kernel.o: In function `mmput':
> kernel/kernel.o(.text+0x1853): undefined reference to `atomic_dec_and_lock'
> kernel/kernel.o: In function `free_uid':
> kernel/kernel.o(.text+0xaea0): undefined reference to `atomic_dec_and_lock'
> fs/fs.o: In function `kill_super':
> fs/fs.o(.text+0x7002): undefined reference to `atomic_dec_and_lock'
> fs/fs.o: In function `dput':
> fs/fs.o(.text+0x13365): undefined reference to `atomic_dec_and_lock'
> fs/fs.o: In function `iput':
> fs/fs.o(.text+0x15ed2): undefined reference to `atomic_dec_and_lock'
>
> --
> Cliff Albert | RIPE: CA3348-RIPE | www.oisec.net
> cliff@oisec.net | 6BONE: CA2-6BONE | icq 18461740
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-08-27 19:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-27 1:57 Updated Linux kernel preemption patches Robert Love
2001-08-27 3:06 ` Daniel Phillips
2001-08-27 3:09 ` Robert Love
2001-08-27 7:38 ` Cliff Albert
2001-08-27 13:46 ` Robert Love
2001-08-27 15:20 ` Cliff Albert
2001-08-27 19:31 ` J Sloan [this message]
2001-08-27 19:44 ` Robert Love
2001-08-27 21:12 ` Andrey Nekrasov
2001-08-27 21:35 ` Robert Love
2001-08-27 21:18 ` Robert Love
2001-08-27 21:24 ` Cliff Albert
2001-08-27 21:40 ` Robert Love
2001-08-27 23:06 ` Andrey Nekrasov
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=3B8AA02D.6F7561AB@lexus.com \
--to=jjs@toyota.com \
--cc=cliff@oisec.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.