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:	Mon, 7 Dec 2009 11:27:40 +0800
From:	"Zhang, Sonic" <Sonic.Zhang@...log.com>
To:	"Jie Zhang" <jie.zhang@...log.com>,
	"David Howells" <dhowells@...hat.com>
CC:	<uclinux-dist-devel@...ckfin.uclinux.org>,
	"Greg Ungerer" <gerg@...inux.org>,
	"uClinux development list" <uclinux-dev@...inux.org>,
	"David McCullough" <davidm@...pgear.com>,
	<linux-kernel@...r.kernel.org>
Subject: RE: [Uclinux-dist-devel] [uClinux-dev] [PATCH/RFC] FDPIC: add hook for arches to customize program header parsing

No. The sram device can not be accessed by any user space application.
The applications can only do malloc/free via system call.

Sonic 

-----Original Message-----
From: uclinux-dist-devel-bounces@...ckfin.uclinux.org
[mailto:uclinux-dist-devel-bounces@...ckfin.uclinux.org] On Behalf Of
Jie Zhang
Sent: Saturday, December 05, 2009 8:28 AM
To: David Howells
Cc: uclinux-dist-devel@...ckfin.uclinux.org; Greg Ungerer; uClinux
development list; David McCullough; linux-kernel@...r.kernel.org
Subject: Re: [Uclinux-dist-devel] [uClinux-dev] [PATCH/RFC] FDPIC: add
hook for arches to customize program header parsing

On 12/05/2009 01:44 AM, David Howells wrote:
> Mike Frysinger<vapier@...too.org>  wrote:
>
>> 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.
>
> Now that I've ACK'd this, I feel I'm going to have to NAK it.  I'm not

> against the general concept, but:
>
>> +		do_munmap(mm, *maddr, phdr->p_memsz + *disp);
>
> 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?

> debugger.  Do you have a chardev covering the SRAM device?  Perhaps 
> through MTD?
>
Sorry, I don't know the answer to these two questions.


Jie


_______________________________________________
Uclinux-dist-devel mailing list
Uclinux-dist-devel@...ckfin.uclinux.org
https://blackfin.uclinux.org/mailman/listinfo/uclinux-dist-devel
--
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