From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932195AbcEKKZW (ORCPT ); Wed, 11 May 2016 06:25:22 -0400 Received: from vmicros1.altlinux.org ([194.107.17.57]:60528 "EHLO micros1.altlinux.org" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751395AbcEKKZV (ORCPT ); Wed, 11 May 2016 06:25:21 -0400 Date: Wed, 11 May 2016 13:25:18 +0300 From: "Dmitry V. Levin" To: Thomas Gleixner Cc: Ingo Molnar , "H. Peter Anvin" , x86@kernel.org, Christoph Hellwig , LKML , Milosz Tanski , Al Viro Subject: Re: [PATCH] x86: use compat version for preadv2 and pwritev2 Message-ID: <20160511102518.GA31189@altlinux.org> References: <20160511084817.GA29823@altlinux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, May 11, 2016 at 12:14:11PM +0200, Thomas Gleixner wrote: > On Wed, 11 May 2016, Dmitry V. Levin wrote: > > Similar to preadv and pwritev, preadv2 and pwritev2 need compat entries > > in the 32-bit syscall table. > > So this is 2016 and we added a syscalls which require compat support. What's > wrong here? I'm not sure I understand your question, it looks to me as "why do we add syscalls that require compat support". If that's what you are asking, I have no idea, I'm a strace man. -- ldv