[PATCH] Print setsockopt warning to ve log [message #428] |
Wed, 30 November 2005 13:57 |
xemul
Messages: 248 Registered: November 2005
|
Senior Member |
|
|
Patch from Pavel (xemul@):
calling get/setsockopt with SO_BSDCOMPAT wil cause printk happen 5 times.
Do we need it in ve0 logs?
--- ./net/core/sock.c.veprn 2005-11-29 19:23:40.000000000 +0300
+++ ./net/core/sock.c 2005-11-30 16:53:51.857133392 +0300
@@ -173,7 +173,7 @@ static void sock_warn_obsolete_bsdism(co
static char warncomm[16];
if (strcmp(warncomm, current->comm) && warned < 5) {
strcpy(warncomm, current->comm);
- printk(KERN_WARNING "process `%s' is using obsolete "
+ ve_printk(VE_LOG, KERN_WARNING "process `%s' is using obsolete "
"%s SO_BSDCOMPAT\n", warncomm, name);
warned++;
}
|
|
|