linux-kernel - Re: [PATCH] UML utrace support, step 1

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]

Message-Id: <20070316232007.0CE881801C5@magilla.sf.frob.com>
Date:	Fri, 16 Mar 2007 16:20:06 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Jeff Dike <jdike@...toit.com>
Cc:	linux-kernel@...r.kernel.org,
	user-mode-linux-devel@...ts.sourceforge.net
Subject: Re: [PATCH] UML utrace support, step 1

> Did I send the right patch?  The one I meant to send (appended below),
> indeed builds and runs without utrace-regset.patch and
> utrace-core.patch applied.  It's utrace-1 in the following:

That is not the same patch I tried before.  This one does apply and build
fine (after make defconfig ARCH=um).  

Technically utrace_native_view doesn't belong in the tracehook patch (but
in the regset one to follow it), but it is harmless.

I've merged it into my current tree.  You can get this via GIT if you like
that.  I do regular merges from Linus's GIT tree, so any upstream UML
changes that merge cleanly or have trivial conflict fixes I can do will be
taken care of automatically.  For future updates, please send me
incremental changes based on my current stuff; the GIT branches and the
2.6-current patches on my utrace web page always match up.  My patch set
generation uses just one fixed log message for utrace-tracehook-um.patch,
so tell me if you want to adjust it from log text in today's patch.

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