proc: use WARN() rather than printk+backtrace
Use WARN() rather than a printk() + backtrace(); this gives a more standard format message as well as complete information (including line numbers etc) that will be collected by kerneloops.org Signed-off-by: Arjan van de Ven <arjan@linux.intel.com> Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
This commit is contained in:
parent
1e0edd3f67
commit
6c2f91e077
|
@ -547,9 +547,8 @@ static int proc_register(struct proc_dir_entry * dir, struct proc_dir_entry * dp
|
||||||
|
|
||||||
for (tmp = dir->subdir; tmp; tmp = tmp->next)
|
for (tmp = dir->subdir; tmp; tmp = tmp->next)
|
||||||
if (strcmp(tmp->name, dp->name) == 0) {
|
if (strcmp(tmp->name, dp->name) == 0) {
|
||||||
printk(KERN_WARNING "proc_dir_entry '%s/%s' already registered\n",
|
WARN(1, KERN_WARNING "proc_dir_entry '%s/%s' already registered\n",
|
||||||
dir->name, dp->name);
|
dir->name, dp->name);
|
||||||
dump_stack();
|
|
||||||
break;
|
break;
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue