From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756309AbaCZVQp (ORCPT ); Wed, 26 Mar 2014 17:16:45 -0400 Received: from cantor2.suse.de ([195.135.220.15]:53008 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754569AbaCZVQn (ORCPT ); Wed, 26 Mar 2014 17:16:43 -0400 Date: Wed, 26 Mar 2014 14:16:38 -0700 From: Michal Hocko To: Jiri Slaby Cc: Josh Boyer , Greg KH , "Linux-Kernel@Vger. Kernel. Org" , "stable@vger.kernel.org" , Kernel Fedora Subject: Re: Feb. Fedora Kernel Patch Report Message-ID: <20140326211637.GB20108@dhcp22.suse.cz> References: <20140325212417.GA6545@kroah.com> <5332E977.8010102@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5332E977.8010102@suse.cz> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed 26-03-14 15:51:35, Jiri Slaby wrote: > On 03/26/2014 02:44 PM, Josh Boyer wrote: > > On Tue, Mar 25, 2014 at 5:24 PM, Greg KH wrote: > >> On Fri, Feb 28, 2014 at 10:13:29AM -0500, Josh Boyer wrote: > >>> cgroup-fixes.patch (rhbz 1045755) > >>> - Upstream commits 0ab02ca8f887908152d1a96db5130fc661d36a1e > >>> - There was a 3.12 version of this patch sent to stable list from > >>> Michal Hocko. I don't remember why it wasn't applied, or why it > >>> wasn't applied for 3.13.y... > >> > >> It didn't apply to 3.13, and I think I was waiting for a backported > >> version, do you have one? > > > > As far as I know we're using this version: > > > > http://thread.gmane.org/gmane.linux.kernel.cgroups/10336/focus=1646465 > > > > The commentary on the thread seems to imply that Michal was going to > > send it again for some reason. Michal, did you send the 3.12/3.13 > > backport for this commit directly to stable? > > In the meantime, I applied to the stable 3.12 Michal's version from suse > enterprise 12. I believe that it is the same as in the link above. > Please confirm. Do not remember why it didn't end up in the stable back then but yes the fix you have queued up seems to be the right one. Thanks -- Michal Hocko SUSE Labs