From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "decui@microsoft.com" <decui@microsoft.com>,
"hare@suse.com" <hare@suse.com>, "hare@suse.de" <hare@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"jth@kernel.org" <jth@kernel.org>
Subject: Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
Date: Tue, 7 Feb 2017 02:56:50 +0000 [thread overview]
Message-ID: <1486436195.2791.1.camel@sandisk.com> (raw)
In-Reply-To: <MWHPR03MB26699D4657FB67A535972208BF430@MWHPR03MB2669.namprd03.prod.outlook.com>
T24gVHVlLCAyMDE3LTAyLTA3IGF0IDAyOjIzICswMDAwLCBEZXh1YW4gQ3VpIHdyb3RlOg0KPiBB
bnkgbmV3cyBvbiB0aGlzIHRocmVhZD8NCj4gDQo+IFRoZSBpc3N1ZSBpcyBzdGlsbCBibG9ja2lu
ZyBMaW51eCBmcm9tIGJvb3RpbmcgdXAgbm9ybWFsbHkgaW4gbXkgdGVzdC4gOi0oDQo+IA0KPiBI
YXZlIHdlIGlkZW50aWZpZWQgdGhlIGZhdWx0eSBwYXRjaD8NCj4gSWYgc28sIGF0IGxlYXN0IEkg
Y2FuIHRyeSB0byByZXZlcnQgaXQgdG8gYm9vdCB1cC4NCg0KSXQncyBpbnRlcmVzdGluZyB0aGF0
IHlvdSBoYXZlIGEgcmVwcm9kdWNpYmxlIHRlc3RjYXNlLiBJZiB5b3UgY2FuIHRlbGwgbWUgaG93
IHRvDQpyZXByb2R1Y2UgdGhpcyBJJ2xsIGhhdmUgYSBsb29rIGF0IGl0IHRvZ2V0aGVyIHdpdGgg
SGFubmVzLg0KDQpCYXJ0LgpXZXN0ZXJuIERpZ2l0YWwgQ29ycG9yYXRpb24gKGFuZCBpdHMgc3Vi
c2lkaWFyaWVzKSBFLW1haWwgQ29uZmlkZW50aWFsaXR5IE5vdGljZSAmIERpc2NsYWltZXI6CgpU
aGlzIGUtbWFpbCBhbmQgYW55IGZpbGVzIHRyYW5zbWl0dGVkIHdpdGggaXQgbWF5IGNvbnRhaW4g
Y29uZmlkZW50aWFsIG9yIGxlZ2FsbHkgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiBvZiBXREMgYW5k
L29yIGl0cyBhZmZpbGlhdGVzLCBhbmQgYXJlIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBv
ZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hpY2ggdGhleSBhcmUgYWRkcmVzc2VkLiBJ
ZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBhbnkgZGlzY2xvc3VyZSwgY29w
eWluZywgZGlzdHJpYnV0aW9uIG9yIGFueSBhY3Rpb24gdGFrZW4gb3Igb21pdHRlZCB0byBiZSB0
YWtlbiBpbiByZWxpYW5jZSBvbiBpdCwgaXMgcHJvaGliaXRlZC4gSWYgeW91IGhhdmUgcmVjZWl2
ZWQgdGhpcyBlLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlh
dGVseSBhbmQgZGVsZXRlIHRoZSBlLW1haWwgaW4gaXRzIGVudGlyZXR5IGZyb20geW91ciBzeXN0
ZW0uCg==
WARNING: multiple messages have this Message-ID (diff)
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "decui@microsoft.com" <decui@microsoft.com>,
"hare@suse.com" <hare@suse.com>, "hare@suse.de" <hare@suse.de>,
"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "hch@lst.de" <hch@lst.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"jth@kernel.org" <jth@kernel.org>
Subject: Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements
Date: Tue, 7 Feb 2017 02:56:50 +0000 [thread overview]
Message-ID: <1486436195.2791.1.camel@sandisk.com> (raw)
In-Reply-To: <MWHPR03MB26699D4657FB67A535972208BF430@MWHPR03MB2669.namprd03.prod.outlook.com>
On Tue, 2017-02-07 at 02:23 +0000, Dexuan Cui wrote:
> Any news on this thread?
>
> The issue is still blocking Linux from booting up normally in my test. :-(
>
> Have we identified the faulty patch?
> If so, at least I can try to revert it to boot up.
It's interesting that you have a reproducible testcase. If you can tell me how to
reproduce this I'll have a look at it together with Hannes.
Bart.
next prev parent reply other threads:[~2017-02-07 2:56 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 9:48 [PATCH] genhd: Do not hold event lock when scheduling workqueue elements Hannes Reinecke
2017-01-31 0:31 ` Bart Van Assche
2017-01-31 0:31 ` Bart Van Assche
2017-01-31 16:15 ` Hannes Reinecke
2017-01-31 16:15 ` Hannes Reinecke
2017-02-03 12:22 ` Dexuan Cui
2017-02-03 12:22 ` Dexuan Cui
2017-02-07 2:23 ` Dexuan Cui
2017-02-07 2:23 ` Dexuan Cui
2017-02-07 2:56 ` Bart Van Assche [this message]
2017-02-07 2:56 ` Bart Van Assche
2017-02-07 3:48 ` Dexuan Cui
2017-02-07 6:29 ` Dexuan Cui
2017-02-07 6:29 ` Dexuan Cui
2017-02-07 16:09 ` Jens Axboe
2017-02-08 10:48 ` Dexuan Cui
2017-02-08 10:48 ` Dexuan Cui
2017-02-08 17:43 ` Boot regression (was "Re: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements") Jens Axboe
2017-02-08 18:03 ` hch
2017-02-09 7:35 ` Dexuan Cui
2017-02-09 7:35 ` Dexuan Cui
2017-02-09 13:08 ` hch
2017-02-10 14:49 ` Dexuan Cui
2017-02-10 14:49 ` Dexuan Cui
2017-02-14 13:47 ` hch
2017-02-14 14:17 ` Dexuan Cui
2017-02-14 14:17 ` Dexuan Cui
2017-02-14 14:28 ` hch
2017-02-14 14:46 ` Dexuan Cui
2017-02-14 14:46 ` Dexuan Cui
2017-02-14 14:51 ` hch
2017-02-14 15:54 ` Dexuan Cui
2017-02-14 15:54 ` Dexuan Cui
2017-02-14 16:34 ` hch
2017-02-15 13:51 ` Dexuan Cui
2017-02-15 13:51 ` Dexuan Cui
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=1486436195.2791.1.camel@sandisk.com \
--to=bart.vanassche@sandisk.com \
--cc=axboe@kernel.dk \
--cc=decui@microsoft.com \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=jth@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.