From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754078AbeC1Pbn (ORCPT ); Wed, 28 Mar 2018 11:31:43 -0400 Received: from esa2.hgst.iphmx.com ([68.232.143.124]:10969 "EHLO esa2.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753119AbeC1Pbj (ORCPT ); Wed, 28 Mar 2018 11:31:39 -0400 X-IronPort-AV: E=Sophos;i="5.48,372,1517846400"; d="scan'208";a="171267713" Subject: Re: [PATCH 1/2] target: drop spin_lock_assert() + irqs_disabled() combo checks To: "bigeasy@linutronix.de" Cc: "rostedt@goodmis.org" , "daniel@bristot.me" , "linux-kernel@vger.kernel.org" , "peterz@infradead.org" , "torvalds@linux-foundation.org" , "tglx@linutronix.de" , "acme@kernel.org" , "nab@linux-iscsi.org" , "williams@redhat.com" , "linux-scsi@vger.kernel.org" , "lclaudio@redhat.com" , "target-devel@vger.kernel.org" , "linux-rt-users@vger.kernel.org" References: <20180321153854.GB24312@kernel.org> <20180322093745.GC4229@kernel.org> <20180323155513.dwbgvblenlji33as@linutronix.de> <1521822325.2535.5.camel@wdc.com> <20180323171736.bcyi2oiolge4l6hl@linutronix.de> <20180326111359.180f1604@gandalf.local.home> <20180328101553.uduqsdbxwnxrhl7a@linutronix.de> <20180328151433.elhw6kgxdxq6fn6b@linutronix.de> From: Bart Van Assche Message-ID: <86c1243e-8733-c94d-d8ff-5c299b8266a6@wdc.com> Date: Wed, 28 Mar 2018 08:31:38 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180328151433.elhw6kgxdxq6fn6b@linutronix.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 03/28/18 08:14, bigeasy@linutronix.de wrote: > On 2018-03-28 15:05:41 [+0000], Bart Van Assche wrote: >> The names of the two functions touched by patch 1/2 start with a double >> underscore. That by itself is already a hint that these should be called with >> a lock held (I know that this is not a universal convention in the Linux >> kernel). I'm fine either way - either with patch 1/2 as posted or patch 1/2 >> with the above comment added. > > Okay. In that case let me update 1/2. > But 2/2 with the comment as Steven suggested is still a no no for you? Although I'm not enthusiast about patch 2/2, if others agree with that patch I'm fine with that patch being sent upstream. Thanks, Bart.