Re: ipc/sem.c: change perform_atomic_semop parameters

From: Dave Jones
Date: Tue Jun 10 2014 - 10:19:49 EST


On Fri, Jun 06, 2014 at 11:50:06PM +0000, Linux Kernel wrote:
> Gitweb: http://git.kernel.org/linus/;a=commit;h=d198cd6d6d02d0a335af2deacb60816ebb4719d1
> Commit: d198cd6d6d02d0a335af2deacb60816ebb4719d1
> Parent: 2f2ed41dcaec34f2d6f224aa84efcc5a9dd8d5c3
> Refname: refs/heads/next
> Author: Manfred Spraul <manfred@xxxxxxxxxxxxxxxx>
> AuthorDate: Fri Jun 6 14:37:49 2014 -0700
> Committer: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
> CommitDate: Fri Jun 6 16:08:15 2014 -0700
>
> ipc/sem.c: change perform_atomic_semop parameters
>
> Right now, perform_atomic_semop gets the content of sem_queue as
> individual fields. Changes that, instead pass a pointer to sem_queue.
>
> This is a preparation for the next patch: it uses sem_queue to store the
> reason why a task must sleep.
>
> Signed-off-by: Manfred Spraul <manfred@xxxxxxxxxxxxxxxx>
> Cc: Davidlohr Bueso <davidlohr.bueso@xxxxxx>
> Cc: Michael Kerrisk <mtk.manpages@xxxxxxxxx>
> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
> Signed-off-by: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>

After this patch, coverity started complaining about a potential deref
after null check. (It may have been a problem before, but the code motion
causes a new 'event')

33. var_compare_op: Comparing un to null implies that un might be null.
1878 if (un && un->semid == -1)
1879 goto out_unlock_free;
1880
1881 queue.sops = sops;
1882 queue.nsops = nsops;
34. alias_transfer: Assigning: queue.undo = un.
1883 queue.undo = un;
1884 queue.pid = task_tgid_vnr(current);
1885 queue.alter = alter;
1886

CID 1222114 (#1 of 1): Dereference after null check (FORWARD_NULL)
35. var_deref_model: Passing &queue to perform_atomic_semop, which dereferences null queue.undo. [show details]
1887 error = perform_atomic_semop(sma, &queue);


Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/