Hello,
When using /proc/net/tcp in the following manner:
while true
do
cat /proc/net/tcp
sleep 3
done
I can regularly get the kernel to hard lock in 2.1.121. (2.1.125
doesn't show any changes in proc.c related to the function
that takes care of this). I can see that Alexey commented in
the code that he also got his machine to hard lock but I cannot
tell from his context whether it was because of using lock_sock
or the current version which uses SOCKHASH_LOCK() (which
translates into a start_bh_atomic()).
I'd like to use this as a clean way to pulling some information out
of the kernel (I've changed what data gets passed back for my thesis)
but I obviously don't want it to lock up during my defense! =)
I must admit to being a bit baffled by why it could crash inside of
the locks. Is this a bug with a known solution waiting to be fixed?
If so, someone pointing me in the right direction could result in
me sending back a patch. It would be nice if this worked right for
2.2.
-Steve
--
______________________________________________________________________________
Steve Shah ([EMAIL PROTECTED]) | SysAdmin/Coder/Gabbernaut/DJ/Writer/Minister
http://www.cs.ucr.edu/~sshah | We're not dropping out, we're infiltrating.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Beating code into submission, one operating system at a time...
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
