From: David Miller <davem@davemloft.net>
To: stable@vger.kernel.org
Subject: [PATCH] SPARC
Date: Fri, 03 Jul 2015 15:32:14 -0700 (PDT) [thread overview]
Message-ID: <20150703.153214.1484455100213965906.davem@davemloft.net> (raw)
[-- Attachment #1: Type: Text/Plain, Size: 101 bytes --]
Please queue up the following Sparc bug fix for 3.14, 3.18, and
4.0 -stable, respectively.
Thanks!
[-- Attachment #2: sparc-Use-GFP_ATOMIC-in-ldc_alloc_exp_dring-as-it-can-be-called-in-softirq-context.patch --]
[-- Type: Text/X-Patch, Size: 1418 bytes --]
>From patchwork Tue Apr 21 14:30:41 2015
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: sparc: Use GFP_ATOMIC in ldc_alloc_exp_dring() as it can be called in
softirq context
From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
X-Patchwork-Id: 463148
Message-Id: <1429626641-199974-1-git-send-email-sowmini.varadhan@oracle.com>
To: sowmini.varadhan@oracle.com, sparclinux@vger.kernel.org
Cc: david.stevens@oracle.com, davem@davemloft.net
Date: Tue, 21 Apr 2015 10:30:41 -0400
[ Upstream commit 671d773297969bebb1732e1cdc1ec03aa53c6be2 ]
Since it is possible for vnet_event_napi to end up doing
vnet_control_pkt_engine -> ... -> vnet_send_attr ->
vnet_port_alloc_tx_ring -> ldc_alloc_exp_dring -> kzalloc()
(i.e., in softirq context), kzalloc() should be called with
GFP_ATOMIC from ldc_alloc_exp_dring.
Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
---
arch/sparc/kernel/ldc.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/sparc/kernel/ldc.c b/arch/sparc/kernel/ldc.c
index d2ae0f7..7d3ca30 100644
--- a/arch/sparc/kernel/ldc.c
+++ b/arch/sparc/kernel/ldc.c
@@ -2290,7 +2290,7 @@ void *ldc_alloc_exp_dring(struct ldc_channel *lp, unsigned int len,
if (len & (8UL - 1))
return ERR_PTR(-EINVAL);
- buf = kzalloc(len, GFP_KERNEL);
+ buf = kzalloc(len, GFP_ATOMIC);
if (!buf)
return ERR_PTR(-ENOMEM);
next reply other threads:[~2015-07-03 22:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 22:32 David Miller [this message]
2015-07-04 2:57 ` [PATCH] SPARC Greg KH
2015-07-09 13:40 ` Luis Henriques
-- strict thread matches above, loose matches on Subject: below --
2017-05-11 2:42 [PATCH] Sparc David Miller
2017-05-11 8:36 ` Greg KH
2017-08-24 3:25 David Miller
2017-08-25 0:41 ` Greg KH
2017-11-20 11:53 David Miller
2017-11-20 20:08 ` Greg KH
2018-01-01 3:36 David Miller
2018-01-01 10:06 ` Greg KH
2018-04-13 17:23 David Miller
2018-04-13 17:38 ` David Miller
2018-04-14 14:05 ` Greg KH
2018-05-22 17:51 David Miller
2018-05-22 18:13 ` Greg KH
2019-06-03 20:38 David Miller
2019-06-04 7:48 ` Greg KH
2020-02-05 14:11 David Miller
2020-02-06 4:54 ` Sasha Levin
2020-02-06 6:49 ` Greg KH
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=20150703.153214.1484455100213965906.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=stable@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 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).