From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:45468 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751154AbeAYPMU (ORCPT ); Thu, 25 Jan 2018 10:12:20 -0500 Date: Thu, 25 Jan 2018 16:12:19 +0100 From: Greg Kroah-Hartman To: Jiri Slaby Cc: Thomas Gleixner , linux-kernel@vger.kernel.org, stable@vger.kernel.org, Li Jinyue , peterz@infradead.org, dvhart@infradead.org, "torvalds@linux-foundation.org" Subject: Re: [PATCH 4.14 17/89] futex: Prevent overflow by strengthen input validation Message-ID: <20180125151219.GA16752@kroah.com> References: <20180122083954.683903493@linuxfoundation.org> <20180122083956.427607580@linuxfoundation.org> <20567b49-e0a3-e9e0-d520-74bbfc20d414@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Thu, Jan 25, 2018 at 03:47:32PM +0100, Jiri Slaby wrote: > On 01/25/2018, 03:30 PM, Thomas Gleixner wrote: > > So what's the problem? > > The problem I see is that every stable kernel now requires updated > strace with their commit from yesterday to build correctly. In > particular, the new stable kernels cause rpm build failures of strace in > all our distros (based on those stable kernels). Sure, we can patch > strace in every distro every nth kernel update, but it's mere > impractical. Kernel should not break userspace, right? Well, when userspace is doing something stupid... :) > BTW why was the patch applied to stable? We actually do pass > -fno-strict-overflow. The same reason it was applied upstream, it fixes a reported issue. Does that mean that all UBSAN overflow error reports are not valid because of how we build the kernel? thanks, greg k-h