On Tue, 2010-12-21 at 00:09 +0100, Michal Marek wrote: > On 20.12.2010 23:27, Keegan McAllister wrote: > > Hi Michal, > > > > The problem we're trying to solve is rebootless updates of modules > > that aren't loaded. While the Ksplice Uptrack software will update a > > loaded module in memory, it also needs to update modules on disk so > > that a later invocation of "modprobe" will find the updated code. > > > > However, if you reboot the system, you want to revert to the modules > > that came with the original kernel. The updated modules might, for > > example, rely on a symbol that wasn't exported by the original kernel. > > Ah, I can see the problem you are trying to solve now. I initially > thought you are providing those special ksplice modules in the alternate > tree (which are installed by custom tools anyway, thus could be handled > by a custom depmod & modprobe invocation). Yea, it's tricky if you're not following Ksplice closely because those guys are doing some pretty fun (and slick) things. FWIW, we met and had coffee a week ago and I gave them some advice, which is where these patches come from. After reviewing them, testing, and pulling in Mike's posts from last week, my plan is to push out a new release (RC though, let's test this stuff) in the next couple of days, before the holidays. Jon. -- To unsubscribe from this list: send the line "unsubscribe linux-modules" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
