public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "C.Y.M" <syphir@syphir.sytes.net>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unknown symbol kill_proc_info in 2.6.10-rc1
Date: Sat, 23 Oct 2004 04:17:42 -0700	[thread overview]
Message-ID: <417A3DD6.1030902@syphir.sytes.net> (raw)
In-Reply-To: <20041023102203.GB30449@infradead.org>

Christoph Hellwig wrote:
> On Sat, Oct 23, 2004 at 03:04:47AM -0700, C.Y.M wrote:
> 
>>Christoph Hellwig wrote:
>>
>>>On Sat, Oct 23, 2004 at 02:21:22AM -0700, C.Y.M wrote:
>>>
>>>
>>>>After building 2.6.10-rc1, i was unable to load my "lufs" module due to 
>>>>an unknown symbol error (kill_proc_info).  When I examined the 
>>>>2.6.10-rc1 patch, I noticed that "EXPORT_SYMBOL(kill_proc_info);" was 
>>>>removed from signal.c.  With the following patch, I was able to resolve 
>>>>my problem, but I am not sure if this is the correct method.  Is there a 
>>>>reason why the kill_proc_info symbol is no longer exported?
>>>
>>>
>>>Because it's not an API you should be using.
>>>
>>>
>>
>>Is there an alternative?
> 
> 
> Maybe you could explain what you're actually trying to do at a higher
> level first.
>
I have been using the lufs module in combination with autofs to be able 
to automount ftp sites on the fly.  But, if lufs is broken due to the 
lack of the "kill_proc_info" symbol being available, perhaps I will just 
remove lufs and find another way (or wait until there is some kind of 
patch for lufs).




  reply	other threads:[~2004-10-23 11:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-23  9:21 Unknown symbol kill_proc_info in 2.6.10-rc1 C.Y.M
2004-10-23  9:57 ` Arjan van de Ven
2004-10-23  9:57 ` Christoph Hellwig
2004-10-23 10:04   ` C.Y.M
2004-10-23 10:22     ` Christoph Hellwig
2004-10-23 11:17       ` C.Y.M [this message]
2004-10-23 11:28         ` Christoph Hellwig

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=417A3DD6.1030902@syphir.sytes.net \
    --to=syphir@syphir.sytes.net \
    --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