From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EC1F8C432C0 for ; Tue, 19 Nov 2019 13:28:57 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C3B4C222C7 for ; Tue, 19 Nov 2019 13:28:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728016AbfKSN24 (ORCPT ); Tue, 19 Nov 2019 08:28:56 -0500 Received: from mx2.suse.de ([195.135.220.15]:44504 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725904AbfKSN24 (ORCPT ); Tue, 19 Nov 2019 08:28:56 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 9E8ECB2B8; Tue, 19 Nov 2019 13:28:54 +0000 (UTC) Date: Tue, 19 Nov 2019 14:28:54 +0100 From: Daniel Wagner To: "Martin K. Petersen" Cc: James Smart , Dick Kennedy , linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] scsi: lpfc: Move work items to a stack list Message-ID: <20191119132854.mwkxx4fixjaoxv4w@beryllium.lan> References: <20191105080855.16881-1-dwagner@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20180716 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Nov 12, 2019 at 10:15:00PM -0500, Martin K. Petersen wrote: > > While trying to understand what's going on in the Oops below I figured > > that it could be the result of the invalid pointer access. The patch > > still needs testing by our customer but indepent of this I think the > > patch fixes a real bug. I was able to reproduce the same stack trace with this patch applied... That is obviously bad. The good news, I have access to this machine, so maybe I able to figure out what's the root cause of this crash.