From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934007AbdEORTX (ORCPT ); Mon, 15 May 2017 13:19:23 -0400 Received: from mail-wm0-f67.google.com ([74.125.82.67]:34914 "EHLO mail-wm0-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756729AbdEORTW (ORCPT ); Mon, 15 May 2017 13:19:22 -0400 From: Manfred Spraul To: mtk.manpages@gmail.com, Andrew Morton , Kees Cook Cc: LKML , 1vier1@web.de, Davidlohr Bueso , mingo@kernel.org, peterz@infradead.org, fabf@skynet.be, Manfred Spraul Subject: [PATCH 0/2] Misc cleanups for ipc Date: Mon, 15 May 2017 19:19:09 +0200 Message-Id: <20170515171912.6298-1-manfred@colorfullife.com> X-Mailer: git-send-email 2.9.3 In-Reply-To: <20170508222345.GA52073@beast> References: <20170508222345.GA52073@beast> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi all, could you check the following three patches? As explained, I try to combine the changes for static analyzers and for the randstruct gcc plugin with cleanups. 0001-ipc-sem.c-remove-sem_base-embed-struct-sem.patch: sem_base is not needed. Instead of improving the casts, remove it entirely. 0002-ipc-merge-ipc_rcu-and-kern_ipc_perm.patch struct ipc_rcu and struct kern_ipc_perm are always used together. Thus merge them. 0003-include-linux-sem.h-Correctly-document-sem_ctime.patch Noticed by chance: The comment regarding sem_ctime is wrong/ misleading. And man semctl(2) contains the same wrong comment. Especially: @Kees: Do the patches resolve all warnings? @Andrew: Could you add them to your tree? And can we still aim for 4.13? @Michael: Should we update man semctl(2)? Several years ago, I did a review and found that sem_ctime is only for Coherent the time of the last change... http://calculix-rpm.sourceforge.net/sysvsem.html -- Manfred