[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Patches] lio_listio() doesn't validate the aio_lio_opcode?

On 2012å02æ23æ 23:36, Carlos O'Donell wrote:

On Thu, Feb 23, 2012 at 12:48 AM, Kang Kai<Kai.Kang@xxxxxxxxxxxxx>  wrote:

The value gets passed down to the AIO layer.

In sysdeps/pthread/aio_misc.c we have code to process LIO_READ,
LIO_WRITE, LIO_DYSNC, LIO_SYNC and then:
~~~
           else
             {
               /* This is an invalid opcode.  */
               aiocbp->aiocb.__return_value = -1;
               __set_errno (EINVAL);
             }
~~~


Why don't set __error_code at same time?

Good question. Please file a bug?

Thanks. I filed a bug on glibc bugzillia:
http://sourceware.org/bugzilla/show_bug.cgi?id=13740

Regards,
Kai



Cheers,
Carlos.


_______________________________________________
Patches mailing list
Patches@xxxxxxxxxx
http://eglibc.org/cgi-bin/mailman/listinfo/patches