summaryrefslogtreecommitdiffstats
path: root/lib/libc/stdio/tmpnam.c
diff options
context:
space:
mode:
authorgreen <green@FreeBSD.org>2004-08-22 18:57:40 +0000
committergreen <green@FreeBSD.org>2004-08-22 18:57:40 +0000
commitf13126589a3656f9cda3ab42d30195773a416e56 (patch)
tree5fadc7d34023c3db9fff404bdb0967e948dbc540 /lib/libc/stdio/tmpnam.c
parenta52623fe5868c94e92560cdd89d2d117d54f2b36 (diff)
downloadFreeBSD-src-f13126589a3656f9cda3ab42d30195773a416e56.zip
FreeBSD-src-f13126589a3656f9cda3ab42d30195773a416e56.tar.gz
The new contigmalloc code is exposing a lot of misuses of busdma memory
allocation. Notably, in this case, the driver tries to allocate several pieces of memory and then fails if the pieces allocated after the first do not come after it physically, and within a specific range (8MB I believe). Of course, this could just as easily fail for any number of reasons, but it almost always fails now that contiguous allocations start at the end of possible specified memory locations rather than the beginning. Allocate all the possibly-needed memory up front, even though it's a waste, to get around this. The least bogus solution would be to take the physical address from the first allocation and create a new tag that specified that further allocations must follow it within that 8MB window, then use that when allocating new channels, but that's left for anyone else that really feels like doing it. Tested by: Erwin Lansing <erwin@lansing.dk>
Diffstat (limited to 'lib/libc/stdio/tmpnam.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud