linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@huawei.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
	Gu Zheng <guz.fnst@cn.fujitsu.com>,
	Lin Feng <linfeng@cn.fujitsu.com>, <linux-pci@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <tangchen@cn.fujitsu.com>,
	<laijs@cn.fujitsu.com>, <wency@cn.fujitsu.com>,
	<izumi.taku@jp.fujitsu.com>, Don Dutile <ddutile@redhat.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] pci-sysfs: replace mutex_lock with mutex_trylock to avoid potential deadlock situation
Date: Mon, 28 Jan 2013 15:38:02 +0800	[thread overview]
Message-ID: <51062ADA.6080903@huawei.com> (raw)
In-Reply-To: <CAE9FiQVV20XktXTfQ2OKQeprL1V2rGORpUf8VBOyDB4Y+VOCNQ@mail.gmail.com>

Hi all,
	I have worked out a draft patch set to serialize hotplug operations,
but encountered some obstacles when dealing with PCI root buses. I will
try to rebase the patch set onto "PCI: Iterate pci host bridge instead of
pci root bus" from Yinghai. And also need to fix bugs reported by Lin Feng
too.

Regards!
Gerry

On 2013-1-26 4:59, Yinghai Lu wrote:
> On Fri, Jan 25, 2013 at 12:30 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> 
>> If we're going to fix the sysfs deadlock (and we should), I want to
>> either see an argument for why we don't have a problem outside of
>> sysfs, or I want to fix sysfs and non-sysfs at the same time.
> 
> Sure.
> 
> Jiang should have one patches to address that?
> 
> Yinghai
> 
> 



      reply	other threads:[~2013-01-28  7:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-27  7:42 [PATCH] pci-sysfs: replace mutex_lock with mutex_trylock to avoid potential deadlock situation Lin Feng
2013-01-03  1:47 ` Lin Feng
2013-01-24 23:12 ` Bjorn Helgaas
2013-01-25 10:02   ` Gu Zheng
2013-01-25 17:44     ` Bjorn Helgaas
2013-01-25 18:57       ` Yinghai Lu
2013-01-25 20:30         ` Bjorn Helgaas
2013-01-25 20:59           ` Yinghai Lu
2013-01-28  7:38             ` Jiang Liu [this message]

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=51062ADA.6080903@huawei.com \
    --to=jiang.liu@huawei.com \
    --cc=bhelgaas@google.com \
    --cc=ddutile@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=guz.fnst@cn.fujitsu.com \
    --cc=izumi.taku@jp.fujitsu.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linfeng@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tangchen@cn.fujitsu.com \
    --cc=wency@cn.fujitsu.com \
    --cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).