Jeff Trawick wrote:

problem not seen in 2.0.43, but seen in HEAD

I think the 22 is EINVAL inside the include filter from the attempt to
read a bogus mmap bucket.
My recent changes to core_output_filter can drive cleanups sooner than they were before. I suspect that has something to do with the bogus mmap bucket. I won't take credit for logging EINVAL as an HTTP error or tacking an error document on to the end of normal output though.

I'll see if I can recreate this.

Greg



Reply via email to