Re: [PATCH -mm][AIO] Fix AIO completion signal notification possible ref leak

2007-02-06 Thread Sébastien Dugué
On Mon, 5 Feb 2007 20:13:35 +0300 Oleg Nesterov <[EMAIL PROTECTED]> wrote: > On 02/05, S?bastien Dugu? wrote: > > > > Make sure we only accept valid sigev_notify values in > > aio_setup_sigevent(), > > namely SIGEV_NONE, SIGEV_THREAD_ID or SIGEV_SIGNAL. > > I think this is correct, but I have

Re: [PATCH -mm][AIO] Fix AIO completion signal notification possible ref leak

2007-02-05 Thread Oleg Nesterov
On 02/05, S?bastien Dugu? wrote: > > Make sure we only accept valid sigev_notify values in aio_setup_sigevent(), > namely SIGEV_NONE, SIGEV_THREAD_ID or SIGEV_SIGNAL. I think this is correct, but I have another concern (most probably I just confused looking at non-applied patch), could you re-c

[PATCH -mm][AIO] Fix AIO completion signal notification possible ref leak

2007-02-05 Thread Sébastien Dugué
Andrew, here is an incremental patch to fix a possible ref leak when users do weird things with the ->sigev_notify flags. Thanks Oleg for spotting this. Sébastien. From: Sébastien Dugué <[EMAIL PROTECTED]> Fix AIO completion signal notification possible ref leak Make sure