From: Christoph Hellwig <hch@infradead.org>
To: Jeff Arnold <jbarnold@MIT.EDU>
Cc: linux-kernel@vger.kernel.org, Tim Abbott <tabbott@MIT.EDU>,
Anders Kaseorg <andersk@MIT.EDU>, Waseem Daher <wdaher@MIT.EDU>,
Denys Vlasenko <vda.linux@googlemail.com>,
Nikanth Karthikesan <knikanth@suse.de>
Subject: Re: [RFC v3 PATCH 6/7] Ksplice: Export symbols needed for Ksplice
Date: Sat, 22 Nov 2008 01:34:07 -0500 [thread overview]
Message-ID: <20081122063407.GA13931@infradead.org> (raw)
In-Reply-To: <1227324961-13273-7-git-send-email-jbarnold@mit.edu>
On Fri, Nov 21, 2008 at 10:36:00PM -0500, Jeff Arnold wrote:
> Ksplice uses init_mm to get access to the ranges of addresses
> containing core kernel text and data. It seems that init_mm was
> scheduled to be unexported entirely in 2.6.26, so move it to
> EXPORT_SYMBOL_GPL (rather than back to EXPORT_SYMBOL).
Umm, no. This is a very clear indicator that your code shouldn't be
modular.
next prev parent reply other threads:[~2008-11-22 6:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 3:35 [RFC v3 PATCH 0/7] Ksplice: Rebootless kernel updates Jeff Arnold
2008-11-22 3:35 ` [RFC v3 PATCH 1/7] Make section names compatible with -ffunction-sections -fdata-sections Jeff Arnold
2008-11-22 3:35 ` [RFC v3 PATCH 2/7] x86: Add an option to compile " Jeff Arnold
2008-11-22 3:35 ` [RFC v3 PATCH 3/7] Ksplice: Make find_symbol return a struct kernel_symbol Jeff Arnold
2008-11-22 3:35 ` [RFC v3 PATCH 4/7] Ksplice: Add module_data_address (the analogue of module_text_address) Jeff Arnold
2008-11-22 3:35 ` [RFC v3 PATCH 5/7] Ksplice: Add functions for walking kallsyms symbols Jeff Arnold
2008-11-22 3:36 ` [RFC v3 PATCH 6/7] Ksplice: Export symbols needed for Ksplice Jeff Arnold
2008-11-22 3:36 ` [RFC v3 PATCH 7/7] Ksplice: Support updating x86-32 and x86-64 Jeff Arnold
2008-11-22 6:34 ` Christoph Hellwig [this message]
2008-11-24 22:13 ` [RFC v3 PATCH 6/7] Ksplice: Export symbols needed for Ksplice Tim Abbott
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=20081122063407.GA13931@infradead.org \
--to=hch@infradead.org \
--cc=andersk@MIT.EDU \
--cc=jbarnold@MIT.EDU \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tabbott@MIT.EDU \
--cc=vda.linux@googlemail.com \
--cc=wdaher@MIT.EDU \
/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
all inboxes | Powered by JetHome®