Re: Panics need better handling

[ndiamond]

Willy Tarreau replied to me:

>> But surely every developer or maintainer
>> of every driver or other part of the
>> kernel also has a clear need for every
>> Linux user to install this. I am not
>> the only one who needs to get these
>> reports, right? Shouldn't this be in
>> the main kernel tree by now, and enabled
>> by default?
>
> Well, yes and no. Yes because it's useful, no because there are so many
> other useful tools which would largely replace it and be more complete
> (kdb, lkcd, ...) that one could wonder why it's in the kernel at all.

Every developer or maintainer of every
driver or other part of the kernel wants
every Linux user to use kdb etc.?
I sure hope not.

> Since it's mainly useful to developers, and not too much intrusive, people
> who need it can easily apply it to their tree.

The information contained in the panic
reports is mainly useful to developers.
By not making the information visible
by default to end users, developers
avoid getting reports from end users.
Is this really what we want?  Do we
want to get reports only from failures
that we personally experience?

Although a particular big company is
famous for that attitude (including
not allowing end users to submit bug
reports unless we pay 4,200 yen to
make the submission), it's interesting
that their X Windows version sometimes
offers to call home with a crash report
after rebooting.  They're no longer
100% dedicated to closing their ears
to failures in the field.  Maybe Linux
isn't ready for this yet, but surely
we should not discourage reports from
end users?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/