linux-kernel - [patch 1/6] s390, block: disable fixed buffer mode when DMA support is disabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.00.1105241650230.29780@chino.kir.corp.google.com>
Date:	Tue, 24 May 2011 16:53:45 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>,
	Heiko Carstens <heiko.carstens@...ibm.com>
cc:	Pekka Enberg <penberg@...nel.org>,
	Christoph Lameter <cl@...ux.com>, linux-s390@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: [patch 1/6] s390, block: disable fixed buffer mode when DMA support
 is disabled

dasd=fixedbuffers must create a SLAB_CACHE_DMA cache, which is not
possible if CONFIG_ZONE_DMA is disabled (a supported configuration
without 64-bit support).

If passed, emit a warning and disable fixed buffer mode.

Signed-off-by: David Rientjes <rientjes@...gle.com>
---
 drivers/s390/block/dasd_devmap.c |    5 +++++
 1 files changed, 5 insertions(+), 0 deletions(-)

diff --git a/drivers/s390/block/dasd_devmap.c b/drivers/s390/block/dasd_devmap.c
--- a/drivers/s390/block/dasd_devmap.c
+++ b/drivers/s390/block/dasd_devmap.c
@@ -282,6 +282,11 @@ dasd_parse_keyword( char *parsestring ) {
 		return residual_str;
 	}
 	if (strncmp("fixedbuffers", parsestring, length) == 0) {
+#ifndef CONFIG_ZONE_DMA
+		DBF_EVENT(DBF_WARNING, "%s", "DMA support disabled, "
+					"fixed buffer mode disabled.");
+		return residual_str;
+#endif
 		if (dasd_page_cache)
 			return residual_str;
 		dasd_page_cache =
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/