From: Frederic Barrat <fbarrat@linux.ibm.com> To: Sasha Levin <sashal@kernel.org>, linux-kernel@vger.kernel.org, stable@vger.kernel.org Cc: "Alastair D'Silva" <alastair@d-silva.org>, Andrew Donnellan <ajd@linux.ibm.com>, Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@lists.ozlabs.org, linux-pci@vger.kernel.org Subject: Re: [PATCH AUTOSEL 5.4 70/78] pci/hotplug/pnv-php: Remove erroneous warning Date: Tue, 21 Apr 2020 13:03:34 +0200 [thread overview] Message-ID: <3f547720-ec27-7a12-d80e-79cd46477daf@linux.ibm.com> (raw) In-Reply-To: <20200418144047.9013-70-sashal@kernel.org> Le 18/04/2020 à 16:40, Sasha Levin a écrit : > From: Frederic Barrat <fbarrat@linux.ibm.com> > > [ Upstream commit 658ab186dd22060408d94f5c5a6d02d809baba44 ] This doesn't need to be backported to stable. Fred > On powernv, when removing a device through hotplug, the following > warning is logged: > > Invalid refcount <.> on <...> > > It may be incorrect, the refcount may be set to a higher value than 1 > and be valid. of_detach_node() can drop more than one reference. As it > doesn't seem trivial to assert the correct value, let's remove the > warning. > > Reviewed-by: Alastair D'Silva <alastair@d-silva.org> > Reviewed-by: Andrew Donnellan <ajd@linux.ibm.com> > Signed-off-by: Frederic Barrat <fbarrat@linux.ibm.com> > Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> > Link: https://lore.kernel.org/r/20191121134918.7155-7-fbarrat@linux.ibm.com > Signed-off-by: Sasha Levin <sashal@kernel.org> > --- > drivers/pci/hotplug/pnv_php.c | 6 ------ > 1 file changed, 6 deletions(-) > > diff --git a/drivers/pci/hotplug/pnv_php.c b/drivers/pci/hotplug/pnv_php.c > index d7b2b47bc33eb..6037983c6e46b 100644 > --- a/drivers/pci/hotplug/pnv_php.c > +++ b/drivers/pci/hotplug/pnv_php.c > @@ -151,17 +151,11 @@ static void pnv_php_rmv_pdns(struct device_node *dn) > static void pnv_php_detach_device_nodes(struct device_node *parent) > { > struct device_node *dn; > - int refcount; > > for_each_child_of_node(parent, dn) { > pnv_php_detach_device_nodes(dn); > > of_node_put(dn); > - refcount = kref_read(&dn->kobj.kref); > - if (refcount != 1) > - pr_warn("Invalid refcount %d on <%pOF>\n", > - refcount, dn); > - > of_detach_node(dn); > } > } >
next prev parent reply other threads:[~2020-04-21 11:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20200418144047.9013-1-sashal@kernel.org> 2020-04-18 14:39 ` [PATCH AUTOSEL 5.4 30/78] drm/nouveau: workaround runpm fail by disabling PCI power management on certain intel bridges Sasha Levin 2020-04-18 14:40 ` [PATCH AUTOSEL 5.4 65/78] PCI/PM: Add pcie_wait_for_link_delay() Sasha Levin 2020-04-18 14:40 ` [PATCH AUTOSEL 5.4 67/78] PCI: pciehp: Prevent deadlock on disconnect Sasha Levin 2020-04-18 14:40 ` [PATCH AUTOSEL 5.4 70/78] pci/hotplug/pnv-php: Remove erroneous warning Sasha Levin 2020-04-21 11:03 ` Frederic Barrat [this message] 2020-04-18 14:40 ` [PATCH AUTOSEL 5.4 77/78] PCI/ASPM: Allow re-enabling Clock PM Sasha Levin 2020-04-18 14:40 ` [PATCH AUTOSEL 5.4 78/78] PCI/PM: Add missing link delays required by the PCIe spec Sasha Levin
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=3f547720-ec27-7a12-d80e-79cd46477daf@linux.ibm.com \ --to=fbarrat@linux.ibm.com \ --cc=ajd@linux.ibm.com \ --cc=alastair@d-silva.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-pci@vger.kernel.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mpe@ellerman.id.au \ --cc=sashal@kernel.org \ --cc=stable@vger.kernel.org \ --subject='Re: [PATCH AUTOSEL 5.4 70/78] pci/hotplug/pnv-php: Remove erroneous warning' \ /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
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).