On Thu, Nov 27, 2014 at 04:02:24AM +0000, Chanho Min wrote: > > -----Original Message----- > > From: Vladimir Murzin [mailto:vladimir.murzin@xxxxxxx] > > Sent: Wednesday, November 26, 2014 12:19 AM > > To: linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux@xxxxxxxxxxxxxxxx > > Cc: chanho.min@xxxxxxx; will.deacon@xxxxxxx; stable@xxxxxxxxxxxxxxx > > Subject: [PATCH] arm: cacheflush: get rid of restarting block > > > > We cannot restart cacheflush safely if a process provides user-defined > > signal handler and signal is pending. In this case -EINTR is returned > > and it is expected that process re-invokes syscall. However, there are > > a few problems with that: > > * looks like nobody bothers checking return value from cacheflush > > * but if it did, we don't provide the restart address for that, so the > > process has to use the same range again > > * ...and again, what might lead to looping forever > > > > So, remove cacheflush restarting code and terminate cache flushing > > as early as fatal signal is pending. > > > > Cc: stable@xxxxxxxxxxxxxxx # 3.12+ > > Reported-by: Chanho Min <chanho.min@xxxxxxx> > > Signed-off-by: Vladimir Murzin <vladimir.murzin@xxxxxxx> > > Acked-by: Will Deacon <will.deacon@xxxxxxx> > > --- > > Hi, > > > > There is my proposal for the problem reported in [1]. Since that > > thread has not been progressing much, I'm addressing the problem in > > separate patch. > > > > Comments? > Thanks, We hope this to be applied. Ok, good. In which case, can you put it into the patch system please, Vladimir? Will -- 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