I googled this issue and found so many people have encountered, but most of them just said "the newer kernel doesn't have this problem, so upgrade kernel". We can't upgrade kernel easily, so we need to *really* solve this problem. On 10/18/2017 04:41 PM, John Hodrien wrote:> On Wed, 18 Oct 2017, wuzhouhui wrote: > >> Does anyone have encountered same problem or advice? > > Expect minimal help when running custom kernel modules on painfully old > CentOS > kernels? > > jh > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos
On 18 October 2017 at 09:50, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote:> I googled this issue and found so many people have encountered, but most > of them just said "the newer kernel doesn't have this problem, so upgrade > kernel". We can't upgrade kernel easily, so we need to *really* solve this > problem. > > >No, you really need to rebase your work on current CentOS as you're so far behind on critical security issues it's just not funny. It also mitigates any ability for someone to actually help and for any fix to reach you.
On 18 October 2017 at 04:50, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote:> I googled this issue and found so many people have encountered, but most of > them just said "the newer kernel doesn't have this problem, so upgrade > kernel". We can't upgrade kernel easily, so we need to *really* solve this > problem. > >If you can't update the kernel then how can anyone fix the problem? The kernel needs to be changed out in some way. [Yes there are ways to binary patch a running kernel but it is a) frought with danger b) experts only area. People who do that do not offer their services for free for a reason.] -- Stephen J Smoogen.
Fine, it seems that upgrade kernel is the only effective solution.> On 18 Oct 2017, at 10:00 PM, Stephen John Smoogen <smooge at gmail.com> wrote: > > On 18 October 2017 at 04:50, wuzhouhui <wuzhouhui14 at mails.ucas.ac.cn> wrote: >> I googled this issue and found so many people have encountered, but most of >> them just said "the newer kernel doesn't have this problem, so upgrade >> kernel". We can't upgrade kernel easily, so we need to *really* solve this >> problem. >> >> > > If you can't update the kernel then how can anyone fix the problem? > The kernel needs to be changed out in some way. [Yes there are ways to > binary patch a running kernel but it is a) frought with danger b) > experts only area. People who do that do not offer their services for > free for a reason.] > > -- > Stephen J Smoogen. > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos