From: "Bryn M. Reeves" <breeves@redhat.com>
To: devzero@web.de
Cc: device-mapper development <dm-devel@redhat.com>
Subject: Re: [PATCH 2.6.20] updated dm-loop patch
Date: Thu, 15 Feb 2007 12:28:10 +0000 [thread overview]
Message-ID: <45D451DA.2000106@redhat.com> (raw)
In-Reply-To: <1628079706@web.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
devzero@web.de wrote:
> 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:
>
Hi Roland,
That's right - I keep my git tree fairly close to upstream, so as soon
as the patch that deprecated invalidate_inode_pages was merged, I
converted dm-loop to use invalidate_mapping_pages instead.
This means that dm-loop will build without warnings on the latest
kernel.org tree but it does mean that you will need the additional patch
you referenced if you want to apply it to a plain 2.6.20 kernel.
Kind regards,
Bryn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFF1FHa6YSQoMYUY94RAl2iAKDAlrTqxDCNP7i/bhexl6JJGW1rNwCgksXz
5limiJOmDRoBKdHDUsU0pFE=
=HwdH
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2007-02-15 12:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-15 11:45 [PATCH 2.6.20] updated dm-loop patch devzero
2007-02-15 12:28 ` Bryn M. Reeves [this message]
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=45D451DA.2000106@redhat.com \
--to=breeves@redhat.com \
--cc=devzero@web.de \
--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.