linux-kernel - Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing

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 for Android: free password hash cracker in your pocket

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

Message-ID: <8bd0f97a0912070209k5c87643cm53a24566f7e63a9f@mail.gmail.com>
Date:	Mon, 7 Dec 2009 05:09:55 -0500
From:	Mike Frysinger <vapier.adi@...il.com>
To:	David Howells <dhowells@...hat.com>
Cc:	Jie Zhang <jie.zhang@...log.com>,
	uClinux development list <uclinux-dev@...inux.org>,
	linux-kernel@...r.kernel.org, Greg Ungerer <gerg@...inux.org>,
	uclinux-dist-devel@...ckfin.uclinux.org,
	David McCullough <davidm@...pgear.com>
Subject: Re: [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize 
	program header parsing

On Sat, Dec 5, 2009 at 10:14, David Howells wrote:
> Jie Zhang <jie.zhang@...log.com> wrote:
>> > There needs to be a mapping covering the SRAM region for the purposes of the
>>
>> Our GDB is still lack of the feature to debug applications using SRAM. So this
>> part of code was not got exercised. So if we remove this line, can this patch
>> got merged?
>
> No.  Firstly, the piece of storage that gets munmapped isn't used, so unmapping
> it isn't wrong.  What you need to do is to put a mapping over the bit of the
> SRAM you wish to use and then fill it and use it.  Ideally, you'd do this
> inside of do_mmap_pgoff() - that way those bits of the SRAM can be shared, but
> I'm not sure how best to do that.

we've looked into trying to represent the SRAM regions with normal
VMA's a few times, but i think the conclusion every time has been that
it isnt [currently] doable.  i vaguely recall it's due to the fact
that Blackfin SRAM is harvard based and VMA's cant cope with this
restriction.  Sonic should be able to provide more details though.

currently we have a simpler allocator for kernel/user space to
leverage so that small pieces can be dynamically allocated/freed.

> But you need to stick a VMA over it so that various checks don't spit
> EFAULT/EIO at you.

we give SRAM's a "pass" in every place where addresses are checked
-mike
--
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/