News for hackers. Stuff that matters.
Re:Are we shooting ourselves in the foot with stack overflows? by chiph on Tuesday February 18, 2014 @08:36AM (#7258017)
But having some additional capacity available gives them the ability to do field upgrades. The firm I worked for a while ago had to undertake a very expensive hardware refresh because there just wasn't any way to get any additional bug fixes into the field -- they were down to 20 bytes free. In something like a car, that you know people are going to drive for 10+ years, you need that extra space not only to make bug fixes, but also to comply with new legislation (such as brake override), and also to offer a few new features to your customers.
Re:Are we shooting ourselves in the foot with stack overflows? by sitkack on Tuesday February 18, 2014 @10:44AM (#7258677)
Another valuable engineering lesson; Always Have Headroom. If one designs or operates to the limit there is no margin for error. Resilient systems can get pushed beyond their acceptable limits and recover.
Re:Are we shooting ourselves in the foot with stack overflows? by pnathan on Tuesday February 18, 2014 @12:21PM (#7259441)
1+.

IMO, You need several sets of limits: standard limits posted to the consumer, engineering limits posted to the techie/maintenance guy/developer/etc, and actual limits.... each of those is comfortably beyond the others. Know the actual limit, but design well under that if at all possible, because the system will be misused.

Re:Are we shooting ourselves in the foot with stack overflows? by weland on Tuesday February 18, 2014 @03:46PM (#7260918)
It would be stupid of me to disagree. One should always leave headroom for bugfixes, future expansion and so on; it's only mindlessly throwing hardware at problems that I disagree with, not futureproof engineering.