Named-chroot.service causes soft lockup, hard lockup or OOM when it was restarted or stopped.
Issue
- Trigger a soft lockup, hard lockup or OOM in /var/log/messages when executing "systemctl restart or stop named-chroot.service".
- Named-chroot.service causes memory leaks and kernel panics.
Environment
- Red Hat Enterprise Linux 7.4
- bind-chroot-9.9.4-50.el7.x86_64
- bind-9.9.4-50.el7.x86_64
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.