From: Greg KH <greg@kroah.com>
To: Oleg Drokin <green@linuxhacker.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] remove EXPORT_SYMBOL(kallsyms_lookup)
Date: Thu, 17 Jun 2004 10:50:58 -0700 [thread overview]
Message-ID: <20040617175058.GA16640@kroah.com> (raw)
In-Reply-To: <200406171731.i5HHVA0M015051@car.linuxhacker.ru>
On Thu, Jun 17, 2004 at 08:31:10PM +0300, Oleg Drokin wrote:
> Hello!
>
> Greg KH <greg@kroah.com> wrote:
> GK> Distros have started to ship kernels with this patch, as it seems that
> GK> some unnamed binary module authors are already abusing this function (as
> GK> well as some open source modules, like the openib code.) I could not
> GK> find any valid reason why this symbol should be exported, so here's a
>
> What if some extra carefully written code detects some (non fatal) problem in
> itself and decides to dump a decoded backtrace to some internal log buffer,
> user will find this later and will send a bugreport to developers?
Do you have an example of code in the current kernel tree that does
this? If not, then feel free to bring up the discussion about exporting
this symbol at that point in time :)
> (yes, there are problems with simply doing dump_stack()).
> Or perhaps we need dump_stack version that will print the dump into a
> supplied buffer then?
That might be useful.
thanks,
greg k-h
next prev parent reply other threads:[~2004-06-17 17:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 16:29 [PATCH] remove EXPORT_SYMBOL(kallsyms_lookup) Greg KH
2004-06-17 17:31 ` Oleg Drokin
2004-06-17 17:50 ` Greg KH [this message]
2004-06-17 19:28 ` Christoph Hellwig
2004-06-17 20:14 ` Dave Kleikamp
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=20040617175058.GA16640@kroah.com \
--to=greg@kroah.com \
--cc=green@linuxhacker.ru \
--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