Thanks Jessica! FYI: # uname -a Linux debian64 4.6-rc4+ #3 SMP Fri May 13 14:52:00 CEST 2016 x86_64 GNU/Linux
But I will try on a 4.6.0 later. Regards Ravineet On 16 May 2016 at 23:06, Jessica Yu <[email protected]> wrote: > +++ Ravineet Singh [16/05/16 11:27 +0200]: > >> HI, >> >> The patch is the same as in the README, i.e: >> --- src.orig/fs/proc/meminfo.c >> +++ src/fs/proc/meminfo.c >> @@ -95,7 +95,7 @@ static int meminfo_proc_show(struct seq_ >> "Committed_AS: %8lu kB\n" >> "VmallocTotal: %8lu kB\n" >> "VmallocUsed: %8lu kB\n" >> - "VmallocChunk: %8lu kB\n" >> + "VMALLOCCHUNK: %8lu kB\n" >> #ifdef CONFIG_MEMORY_FAILURE >> "HardwareCorrupted: %5lu kB\n" >> #endif >> >> and, yes, I see it every time. >> The patch/module is loaded via; >> kpatch load kpatch_0001_Test_kpatch.ko >> and unloaded via kpatch unload >> >> > Hi Ravineet, > > Thanks for the additional information. Unfortunately I haven't been > able to reproduce the module refcount issue on -rc4. As far as > functionality goes, I wouldn't worry about the warning. We technically > don't support -rc kernels, since those kernels are in active > development and tend to be unstable. FWIW I've tested kpatch on the > latest 4.6.0 stable release, and didn't run into any issues, if you'd > like to try upgrading your kernel. > > Jessica > > -- Regards Ravineet
_______________________________________________ kpatch mailing list [email protected] https://www.redhat.com/mailman/listinfo/kpatch
