no MAX_ARG_PAGES -v2
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 24 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | arch: personality independent stack topinclude/ include/ include/ +19 more | +29 | 0 replies | |
| 2/3 | audit: rework execve auditfs/ include/ kernel/ +1 more | +78 | 3 replies | |
| 3/3 | mm: variable length argument supportarch/ arch/ arch/ +12 more | +541 | 9 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.
| Patch | Tony Luck | Ingo Molnar |
|---|---|---|
| Series | A-b | A-b |
| 1/3 | ||
| 2/3 | ||
| 3/3 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [patch 0/3] no MAX_ARG_PAGES -v2
This patch-set aims at removing the current limit on argv+env space aka. MAX_ARG_PAGES.
The new mm is created before the binfmt code runs, the stack is placed at the highest address supported by that architecture.
The argv+env data is then copied from the old mm into the new mm (which is inactive at that time - this introduces some cache coherency issues).
Then we run the binfmt code, which will compute the final stack address. The existing stack will be moved downwards (or upwards on PA-RISC) to the desired place.
This 'trick' heavily relies on the MMU, so for no-MMU archs we stay with the old approach.
---
Plenty of changes all around, changes listed in the individual patches. We hope to have addressed all issues raised.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>