Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760173AbYLQJku (ORCPT ); Wed, 17 Dec 2008 04:40:50 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760064AbYLQJkZ (ORCPT ); Wed, 17 Dec 2008 04:40:25 -0500 Received: from zeniv.linux.org.uk ([195.92.253.2]:43842 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760032AbYLQJkW (ORCPT ); Wed, 17 Dec 2008 04:40:22 -0500 Date: Wed, 17 Dec 2008 09:40:15 +0000 From: Al Viro To: James Morris Cc: Al Viro , linux-audit@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [PATCH 7/15] sanitize AUDIT_MQ_SENDRECV Message-ID: <20081217094015.GD28946@ZenIV.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 17, 2008 at 06:40:54PM +1100, James Morris wrote: > On Wed, 17 Dec 2008, Al Viro wrote: > > > > > * logging the original value of *msg_prio in mq_timedreceive(2) > > is insane - the argument is write-only (i.e. syscall always > > ignores the original value and only overwrites it). > > I wonder if any existing certifications need to be amended. I rather doubt it, but I really don't know the bureaucracy of that. Just to clarify: Old code logs the value of *msg_prio; that value is always ignored by syscall (it may store something there, but that's it - pure output parameter) New code does not change the format of log message; the value in that field of the message is replaced with 0. That's the only difference. Whether that requires amending of the existing certs... bugger if I know. -- 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/