From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Dexuan Cui To: Bart Van Assche , "hare@suse.com" , "hare@suse.de" , "axboe@kernel.dk" CC: "hch@lst.de" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , "jth@kernel.org" Subject: RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements Date: Tue, 7 Feb 2017 06:29:33 +0000 Message-ID: References: <1484732896-22941-1-git-send-email-hare@suse.de> <1485822639.2669.16.camel@sandisk.com> <532c55c4-15da-d2f9-401c-36bc4343756b@suse.com> <1486436195.2791.1.camel@sandisk.com> In-Reply-To: Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 List-ID: PiBGcm9tOiBsaW51eC1ibG9jay1vd25lckB2Z2VyLmtlcm5lbC5vcmcgW21haWx0bzpsaW51eC1i bG9jay0NCj4gb3duZXJAdmdlci5rZXJuZWwub3JnXSBPbiBCZWhhbGYgT2YgRGV4dWFuIEN1aQ0K PiB3aXRoIHRoZSBsaW51eC1uZXh0IGtlcm5lbC4NCj4gDQo+IEkgY2FuIGJvb3QgdGhlIGd1ZXN0 IHdpdGggbGludXgtbmV4dCdzIG5leHQtMjAxNzAxMzAgd2l0aG91dCBhbnkgaXNzdWUsDQo+IGJ1 dCBzaW5jZSBuZXh0LTIwMTcwMTMxIEkgaGF2ZW4ndCBzdWNjZWVkZWQgaW4gYm9vdGluZyB0aGUg Z3Vlc3QuDQo+IA0KPiBXaXRoIG5leHQtMjAxNzAyMDMgKG1lbnRpb25lZCBpbiBteSBtYWlsIGxh c3QgRnJpZGF5KSwgSSBnb3QgdGhlIHNhbWUNCj4gY2FsbHRyYWNlIGFzIEhhbm5lcy4NCj4gDQo+ IFdpdGggdG9kYXkncyBsaW51eC1uZXh0IChuZXh0LTIwMTcwMjA2KSwgYWN0dWFsbHkgdGhlIGNh bGx0cmFjZSBjaGFuZ2VkIHRvDQo+IHRoZSBiZWxvdy4NCj4gWyAgMTIyLjAyMzAzNl0gID8gcmVt b3ZlX3dhaXRfcXVldWUrMHg3MC8weDcwDQo+IFsgIDEyMi4wNTEzODNdICBhc3luY19zeW5jaHJv bml6ZV9mdWxsKzB4MTcvMHgyMA0KPiBbICAxMjIuMDc2OTI1XSAgZG9faW5pdF9tb2R1bGUrMHhj MS8weDFmOQ0KPiBbICAxMjIuMDk3NTMwXSAgbG9hZF9tb2R1bGUrMHgyNGJjLzB4Mjk4MA0KIA0K SSBkb24ndCBrbm93IHdoeSBpdCBoYW5ncyBoZXJlLCBidXQgdGhpcyBpcyB0aGUgc2FtZSBjYWxs dHJhY2UgaW4gbXkNCmxhc3QtRnJpZGF5IG1haWwsIHdoaWNoIGNvbnRhaW5zIDIgY2FsbHRyYWNl cy4gSXQgbG9va3MgdGhlIG90aGVyIGNhbGx0cmFjZSBoYXMNCmJlZW4gcmVzb2x2ZWQgYnkgc29t ZSBjaGFuZ2VzIGJldHdlZW4gbmV4dC0yMDE3MDIwMyBhbmQgdG9kYXkuDQoNCkhlcmUgdGhlIGtl cm5lbCBpcyB0cnlpbmcgdG8gbG9hZCB0aGUgSHlwZXItViBzdG9yYWdlIGRyaXZlciAoaHZfc3Rv cnZzYyksIGFuZA0KdGhlIGRyaXZlcidzIF9faW5pdCBhbmQgLnByb2JlIGhhdmUgZmluaXNoZWQg c3VjY2Vzc2Z1bGx5IGFuZCB0aGVuIHRoZSBrZXJuZWwNCmhhbmdzIGhlcmUuDQoNCkkgYmVsaWV2 ZSBzb21ldGhpbmcgaXMgYnJva2VuIHJlY2VudGx5LCBiZWNhdXNlIEkgZG9uJ3QgaGF2ZSBhbnkg aXNzdWUgYmVmb3JlDQpKYW4gMzEuIA0KDQpUaGFua3MsDQotLSBEZXh1YW4NCg== From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752889AbdBGG3g (ORCPT ); Tue, 7 Feb 2017 01:29:36 -0500 Received: from mail-co1nam03on0123.outbound.protection.outlook.com ([104.47.40.123]:3072 "EHLO NAM03-CO1-obe.outbound.protection.outlook.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752502AbdBGG3f (ORCPT ); Tue, 7 Feb 2017 01:29:35 -0500 From: Dexuan Cui To: Bart Van Assche , "hare@suse.com" , "hare@suse.de" , "axboe@kernel.dk" CC: "hch@lst.de" , "linux-kernel@vger.kernel.org" , "linux-block@vger.kernel.org" , "jth@kernel.org" Subject: RE: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements Thread-Topic: [PATCH] genhd: Do not hold event lock when scheduling workqueue elements Thread-Index: AQHSe9062dHV0XX4/EGXRjibwyBPjaFXNu6QgAWiPdCAAArCAIAACQ5ggAAwHGA= Date: Tue, 7 Feb 2017 06:29:33 +0000 Message-ID: References: <1484732896-22941-1-git-send-email-hare@suse.de> <1485822639.2669.16.camel@sandisk.com> <532c55c4-15da-d2f9-401c-36bc4343756b@suse.com> <1486436195.2791.1.camel@sandisk.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=decui@microsoft.com; x-originating-ip: [2404:f801:9000:18::54b] x-ms-office365-filtering-correlation-id: e6dabe91-3778-455f-24b3-08d44f22ae0f x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(48565401081);SRVR:MWHPR03MB2672; x-microsoft-exchange-diagnostics: 1;MWHPR03MB2672;7:2dLxBUmD5XZ5fBt3f3PGoAOYN9nuT5dy6rYo0KsPTGzT0t3mGiDLMiPHJR7nwyDy+S3fxZQKn9nGB6wTHeUX3oXaqTesfxu4gqPGYr9FWlRSZs4xi+y24tcIvSbIFcYdZl1Uc6EYjmKwyRxmrQkWIrBVsLGC41Zfckj3Ak6b4pIaLIhW5YDM54/qWRkO2nooWE/TR3DqfHWtAJPmzy8mxTGuEP1QAnG/J3GIui5bLh8ThOgGsYzdrFSrXbmx5IfcXxTY0SATY54jSLpQPBMnGuC1AK8vFkCumaRVgzIPW6qln+pohnNLh8gBYUT3S7vFcum3wfGO2BUh5IGDLV+la9VHYtHrjyBzOuyPQCS7sXwsMAvOTVzV83oQLrWyFzXixo13z4uYi3CF0hXNPU3zrjVHXPFzmQNQ6rsqe0CuyuwDIBdnxWxHIvfEvbs9KCfCYKBqTER1SWHZOlDVpfkeal0QR0HE7ENsNN6OEBf+LFf939Z6HTVrgxzsr7D/fEk2yBqt0xFybXP2lEwuI/qdNU0lr5EiR5GO+W83cgOdt18= x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(9452136761055)(131327999870524); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(61425038)(6040375)(601004)(2401047)(2017020603015)(8121501046)(5005006)(20170203043)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123555025)(20161123562025)(20161123560025)(20161123558025)(20161123564025)(6072148)(6042181);SRVR:MWHPR03MB2672;BCL:0;PCL:0;RULEID:;SRVR:MWHPR03MB2672; x-forefront-prvs: 0211965D06 x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(7916002)(189002)(199003)(38730400002)(305945005)(54356999)(74316002)(9686003)(8656002)(7736002)(229853002)(77096006)(99286003)(2950100002)(7696004)(122556002)(5660300001)(86362001)(2201001)(55016002)(6506006)(50986999)(54906002)(86612001)(76176999)(6436002)(189998001)(25786008)(97736004)(81156014)(105586002)(106356001)(106116001)(102836003)(10090500001)(8676002)(81166006)(6116002)(2501003)(92566002)(8990500004)(2906002)(53936002)(2900100001)(6246003)(10290500002)(101416001)(1691005)(5005710100001)(33656002)(93886004)(68736007)(3660700001)(4326007)(3280700002)(8936002);DIR:OUT;SFP:1102;SCL:1;SRVR:MWHPR03MB2672;H:MWHPR03MB2669.namprd03.prod.outlook.com;FPR:;SPF:None;PTR:InfoNoRecords;MX:1;A:1;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Feb 2017 06:29:33.1761 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR03MB2672 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v176TgEp013677 > 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