[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20100223105959.a50dbe11.sfr@canb.auug.org.au>
Date: Tue, 23 Feb 2010 10:59:59 +1100
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: Ingo Molnar <mingo@...e.hu>, mingo@...hat.com,
linux-kernel@...r.kernel.org, roland@...hat.com,
suresh.b.siddha@...el.com, tglx@...utronix.de, hjl.tools@...il.com,
linux-tip-commits@...r.kernel.org
Subject: Re: linux-next requirements (Was: Re: [tip:x86/ptrace] ptrace: Add
support for generic PTRACE_GETREGSET/PTRACE_SETREGSET)
Hi Peter,
On Mon, 22 Feb 2010 14:57:28 -0800 "H. Peter Anvin" <hpa@...or.com> wrote:
>
> Either which way, Roland has a mitigation patch -- which basically
> disables the broken bits of PARISC until the PARISC maintainers fix it.
> What is the best way to handle that kind of stuff?
Well, now that Roland has made at least one of the PARISC maintainers
aware of the problem, we could wait a little while to see if a solution
is forthcoming from them. If not, then maybe Roland's patch could be
applied to the appropriate tip tree or we could just leave PARISC broken
in linux-next until they decide to fix it. Note that some of the PARISC
builds are already broken in linux-next for other reasons.
Are there any downsides to Roland's patch as far as PARISC is concerned
(apart from the loss of some functionality, of course)?
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists