On Wed, Jul 30, 2014 at 08:50:07AM -0700, Greg Kroah-Hartman wrote: > On Wed, Jul 30, 2014 at 05:10:29PM +0400, Max Filippov wrote: > > Hi Greg, > > > > On Tue, Jul 29, 2014 at 8:57 AM, <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > > > The patch below does not apply to the 3.15-stable tree. > > > If someone wants it applied there, or to any other stable or longterm > > > tree, then please email the backport, including the original git commit > > > id to <stable@xxxxxxxxxxxxxxx>. > > > > On my side this patch applies clearly to the current v3.15.7. > > Could this message be caused by anything else besides the > > literal patch applicability (e.g. the patch size)? > > > > > ------------------ original commit in Linus's tree ------------------ > > > > > > From 17290231df16eeee5dfc198dbf5ee4b419996dcd Mon Sep 17 00:00:00 2001 > > > From: Max Filippov <jcmvbkbc@xxxxxxxxx> > > > Date: Sat, 24 May 2014 21:48:28 +0400 > > > Subject: [PATCH] xtensa: add fixup for double exception raised in window > > > overflow > > > > > > There are two FIXMEs in the double exception handler 'for the extremely > > > unlikely case'. This case gets hit by gcc during kernel build once in > > > a few hours, resulting in an unrecoverable exception condition. > > > > > > Provide missing fixup routine to handle this case. Double exception > > > literals now need 8 more bytes, add them to the linker script. > > > > > > Also replace bbsi instructions with bbsi.l as we're branching depending > > > on 8th and 7th LSB-based bits of exception address. > > > > > > This may be tested by adding the explicit DTLB invalidation to window > > > overflow handlers, like the following: > > > > > > --- a/arch/xtensa/kernel/vectors.S > > > +++ b/arch/xtensa/kernel/vectors.S > > > @@ -592,6 +592,14 @@ ENDPROC(_WindowUnderflow4) > > > ENTRY_ALIGN64(_WindowOverflow8) > > > Odds are patch is complaining about the diff in the changelog comment > like this, I'll try it again after this round of kernels are released on > Friday, thanks for looking at it. Yes, that was it, it's now applied to the tree, thanks. greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html