Messages in this thread | | | Date | Sun, 10 Jun 2001 18:02:08 +0200 (METDST) | From | Alois Treindl <> | Subject | Re: [PATCH] Re: Oops with kernel 2.4.5 on heavy disk traffic |
| |
On Sun, 10 Jun 2001, Alexander Viro wrote:
> Please, apply. What's happing here is simple - we set i_ino by > PID and get something out of range of per-process inode. Confusion > follows... Fix: move initializing ->u.proc_i.task past the check. > Then proc_delete_inode() will be happy with it. > Alois, Bryce - that ought to fix the oopsen you see.
Alexander
do I read this right: this is not a very critical bug? In my case, it was 'top' which crashed twice (I was unable to reproduce this while trying hard in the last 4 hours, after the original two cases).
Are any processes which are not - like top or ps - trying to read the /proc file system likely to be affected by the bug?
I am a bit worried about applying 'unauthorized' kernel paches to my server. This has created problems for me in the past.
So, it the bug is non critical, I would rather accept the occasional crash of 'top' or 'ps' than playing around with kernel code.
Please, comment.
Alois
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |