4 ms·
I think what he's trying to suggest is that the customer may have been able to isolate the issue faster by walking through the provisioning settings for the mac
by brightball 6y ago
I think what he's trying to suggest is that the customer may have been able to isolate the issue faster by walking through the provisioning settings for the machine to identify core changes.
The bug report resulted in a core fix, which is a better result than if the customer had fixed it themselves of course.
- anonymousisme 6y agoAlso, it was very nice of Google to follow up and submit the patch to LKML. IMHO this goes beyond the scope of their role. They could have taken a more selfish approach and accepted the bug as "normal" behavior, and advised their customer to not configure the buffer to such an enormous size.
- indigodaddy 6y agoWas thinking the exact same thought as I finished up the article...
- lalos 6y agoAny decent engineer would smile at the fact that they just found a bug in this type of open source stack and happily submit it. Feel this is more of a side effect of individual behavior rather than company policy.
- mcguire 6y ago"Professional responsibility", if nothing else.
- calvinmorrison 6y agountil you hit something like "bug reports should be subitted to here, not there and filled out with appropriate information, matching triplicate documents and make sure to CC the grand puba, also CLOSED-WONTFIX" enough times and you just stop submitting requests.
- saagarjha 6y agoUnfortunately, not every engineer has an employer that would let them do this…