From: Sinan Kaya <okaya@codeaurora.org>
To: Govindarajulu Varadarajan <gvaradar@cisco.com>,
benve@cisco.com, bhelgaas@google.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, jlbec@evilplan.org, hch@lst.de,
mingo@redhat.com, peterz@infradead.org
Subject: Re: [PATCH V2] PCI: AER: fix deadlock in do_recovery
Date: Sat, 30 Sep 2017 09:31:35 -0400 [thread overview]
Message-ID: <a9b14502-4ac6-58dc-89ee-a91354f4d2da@codeaurora.org> (raw)
In-Reply-To: <20170930054938.43271-1-gvaradar@cisco.com>
On 9/30/2017 1:49 AM, Govindarajulu Varadarajan wrote:
> This patch does a pci_bus_walk and adds all the devices to a list. After
> unlocking (up_read) &pci_bus_sem, we go through the list and call
> err_handler of the devices with devic_lock() held. This way, we dont try
> to hold both locks at same time.
I do like this approach with some more feedback.
I need a little bit of help here from someone that knows get/put device calls.
I understand get_device() and put_device() are there to increment/decrement
reference counters. This patch seems to use them as an alternative for device_lock()
and device_unlock() API.
If this is a good assumption, then you can get away with just replacing device_lock()
with get_device() and device_unlock() with put_device() in the existing code as
well. Then, you don't need to build a linklist.
A nit is your history messages in the commit message belongs to a cover letter.
--
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.
next prev parent reply other threads:[~2017-09-30 13:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-30 5:49 Govindarajulu Varadarajan
2017-09-30 13:31 ` Sinan Kaya [this message]
2017-10-03 0:19 ` Govindarajulu Varadarajan
2017-10-01 7:55 ` Christoph Hellwig
2017-10-03 0:14 ` Govindarajulu Varadarajan
2017-10-03 8:09 ` Christoph Hellwig
2017-10-03 21:15 ` Bjorn Helgaas
2017-10-05 15:05 ` Wei Yang
2017-10-05 18:42 ` Bjorn Helgaas
2017-10-06 1:11 ` Wei Yang
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=a9b14502-4ac6-58dc-89ee-a91354f4d2da@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=benve@cisco.com \
--cc=bhelgaas@google.com \
--cc=gvaradar@cisco.com \
--cc=hch@lst.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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
Powered by JetHome