Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S936778AbdIZBq7 (ORCPT ); Mon, 25 Sep 2017 21:46:59 -0400 Received: from zeniv.linux.org.uk ([195.92.253.2]:52620 "EHLO ZenIV.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934961AbdIZBq6 (ORCPT ); Mon, 25 Sep 2017 21:46:58 -0400 Date: Tue, 26 Sep 2017 02:46:56 +0100 From: Al Viro To: Linus Torvalds Cc: Kyle Huey , open list , "Robert O'Callahan" Subject: Re: [git pull] vfs.git regression fix Re: Regression related to ipc shmctl compat Message-ID: <20170926014656.GY32076@ZenIV.linux.org.uk> References: <20170926010036.GX32076@ZenIV.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.8.3 (2017-05-23) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 461 Lines: 12 On Mon, Sep 25, 2017 at 06:37:28PM -0700, Linus Torvalds wrote: > And I think your recent compat cleanup work actually made it worse, > showing new warnings (including the one that was a real bug) Actually, they are not new - try make C=2 ipc/compat.o on v4.13 and you'll see their previous locations. > Patch to at least fix the address space warnings in ipc/ attached. Which tree do you prefer it to go through? Direct to mainline, or vfs.git #for-next?