tipc: limit error messages relating to memory leak to one line
With the default name table size of 1024, it is possible that the sanity check in tipc_nametbl_stop could spam out 1024 essentially identical error messages if memory was corrupted or similar. Limit it to issuing no more than a single message. The actual chain number (i.e. 0 --> 1023) wouldn't provide any useful insight if/when such an instance happened, so don't bother printing out that value. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
This commit is contained in:
@@ -940,8 +940,10 @@ void tipc_nametbl_stop(void)
|
|||||||
/* Verify name table is empty, then release it */
|
/* Verify name table is empty, then release it */
|
||||||
write_lock_bh(&tipc_nametbl_lock);
|
write_lock_bh(&tipc_nametbl_lock);
|
||||||
for (i = 0; i < tipc_nametbl_size; i++) {
|
for (i = 0; i < tipc_nametbl_size; i++) {
|
||||||
if (!hlist_empty(&table.types[i]))
|
if (hlist_empty(&table.types[i]))
|
||||||
err("tipc_nametbl_stop(): hash chain %u is non-null\n", i);
|
continue;
|
||||||
|
err("tipc_nametbl_stop(): orphaned hash chain detected\n");
|
||||||
|
break;
|
||||||
}
|
}
|
||||||
kfree(table.types);
|
kfree(table.types);
|
||||||
table.types = NULL;
|
table.types = NULL;
|
||||||
|
Reference in New Issue
Block a user