kernel-2.6.9: make sock_init() notice errors

Hi list,
by accident i found that that sock_init never checks the return code of called init functions. I have no idea why this is not done so i added only a printk() to inform the user about the problem.
The function returns no error indicator. i left it this way.

Quoted 5 lines · walter harms

Hi list,
by accident i found that that sock_init never checks the return code of called init functions. I have no idea why this is not done so i added only a printk() to inform the user about the problem.
The function returns no error indicator. i left it this way.

I don't like this patch: it doesn't really do anything useful... ie. if user runs out of memory on boot, he'll have other problems than caring about sock_init failing somewhere.

Comments?

Also, there's still whitespace damage like:

Review

Quoted 2 lines

(quoted diff) +2 -0

+	ret=init_inodecache();
+	if ( ret < 0 ) {

Quoted 5 lines · walter harms

Hi list,
by accident i found that that sock_init never checks the return code of called init functions. I have no idea why this is not done so i added only a printk() to inform the user about the problem.
The function returns no error indicator. i left it this way.

I don't like this patch: it doesn't really do anything useful... ie. if user runs out of memory on boot, he'll have other problems than caring about sock_init failing somewhere.

Comments?

Hi domen, hi list,

its true that the user can not do much about missing memmory but he should know WHAT error occured.
NTL not checking returncodes is an error.
Continuing when one earlier function did not work is also an error and may cause problems in unexspected places.
Since this is an init code its no performance consideration to be made.

re,
walter

Quoted 4 lines · Domen Puncer

Also, there's still whitespace damage like:

Review

Quoted 2 lines

(quoted diff) +2 -0

+	ret=init_inodecache();
+	if ( ret < 0 ) {