Dear Aptly-Named User, The first clue you need to get is that you shouldn't send MIME-encoded, HTML crap to open source mailing lists. Repeatedly sending the same question to half a dozen mailing lists won't solve your problem. (Everyone heard you the first N times already, and it's unlikely that anyone new signed up within the last week who can magically fix the failing mmap cll for you. You have a 100% reproducible problem: no timing dependencies or race conditions. Everytime you make the call with more than a certain size, you nicely get this predictable EINVAL result. You have the source code to everything; you can add debug printk calls anywhere you want and rebuild the kernel. If there are multiple places that can produce an -EINVAL return value, you can precisely identify which one is doing it. Golly, gee, lucky you! This is like the software equivalent of taking a shot against a wide-open net: just kick the ball! What is missing?
