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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Sat, 13 Jun 2009 17:13:23 +0100
From:	Jamie Lokier <jamie@...reable.org>
To:	uClinux development list <uclinux-dev@...inux.org>
Cc:	linux-kernel@...r.kernel.org, Jie Zhang <jie.zhang@...log.com>,
	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

Mike Frysinger wrote:
> From: Jie Zhang <jie.zhang@...log.com>
> 
> The Blackfin port has custom program header flags/addresses for
> automatically loading regions into the dedicated on-chip SRAM.  So add a
> hook for ports to leverage.

What does this have to do with FDPIC?  I don't see anything that is
specific to FDPIC about this code, other than FDPIC being the type of
ELF used on Blackfin.  If an MMU were added to some future Blackfins,
wouldn't this code be used for non-FDPIC ELF too?

It looks like a way for certain special executables to load themselves
into fixed regions of the on-chip SRAM - and promptly crash if another
executable does the same.  Not so much a general executable format, as
a hack to load something specific which should only be done once at a
time.  What am I missing here?

-- Jamie
--
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/