I think a security option that does the following would make sense: 1. exec should reduce the hard-limit to FD_SETSIZE unless it's passed a flag 2. When a pro

I think a security option that does the following would make sense: 1. exec should reduce the hard-limit to FD_SETSIZE unless it's passed a flag 2. When a process calls `select` while having a hard-limit > FD_SETSIZE, it gets terminated. (Strictly speaking this doesn't prevent the memory corruption, since it happens in select's support macros, not select itself. But I'd expect it to be good enough in practice) A modern application which doesn't use `select` should raise its own hard-limit during startup, option into the select-termination in exchange for the ability to open many files.