From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751805AbdH2JBs (ORCPT ); Tue, 29 Aug 2017 05:01:48 -0400 Received: from bombadil.infradead.org ([65.50.211.133]:50184 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751368AbdH2JBq (ORCPT ); Tue, 29 Aug 2017 05:01:46 -0400 Date: Tue, 29 Aug 2017 11:01:30 +0200 From: Peter Zijlstra To: Byungchul Park Cc: mingo@kernel.org, tj@kernel.org, boqun.feng@gmail.com, david@fromorbit.com, johannes@sipsolutions.net, oleg@redhat.com, linux-kernel@vger.kernel.org, kernel-team@lge.com Subject: Re: [PATCH 4/4] lockdep: Fix workqueue crossrelease annotation Message-ID: <20170829090130.m5zarou3t3tjfjlf@hirez.programming.kicks-ass.net> References: <20170823115843.662056844@infradead.org> <20170823121432.990701317@infradead.org> <20170829064637.GC3240@X58A-UD3R> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170829064637.GC3240@X58A-UD3R> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 29, 2017 at 03:46:38PM +0900, Byungchul Park wrote: > How does a maintainer choose a very work-around method and avoid > problems rather than fix a root cause? I am very disappointed. Time.. we need this sorted before we push the whole lot to Linus in the next window. Fixing the recursive-read thing is far more work (although Boqun did post some patches for that, which I still have to look at).