From: valdis.kletnieks@vt.edu
To: Manfred Spraul <manfred@colorfullife.com>,
Kees Cook <keescook@chromium.org>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: linux-next 20170519 - semaphores broken
Date: Sat, 20 May 2017 16:18:50 -0400 [thread overview]
Message-ID: <3130.1495311530@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 954 bytes --]
Seeing problems with programs that use semaphores. The one
that I'm getting bit by is jackd. strace says:
getuid() = 967
semget(0x282929, 0, 000) = 229376
semop(229376, [{0, -1, SEM_UNDO}], 1) = -1 EIDRM (Identifier removed)
write(2, "JACK semaphore error: semop (Ide"..., 49JACK semaphore error: semop (Identifier removed)
) = 49
Bisects down to this commit, and reverting it from 20170519 makes things work
again. No idea why this causes indigestion, there's probably something subtly
wrong here....
commit 337f43326737b5eb28eb13f43c27a5788da0f913
Author: Manfred Spraul <manfred@colorfullife.com>
Date: Fri May 19 07:39:23 2017 +1000
ipc: merge ipc_rcu and kern_ipc_perm
ipc has two management structures that exist for every id:
- struct kern_ipc_perm, it contains e.g. the permissions.
- struct ipc_rcu, it contains the rcu head for rcu handling and
the refcount.
[-- Attachment #2: Type: application/pgp-signature, Size: 486 bytes --]
next reply other threads:[~2017-05-21 0:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 20:18 valdis.kletnieks [this message]
2017-05-21 5:20 ` Kees Cook
2017-05-21 18:12 ` Manfred Spraul
2017-05-23 20:27 ` Kees Cook
2017-05-21 14:09 ` Manfred Spraul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3130.1495311530@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®