linux-kernel - [PATCH -next 0/5] ipc: EIDRM/EINVAL returns & misc updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat,  6 Jun 2015 06:37:55 -0700
From:	Davidlohr Bueso <dave@...olabs.net>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Manfred Spraul <manfred@...orfullife.com>, dave@...olabs.net,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: [PATCH -next 0/5] ipc: EIDRM/EINVAL returns & misc updates

Hello,

Patches 1,2: Are a resend, I've incorporated them to the set,
based on Manfred's comments.

Patch 3: is a trivial function rename.

Patches 4,5: are attempts to order how Linux ipc deals with EIDRM
and EINVAL return error codes. By looking at corresponding manpages
two possible inverted return codes are returned, these patches
make the manpages accurate now -- but I may have missed something,
and we are changing semantics. afaik EIDRM is specific to Linux
(other OSes only rely on EINVAL), which is already messy, so lets
try to make this consistent at least. 

Passes all ipc related ltp tests.

Thanks!

Davidlohr Bueso (5):
  ipc,shm: move BUG_ON check into shm_lock
  ipc,msg: provide barrier pairings for lockless receive
  ipc: rename ipc_obtain_object
  ipc,sysv: make return -EIDRM when racing with RMID consistent
  ipc,sysv: return -EINVAL upon incorrect id/seqnum

 ipc/msg.c  | 50 +++++++++++++++++++++++++++++++++++++++-----------
 ipc/sem.c  |  4 ++--
 ipc/shm.c  | 13 ++++++++-----
 ipc/util.c | 23 +++++++++++++----------
 ipc/util.h |  2 +-
 5 files changed, 63 insertions(+), 29 deletions(-)

-- 
2.1.4

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