Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755352AbcDKVng (ORCPT ); Mon, 11 Apr 2016 17:43:36 -0400 Received: from mail-bn1on0119.outbound.protection.outlook.com ([157.56.110.119]:35611 "EHLO na01-bn1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752104AbcDKVnf (ORCPT ); Mon, 11 Apr 2016 17:43:35 -0400 From: Quinn Tran To: Joseph Salisbury CC: Dept-Eng QLA2xxx Upstream , "jejb@linux.vnet.ibm.com" , "Martin K. Petersen" , linux-scsi , linux-kernel , "hch@lst.de" , "bart.vanassche@sandisk.com" , Himanshu Madhani , "nab@linux-iscsi.org" Subject: Re: [4.5-rc4 Regression] qla2xxx: Add irq affinity notification Thread-Topic: [4.5-rc4 Regression] qla2xxx: Add irq affinity notification Thread-Index: AQHRlBdN/a0v9cGyvEmzF3qmz5nq8Z+El0UAgACEG4D//7lGgA== Date: Mon, 11 Apr 2016 21:28:30 +0000 Message-ID: <44AC3861-DFD2-4420-9ACA-E6AE7A3BDE99@qlogic.com> References: <570BDE44.5020301@canonical.com> <32AB2218-5D39-4968-A07F-E527B0557F04@qlogic.com> <570BEFE1.6040703@canonical.com> In-Reply-To: <570BEFE1.6040703@canonical.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/0.0.0.160212 authentication-results: canonical.com; dkim=none (message not signed) header.d=none;canonical.com; dmarc=none action=none header.from=qlogic.com; x-ms-exchange-messagesentrepresentingtype: 1 x-originating-ip: [198.186.0.2] x-ms-office365-filtering-correlation-id: b72eac00-c90d-4b36-fda2-08d362503a58 x-microsoft-exchange-diagnostics: 1;DM2PR11MB0105;5:wLkcz9Z9sUPMqbuoGuOlj7LY4yp99DSezN+lItAyAg3yyqM/xAcQUtihJ8HwYd5rWIXIkzLAWP9wC0F4Dj8hgfTwJpWRA9oI8ilqXSvrnAP7R/H+YXIfeSDIIl7zM/CdnlsvzniJIB6+gnSWXGb04A==;24:3slSvTF8D5aTgucgxMQy0upaUVEgHTDmqD5ogUC11iIDeocbK+w2xSS49FhzpNk7vilBW60gv9ovaQh+2eCzP5blI935UyJrcmGMKBMVHNE=;20:JVZ7mp2GJ0Yz40iY/iaLcbc5DJCcivRwgGuGLRGzbhPxxzDHk1pPJLWFV3upd8x6BZz6ckidjTIlfjWmZK3omt/j0Gf6j/bwYzsKy4sgNpcQWK+myIFB4x4yTyYLtzy7XtyFYeTV3JzhT9TA+DCgkxFl/INPSrTRQl2Avz+T+Hc= x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0105; x-ld-processed: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba,ExtAddr x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(601004)(2401047)(5005006)(8121501046)(10201501046)(3002001);SRVR:DM2PR11MB0105;BCL:0;PCL:0;RULEID:;SRVR:DM2PR11MB0105; x-forefront-prvs: 09090B6B69 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(13464003)(377454003)(24454002)(5890100001)(66066001)(19580395003)(19580405001)(189998001)(15650500001)(7110500001)(1720100001)(10400500002)(1220700001)(164054004)(86362001)(50986999)(1096002)(2420400007)(5004730100002)(5002640100001)(87936001)(15975445007)(33656002)(15395725005)(82746002)(2900100001)(2950100001)(4001350100001)(3280700002)(10710500007)(36756003)(4326007)(122556002)(77096005)(3846002)(102836003)(6116002)(99286002)(83716003)(15198665003)(81166005)(106116001)(3660700001)(586003)(83506001)(76176999)(54356999)(2906002)(110136002)(5008740100001)(92566002)(7059030)(104396002)(10090945008)(16193025007);DIR:OUT;SFP:1102;SCL:1;SRVR:DM2PR11MB0105;H:SN1PR11MB0655.namprd11.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:23 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" Content-ID: <1A22D2974E54E14C8CBDC4B2355A5EFD@namprd11.prod.outlook.com> MIME-Version: 1.0 X-OriginatorOrg: qlogic.com X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2016 21:28:30.2185 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0d68a1f9-1490-4d0e-8767-a87dab3ef2ba X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR11MB0105 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id u3BLhfbF005737 Content-Length: 4545 Lines: 123 Joe, I see the crash point. We’re accessing Null pointer. The adapter in use is an older 4G adapter, where it does not have MSIX support. We’re tripping over the same shared code segment. The following is the propose fix. Let me know if it works. I’ll will follow up with a patch for upstream submission. Thanks. diff --git a/drivers/scsi/qla2xxx/qla_isr.c b/drivers/scsi/qla2xxx/qla_isr.c index 4af9547..79469de 100644 --- a/drivers/scsi/qla2xxx/qla_isr.c +++ b/drivers/scsi/qla2xxx/qla_isr.c @@ -2552,7 +2552,7 @@ void qla24xx_process_response_queue(struct scsi_qla_host *vha, if (!vha->flags.online) return; - if (rsp->msix->cpuid != smp_processor_id()) { + if (rsp->msix && (rsp->msix->cpuid != smp_processor_id())) { /* if kernel does not notify qla of IRQ's CPU change, * then set it here. */ Regards, Quinn Tran -----Original Message----- From: Joseph Salisbury Date: Monday, April 11, 2016 at 11:41 AM To: Quinn Tran Cc: Dept-Eng QLA2xxx Upstream , "jejb@linux.vnet.ibm.com" , "Martin K. Petersen" , linux-scsi , linux-kernel , "hch@lst.de" , "bart.vanassche@sandisk.com" , Himanshu Madhani , Nicholas Bellinger Subject: Re: [4.5-rc4 Regression] qla2xxx: Add irq affinity notification >On 04/11/2016 01:48 PM, Quinn Tran wrote: >> Joe, >> >> How do I get access to this specific Ubuntu kernel where the bug is found? Is there stack trace/bug report that you could share? Any data would be helpful. Thanks. >The git tree for the specific Ubuntu kernel that exhibits this bug can >be found here: >git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/xenial > >The bug can be found here, and has screen shots of the panic as well as >dmesg under the "Attachments" header: >http://pad.lv/1554003 > >Just let me know if additional debug information is needed. > > >> >> In the mean time, I will download 4.5 rc4 to re-verify. >> >> Regards, >> Quinn Tran >> >> >> >> >> >> >> -----Original Message----- >> From: Joseph Salisbury >> Date: Monday, April 11, 2016 at 10:26 AM >> To: Quinn Tran >> Cc: Dept-Eng QLA2xxx Upstream , "jejb@linux.vnet.ibm.com" , "Martin K. Petersen" , linux-scsi , linux-kernel , "hch@lst.de" , "bart.vanassche@sandisk.com" , Himanshu Madhani , Nicholas Bellinger >> Subject: [4.5-rc4 Regression] qla2xxx: Add irq affinity notification >> >>> Hello Quinn, >>> >>> A kernel bug report was opened against Ubuntu [0]. After a kernel >>> bisect, it was found that reverting the following commit resolved this bug: >>> >>> commit cdb898c52d1dfad4b4800b83a58b3fe5d352edde >>> Author: Quinn Tran >>> Date: Thu Dec 17 14:57:05 2015 -0500 >>> >>> qla2xxx: Add irq affinity notification >>> >>> >>> However, the prior commit also required the following three commits to >>> also be reverted: >>> >>> commit 5327c7dbd1a7fd980608f44789076a636e5ee5fc >>> Author: Quinn Tran >>> Date: Wed Feb 10 18:59:14 2016 -0500 >>> >>> qla2xxx: use TARGET_SCF_USE_CPUID flag to indiate CPU Affinity >>> >>> commit 9095adaab8c1d82707e4e9961b6ad79b62f3361b >>> Author: Quinn Tran >>> Date: Wed Feb 10 18:59:13 2016 -0500 >>> >>> target/transport: add flag to indicate CPU Affinity is observed >>> >>> commit fb3269baf4ecc2ce6d17d4eb537080035bdf6d5b >>> Author: Quinn Tran >>> Date: Thu Dec 17 14:57:06 2015 -0500 >>> >>> qla2xxx: Add selective command queuing >>> >>> >>> >>> The regression was introduced as of v4.5-rc4. >>> >>> I was hoping to get your feedback, since you are the patch author. The >>> dependant reverts all look like they are improving cpu affinity, which >>> would likely impact performance. Do you thing there is a way forward >>> instead of the reverts, or would it be best to submit a revert request? >>> >>> >>> Thanks, >>> >>> Joe >>> >>> >>> [0] http://pad.lv/1554003 >>> >>> >