MP> So you think that all bugs _must_ be reproducable? Good opinion ;-)
This is ABSOLUTELY MUST if you wish fix for them :-) Read files in
Documentation subdir -- there are info about creating usefull bug-report.
MP> I think the author of serial driver should go through the file,
MP> and check any division (grep '[^\*]\/[^\*]' serial.c). He surely
MP> understand his code better than me and can find it in less time.
Looks like you misunderstood situation even more :-(( Why you are so sure that
error in serial.c ? Just since it was produced by setserial ??? Gosh. You are
joking, right ? Error could be in A LOT OF places in kernel or even in setserial
itself (kernel is not designed to cope with all broken programs started by
root) including all libraries used by setserial and even compiler used to
compiler kernel/or setserial. To find source of error you should be able to
reproduce it or AT LEAST have kernel compilation options handy and decrypted
(via ksymoops) oops-message. Thus you bug report is COMPLETELY useless. All bug
reports where are no usefull info (like your bugreport) are forwarded to
/dev/null by all matainers. One exception: if you just found already well-known
bug.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/