On Fri, Apr 26, 2013 at 2:05 PM, Sedat Dilek <sedat.dilek@xxxxxxxxx> wrote: > On Fri, Apr 26, 2013 at 1:27 AM, <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: >> The mm-of-the-moment snapshot 2013-04-25-16-24 has been uploaded to >> >> http://www.ozlabs.org/~akpm/mmotm/ >> > > Hi Andrew, > > Nice to see that IPC-SEM is now safe again with Linux-Next (next-20130426). > > Affected patches... > > ipcsem-fine-grained-locking-for-semtimedop-do-not-call-sem_lock-when-bogus-sma.patch > ipcsem-fine-grained-locking-for-semtimedop-fix-lockdep-false-positive.patch > ipcsem-fine-grained-locking-for-semtimedop-fix-locking-in-semctl_main.patch > ipcsem-fine-grained-locking-for-semtimedop-ipc-make-refcounter-atomic-fix.patch > ipcsem-fine-grained-locking-for-semtimedop-ipc-make-refcounter-atomic.patch > ipcsem-fine-grained-locking-for-semtimedop-untangle-rcu-locking-with-find_alloc_undo.patch > > Just see one patch has my Tested-by (Reported-by) ... > > All these 6 ipc-sem-next patches were tested several times by me. > > It took me approx 2 weeks and XX kernel-builds. > Please gimme appropriate credits, Thanks. > Today I got several mails on IPC-SEM stuff with CCs to me and Tested-by/Reported-by. All credits were given/respected. Thanks. Hope I could help. - Sedat - > Have a nice weekend, > - Sedat - > > P.S.: Check for Sedat's credits. > > ipcsem-fine-grained-locking-for-semtimedop-fix-lockdep-false-positive.patch:Cc: > Sedat Dilek <sedat.dilek@xxxxxxxxx> > > ipcsem-fine-grained-locking-for-semtimedop-ipc-make-refcounter-atomic.patch:Sedat > reported an issue leading to a NULL dereference in update_queue(): > ipcsem-fine-grained-locking-for-semtimedop-ipc-make-refcounter-atomic.patch:Tested-by: > Sedat Dilek <sedat.dilek@xxxxxxxxx> > > ipcsem-fine-grained-locking-for-semtimedop-ipc-make-refcounter-atomic.patch:Reported-by: > Sedat Dilek <sedat.dilek@xxxxxxxxx> > > ipcsem-fine-grained-locking-for-semtimedop-ipc-make-refcounter-atomic.patch:Cc: > Sedat Dilek <sedat.dilek@xxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
