Re: bug in /net/core/dev.c

Hi, Here is the patch again for the benefit of those who are allergic to opening enclosures. I believe it will only take about 30 seconds of "real thinking" for those familiar with dev.c to make an evaluation of the patch. Those already familiar with the bug can skip this paragraph, The bug fi

bug in /net/core/dev.c

Hi, I found this bug in dev.c It happens if register_netdevice is called before net_dev_init which can happen from init functions, when device drivers are compiled into the kernel. The dev->refcnt will go up to 2 ( it should be 1) unregister_netdevice will usually loop forever waiting for th

Is a process with a priority of 0 legal ?

If it is the 2.2.16 scheduler & other linux'es have a bug. The following code snippets can go into a tight loop. while (p != &init_task) { if (can_schedule(p)) { int weight = goodness(prev, p, this_cpu); if (weight > c) c = weight, next = p; }

Question regarding kernel_threads

Hi, I'm using kernel threads in my driver & they work fine however I'm getting left with zombie processes when they exit. As I have no parent process calling wait. I've tried attaching making init my parent process this doesn't appear to help. The new daemonize function in 2.3 doesn't fix this