All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux_developer@hotmail.com (Linux Kernel Developer),
	linux-kernel@vger.kernel.org
Subject: Re: Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17
Date: Tue, 31 Oct 2000 01:08:13 +1100	[thread overview]
Message-ID: <4793.972914893@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Mon, 30 Oct 2000 14:02:38 -0000." <E13qFWK-0006uI-00@the-village.bc.nu>

On Mon, 30 Oct 2000 14:02:38 +0000 (GMT), 
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
>> As part of the 2.5 kbuild redesign, symbol versions will be completely
>> redone.  One of the things on my todo list is to detect this mismatch.
>> There are some problems in doing that which I may or may not be able to
>> overcome, but if the field names are different between C and C++ then I
>> can never detect this mismatch correctly.
>
>The symbol generation code never sees the C++ names, never will and never can.
>I still don't see any problem.

2.4 symbol generation code never sees the C++ names, 2.5 code might.
To detect a mismatch between kernel headers and the module version
file, I have to generate the checksum for the consumer of the symbol
(C++) as well as the generator of the symbol (C) and compare them.

There are issues involving partially defined structures which might
make this impossible to do, although I have some ideas on that front.
But if kernel code uses C names and module code uses C++ names there
will always be a spurious mismatch.  That would prevent symbol versions
from picking up some user errors.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-10-30 14:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-30 11:09 Need info on the use of certain datastructures and the first C++ keyword patch for 2.2.17 Linux Kernel Developer
2000-10-30 12:00 ` J . A . Magallon
2000-10-30 12:46   ` Keith Owens
2000-10-31  8:13   ` Linux Kernel Developer
2000-10-30 13:04 ` Alan Cox
2000-10-30 13:20   ` Keith Owens
2000-10-30 13:41     ` Alan Cox
2000-10-30 13:56       ` Keith Owens
2000-10-30 14:02         ` Alan Cox
2000-10-30 14:08           ` Keith Owens [this message]
2000-10-30 18:16             ` Alan Cox
2000-10-30 21:04               ` Keith Owens
2000-10-31  8:13   ` Linux Kernel Developer

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=4793.972914893@ocs3.ocs-net \
    --to=kaos@ocs.com.au \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux_developer@hotmail.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.