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:	Wed, 11 Mar 2015 16:13:05 +0100
From:	Gregory CLEMENT <gregory.clement@...e-electrons.com>
To:	Stas Sergeev <stsp@...t.ru>,
	Russell King - ARM Linux <linux@....linux.org.uk>
CC:	Linux kernel <linux-kernel@...r.kernel.org>,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] n_tty: use kmalloc() instead of vmalloc() to avoid crash
 on armada-xp

On 11/03/2015 16:01, Stas Sergeev wrote:
> 11.03.2015 16:14, Russell King - ARM Linux пишет:
>> On Wed, Mar 11, 2015 at 01:44:57PM +0100, Gregory CLEMENT wrote:
>>> Hi Stas,
>>>
>>> On 10/03/2015 17:54, Stas Sergeev wrote:
>>>> Hello, the patch below is needed for a successful boot on armada-xp.
>>>>
>>> I am really surprised by this patch because I used the Armada XP based
>>> board in a daily base and I never saw this issue.
>> Can you provide some details about your board - does it have 8GB of
>> memory, ranging from 0-0xf0000000, and 4G-8G ?
> I wonder about this 256Mb memory hole.

This is where the SoC registers are.

> There is only one dimm for whole 8Gb.
> It seems 0xf000000-0xffffffff is used for PCI though:
> ---
> 
> 0xf3000000-0xf303ffff 64bit]
> [  119.290027] pci 0000:00:00.0: BAR 2: set to [mem
> 0xf3000000-0xf303ffff 64bit] (PCI address [0xf3000000-0xf303ffff])
> [  119.300509] pci 0000:00:00.0: BAR 0: assigned [mem
> 0xf3040000-0xf305ffff 64bit]
> [  119.307883] pci 0000:00:00.0: BAR 0: set to [mem
> 0xf3040000-0xf305ffff 64bit] (PCI address [0xf3040000-0xf305ffff])
> [  119.318367] pci 0000:00:00.0: BAR 6: assigned [mem
> 0xf3060000-0xf306ffff pref]
> 
> ---
> 
> Does this mean that the 256Mb of physical memory is
> completely unaccessable on this board?
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ