All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thorkild Stray <thorkild@linpro.no>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Compilation of 2.5.1-pre11 fails w/LVM as module
Date: 17 Dec 2001 07:05:58 +0100	[thread overview]
Message-ID: <nnd71efkjd.fsf@false.linpro.no> (raw)
In-Reply-To: <33364.62.211.145.13.1008513364.squirrel@gtsmail.gts.it>
In-Reply-To: <33364.62.211.145.13.1008513364.squirrel@gtsmail.gts.it>

<s.rivoir@gts.it> writes:

> As stated in the subject, this is 'make modules' output:
> 
> make[2]: Entering directory `/us2/usr/src/linux/drivers/md'
> gcc -D__KERNEL__ -I/us2/usr/src/linux/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing-fno-common -pipe -mpreferred-stack-boundary=2 -march=i686
> -malign-functions=4  -DMODULE   -c -o lvm.o lvm.clvm.c: In function `lvm_user_bmap':
> lvm.c:1046: request for member `bv_len' in something not a structure or union
> make[2]: *** [lvm.o] Error 1
> make[2]: Leaving directory `/us2/usr/src/linux/drivers/md'
> make[1]: *** [_modsubdir_md] Error 2
> make[1]: Leaving directory `/us2/usr/src/linux/drivers'
> make: *** [_mod_drivers] Error 2
> Sorry if already issued by someone else :)

This can be fixed (so that is compiles) by just changing line 1046 from:

bio.bi_io_vec.bv_len = lvm_get_blksize(bio.bi_dev);

to

bio.bi_io_vec->bv_len = lvm_get_blksize(bio.bi_dev);

This is due to changes in the I/O layer. You used to only have one
bio_vec struct in the bio struct, but now it has changed to a linked
list.

Warning: This makes it compile, but it does not necessarily make it
work, but I might. :) Since the rest of LVM hasn't been changed to
use the new linked-list-possibility, it shouldn't make a difference.


-- 
Thorkild Stray, Linpro AS                              <thorkild@linpro.no>

      reply	other threads:[~2001-12-17  6:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-16 14:36 Compilation of 2.5.1-pre11 fails w/LVM as module s.rivoir
2001-12-17  6:05 ` Thorkild Stray [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=nnd71efkjd.fsf@false.linpro.no \
    --to=thorkild@linpro.no \
    --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.