RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements

From	Dexuan Cui <decui@microsoft.com>
Newsgroups	linux.kernel
Subject	RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
Date	2017-02-07 07:30 +0100
Message-ID	<t87rP-7wp-3@gated-at.bofh.it> (permalink)
References	(2 earlier) <t5JjY-2Qa-5@gated-at.bofh.it> <t6La2-1wS-7@gated-at.bofh.it> <t83HA-4X1-7@gated-at.bofh.it> <t84aB-58r-5@gated-at.bofh.it> <t84WZ-5LX-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

> From: linux-block-owner@vger.kernel.org [mailto:linux-block-
> owner@vger.kernel.org] On Behalf Of Dexuan Cui
> with the linux-next kernel.
> 
> I can boot the guest with linux-next's next-20170130 without any issue,
> but since next-20170131 I haven't succeeded in booting the guest.
> 
> With next-20170203 (mentioned in my mail last Friday), I got the same
> calltrace as Hannes.
> 
> With today's linux-next (next-20170206), actually the calltrace changed to
> the below.
> [  122.023036]  ? remove_wait_queue+0x70/0x70
> [  122.051383]  async_synchronize_full+0x17/0x20
> [  122.076925]  do_init_module+0xc1/0x1f9
> [  122.097530]  load_module+0x24bc/0x2980
 
I don't know why it hangs here, but this is the same calltrace in my
last-Friday mail, which contains 2 calltraces. It looks the other calltrace has
been resolved by some changes between next-20170203 and today.

Here the kernel is trying to load the Hyper-V storage driver (hv_storvsc), and
the driver's __init and .probe have finished successfully and then the kernel
hangs here.

I believe something is broken recently, because I don't have any issue before
Jan 31. 

Thanks,
-- Dexuan

Thread

Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Hannes Reinecke <hare@suse.com> - 2017-01-31 17:20 +0100
  RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-03 13:30 +0100
    RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-07 03:30 +0100
      Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Bart Van Assche <Bart.VanAssche@sandisk.com> - 2017-02-07 04:00 +0100
        RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-07 07:30 +0100
          Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Jens Axboe <axboe@kernel.dk> - 2017-02-07 17:20 +0100
            RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue  elements Dexuan Cui <decui@microsoft.com> - 2017-02-08 12:00 +0100
              Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when  scheduling workqueue elements") Jens Axboe <axboe@kernel.dk> - 2017-02-08 18:50 +0100
                Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event         lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-08 19:20 +0100
                RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock  when scheduling workqueue elements") Dexuan Cui <decui@microsoft.com> - 2017-02-09 08:40 +0100
                Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event         lock when scheduling workqueue elements") "hch@lst.de" <hch@lst.de> - 2017-02-09 14:40 +0100

csiph-web