From: Long Li <longli@microsoft.com>
To: Greg KH <greg@kroah.com>
Cc: KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject
Date: Mon, 27 Feb 2017 21:51:46 +0000 [thread overview]
Message-ID: <BN3PR03MB22271398236EE893B6AB53BACE570@BN3PR03MB2227.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20170225080218.GA2291@kroah.com>
Ok, I will resend.
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Saturday, February 25, 2017 12:02 AM
> To: Long Li <longli@microsoft.com>
> Cc: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
> <haiyangz@microsoft.com>; Bjorn Helgaas <bhelgaas@google.com>;
> devel@linuxdriverproject.org; linux-kernel@vger.kernel.org; linux-
> pci@vger.kernel.org
> Subject: Re: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject
>
> On Fri, Feb 24, 2017 at 09:49:17PM +0000, Long Li wrote:
> > A PCI_EJECT message can arrive at the same time we are calling
> pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS
> message or in create_root_hv_pci_bus(), in this case we could potentailly
> modify the bus from multiple places. Properly lock the bus access.
>
> Properly wrap your changelog comments at 72 columns like your editor is
> telling you to do...
WARNING: multiple messages have this Message-ID (diff)
From: Long Li <longli@microsoft.com>
To: Greg KH <greg@kroah.com>
Cc: KY Srinivasan <kys@microsoft.com>,
Haiyang Zhang <haiyangz@microsoft.com>,
Bjorn Helgaas <bhelgaas@google.com>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: RE: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject
Date: Mon, 27 Feb 2017 21:51:46 +0000 [thread overview]
Message-ID: <BN3PR03MB22271398236EE893B6AB53BACE570@BN3PR03MB2227.namprd03.prod.outlook.com> (raw)
In-Reply-To: <20170225080218.GA2291@kroah.com>
Ok, I will resend.
> -----Original Message-----
> From: Greg KH [mailto:greg@kroah.com]
> Sent: Saturday, February 25, 2017 12:02 AM
> To: Long Li <longli@microsoft.com>
> Cc: KY Srinivasan <kys@microsoft.com>; Haiyang Zhang
> <haiyangz@microsoft.com>; Bjorn Helgaas <bhelgaas@google.com>;
> devel@linuxdriverproject.org; linux-kernel@vger.kernel.org; linux-
> pci@vger.kernel.org
> Subject: Re: [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eje=
ct
>=20
> On Fri, Feb 24, 2017 at 09:49:17PM +0000, Long Li wrote:
> > A PCI_EJECT message can arrive at the same time we are calling
> pci_scan_child_bus in the workqueue for the previous PCI_BUS_RELATIONS
> message or in create_root_hv_pci_bus(), in this case we could potentailly
> modify the bus from multiple places. Properly lock the bus access.
>=20
> Properly wrap your changelog comments at 72 columns like your editor is
> telling you to do...
next prev parent reply other threads:[~2017-02-27 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 21:49 [Resend PATCH 2/2 v3] pci-hyperv: lock pci bus on device eject Long Li
2017-02-24 21:49 ` Long Li
2017-02-25 8:02 ` Greg KH
2017-02-27 21:51 ` Long Li [this message]
2017-02-27 21:51 ` Long Li
[not found] <1485236759-27699-1-git-send-email-longli@exchange.microsoft.com>
2017-01-27 18:42 ` KY Srinivasan
2017-01-27 18:42 ` KY Srinivasan
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=BN3PR03MB22271398236EE893B6AB53BACE570@BN3PR03MB2227.namprd03.prod.outlook.com \
--to=longli@microsoft.com \
--cc=bhelgaas@google.com \
--cc=devel@linuxdriverproject.org \
--cc=greg@kroah.com \
--cc=haiyangz@microsoft.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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.