From: DevilKin <devilkin@gmx.net>
To: Ishan Oshadi Jayawardena <ioshadi@sltnet.lk>,
linux-kernel@vger.kernel.org
Subject: Re: 2.4.14 loopback blk dev compilation trouble
Date: Wed, 21 Nov 2001 08:58:35 +0100 [thread overview]
Message-ID: <5.1.0.14.2.20011121085726.00aaf648@pop.gmx.net> (raw)
In-Reply-To: <3BFBBE98.68052D11@sltnet.lk>
At 08:47 21/11/2001 -0600, Ishan Oshadi Jayawardena wrote:
>Greetings.
> I've seen that the compilation of off-the-server
>2.4.14 tree fails at the end of 'make bzImage' because
>drivers/block/loop.c uses the deactivate_page() function,
>which seems to have been removed from the source tree.
> By following the progress of the kernel through
>2.4.12, 2.4.13, and 2.4.14 patches, I've seen that
>page_cache_release() does the same things as
>deactivate_page(). Both these functions are used in the
>together twice in drivers/block/loop.c. I compiled
>the 2.4.14 kernel by commenting out the references to
>deactivate_page() but leaving page_cache_release(), and
>loopback block devs work; but I do not have the resources
>to check it for memory leaks etc.
> I _think_ I've done the right thing, but
>would appreciate verification by a regular kernel-
>hacker :-)
>I searched the net for some reference to this problem,
>but couldn't find anything so far.
>
>(I've compiled loop blk-dev support in to the kernel.)
That's the correct way to correct the compilation problem. It has been
reported 22987432 times already...
DK
prev parent reply other threads:[~2001-11-21 8:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 14:47 Ishan Oshadi Jayawardena
2001-11-21 7:57 ` Anuradha Ratnaweera
2001-11-21 7:58 ` DevilKin [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=5.1.0.14.2.20011121085726.00aaf648@pop.gmx.net \
--to=devilkin@gmx.net \
--cc=ioshadi@sltnet.lk \
--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®