Re:A Google Cloud support engineer solves a tough DNS case
by anonymousisme on Tuesday May 19, 2020 @03:04PM
(#23238775)
Also, 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.
Re:A Google Cloud support engineer solves a tough DNS case
by lalos on Tuesday May 19, 2020 @03:19PM
(#23238942)
Any 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.
Re:A Google Cloud support engineer solves a tough DNS case
by calvinmorrison on Tuesday May 19, 2020 @03:52PM
(#23239349)
until 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.
Re:A Google Cloud support engineer solves a tough DNS case
by saagarjha on Tuesday May 19, 2020 @05:09PM
(#23240220)
Unfortunately, not every engineer has an employer that would let them do this…
Re:A Google Cloud support engineer solves a tough DNS case
by mcguire on Tuesday May 19, 2020 @03:42PM
(#23239237)
"Professional responsibility", if nothing else.
Re:A Google Cloud support engineer solves a tough DNS case
by indigodaddy on Tuesday May 19, 2020 @03:08PM
(#23238820)
Was thinking the exact same thought as I finished up the article...
The bug report resulted in a core fix, which is a better result than if the customer had fixed it themselves of course.