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;
Date:   Fri, 12 Apr 2019 10:10:41 -0700 (PDT)
Message-Id: <20190412.101041.259784853562829642.davem@davemloft.net>
To:     dongli.zhang@oracle.com
Cc:     xen-devel@lists.xenproject.org, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, wei.liu2@citrix.com,
        paul.durrant@citrix.com, joe.jin@oracle.com, junxiao.bi@oracle.com,
        jie.l.li@oracle.com
Subject: Re: [PATCH 1/1] xen-netback: add reference from xenvif to
 backend_info to facilitate coredump analysis
From:   David Miller <davem@davemloft.net>
In-Reply-To: <1555052004-31855-1-git-send-email-dongli.zhang@oracle.com>
References: <1555052004-31855-1-git-send-email-dongli.zhang@oracle.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

From: Dongli Zhang <dongli.zhang@oracle.com>
Date: Fri, 12 Apr 2019 14:53:24 +0800

> During coredump analysis, it is not easy to obtain the address of
> backend_info in xen-netback.
> 
> So far there are two ways to obtain backend_info:
> 
> 1. Do what xenbus_device_find() does for vmcore to find the xenbus_device
> and then derive it from dev_get_drvdata().
> 
> 2. Extract backend_info from callstack of xenwatch (e.g., netback_remove()
> or frontend_changed()).
> 
> This patch adds a reference from xenvif to backend_info so that it would be
> much more easier to obtain backend_info during coredump analysis.
> 
> Signed-off-by: Dongli Zhang <dongli.zhang@oracle.com>

Applied to net-next.