From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754583Ab3KCUTW (ORCPT ); Sun, 3 Nov 2013 15:19:22 -0500 Received: from mx1.redhat.com ([209.132.183.28]:4302 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753678Ab3KCUTV (ORCPT ); Sun, 3 Nov 2013 15:19:21 -0500 Date: Sun, 3 Nov 2013 21:20:37 +0100 From: Oleg Nesterov To: Namhyung Kim Cc: Steven Rostedt , Namhyung Kim , Masami Hiramatsu , Hyeoncheol Lee , Hemant Kumar , LKML , Srikar Dronamraju , "zhangwei(Jovi)" , Arnaldo Carvalho de Melo Subject: Re: [PATCH 10/13] tracing/uprobes: Fetch args before reserving a ring buffer Message-ID: <20131103202037.GA2785@redhat.com> References: <1383029621-7384-1-git-send-email-namhyung@kernel.org> <1383029621-7384-11-git-send-email-namhyung@kernel.org> <20131101150910.GA18278@redhat.com> <20131101152232.GA2703@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131101152232.GA2703@redhat.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/01, Oleg Nesterov wrote: > > Ah, please ignore... handler_chain() is not self-serialized, so > tu->buffer needs locking/waiting too. Still I have to admit that I strongly dislike this yet another (and imho strange) memory pool. However, I am not going to argue because I can't suggest something better right now. But. Perhaps it makes sense to at least add a couple of trivial helpers in 10/13? Something like arg_buf_get/put/init, just to simplify the potential changes. Also. I think we should not use this pool unconditionally but again, this is another improvement we can do later. Oleg.