From: Tejun Heo <tj@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Hugh Dickins <hughd@google.com>,
Steven Rostedt <rostedt@goodmis.org>,
Li Zefan <lizefan@huawei.com>,
Markus Blank-Burian <burian@muenster.de>,
Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
David Rientjes <rientjes@google.com>,
Ying Han <yinghan@google.com>, Greg Thelen <gthelen@google.com>,
Michel Lespinasse <walken@google.com>,
cgroups@vger.kernel.org,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Alexander Duyck <alexander.h.duyck@intel.com>,
Yinghai Lu <yinghai@kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: Possible regression with cgroups in 3.11
Date: Sat, 16 Nov 2013 13:53:56 +0900 [thread overview]
Message-ID: <20131116045356.GA5618@mtj.dyndns.org> (raw)
In-Reply-To: <20131116002820.GA31073@google.com>
Hello, Bjorn.
On Fri, Nov 15, 2013 at 05:28:20PM -0700, Bjorn Helgaas wrote:
> It would be better to fix PCI so we don't call VF driver .probe() methods
> from inside a PF driver .probe() method, but that's a bigger project.
Yeah, if pci doesn't need the recursion, we can simply revert restore
the lockdep annoation on work_on_cpu().
> @@ -293,7 +293,9 @@ static int pci_call_probe(struct pci_driver *drv, struct pci_dev *dev,
> its local memory on the right node without any need to
> change it. */
> node = dev_to_node(&dev->dev);
> - if (node >= 0) {
> + preempt_disable();
> +
> + if (node >= 0 && node != numa_node_id()) {
A bit of comment here would be nice but yeah I think this should work.
Can you please also queue the revert of c2fda509667b ("workqueue:
allow work_on_cpu() to be called recursively") after this patch?
Please feel free to add my acked-by.
Thanks.
--
tejun
next prev parent reply other threads:[~2013-11-16 4:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5258E584.70500@huawei.com>
[not found] ` <CA+SBX_MQVMuzWKroASK7Cr5J8cu9ajGo=CWr7SRs+OWh83h4_w@mail.gmail.com>
[not found] ` <525CB337.8050105@huawei.com>
[not found] ` <CA+SBX_Ogo8HP81o+vrJ8ozSBN6gPwzc8WNOV3Uya=4AYv+CCyQ@mail.gmail.com>
[not found] ` <CA+SBX_OJBbYzrNX5Mi4rmM2SANShXMmAvuPGczAyBdx8F2hBDQ@mail.gmail.com>
[not found] ` <5270BFE7.4000602@huawei.com>
[not found] ` <alpine.LNX.2.00.1310301606080.2333@eggly.anvils>
[not found] ` <20131031130647.0ff6f2c7@gandalf.local.home>
[not found] ` <alpine.LNX.2.00.1310311442030.2633@eggly.anvils>
[not found] ` <20131113032804.GB19394@mtj.dyndns.org>
2013-11-13 7:38 ` Possible regression with cgroups in 3.11 Tejun Heo
2013-11-16 0:28 ` Bjorn Helgaas
2013-11-16 4:53 ` Tejun Heo [this message]
2013-11-18 18:14 ` Bjorn Helgaas
2013-11-18 19:29 ` Yinghai Lu
2013-11-18 20:39 ` Bjorn Helgaas
2013-11-21 4:26 ` Sasha Levin
2013-11-21 4:47 ` Bjorn Helgaas
2013-11-25 21:57 ` Bjorn Helgaas
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=20131116045356.GA5618@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=alexander.h.duyck@intel.com \
--cc=bhelgaas@google.com \
--cc=burian@muenster.de \
--cc=cgroups@vger.kernel.org \
--cc=gthelen@google.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
--cc=rjw@sisk.pl \
--cc=rostedt@goodmis.org \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
--cc=walken@google.com \
--cc=yinghai@kernel.org \
--cc=yinghan@google.com \
/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).