From: kys@exchange.microsoft.com
To: helgaas@kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
marcelo.cerri@canonical.com, sthemmin@microsoft.com
Cc: "K. Y. Srinivasan" <kys@microsoft.com>, <stable@vger.kernel.org>
Subject: [PATCH 2/2] pci-hyperv: Fix an atomic bug
Date: Fri, 24 Mar 2017 11:07:22 -0700 [thread overview]
Message-ID: <1490378842-26950-3-git-send-email-kys@exchange.microsoft.com> (raw)
In-Reply-To: <1490378800-26907-1-git-send-email-kys@exchange.microsoft.com>
From: K. Y. Srinivasan <kys@microsoft.com>
The memory allocation here needs to be non-blocking.
Fix the issue.
Signed-off-by: K. Y. Srinivasan <kys@microsoft.com>
Cc: <stable@vger.kernel.org>
---
drivers/pci/host/pci-hyperv.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/pci/host/pci-hyperv.c b/drivers/pci/host/pci-hyperv.c
index 32a16fb..85088a1 100644
--- a/drivers/pci/host/pci-hyperv.c
+++ b/drivers/pci/host/pci-hyperv.c
@@ -877,7 +877,7 @@ static void hv_compose_msi_msg(struct irq_data *data, struct msi_msg *msg)
hv_int_desc_free(hpdev, int_desc);
}
- int_desc = kzalloc(sizeof(*int_desc), GFP_KERNEL);
+ int_desc = kzalloc(sizeof(*int_desc), GFP_ATOMIC);
if (!int_desc)
goto drop_reference;
--
1.7.1
next prev parent reply other threads:[~2017-03-24 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-24 18:06 [PATCH 0/2] pci-hyperv: Some miscellaneous fixes kys
2017-03-24 18:07 ` [PATCH 1/2] PCI: hv: Fix a bug in specifying CPU affinity kys
2017-03-24 18:07 ` [PATCH 1/2] pci-hyperv: " kys
2017-03-27 18:13 ` Long Li
2017-03-27 18:13 ` Long Li
2017-03-24 18:07 ` kys [this message]
2017-03-27 18:14 ` [PATCH 2/2] pci-hyperv: Fix an atomic bug Long Li
2017-03-27 18:14 ` Long Li
2017-04-04 19:03 ` [PATCH 0/2] pci-hyperv: Some miscellaneous fixes Bjorn Helgaas
2017-04-04 19:54 ` KY Srinivasan
2017-04-04 19:54 ` KY Srinivasan
2017-04-04 20:39 ` Bjorn Helgaas
2017-04-04 21:47 ` KY Srinivasan
2017-04-04 21:47 ` 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=1490378842-26950-3-git-send-email-kys@exchange.microsoft.com \
--to=kys@exchange.microsoft.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=helgaas@kernel.org \
--cc=jasowang@redhat.com \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=olaf@aepfle.de \
--cc=stable@vger.kernel.org \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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 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.