Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 Jan 2016 14:53:07 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-amd64@FreeBSD.org
Subject:   [Bug 206396] Crash while concurrent POSIX semaphore access
Message-ID:  <bug-206396-6-d5aTCnDVZ4@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206396-6@https.bugs.freebsd.org/bugzilla/>
References:  <bug-206396-6@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D206396

--- Comment #1 from commit-hook@freebsd.org ---
A commit references this bug:

Author: jilles
Date: Fri Jan 22 14:52:31 UTC 2016
New revision: 294565
URL: https://svnweb.freebsd.org/changeset/base/294565

Log:
  sem: Don't free nameinfo that is still in list when open() fails.

  This bug could be reproduced easily by calling sem_open() with O_CREAT |
  O_EXCL on a semaphore that is already open in the process. The struct
  sem_nameinfo would be freed while still in sem_list and later calls to
  sem_open() or sem_close() could access freed memory.

  PR:           206396
  MFC after:    5 days

Changes:
  head/lib/libc/gen/sem_new.c
  head/tools/regression/posixsem2/semtest.c

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-206396-6-d5aTCnDVZ4>