linux-kernel - Re: [PATCH][kgdb][v3] Make mem access function weak in kgdb.c and kgdb.h

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

Date:	Mon, 22 Sep 2008 10:40:28 +0800
From:	"Sonic Zhang" <sonic.adi@...il.com>
To:	"Jason Wessel" <jason.wessel@...driver.com>
Cc:	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	"kgdb mailing list" <kgdb-bugreport@...ts.sourceforge.net>
Subject: Re: [PATCH][kgdb][v3] Make mem access function weak in kgdb.c and kgdb.h

The kgdb patch for blackfin is targeted to the 2.6.28 kernel, because
2.6.27 kernel doesn't accept big changes in this stage.

Sonic

On Fri, Sep 19, 2008 at 7:29 PM, Jason Wessel
<jason.wessel@...driver.com> wrote:
>
> One question I had, was if this work was targeted to the 2.6.27 kernel
> or the 2.6.28 kernel.  I figure there are blackfin fin specific patches
> to go in with this, and I can attempt to sync with your blackfin pull
> requests.
>
> Thanks,
> Jason.
>
> Sonic Zhang wrote:
>> Hi Jason,
>>
>> Any comments?
>>
>> Sonic Zhang
>>
>> On Tue, Sep 16, 2008 at 9:49 AM, sonic zhang <sonic.adi@...il.com> wrote:
>>
>>> L1 instruction memory and MMR memory on blackfin can not be accessed by
>>> common functions probe_kernel_read() and probe_kernel_write().
>>> Blackfin asks for 2/4 byte align access to MMR memory and DMA access to
>>> L1 instruction memory. These functions need to be reimplemented in
>>> architecture specific kgdb.c. Update documentation and prototypes as
>>> well.
>>>
>>> Signed-off-by: Sonic Zhang <sonic.adi@...il.com>
>>>
>
>
--
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/