From: "H. Peter Anvin" <hpa@zytor.com>
To: Ian Kent <raven@themaw.net>
Cc: Sage Weil <sage@newdream.net>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
akpm@linux-foundation.org, Al Viro <viro@zeniv.linux.org.uk>,
Yehuda Sadeh <yehuda@newdream.net>,
Jon Masters <jcm@jonmasters.org>
Subject: Re: [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held
Date: Thu, 25 Jun 2009 06:41:01 -0700 [thread overview]
Message-ID: <4A437E6D.3030207@zytor.com> (raw)
In-Reply-To: <4A432569.7050404@themaw.net>
Ian Kent wrote:
>
> We probably have to accept that people doing insmod with a specific
> path are going to have a problem and they shouldn't use that method
> anyway. But, AFAICS using a MODULE_ALIAS() in the kernel module will
> allow for the name change but doesn't seem to take account of the
> directory name change. Is that correct?
>
I'm not sure what that's supposed to mean. Generally the directory a
module appears in doesn't matter.
> There are those that may have an alias in the module-init-tools
> configuration as well. But we need get rid of that practice as well as,
> for a long time now, the alias hasn't been needed.
>
> Anyone have any thoughts how we might better handle these difficulties?
I suspect the MODULE_ALIAS should just do it.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2009-06-25 13:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 20:16 [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held Sage Weil
2009-03-19 20:16 ` [PATCH 2/2] vfs: clean up real_lookup Sage Weil
2009-03-19 20:22 ` Christoph Hellwig
2009-03-19 20:35 ` Sage Weil
2009-03-19 20:23 ` [PATCH 1/2] vfs: make real_lookup do dentry revalidation with i_mutex held Christoph Hellwig
2009-03-24 4:14 ` Ian Kent
2009-03-24 4:18 ` Ian Kent
2009-03-25 4:29 ` Sage Weil
2009-03-25 6:08 ` Ian Kent
2009-03-25 16:11 ` Ian Kent
2009-03-25 19:11 ` Sage Weil
2009-03-26 2:09 ` Ian Kent
2009-03-26 3:53 ` Sage Weil
2009-03-26 8:00 ` Ian Kent
2009-03-26 10:38 ` Ian Kent
2009-03-29 8:53 ` Ian Kent
2009-04-03 0:58 ` Sage Weil
2009-04-03 2:00 ` Ian Kent
2009-04-03 3:07 ` Sage Weil
2009-06-22 17:15 ` Sage Weil
2009-06-23 0:37 ` Ian Kent
2009-06-23 2:40 ` H. Peter Anvin
2009-06-25 7:21 ` Ian Kent
2009-06-25 13:41 ` H. Peter Anvin [this message]
2009-06-25 13:58 ` Christoph Hellwig
2009-06-23 2:42 ` H. Peter Anvin
2009-06-24 2:28 ` Ian Kent
2009-06-24 5:45 ` Sage Weil
2009-06-24 9:17 ` Ian Kent
2009-06-24 17:46 ` Sage Weil
2009-06-25 2:50 ` Ian Kent
2009-06-25 4:13 ` Ian Kent
2009-06-25 4:49 ` Sage Weil
2009-06-25 5:52 ` Ian Kent
2009-09-17 6:36 ` Ian Kent
2009-07-20 2:45 ` Ian Kent
2009-07-28 22:47 ` Sage Weil
2009-07-29 2:59 ` Ian Kent
2009-07-29 16:57 ` Sage Weil
2009-07-30 0:56 ` Ian Kent
2009-07-30 17:47 ` Sage Weil
2009-07-31 2:03 ` Ian Kent
2009-03-26 3:54 ` Ian Kent
2009-03-26 4:03 ` Sage Weil
2009-03-26 5:07 ` Ian Kent
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=4A437E6D.3030207@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=jcm@jonmasters.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=raven@themaw.net \
--cc=sage@newdream.net \
--cc=viro@zeniv.linux.org.uk \
--cc=yehuda@newdream.net \
/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.