From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752571AbdBGC6p (ORCPT <rfc822;w@1wt.eu>);
        Mon, 6 Feb 2017 21:58:45 -0500
Received: from esa1.hgst.iphmx.com ([68.232.141.245]:38491 "EHLO
        esa1.hgst.iphmx.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751805AbdBGC6n (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 6 Feb 2017 21:58:43 -0500
X-IronPort-AV: E=Sophos;i="5.33,344,1477929600"; 
   d="scan'208";a="79377554"
X-AuditID: ac1c2134-b098598000000c3b-b8-5899421cf968
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
Thread-Topic: [PATCH] genhd: Do not hold event lock when scheduling
 workqueue elements
Thread-Index: AQHSgO3U7De0QABQS0Odx2B5qtTRbQ==
Date: Tue, 7 Feb 2017 02:56:50 +0000
Message-ID: <1486436195.2791.1.camel@sandisk.com>
References: <1484732896-22941-1-git-send-email-hare@suse.de>
         <1485822639.2669.16.camel@sandisk.com>
         <532c55c4-15da-d2f9-401c-36bc4343756b@suse.com>
         <MWHPR03MB2669B8A45A07846AF0A06E46BF4F0@MWHPR03MB2669.namprd03.prod.outlook.com>
         <MWHPR03MB26699D4657FB67A535972208BF430@MWHPR03MB2669.namprd03.prod.outlook.com>
In-Reply-To: <MWHPR03MB26699D4657FB67A535972208BF430@MWHPR03MB2669.namprd03.prod.outlook.com>
Accept-Language: nl-NL, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.28.1.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <AAF38E85704DB34E9A9BD78213856FF1@sandisk.com>
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrBIsWRmVeSWpSXmKPExsWyRobxn66s08wIg665bBar7/azWexr2cRo
        seDNXjaLPYsmMVmsXH2UyeLhl1ssFntvaVtc3jWHzYHD4/LZUo9NqzrZPHbfbGDzaN3xl91j
        /ZarLB6bT1d7fN4kF8AexWWTkpqTWZZapG+XwJWx9MUuxoI9LBXL5s5la2Bcw9LFyMkhIWAi
        MeviCvYuRi4OIYElTBKzli5jhnDOM0q8WPKLHaSKTcBIYvaEPSwgCRGBGYwSN1segrUwCxxg
        lNj//gYrSJWwQLjEyoafjCC2iECExOkHn1ghbD2J1qPnmUFsFgEViZaPz4DiHBy8AoYSHRNT
        IbYdZJK4N7cZrJdTIFZi5ff7YDWMArISLa+5QcLMAuISt57MZ4I4W0BiyR6IkRICohIvH/9j
        hbAVJD6v+McG0sosoCmxfpc+RKuVxOzVL1ghbEWJKd0Pwf7iFRCUODnzCcsERrFZSDbMQuie
        haR7FpLuWUi6FzCyrmIUK05MLs5NTy0wNNUrTsxLySzO1kvOz93ECI5fRZMdjB0b3Q8xCnAw
        KvHwKkyZESHEmlhWXJl7iFGCg1lJhPew7swIId6UxMqq1KL8+KLSnNTiQ4zSHCxK4rxLtadG
        CAmkJ5akZqemFqQWwWSZODilGhgXbrqY/3kRu4C9Y/4St62zA5x6F919wdN50fIrL9cO/d6U
        X9a/+xc9ev1C9bLUZjndDVOmVsacKP3wvfTExUl7Pi07GTNFf7PaxSsPH/qtjIlKt3/2I0SW
        pTOi/E65RTCT2KGEgLpDZa7qEc6HTaTcv9hxlLgvPyDA4JjhE+fJd3aWwX2zVE4lluKMREMt
        5qLiRADY0nLZ2wIAAA==
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by mail.home.local id v172wmZ2011613

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.