On Mon, Dec 03, 2007 at 01:28:33PM +0100, Ingo Molnar wrote:
lsof | grep programname
Not sure it is better on all measures.
One problem is how to distingush again between program abort
(which only affects the program) and IO abort (which leaves
EIO marked pages in the page cache affecting other processes too)
umount -f does this at last.
I didn't think TASK_KILLABLE has solved that cleanly (although
I admit I haven't read the latest patchkit, perhaps that has changed
over the first iteration)
But it also probably doesn't make things much worse than they were before.
Not sure what is that less intelligent in retry (you're
refering to more CPU cycles needed?), but I admit I haven't
thought very deeply about that.
The clear blame vector bit was unclear.
Well i consider a backtrace excessively bogus.
So it will hit everybody first before they can figure out how
to get rid of it? That was the part I was objecting too.
If it is decided to warn about something which is not 100% clear a bug
(and I think I have established this for now -- at least you didn't
object to many of my examples...) then the likely
false positives shouldn't be too obnoxious. Backtraces are unfortunately
obnoxious and always come at a high cost (worried user, linux reputation
as a buggy OS, mailing list bandwidth, support load etc.) and having that
for too many false positives is a bad thing.
My objection was not really for SLES, but for general Linux kernel