Techwizz/kernel-fxtec-pro1x
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

itimer: Use printk_once instead of WARN_ONCE

Browse source 
David pointed out, that WARN_ONCE() to report usage of an deprecated
misfeature make folks unhappy. Use printk_once() instead.

Andrew told me to stop grumbling and to remove the silly typecast
while touching the file.

Reported-by: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
This commit is contained in:
Thomas Gleixner 2012-04-10 10:50:55 +02:00
parent 6f103929f8
commit 9886f44412
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
kernel/itimer.c
View file

@ -285,9 +285,10 @@ SYSCALL_DEFINE3(setitimer, int, which, struct itimerval __user *, value,
if(copy_from_user(&set_buffer, value, sizeof(set_buffer))) if(copy_from_user(&set_buffer, value, sizeof(set_buffer)))
return -EFAULT; return -EFAULT;
} else { } else {
memset((char *) &set_buffer, 0, sizeof(set_buffer)); memset(&set_buffer, 0, sizeof(set_buffer));
WARN_ONCE(1, "setitimer: new_value pointer is NULL." printk_once(KERN_WARNING "%s calls setitimer() with new_value NULL pointer."
" Misfeature support will be removed\n"); " Misfeature support will be removed\n",
current->comm);
} }
error = do_setitimer(which, &set_buffer, ovalue ? &get_buffer : NULL); error = do_setitimer(which, &set_buffer, ovalue ? &get_buffer : NULL);