From: devzero@web.de
To: "Bryn M. Reeves" <breeves@redhat.com>,
device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 2.6.20] updated dm-loop patch
Date: Thu, 15 Feb 2007 12:45:14 +0100 [thread overview]
Message-ID: <1628079706@web.de> (raw)
Hi Bryn,
with this patch and also with 0.415 i have the following problem when compiling it with stock 2.6.20 :
Building modules, stage 2.
MODPOST 1 modules
WARNING: "invalidate_mapping_pages" [drivers/md/dm-loop.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
i found , that this was due to missing
EXPORT_SYMBOL(invalidate_mapping_pages);
in mm/truncate.c
i found
http://lkml.org/lkml/2007/1/3/154
it looks that this didn`t go into 2.6.20 and we need at least 2.6.20-git11 ?
changelog at http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.20-git11.log telling that it had just had been merged on 10th of february:
commit 54bc485522afdac33de5504da2ea8cdcc690674e
Author: Anton Altaparmakov <aia21@cam.ac.uk>
Date: Sat Feb 10 01:45:38 2007 -0800
[PATCH] Export invalidate_mapping_pages() to modules
It makes no sense to me to export invalidate_inode_pages() and not
invalidate_mapping_pages() and I actually need invalidate_mapping_pages()
because of its range specification ability...
akpm: also remove the export of invalidate_inode_pages() by making it an
inlined wrapper.
so, we need 2.6.20-git11 for dm-loop or we would need to modify mm/truncate.c manually !?
regards
roland
> -----Ursprüngliche Nachricht-----
> Von: "Bryn M. Reeves" <breeves@redhat.com>
> Gesendet: 15.02.07 01:52:12
> An: device-mapper development <dm-devel@redhat.com>
> Betreff: Re: [dm-devel] [PATCH 2.6.20] updated dm-loop patch
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Bryn M. Reeves wrote:
> > This version of the patch fixes a couple of problems that Roland found
> > with file offsets & the use of some conversion routines from dm.h:
>
> Unfortunately, it also added a new bug: in backing out some other
> changes I'd accidentally reverted to a version of the patch with some
> experimental changes to the file I/O workqueue. This was incomplete and
> harms performance for file mapped loop devices.
>
> The attached version changes this back to the previous per-loop device
> workqueue.
>
> Apologies for the confusion.
>
> Kind regards,
>
> Bryn.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFF066R6YSQoMYUY94RArhtAJ9J0Cc5o+Hg3NjzX8iikrIli9UlYgCggLaE
> /hJdDhTkiybsmfxz8SdLVko=
> =4pK0
> -----END PGP SIGNATURE-----
>
>
_____________________________________________________________________
Der WEB.DE SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
http://smartsurfer.web.de/?mc=100071&distributionid=000000000066
next reply other threads:[~2007-02-15 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 11:45 devzero [this message]
2007-02-15 12:28 ` [PATCH 2.6.20] updated dm-loop patch Bryn M. Reeves
2007-02-21 0:14 ` roland
-- strict thread matches above, loose matches on Subject: below --
2007-02-15 22:30 devzero
2007-02-12 8:49 roland
2007-02-12 15:24 ` Bryn M. Reeves
2007-02-06 11:35 Bryn M. Reeves
2007-02-13 20:20 ` Bryn M. Reeves
2007-02-15 0:51 ` Bryn M. Reeves
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=1628079706@web.de \
--to=devzero@web.de \
--cc=breeves@redhat.com \
--cc=dm-devel@redhat.com \
/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.