From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "François Cami" <stilgar2k@wanadoo.fr>
Cc: joeja@mindspring.com, linux-kernel@vger.kernel.org
Subject: Re: loop back broken in 2.2.14
Date: Sun, 11 Nov 2001 16:38:17 -0500 [thread overview]
Message-ID: <3BEEEFC9.4F245772@mandrakesoft.com> (raw)
In-Reply-To: <3BEEED3E.58867BFE@mindspring.com> <3BEEEF1E.8050306@wanadoo.fr>
François Cami wrote:
>
> Joe wrote:
>
> > compile 2.2.14.
> >
> > Then
> >
> > # modprobe -a loop
> > /lib/modules/2.4.14/kernel/drivers/block/loop.o: unresolved symbol
> > deactivate_page
> > /lib/modules/2.4.14/kernel/drivers/block/loop.o: insmod
> > /lib/modules/2.4.14/kernel/drivers/block/loop.o failed
> > /lib/modules/2.4.14/kernel/drivers/block/loop.o: insmod loop failed
> >
> > do recursive grep through kernel tree:
> >
> > # rgrep -rl deactivate_page *
> > drivers/block/loop.c
> > drivers/block/loop.o
> >
> > Is there a fix for this?
>
> yes, see 2.4.15pre1
> warning, the iptables code in 2.4.15pre1 and pre2 seems broken.
and further it is likely that pre3 fixes iptables code :)
(it looks like the patch got reverted)
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-11 21:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 21:27 loop back broken in 2.2.14 Joe
2001-11-11 21:35 ` François Cami
2001-11-11 21:38 ` Jeff Garzik [this message]
2001-11-11 22:28 ` J Sloan
2001-11-11 22:55 ` J Sloan
2001-11-11 21:36 ` elko
2001-11-11 21:55 ` Adrian Bunk
-- strict thread matches above, loose matches on Subject: below --
2001-11-12 17:40 joeja
2001-11-12 20:41 ` J Sloan
2001-11-14 18:17 Re: " joeja
2001-11-15 21:37 ` Michael Peddemors
2001-11-15 23:31 ` J.A. Magallon
2001-11-16 4:52 ` Joe
2001-11-15 23:38 Mr R A Mercer
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=3BEEEFC9.4F245772@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=joeja@mindspring.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stilgar2k@wanadoo.fr \
/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.