From: Keith Busch <kbusch@meta.com>
To: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>
Cc: Tony Battersby <tonyb@cybernetics.com>, Keith Busch <kbusch@kernel.org>
Subject: [PATCH 07/11] dmapool: rearrange page alloc failure handling
Date: Mon, 5 Dec 2022 06:59:33 -0800 [thread overview]
Message-ID: <20221205145937.54367-8-kbusch@meta.com> (raw)
In-Reply-To: <20221205145937.54367-1-kbusch@meta.com>
From: Keith Busch <kbusch@kernel.org>
Handle the error in a condition so the good path can be in the normal
flow.
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
mm/dmapool.c | 18 +++++++++---------
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/mm/dmapool.c b/mm/dmapool.c
index 8a7aa19e650a1..f77e2af4941de 100644
--- a/mm/dmapool.c
+++ b/mm/dmapool.c
@@ -222,17 +222,17 @@ static struct dma_page *pool_alloc_page(struct dma_pool *pool, gfp_t mem_flags)
return NULL;
page->vaddr = dma_alloc_coherent(pool->dev, pool->allocation,
&page->dma, mem_flags);
- if (page->vaddr) {
-#ifdef DMAPOOL_DEBUG
- memset(page->vaddr, POOL_POISON_FREED, pool->allocation);
-#endif
- pool_initialise_page(pool, page);
- page->in_use = 0;
- page->offset = 0;
- } else {
+ if (!page->vaddr) {
kfree(page);
- page = NULL;
+ return NULL;
}
+#ifdef DMAPOOL_DEBUG
+ memset(page->vaddr, POOL_POISON_FREED, pool->allocation);
+#endif
+ pool_initialise_page(pool, page);
+ page->in_use = 0;
+ page->offset = 0;
+
return page;
}
--
2.30.2
next prev parent reply other threads:[~2022-12-05 15:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 14:59 [PATCH 00/11] dmapool enhancements Keith Busch
2022-12-05 14:59 ` [PATCH 01/11] dmapool: add alloc/free performance test Keith Busch
2022-12-06 2:17 ` kernel test robot
2022-12-05 14:59 ` [PATCH 02/11] dmapool: remove checks for dev == NULL Keith Busch
2022-12-05 14:59 ` [PATCH 03/11] dmapool: use sysfs_emit() instead of scnprintf() Keith Busch
2022-12-05 14:59 ` [PATCH 04/11] dmapool: cleanup integer types Keith Busch
2022-12-05 14:59 ` [PATCH 05/11] dmapool: speedup DMAPOOL_DEBUG with init_on_alloc Keith Busch
2022-12-05 14:59 ` [PATCH 06/11] dmapool: move debug code to own functions Keith Busch
2022-12-05 14:59 ` Keith Busch [this message]
2022-12-05 14:59 ` [PATCH 08/11] dmapool: consolidate page initialization Keith Busch
2022-12-05 14:59 ` [PATCH 09/11] dmapool: simplify freeing Keith Busch
2022-12-05 14:59 ` [PATCH 10/11] dmapool: don't memset on free twice Keith Busch
2022-12-05 14:59 ` [PATCH 11/11] dmapool: link blocks across pages Keith Busch
2022-12-05 18:07 ` Tony Battersby
2022-12-05 22:34 ` kernel test robot
2022-12-11 15:24 ` kernel test robot
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=20221205145937.54367-8-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=tonyb@cybernetics.com \
--cc=willy@infradead.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