RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "hch@xxxxxx" <hch@xxxxxx>
Subject: RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
From: Dexuan Cui <decui@xxxxxxxxxxxxx>
Date: Tue, 14 Feb 2017 14:46:41 +0000
Accept-language: en-US
Cc: Jens Axboe <axboe@xxxxxxxxx>, Bart Van Assche <Bart.VanAssche@xxxxxxxxxxx>, "hare@xxxxxxxx" <hare@xxxxxxxx>, "hare@xxxxxxx" <hare@xxxxxxx>, "Martin K. Petersen" <martin.petersen@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "linux-block@xxxxxxxxxxxxxxx" <linux-block@xxxxxxxxxxxxxxx>, "jth@xxxxxxxxxx" <jth@xxxxxxxxxx>, Nick Meier <Nick.Meier@xxxxxxxxxxxxx>, "Alex Ng (LIS)" <alexng@xxxxxxxxxxxxx>, Long Li <longli@xxxxxxxxxxxxx>, "Adrian Suhov (Cloudbase Solutions SRL)" <v-adsuho@xxxxxxxxxxxxx>, "Chris Valean (Cloudbase Solutions SRL)" <v-chvale@xxxxxxxxxxxxx>
In-reply-to: <20170214142837.GB20706@lst.de>

> From: hch@xxxxxx [mailto:hch@xxxxxx]
> Sent: Tuesday, February 14, 2017 22:29
> To: Dexuan Cui <decui@xxxxxxxxxxxxx>
> Subject: Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock
> when scheduling workqueue elements")
> 
> Ok, thanks for testing.  Can you try the patch below?  It fixes a
> clear problem which was partially papered over before the commit
> you bisected to, although it can't explain why blk-mq still works.

Still bad luck. :-(

BTW, I'm using the first "bad" commit (scsi: allocate scsi_cmnd structures as
part of struct request) + the 2 patches you provided today.

I suppose I don't need to test the 2 patches on the latest linux-next repo.

Thanks,
-- Dexuan

Follow-Ups:
- Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: hch@xxxxxx

References:
- RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
  - From: Dexuan Cui
- Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
  - From: Jens Axboe
- RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
  - From: Dexuan Cui
- Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: Jens Axboe
- Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: hch@xxxxxx
- RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: Dexuan Cui
- Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: hch@xxxxxx
- Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: hch@xxxxxx
- RE: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: Dexuan Cui
- Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
  - From: hch@xxxxxx

Prev by Date: Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Next by Date: Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Previous by thread: Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Next by thread: Re: Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements")
Index(es):
- Date
- Thread

[Index of Archives] [Linux RAID] [Linux SCSI] [Linux ATA RAID] [IDE] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Device Mapper]