All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Riesen <fork0@users.sf.net>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert module directory hierarchy and depmod invocation
Date: Fri, 13 Dec 2002 20:43:40 +0100	[thread overview]
Message-ID: <20021213194340.GA1050@steel> (raw)
In-Reply-To: <20021213030554.F27312C14D@lists.samba.org>

Rusty Russell, Fri, Dec 13, 2002 04:04:57 +0100:
> While the kernel, depmod et. al. don't care, other tools want the
> directory hierarchy under /lib/modules/`uname -r`/.  Sure, it's bogus
> for them to rely on kernel source layout, but noone has come up with a
> better alternative, so revert.
> 
> NOTE: You *still* can't have two modules of the same name!  (You never
> could).
> 

Are you sure it actually is the patch which does what
you have described?
And where can one find the patch, btw?

> Name: Module init reentry fix
> Author: Rusty Russell
> Status: Tested on 2.5.51
> 
> D: This changes the code to drop the module_mutex() before calling the
> D: module's init function, so module init functions can call
> D: request_module().  This was trivial before someone broke the module
> D: code to start non-live.  Now it requires us to keep info on the
> D: exact module state.
> 
> diff -urpN --exclude TAGS -X /home/rusty/devel/kernel/kernel-patches/current-dontdiff --minimal .27854-linux-2.5.51/include/linux/module.h .27854-linux-2.5.51.updated/include/linux/module.h
> --- .27854-linux-2.5.51/include/linux/module.h	2002-12-10 15:56:53.000000000 +1100
> +++ .27854-linux-2.5.51.updated/include/linux/module.h	2002-12-12 11:31:28.000000000 +1100

      reply	other threads:[~2002-12-13 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  3:04 [PATCH] Revert module directory hierarchy and depmod invocation Rusty Russell
2002-12-13 19:43 ` Alex Riesen [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=20021213194340.GA1050@steel \
    --to=fork0@users.sf.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /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.