linux-kernel - Re: Memory trample when using /dev/mem

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-prev] [day] [month] [year] [list]

Message-ID: <CAFLxGvzOnEbNYn1ovXL+e6pwk=+bVfWXsSoEWq9R2+O1Amu5rA@mail.gmail.com>
Date:	Sat, 11 Oct 2014 11:04:30 +0200
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Hu Keping <hukeping@...wei.com>
Cc:	Arnd Bergmann <arnd@...db.de>,
	Greg KH <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>, sdu.liu@...wei.com,
	wangnan0@...wei.com, peifeiyue@...wei.com
Subject: Re: Memory trample when using /dev/mem

On Sat, Oct 11, 2014 at 10:51 AM, Hu Keping <hukeping@...wei.com> wrote:
> As there are many drivers using /dev/mem and we can not
> make sure that the different task will not trample on
> each others memory.Shall we add some printk to help locating the problem
> when error happened?

Actually no driver should use /dev/mem.
Please have a look at UIO.

-- 
Thanks,
//richard
--
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/