Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp1448709yba; Sat, 6 Apr 2019 12:36:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqw5vi8aw8o7lthjLhTkLMSLZdLtVj6IY0VgdvC8M8s4VT4zeR97YF1/0pRrIijdozk5HvVM X-Received: by 2002:a63:da4e:: with SMTP id l14mr18499461pgj.96.1554579395989; Sat, 06 Apr 2019 12:36:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554579395; cv=none; d=google.com; s=arc-20160816; b=Y5QFrPpOF2bDEeFtZz9vEVgwmTM3W+aaG40y7wL+9zAd+N6NyQgXhI0hp2zHJrpSDA cB9xu6tOZND6qH0ypvOkbIJtDQjxGGSVqD1AC2C8C8ufhNJj146rohO6Kj8kUjCUpmjZ F47hGHkAMpmZ33upad1zaq/ImqIDsIfSVt4SeVj0DVUrUuzHcvnVmCdGtt67pOFdi2r1 3dHaBjPDzzbGfmoiAffAeUGnCR7fWJfdytFDcvl5BQ/939szNiiBwaqpq2ddYaqQxRH6 iAnKKdGv+VPDeNJT5LorKaFOxMCUABNJ2kGVcWxXASuPTCI2C3I3Vw+WhwnJxloA731M qtiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=tE61QvLDmm1XPqbXzI5lzXOoTay0BqBzsTx2Nzsk/2U=; b=BE+uV6CmgF22XL+Yi6mTrOCXIz72N2Qs57WMJv/+hHbeQgF/svR45PRJz5+lF03J95 e8G12JK5fLnIKI943HQrgBDli67Rf51JN7QOgeyU97C8u0QZWvYve7og+Ye6wO0vwtW1 HJR4rGSzjM45X3zdw9jse9fVbOA4b4W1p9o/XJO4Kat0/zTkTo+AM9dMRGVaqdqdEqo1 F8v6W51SgkTBUe4Vx3eBee26/3RS/fDnSy/iRZoZwI3rSMDxLib84jZZq7YIlWJ7PJL8 4df5NMFAAFR65ZLR1O55/gwJA34cuR+RgqWH7F1D4scj2jkgnXwKdjDEoQ3q2dccOJMe yDqg== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=iLL0zxzi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v43si5986288pgn.32.2019.04.06.12.36.20; Sat, 06 Apr 2019 12:36:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@gmail.com header.s=20161025 header.b=iLL0zxzi; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726661AbfDFTe0 (ORCPT + 99 others); Sat, 6 Apr 2019 15:34:26 -0400 Received: from mail-pf1-f196.google.com ([209.85.210.196]:45696 "EHLO mail-pf1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726427AbfDFTe0 (ORCPT ); Sat, 6 Apr 2019 15:34:26 -0400 Received: by mail-pf1-f196.google.com with SMTP id e24so5156418pfi.12; Sat, 06 Apr 2019 12:34:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=tE61QvLDmm1XPqbXzI5lzXOoTay0BqBzsTx2Nzsk/2U=; b=iLL0zxziFTpuGbZMraU129T6IR158tcENueZDS/bLSdZjfA/GU7qtbMTiFSRBZ28IC A+mEXoq3H0KO2bFASmpn3y5LQ+aowdiP3y4VsRsfDC0ashiSFfJ8ExsBdtqrs5DDiMBn R+h1MB/f9QkyOLe833xmrXOXQ2feqrJv4j6FDVPubnl5vEka9Uya1ZLDP1LhDyIk8usj UVN6Mjh5oQ1rDMdV+q0G73ag4lP5EI3QbjpNKGbZFCTjPdsa4aUsKqi8YxUIzfidbtoS 0h5wx+AKp2u/Kewc/ib42CuJsv/XD+ZbC2EyvexXNOs/sWF50cWLqek9QAJ7WW5jZEJy bVgw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=tE61QvLDmm1XPqbXzI5lzXOoTay0BqBzsTx2Nzsk/2U=; b=TZKrvBDHtXqXYXCISxS7B2sJFcEaHOGrwBXaodsH1cnMr4B6bo/bdqIzsWTwOdUztS i4L/AUyXfo9KtG6HO0R60NApHa5FUNHqL7ZUfHMq+pNEiwzSCrfruxbFWYIvn3Ybjuno pRcAMJUkteqFxlig3OkNZXbbeHL4TL1Yra+/tL9Q97P/avIbas9IfezabbFzXzSsy4fR 4LS1Noe4hxrzLNn1ZUpvjl1vw0x1NBtBiy2Xlzn3BWvyV7H0el68rTkje4otQC3cEBX3 xvaHZlqXQILEnU+tL4NKzgvwDFCp4NNXpptIbqEQKLjjG5scKcYsimJ5Te6KVky+SwQk 8o1g== X-Gm-Message-State: APjAAAVj4f1iZ21siUat/wmurmHx57SX58wFsuxN+mxQZMPAcNh1gajT 2HWpbMP6ZeyhEn8LLj7VJREKDStO X-Received: by 2002:a65:4302:: with SMTP id j2mr18411442pgq.291.1554579265237; Sat, 06 Apr 2019 12:34:25 -0700 (PDT) Received: from server.roeck-us.net ([2600:1700:e321:62f0:329c:23ff:fee3:9d7c]) by smtp.gmail.com with ESMTPSA id t5sm9792434pfl.106.2019.04.06.12.34.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Apr 2019 12:34:24 -0700 (PDT) Subject: Re: [PATCH] xsysace: Fix error handling in ace_setup To: Jens Axboe , Michal Simek Cc: linux-arm-kernel@lists.infradead.org, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org References: <1550594996-11453-1-git-send-email-linux@roeck-us.net> <20190405224458.GA19556@roeck-us.net> <0c428aac-f488-525a-49d1-506ce92be418@kernel.dk> From: Guenter Roeck Message-ID: Date: Sat, 6 Apr 2019 12:34:23 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <0c428aac-f488-525a-49d1-506ce92be418@kernel.dk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 4/5/19 4:06 PM, Jens Axboe wrote: > On 4/5/19 4:44 PM, Guenter Roeck wrote: >> Hi, >> >> On Tue, Feb 19, 2019 at 08:49:56AM -0800, Guenter Roeck wrote: >>> If xace hardware reports a bad version number, the error handling code >>> in ace_setup() calls put_disk(), followed by queue cleanup. However, since >>> the disk data structure has the queue pointer set, put_disk() also >>> cleans and releases the queue. This results in blk_cleanup_queue() >>> accessing an already released data structure, which in turn may result >>> in a crash such as the following. >>> >> >> This crash is now quite persistent in mainline. The fix didn't make it. >> Should I stop testing virtex-ml507 with qemu ? > > I've applied the fix now. > > But given Michal's comments, should we kill the driver for 5.2? > If the driver is no longer used or maintained, removing it would indeed make sense. Guenter