mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Satish Eerpini <eerpini@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: patching kdb to Centos kernel : error
Date: Sun, 17 Aug 2008 02:42:11 -0400	[thread overview]
Message-ID: <23408.1218955331@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 17 Aug 2008 11:30:41 +0530." <93655eb70808162300i4286eac9p9aa34cf23359ff72@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1597 bytes --]

On Sun, 17 Aug 2008 11:30:41 +0530, Satish Eerpini said:
> hi everyone , i was trying to patch kdb with CentOS 5.0 kernel
> (2.6.18-8) 

You might want to make sure you're using a 2.6.18-vintage kdb patch, as
trying to fit a 2.6.26 kdb onto a 2.6.18 kernel is unlikely to bring joy.

> resolve) ,.... but apart from the rejects during the kernel
> compilation i got the following error which does not seem to have
> anything to do with the rejects ............

No, the rejects during the patch are almost certainly related to your
compile errors...

>  the code(in kdb/modules/kdbm_pg.c) which is causing the second error
> is something like this :
> 
>              iaddr += offsetof(struct inode, u);
> 
> what i am not able to understand is that if 'u' is not a correct
> member of the inode , .. then what did they( whoever wrote this piece
> code) intend by 'u' ? , .....

Your kdb patch probably includes a patch to include/linux/fs.h that adds a
member 'u' to a 'struct inode'.  If this generated a reject, then the member 'u'
won't be in the struct, and your compile dies...

> and for the first error , ... i just checked out the code ....
> according to the line no shown in the error .....the code is :
> 
>              kdb_page_flags(page, Checked);
> 
> and i don't see any function PageChecked ....! so what can the error
> actually mean ??

kdb_page_flags is probably a macro that does something like:

#define kdb_page_flags(a,b) (..... Page##b)

The 'implicit declaration' is most likely a missing #include someplace,
which again hints at the rejects from a misapplied patch...

[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  reply	other threads:[~2008-08-17  6:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-17  6:00 Satish Eerpini
2008-08-17  6:42 ` Valdis.Kletnieks [this message]
2008-08-17 11:13   ` Satish Eerpini

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=23408.1218955331@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=eerpini@gmail.com \
    --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®