public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Zander <phoenix@minion.de>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Where did vm_operations_struct->unmap in 2.4.0 go?
Date: Sat, 13 Jan 2001 12:46:00 +0100	[thread overview]
Message-ID: <20010113124559.A2108@chronos> (raw)
In-Reply-To: <20010112201130.A710@chronos> <3654.979348291@ocs3.ocs-net>
In-Reply-To: <3654.979348291@ocs3.ocs-net>; from kaos@ocs.com.au on Sat, Jan 13, 2001 at 12:11:31PM +1100

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

On Sat, Jan 13, 2001 at 12:11:31PM +1100, kaos@ocs.com.au wrote:
> My apologies.  I read the patch, not the full source code and the patch
> does not have enough programming context to show that the driver is
> only searching its own symbol space.  In my own defense, the references
> to spinlock_t unload_lock and MOD_CAN_QUERY(mp) in the patch are highly
> misleading, those statements only make sense when you are looking at a
> symbol table for another module.  When searching your own symbol table
> the current module must be live with a non-zero use count, not being
> unloaded and it can always be queried.
> 
> >Contrary to what you're saying, the patch does not just inline the old
> >get_module_symbol algorithm nor does it access any of module.c's internal
> >data.
> 
> unload_lock and MOD_CAN_QUERY were copied verbatim from the old
> get_module_symbol, even though they are completely unnecessary.  That
> looks like inlining the old algorithm to me.
> 
> struct module_symbol, mp->nsyms and mp->syms are module.c internal
> data.  If it is ever necessary to change those structures, nothing
> outside module.c, the 32/64 handlers for module system calls and
> modutils should be affected.  Now if I change module_symbol, other bits
> of the kernel will unexpectedly break, this is not good.

I see what you mean. What do you suggest should be done in the context of
the driver? As you can easily tell, I'm not overly familiar with the 
internal workings of the kernel. That and the mere impossibility to get 
any kind of help at the mere mention of the Nvidia driver module ("go bitch
at nvidia", "who cares", ...) do not exactly make it easier to fix problems 
that arise from changes to the kernel. 

--
----------------------------------------------------------------------
 christian zander              we come to bury dos, not to praise it.
 zander@hdz.uni-dortmund.de    -- paul vojta
----------------------------------------------------------------------

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

  parent reply	other threads:[~2001-01-13 11:48 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3A5EFC56.F1A5BCE0@mira.net>
2001-01-12 19:11 ` Where did vm_operations_struct->unmap in 2.4.0 go? Christian Zander
2001-01-13  1:11   ` Keith Owens
2001-01-13 10:46     ` David Woodhouse
2001-01-13 12:06       ` Keith Owens
2001-01-13 15:09         ` David Woodhouse
2001-01-13 19:03           ` Russell King
2001-01-14  0:21           ` Keith Owens
2001-01-14  9:43             ` David Woodhouse
2001-01-14 10:05               ` Keith Owens
2001-01-14 10:45                 ` David Woodhouse
2001-01-14  4:04           ` Linus Torvalds
2001-01-14 17:46             ` David Woodhouse
2001-01-14 19:12               ` Linus Torvalds
2001-01-14 20:02                 ` David Woodhouse
2001-01-14 20:15                   ` Linus Torvalds
2001-01-14 21:15                     ` David Woodhouse
2001-01-14 21:47                       ` Linus Torvalds
2001-01-14 21:57                         ` David Woodhouse
2001-01-14 23:00                         ` Keith Owens
2001-01-15  9:09                           ` David Woodhouse
2001-01-13 11:46     ` Christian Zander [this message]
2001-01-13 12:23       ` Keith Owens
2001-01-10  3:27 Allen Unueco
2001-01-10  3:50 ` Keith Owens
2001-01-11  5:38 ` Antony Suter
2001-01-11  6:05   ` Keith Owens
2001-01-11 11:42     ` David Woodhouse
2001-01-11 12:12       ` Keith Owens
2001-01-11 12:32         ` David Woodhouse
2001-01-11 12:46           ` Keith Owens
2001-01-11 13:09             ` Alan Cox
2001-01-11 13:14               ` Keith Owens
2001-01-12  2:12                 ` Ingo Oeser
2001-01-12  2:30                   ` Keith Owens
2001-01-12 10:27                     ` David Woodhouse
2001-01-12 11:55                       ` Keith Owens
2001-01-12 13:40                         ` David Woodhouse
2001-01-12 12:01                     ` Daniel Phillips
2001-01-12 12:18                       ` Keith Owens
2001-01-14 10:16                         ` Kai Henningsen
2001-01-11 13:25             ` David Woodhouse

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=20010113124559.A2108@chronos \
    --to=phoenix@minion.de \
    --cc=kaos@ocs.com.au \
    --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