[RHEL 5.4] [RHEL 4.8]SIGSEGV on aio_read()/aio_write() after failed to create a helper thread

Solution Verified - Updated -

Issue

  • If you called aio_read()/aio_write() and it failed to create a helper thread for it due to something wrong, the next calling will result in SIGSEGV, because the first failure has corrupted the AIO linked lists (freelist and requestlist).

Environment

  • Red Hat Enteprise Linux 5 Update 4
  • glibc-2.5-42
  • Red Hat Enterprise Linux 4 update 8
  • glibc-2.3.4-2.43.el4_8.2
  • Architecture: x86_64

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.