From: Bruno Vidal <bruno_vidal@hpfrcu03.france.hp.com>
To: "parisc-linux@lists.parisc-linux.org"
<parisc-linux@lists.parisc-linux.org>
Subject: [parisc-linux] Probleme while compiling last CVS kernel.
Date: Thu, 06 Jun 2002 14:44:42 +0200 [thread overview]
Message-ID: <3CFF593A.18910E50@admin.france.hp.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2226 bytes --]
Hi
I've started this morning to download latest CVS bits.
I've prepared a patche for this version from my dump driver,
and try to recompile everything, but I've found a problem
with LVM !!! See:
make dep: okay
make vmlinux:
ioctl32.c:2009: warning: assignment makes pointer from integer without a cast
ioctl32.c:2030: structure has no member named `inode'
ioctl32.c:2049: warning: passing arg 2 of `lcopy_from_user' makes pointer from integer without a cast
ioctl32.c:2067: structure has no member named `inode'
ioctl32.c:2078: warning: passing arg 2 of `lcopy_from_user' makes pointer from integer without a cast
ioctl32.c:2082: warning: assignment makes integer from pointer without a cast
ioctl32.c:2086: structure has no member named `inode'
ioctl32.c:1985: warning: `v' might be used uninitialized in this function
-> in this file it is:
v->pv[i]->pe = NULL; v->pv[i]->inode = NULL;
and
p.pe = NULL; p.inode = NULL;
It complains that there is no "inode" in structure pv[i].
So in this line v is a struct vg_t. In this structure
pv[i] is a pv_t structure, I've found this struture in
include/linux/lvm.h, and it is right, there is no "inode",
in it !!!! Is this LVM code broken ?
typedef struct pv_v2 {
char id[2]; /* Identifier */
unsigned short version; /* HM lvm version */
lvm_disk_data_t pv_on_disk;
lvm_disk_data_t vg_on_disk;
lvm_disk_data_t pv_uuidlist_on_disk;
lvm_disk_data_t lv_on_disk;
lvm_disk_data_t pe_on_disk;
char pv_name[NAME_LEN];
char vg_name[NAME_LEN];
char system_id[NAME_LEN]; /* for vgexport/vgimport */
kdev_t pv_dev;
uint pv_number;
uint pv_status;
uint pv_allocatable;
uint pv_size; /* HM */
uint lv_cur;
uint pe_size;
uint pe_total;
uint pe_allocated;
uint pe_stale; /* for future use */
pe_disk_t *pe; /* HM */
struct block_device *bd;
char pv_uuid[UUID_LEN+1];
#ifndef __KERNEL__
uint32_t pe_start; /* in sectors */
#endif
} pv_t;
--
Vidal Bruno, (770-4271)
SSD-HA Team, HP-UX & LINUX Support
bruno_vidal@admin.france.hp.com
[-- Attachment #2: Card for Bruno Vidal --]
[-- Type: text/x-vcard, Size: 386 bytes --]
begin:vcard
n:Bruno;VIDAL
tel;fax:01-69-82-60-14
tel;work:01-69-29-42-71
x-mozilla-html:TRUE
url:www.france.hp.com
org:Solution Center
version:2.1
email;internet:bruno_vidal@hp.com
title:Expert Logiciel Environnement Haute Disponibilité
adr;quoted-printable:;;HP France=0D=0A;Z.A de Courtaboeuf;1 Av. du Canada;91947 Les Ulis cedex;France
x-mozilla-cpt:;26208
fn:VIDAL Bruno
end:vcard
next reply other threads:[~2002-06-06 12:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 12:44 Bruno Vidal [this message]
2002-06-06 13:00 ` [parisc-linux] Probleme while compiling last CVS kernel Patrick Caulfield
2002-06-06 18:34 ` joel.soete
2002-06-06 18:43 ` Patrick Caulfield
2002-06-07 6:05 ` joel.soete
2002-06-07 7:16 ` joel.soete
2002-06-07 7:24 ` Patrick Caulfield
2002-06-07 7:28 ` joel.soete
2002-06-07 7:34 ` Patrick Caulfield
2002-06-07 7:39 ` joel.soete
-- strict thread matches above, loose matches on Subject: below --
2002-06-07 15:31 joel.soete
2002-06-07 18:24 ` Patrick Caulfield
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=3CFF593A.18910E50@admin.france.hp.com \
--to=bruno_vidal@hpfrcu03.france.hp.com \
--cc=parisc-linux@lists.parisc-linux.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