linux-kernel - Re: [PATCH] ia64: remove paravirt code

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: <CA+8MBb+LSDWDVpo7C_Xp7j4WgrnYUXHDyLzxTDY=0_OgVEDrjg@mail.gmail.com>
Date:	Thu, 11 Jun 2015 15:39:05 -0700
From:	Tony Luck <tony.luck@...il.com>
To:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
Cc:	"Yu, Fenghua" <fenghua.yu@...el.com>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	pbonzini@...hat.com, Boris Ostrovsky <boris.ostrovsky@...cle.com>,
	Chris Wright <chrisw@...s-sol.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Alok Kataria <akataria@...are.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [PATCH] ia64: remove paravirt code

On Wed, Jun 10, 2015 at 4:40 PM, Luis R. Rodriguez
<mcgrof@...not-panic.com> wrote:
> Its quite a huge chunk of code removed, I doubt that .o files would
> remain intact after this, but I could be wrong. I think run time
> validation and examination of the code changes, understanding of the
> code changes is necessary, but also likely just as run time tests.

Actually it seems the most of the .o files below arch/ia64/kernel look quite
similar ... some post-processing of the "objdump -d" output the squash
out addreses ... and the before/after .o files have few enough differences
that they can be looked at manually.

> Is there no ia64 regression test suite?
Not really.

> I don't see ia64 getting much love anyway these days so would it not
> hurt to merge and spin through linux-next for a while and if no issues
> are reported make it fly in?

Not sure how many people besides me are booting linux-next kernels.

Still - let's give it a try,

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