Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | fix off-by-one in bounds check in fpathconf | Rich Felker | 2015-03-30 | 1 | -1/+1 |
| | | | | | | | | this error resulted in an out-of-bounds read, as opposed to a reported error, when calling the function with an argument one greater than the max valid index. (cherry picked from commit 3bed89aa7456d9fe30e550cb5e21f8911036695b) | ||||
* | support configurable page size on mips, powerpc and microblaze | Szabolcs Nagy | 2013-09-15 | 1 | -5/+5 |
| | | | | | | | | | | | | | | | | PAGE_SIZE was hardcoded to 4096, which is historically what most systems use, but on several archs it is a kernel config parameter, user space can only know it at execution time from the aux vector. PAGE_SIZE and PAGESIZE are not defined on archs where page size is a runtime parameter, applications should use sysconf(_SC_PAGE_SIZE) to query it. Internally libc code defines PAGE_SIZE to libc.page_size, which is set to aux[AT_PAGESZ] in __init_libc and early in __dynlink as well. (Note that libc.page_size can be accessed without GOT, ie. before relocations are done) Some fpathconf settings are hardcoded to 4096, these should be actually queried from the filesystem using statfs. | ||||
* | in pathconf, -1, not 0, means unsupported.. syncio presumably works, too. | Rich Felker | 2011-08-16 | 1 | -3/+3 |
| | |||||
* | fix bogus pathconf result for file size bits | Rich Felker | 2011-08-16 | 1 | -1/+1 |
| | |||||
* | initial check-in, version 0.5.0 v0.5.0 | Rich Felker | 2011-02-12 | 1 | -0/+35 |