Messages in this thread | | | Date | Sat, 21 Feb 1998 13:42:06 -0500 | From | Bill Hawes <> | Subject | Re: sysclt messages with 2.1.88 |
| |
A.N.Kuznetsov wrote: > > In article <k2wweoud5g.fsf@zero.aec.at> you wrote: > : > unregister_proc_table: neigh not empty! > : > unregister_proc_table: ipv4 not empty! > : > unregister_proc_table: net not empty! > : > > : > What was going on (and wrong)? > > : Just comment out the printk in kernel/sysctl.c. It is harmless. > > Are you sure? I am not. It is possible this operation results in > some zombie d_entry or inode. That guy who inserted > these printks is likely to have any resons to make it. > Actually, it would be intersting to know his opinion.
I put the message in originally while looking for potential problems in freeing sysctl table memory. At the time I was concerned that if a /proc entry wasn't deleted immediately, it would never get freed.
But actually the case is that several sysctl tables may have pointers to the same /proc subdir, and only the last sysctl to be freed would actually release the /proc dir. (At the time of the last free the /proc subdir should be empty so that it can be removed).
So the messages should be harmless and can be removed.
Regards, Bill
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |