This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH v2 0/3] posix: Execute file function fixes
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: Adhemerval Zanella <adhemerval dot zanella at linaro dot org>
- Cc: libc-alpha at sourceware dot org
- Date: Sat, 20 Feb 2016 10:25:43 -0800
- Subject: Re: [PATCH v2 0/3] posix: Execute file function fixes
- Authentication-results: sourceware.org; auth=none
- References: <1455905134-21014-1-git-send-email-adhemerval dot zanella at linaro dot org> <56C75FE3 dot 2030606 at cs dot ucla dot edu> <56C769A9 dot 6080301 at linaro dot org> <56C773F2 dot 5000608 at cs dot ucla dot edu> <55B9700F-CABA-41B9-88BD-0822F85A5DDA at linaro dot org> <56C7A17F dot 3090701 at cs dot ucla dot edu> <847ABB4E-E0F9-4EB9-939F-B9A24C279D1E at linaro dot org>
Adhemerval Zanella wrote:
Execlp can not because since it can be used in following vfork.
I guess that's OK. Please document that execlp has the same limitations that
execl and execle do, in this area.
the only missing point is total mmap area of posix_spawn which sets a hard limit for old shell argument handling and posix_spawnp. We can either document these limit or add a logic to calculate total argument list and mmap an area to accommodate all of it.
It's better to not impose hard limits of our own.
One other hard limit is that argc cannot exceed INT_MAX; posix_spawn* should
ensure that the argc it computes doesn't go past that.