Zach Brown wrote:
Report counts may be too high due to duplicate recognition of the very
same report.¹
this is true however it's .. a hard issue. It's really hard to
distinguish a duplicate report from
two reports of the same bug.
Can we hack some data in to oops output to help? Say a giant per-boot
anonymous random number (yeah, I know, harder than it sounds) and then
an incrementing oops counter.
there already is a per-boot UUID afaik, just a matter of printing that..
I'll look into that, but it does add extra info to the oops print
That'd also let you discover that the
latter oopses in a chain of oopses might be fall-out from the head of
the chain.
this is there already and taken care of ;)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
