Date: Sat, 2 May 2020 13:54:23 +0200 From: Solar Designer <solar@...nwall.com> To: lkrg-users@...ts.openwall.com Subject: Re: fake alert (?) On Sat, May 02, 2020 at 11:41:17AM +0300, Nikolay Zorin wrote: > and also: I tried the last commit of the SRC, where didn't work on > CentOS 6.10, on VmWare 6.7 and CentOS 7.4 - work, no warn\error > > I update src from git (commit > 'c8e18884a6bb18b4ddcccfd9c2776e4c3472392f', from 'Date: Fri May 1 > 21:59:28 2020 -0400') and.. and on KVM CentOS 6.10 (version KVM is > 0.12.1.2-2.491) kernel with this module work, I find the above confusing. First you say that "the last commit of the SRC" didn't work on CentOS 6.10, then you say "I update src from git" and it works "on KVM CentOS 6.10". What has changed between these two? Different hypervisors? Anything else? When you list CentOS versions, are those always the guest kernels? We never tried to support RHEL/CentOS 6.x kernels, targeting 7.x as a minimum. It's unexpected, but good news if/that LKRG works on CentOS 6.x at all. If we just happen to readily have that support, maybe we should start supporting those older kernels as there are still plenty of RHEL/CentOS/SCL 6.x systems in use. > but with warn (approx one > time in or 50 sec or 5 min, no visible dependets): > > May 2 04:21:29 auto kernel: [ 277.179232] [p_lkrg] [JUMP_LABEL] > Updating kernel core .text section hash! > May 2 04:25:45 auto kernel: [ 533.327245] [p_lkrg] [JUMP_LABEL] New > modification: type[JUMP_LABEL_JMP]! [...] > I tried VmWare 6.7, CentOS 7.4 (KVM version is 1.5.3-167) - same behavior > > P.S. default 'log_level' is 3 As I understand, this is normal behavior. Adam, maybe we should change the log level for these messages (and also for "batch mode" jump label updates?) from WARN to INFO, so they're not logged by default. Alexander P.S. Unfortunately, Nikolay's messages lack Message-ID headers, which is why our replies are not getting to the same thread.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.