How to solve call trace produced by security_ops_task_setrlimit() with bind

domain-name-system centos security redhat bind

6,948

This message is harmless and can be ignored. It is a note to kernel developers.

Red Hat also published a statement to this effect in its KB (subscribers only, boo).

6,948

Author by

shakaran

>>>English:<<< I am a student of Computer Engineering in Spain. I use Ubuntu and I like to support the world of free software. Currently developing a project on an online role-playing game as RPG-based web interfaces and aspirations motor 3D based Blender. The website of the project: www.apogeus.es Other projects: Tivion - A simple player for online TV streaming. www.shakaran.net/blog/tivion Quijost - A really cheap and professional hosting www.quijost.com >>>Spanish<<< Soy un estudiante de Ingeniería Informática en España. Utilizo Ubuntu y me gusta apoyar el mundo del software libre. Actualmente desarrollo un proyecto sobre un juego de rol online como RPG basado en interfaces web y con aspiraciones de motor en 3D basado en Blender. La pagina web del proyecto: www.apogeus.es Otros proyectos: Tivion - Un simple reproductor para canales de TV streaming. www.shakaran.net/blog/tivion Quijost - Un hospedaje realmente barato y profesional www.quijost.com

Updated on September 18, 2022

Comments

shakaran almost 2 years
I have a machine with CentOS 5.9 and VMware installed.

Currently I am using BIND 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.6 (default shipped with distribution).

When I restart the machine, I can see this message on screen just when the named service is started:
```
Starting named: You need to implement a remote task_setrlimit in your security module and call it directly from this functionWARNING: at security/security.c:51 security_ops_task_setrlimit()

Call Trace:
[<ffffffff8012eeeb>] security_ops_task_setrlimit+0x87/0x96
[<ffffffff8009dc0a>] do_prlimit+0xd7/0x1d2
[<ffffffff8009ed53>] sys_setrlimit+0x36/0x43
[<ffffffff8005d29e>] tracesys+0xd5/0xdf
```
This error doesn't seem affect to bind, the service works fine, but I would know what produces the warning error and how to solve it.
Falcon Momot almost 11 years

This seems to address the symptoms, more than the problem. One generally doesn't turn off logging to resolve errors being logged... I'd hope that sometime the responsible kernel developer might issue a patch for that.