From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754499AbbIOOcF (ORCPT ); Tue, 15 Sep 2015 10:32:05 -0400 Received: from s3.sipsolutions.net ([5.9.151.49]:34737 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752968AbbIOOcD (ORCPT ); Tue, 15 Sep 2015 10:32:03 -0400 Message-ID: <1442327514.1914.31.camel@sipsolutions.net> Subject: Re: [PATCH RFC v3 1/6] exterr: Introduce extended syscall error reporting From: Johannes Berg To: Alexander Shishkin , Jonathan Corbet Cc: Peter Zijlstra , Ingo Molnar , linux-kernel@vger.kernel.org, vince@deater.net, eranian@google.com, Arnaldo Carvalho de Melo Date: Tue, 15 Sep 2015 16:31:54 +0200 In-Reply-To: <87a8snn4zz.fsf@ashishki-desk.ger.corp.intel.com> References: <1441987205-4021-1-git-send-email-alexander.shishkin@linux.intel.com> <1441987205-4021-2-git-send-email-alexander.shishkin@linux.intel.com> <20150914141931.39f6be92@lwn.net> <87a8snn4zz.fsf@ashishki-desk.ger.corp.intel.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.16.3-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2015-09-15 at 17:15 +0300, Alexander Shishkin wrote: > > > It seems to me that current->ext_err_code needs to be cleared on > > each system call entry (except for your special prctl() of > > course!). > > I'd say, it should be up to the program to decide for how long they > want to keep the extended error code around. > I'm not convinced that works - imagine a library wanting to use the prctl(), but the main application isn't doing that. Should the library clear it before every call, to be sure it's not getting stale data? etc. johannes