linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Manjunath Patil <manjunath.b.patil@oracle.com>
To: Juergen Gross <jgross@suse.com>,
	boris.ostrovsky@oracle.com, konrad.wilk@oracle.com,
	roger.pau@citrix.com
Cc: axboe@kernel.dk, xen-devel@lists.xenproject.org,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [Xen-devel] [PATCH v2] xen-blkfront: fix kernel panic with blkfront_remove()
Date: Fri, 9 Nov 2018 11:08:56 -0800	[thread overview]
Message-ID: <28e89b14-add7-348d-f054-975af74bdf52@oracle.com> (raw)
In-Reply-To: <9414b993-15f6-941a-fc2b-e96147e4fb26@suse.com>

oops! sorry for not noticing this.

-Manjunath

On 11/8/2018 10:16 PM, Juergen Gross wrote:
> On 09/11/2018 02:10, Manjunath Patil wrote:
>> When we try to detach the device, blkfront_remove() tries to access
>> blkfront_info leading to kernel panic.
>>
>> Typical call stack involving panic -
>>   #10 page_fault at ffffffff816f25df
>>       [exception RIP: blkif_free+46]
>>   #11 blkfront_remove at ffffffffa004de47 [xen_blkfront]
>>   #12 xenbus_dev_remove at ffffffff813faa4c
>>   #13 __device_release_driver at ffffffff814769aa
>>   #14 device_release_driver at ffffffff81476a63
>>   #15 bus_remove_device at ffffffff814762eb
>>   #16 device_del at ffffffff81472684
>>   #17 device_unregister at ffffffff814727e2
>>   #18 xenbus_dev_changed at ffffffff813fa89f
>>   #19 frontend_changed at ffffffff813fca19
>>   #20 xenwatch_thread at ffffffff813f88f9
>>   #21 kthread at ffffffff810a486b
>>   #22 ret_from_fork at ffffffff816ed2a8
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Manjunath Patil <manjunath.b.patil@oracle.com>
> Commit f92898e7f32e3 already added that.
>
>
> Juergen


      reply	other threads:[~2018-11-09 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-09  1:10 Manjunath Patil
2018-11-09  6:16 ` Juergen Gross
2018-11-09 19:08   ` Manjunath Patil [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28e89b14-add7-348d-f054-975af74bdf52@oracle.com \
    --to=manjunath.b.patil@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=boris.ostrovsky@oracle.com \
    --cc=jgross@suse.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roger.pau@citrix.com \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --subject='Re: [Xen-devel] [PATCH v2] xen-blkfront: fix kernel panic with blkfront_remove()' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).