linux-kernel - Re: [PATCH 00/10] Enhance /dev/mem to allow read/write of arbitrary physical addresses

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

Date:	Tue, 21 Jun 2011 09:03:18 -0400 (EDT)
From:	Dave Anderson <anderson@...hat.com>
To:	Cong Wang <amwang@...hat.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 00/10] Enhance /dev/mem to allow read/write of arbitrary
 physical addresses



----- Original Message -----
> 于 2011年06月20日 21:24, Dave Anderson 写道:
> >> On Mon, Jun 20, 2011 at 10:42:47, Amerigo Wang<amwang@...hat.com>
> >
> > I don't know what you mean by I "didn't consider it", because
> > the crash utility does support using /proc/kcore as an alternative
> > live memory source.
> 
> Sorry, I recall that in our last discussion you didn't
> mention this. But it is good to know that crash supports this!
> 
> >
> > The problem is that /proc/kcore can only access highmem if it
> > is mapped as kernel virtual address. So it cannot read 32-bit
> > highmem PTE's, user-space memory, etc.
> >
> 
> Hmm, looking at the code, you are right, it only has
> low memory in kernel space.
> 
> But what's the problem of adding highmem into kcore? :-/
> 
> Thanks.

/proc/kcore was presumably designed for use by gdb with a vmlinux
namelist, and like user-space core dumps, the PT_LOAD segments 
reference virtual address regions with p_vaddr/p_paddr pairs.

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