linux-kernel - Re: [PATCH 07/10] um: Set __HAVE_ARCH_GATE_AREA for x86

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:	Sat, 23 Jul 2011 14:15:08 +0200
From:	Richard Weinberger <richard@....at>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [PATCH 07/10] um: Set __HAVE_ARCH_GATE_AREA for x86_64

Am Samstag 23 Juli 2011, 01:01:27 schrieb Andrew Morton:
> On Thu, 21 Jul 2011 11:18:31 +0200
> 
> Richard Weinberger <richard@....at> wrote:
> > Implement arch_vma_name() and make get_gate_vma(),
> > in_gate_area() and in_gate_area_no_mm() a nop.
> > 
> > We need arch_vma_name() to support vDSO.
> 
> Well this is awkward.

Why?
Without it UML's vDSO will have no name.
E.g. when reading /proc/<pid>/maps

> >  arch/um/sys-x86_64/asm/elf.h |    1 +
> >  arch/um/sys-x86_64/mem.c     |   22 ++++++++++++++++++++++
> >  2 files changed, 23 insertions(+), 0 deletions(-)
> 
> Your um-clean-up-vm-flagsh.patch deleted arch/um/sys-x86_64/mem.c.
> 
> There's not really any appropriate .c file in arch/um/sys-x86_64 for
> these functions so I changed the patch to reinstate mem.c.
> 
> Then I changed my maind and dropped it ;) Hopefully none of the other
> patches depended on this one.
> 
> Then I looked at um-implement-a-x86_64-vdso.patch, got nervous and
> undropped um-set-__have_arch_gate_area-for-x86_64.patch.

I see, you've had some fun with this patch. ;-)
Sorry for that, I completely forgot rebasing my patches to mmotm.

Thanks,
//richard
--
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/