Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932444AbbFFNiS (ORCPT ); Sat, 6 Jun 2015 09:38:18 -0400 Received: from smtp2.provo.novell.com ([137.65.250.81]:59828 "EHLO smtp2.provo.novell.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752814AbbFFNiK (ORCPT ); Sat, 6 Jun 2015 09:38:10 -0400 From: Davidlohr Bueso To: Andrew Morton Cc: Manfred Spraul , dave@stgolabs.net, linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: [PATCH -next 0/5] ipc: EIDRM/EINVAL returns & misc updates Date: Sat, 6 Jun 2015 06:37:55 -0700 Message-Id: <1433597880-8571-1-git-send-email-dave@stgolabs.net> X-Mailer: git-send-email 2.1.4 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1379 Lines: 41 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/