DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Uq3B/B3nkk8AJ4YG7XJW4t+y4kSx1fF89mHZYUAKk051MmHYrUac74Bng14+XQn/xmfd7WnpRhwzf8YMpByMetfeu0jEAV5Odyu3t77bV3lHTP44RS/WVu+cH3TzOpUP9jgaIJPhL1yQ1fapjv0fU4HPh6qTehJkTCdeBdYWL9s=
Message-ID: <d120d5000601241508l1a93aae7ubdf8206209be405c@mail.gmail.com>
Date: Tue, 24 Jan 2006 18:08:54 -0500
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Reply-To: dtor_core@ameritech.net
To: Al Viro <viro@ftp.linux.org.uk>
Subject: Re: [PATCH] Export symbols so CONFIG_INPUT works as a module
Cc: Dave Jones <davej@redhat.com>, Martin Michlmayr <tbm@cyrius.com>,
       linux-kernel@vger.kernel.org
In-Reply-To: <20060124184114.GS27946@ftp.linux.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
References: <20060124181945.GA21955@deprecation.cyrius.com>
	 <20060124183432.GA27917@redhat.com>
	 <20060124184114.GS27946@ftp.linux.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1374
Lines: 32

On 1/24/06, Al Viro <viro@ftp.linux.org.uk> wrote:
> On Tue, Jan 24, 2006 at 01:34:32PM -0500, Dave Jones wrote:
> > On Tue, Jan 24, 2006 at 06:19:45PM +0000, Martin Michlmayr wrote:
> >  > Currently, modular input support fails to load with the following error:
> >  >
> >  > qube:# modprobe input
> >  > input: Unknown symbol kobject_get_path
> >  > input: Unknown symbol add_input_randomness
> >  >
> >  > In the short run, this can be solved by exporting these two symbols.
> >  > There have been discussions about fixing this in a different manner,
> >  > see http://www.ussg.iu.edu/hypermail/linux/kernel/0505.2/1068.html
> >  > Since this was in the days of 2.6.12-rc4 and modular input support is
> >  > still broken, I suggest these symbols to be exported for now.
> >
> > Is there actually any practical reason why you would want to
> > make the input layer modular ?
>
> More interesting question: is pis^H^H^Hsysfs interaction in there safe for
> modular code?

The core should be safe, at least I was trying to make it this way, so
if you see something wrong - shout. Locking is another question
though...

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