On 14 Sep 2010 at 11:51, Roland McGrath wrote: > > no it doesn't have to, similarly to how it doesn't have to hardcode > > _SC_PAGESIZE either, AT_PAGESZ tells userland what it needs to know > > and i think AT_ARGMAX could exist just as well. > > I was referring to the ways available to userland heretofore. Certainly, > the kernel could add new ways and then userland could do different things > (with new kernels). > > auxv in particular is not a mechanism that could fit for this. The actual > limit depends on rlimits of the calling process, and rlimits can change > during the life of the program. obviously an AT_ARGMAX computed at execve time would be based on the rlimits as well and if later userland changed the rlimits, it'd be userland's problem, not that of the kernel (or the kernel could refuse a change that would violate its earlier promise). > auxv is only appropriate for things that > are known at the time of the exec and won't change thereafter. you mean stuff like AT_EUID et al.? ;) -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
