Re: [PATCH 6/7] Ksplice: Export symbols needed for Ksplice
- From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
- Date: Mon, 16 Feb 2009 17:41:33 +1030
On Friday 13 February 2009 12:16:40 Tim Abbott wrote:
On Wed, 4 Feb 2009, Rusty Russell wrote:
On Saturday 06 December 2008 10:33:59 Jeff Arnold wrote:
From: Tim Abbott <tabbott@xxxxxxx>
Ksplice uses several functions from module.c in order to resolve
symbols and implement dependency handling. Calling these functions
requires holding module_mutex, so it is exported.
I have fought every attempt to export that. It was long a cause of misery
and pain; people saw the lock and so started grabbing it.
Any chance we can find another way?
It is definitely possible, but it wouldn't be pretty. There are a few
things that we use module_mutex for:
Yes, having looked through the code I don't think the export can be avoided.
Thanks,
Rusty.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: [PATCH 6/7] Ksplice: Export symbols needed for Ksplice
- From: Rusty Russell
- Re: [PATCH 6/7] Ksplice: Export symbols needed for Ksplice
- From: Tim Abbott
- Re: [PATCH 6/7] Ksplice: Export symbols needed for Ksplice
- Prev by Date: [PULL] cpumask bugfixes (re-xmit)
- Next by Date: Re: [PATCH NET-NEXT 0/10] hardware time stamping with new fields in shinfo
- Previous by thread: Re: [PATCH 6/7] Ksplice: Export symbols needed for Ksplice
- Next by thread: Staging: benet: convert netif_rx_* to napi_*
- Index(es):
Relevant Pages
|
