[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <201106171038.25988.ptesarik@suse.cz>
Date: Fri, 17 Jun 2011 10:38:25 +0200
From: Petr Tesarik <ptesarik@...e.cz>
To: Andrew Morton <akpm@...ux-foundation.org>,
Fenghua Yu <fenghua.yu@...el.com>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...hat.com>,
Paul Mundt <lethal@...ux-sh.org>,
Russell King <linux@....linux.org.uk>,
Thomas Gleixner <tglx@...utronix.de>,
Tony Luck <tony.luck@...el.com>, x86@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-ia64@...r.kernel.org,
linux-sh@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: [PATCH 00/10] Enhance /dev/mem to allow read/write of arbitrary physical addresses
This patch series enhances /dev/mem, so that read and write is possible
at any address. The patchset includes actual implementation for x86.
Petr Tesarik (10):
Return EOF on out-of-bounds read from /dev/mem
(un)xlate_dev_mem_ptr: use phys_addr_t for the @phys parameter
x86: translate highmem /dev/mem pointers
ia64: change xlate_dev_mem_ptr's argument to phys_addr_t
valid_phys_addr_range: use phys_addr_t for the @addr parameter
sh: change valid_phys_addr_range's @addr param to phys_addr_t
arm: change valid_phys_addr_range's @addr param to phys_addr_t
ia64: change valid_phys_addr_range's @addr param to phys_addr_t
x86: provide arch-specific valid_phys_addr_range()
Allow reading/writing all memory through /dev/mem
arch/arm/include/asm/io.h | 2 +-
arch/arm/mm/mmap.c | 2 +-
arch/ia64/include/asm/io.h | 2 +-
arch/ia64/include/asm/uaccess.h | 2 +-
arch/ia64/kernel/efi.c | 2 +-
arch/sh/include/asm/io.h | 2 +-
arch/sh/mm/mmap.c | 2 +-
arch/x86/include/asm/io.h | 15 +++++++++++++--
arch/x86/mm/ioremap.c | 24 ++++++++++++++++++------
drivers/char/mem.c | 14 ++++++++++----
10 files changed, 48 insertions(+), 19 deletions(-)
--
1.7.3.4
--
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/
Powered by blists - more mailing lists