From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755456AbcAYHZ3 (ORCPT ); Mon, 25 Jan 2016 02:25:29 -0500 Received: from LGEAMRELO11.lge.com ([156.147.23.51]:55606 "EHLO lgeamrelo11.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751458AbcAYHZY (ORCPT ); Mon, 25 Jan 2016 02:25:24 -0500 X-Original-SENDERIP: 156.147.1.126 X-Original-MAILFROM: byungchul.park@lge.com X-Original-SENDERIP: 10.177.222.33 X-Original-MAILFROM: byungchul.park@lge.com Date: Mon, 25 Jan 2016 16:25:03 +0900 From: Byungchul Park To: Peter Zijlstra Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [STABLE] kernel oops which can be fixed by peterz's patches Message-ID: <20160125072503.GB17836@X58A-UD3R> References: <20160105085211.GB3621@X58A-UD3R> <20160105091444.GZ6357@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160105091444.GZ6357@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jan 05, 2016 at 10:14:44AM +0100, Peter Zijlstra wrote: > So the reason I didn't mark them for stable is that they were non > trivial, however they've been in for a while now and nothing broke, so I > suppose backporting them isn't a problem. Hello, What do you think about the way to solve this oops problem? Could you just give your opinion of the way? Or ack or nack about this backporting?