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]
Message-ID: <8bd0f97a0906130940j6b5e578bha8193f59d03c2f05@mail.gmail.com>
Date:	Sat, 13 Jun 2009 12:40:45 -0400
From:	Mike Frysinger <vapier.adi@...il.com>
To:	Jamie Lokier <jamie@...reable.org>
Cc:	uClinux development list <uclinux-dev@...inux.org>,
	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

On Sat, Jun 13, 2009 at 12:13, Jamie Lokier wrote:
> 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?

no, because with a MMU, the memory would be virtualized and we could
handle it dynamically

> 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?

the addresses are keys, not fixed and/or "real" addresses
-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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ