> > Brad, sorry, I have bad news. glibc sysconf(_SC_ARG_MAX) is implemented > > by hard coded RLIMIT_STACK/4 heuristics. That said, at least _now_, we > > can't change this even though you disliked. That said, we can't break > > userland even though userland library is very crazy. > > I'm sorry you think it's "very crazy" to implement the required > functionality in the only way available. POSIX requires that execve > fail with E2BIG when the ARG_MAX limit is exceeded. sysconf has to > return the correct actual limit that execve will enforce so that a > conforming application knows how much it can safely attempt to use. > Since the kernel uses the hard-coded RLIMIT_STACK/4 heuristic and does > not expose the true manifest limit any other way, sysconf has to > parallel the kernel's calculation. Hmm... Probably my poor english leaded to misunderstood. I didn't intent glibc is very crazy. I only intended to "even if userland is crazy, I disagree to break userland". And yes, we obviously need to expose ARG_MAX limit to libc. a duplicated heuristic code easily makes confusion and mistake. nobody want such fragile state. however, it's a bit offtopic. anyway. Thanks. -- 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
