This patch fixes the issue. I had a similar fix, but yours is more complete. Thanks.
Another thought. As I looked at this multiblock code I realize it will have some impact on memory usage. Thinking it might be good to have an option to disable the function at runtime so one can chose between memory savings and performance. Particularly in the main branch where these OPENSS_NO_XXX compile time options are going away ? >-- Original Message -- > > > > >On 28/02/15 06:53, Erik Forsberg wrote: >> Hi. >> I seem to have run into a really hard to pin down issue in >> OpenSSL 1.0.2. Normally, it simply causes an EFAULT during >> a write syscall, which makes me close the connection, but >> to investigate, I added a core dump at that time. This is what I see >> > > >Hi Erik > >Thanks for the really useful analysis of this issue. > >Please could you try out the attached patch and see if that solves >things for you? Let me know how you get on. > >Many thanks > >Matt > > >Attachment: multiblock.patch (0.5 KB) > >_______________________________________________ >openssl-dev mailing list >To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev _______________________________________________ openssl-dev mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev
