Issue

• panic in aio_put_req triggered by incorrect reference counter while doing AIO on a file residing on VxFS
• Kernel oops in aio_put_req(), indicating an incorrect 'req->ki_users' value.
• Oops message similar to the following:

Kernel BUG at fs/aio.c:647
invalid opcode: 0000 [1] SMP
Modules linked in: mptctl mptbase ipmi_si(U) ipmi_devintf(U) ipmi_msghandler(U) vxodm(PFU) vxgms(PU) vxglm(PU) vxfen(PU) gab(PU) llt(PU) autofs4 hidp l2cap bluetooth dmpalua(PU) vxspec(PFU) vxio(PFU) vxdmp(PU) lockd sunrpc vxportal(PFU) fdd(PFU) vxfs(PU) dm_round_robin ...
Pid: 28493, comm: java Tainted: PF    2.6.18-194.11.4.el5 #1
RIP: 0010:[<ffffffff800ef5be>]  [<ffffffff800ef5be>] __aio_put_req+0x2b/0x1de
...
Process java (pid: 28493, threadinfo ffff8104ea570000, task ffff8105069e80c0)
...
Call Trace:
[<ffffffff800ef793>] aio_put_req+0x22/0x30
[<ffffffff800f0a0f>] io_submit_one+0x46d/0x499
[<ffffffff800f0f4f>] sys_io_submit+0xbe/0x1a4
[<ffffffff8005d28d>] tracesys+0xd5/0xe0

Code: 0f 0b 68 8d 2b 2b 80 c2 87 02 31 c0 85 d2 0f 85 96 01 00 00
RIP  [<ffffffff800ef5be>] __aio_put_req+0x2b/0x1de