Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758814Ab1FGWGH (ORCPT ); Tue, 7 Jun 2011 18:06:07 -0400 Received: from mail.lang.hm ([64.81.33.126]:50620 "EHLO bifrost.lang.hm" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757778Ab1FGWGG (ORCPT ); Tue, 7 Jun 2011 18:06:06 -0400 Date: Tue, 7 Jun 2011 15:05:56 -0700 (PDT) From: david@lang.hm X-X-Sender: dlang@asgard.lang.hm To: Stefan Priebe - Profihost AG cc: Theodore Tso , linux-kernel@vger.kernel.org Subject: Re: XFS problem in 2.6.32 In-Reply-To: <4DEE9EDA.90001@profihost.ag> Message-ID: References: <4DEE1D96.6020208@profihost.ag> <6D8DA3D2-D90B-4D82-BDC9-C3F0264A68BF@mit.edu> <4DEE2C70.8060301@profihost.ag> <4DEE9EDA.90001@profihost.ag> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1476 Lines: 30 On Tue, 7 Jun 2011, Stefan Priebe - Profihost AG wrote: >> whoever the maintainer of the -stable/-longterm tree is (be it an >> individual or a team employeed by some comapny) then looks at the patch >> and considers backporting it (if it's too hard, or to intrusive, they >> may decide not to). > So i have to contact Greg Kohan from SUSE directly? if he's the maintainer of the longterm tree, then yes, you would contact him or the stable mailing list. >> the idea of the lonterm kernels is that organizations need to maintain a >> kernel for a long time due to commitments that they have made (Debian >> doesn't want to change the kernel it ships in a stable version, RedHat >> doesn't want to change the kernel version in a RHEL release, etc), and >> so they publicly announce this so that anyone else wanting to use the >> same kernel version can share in the work (and therefor everyone can >> benifit from each other's work) > That was what i thoght. So a bug like this should get fixed right? Otherwise > this makes no sense. Sadly Redhat has ported the fix back in his RHEL 6 > 2.6.32 kernel but they haven't send the patch to stable / vanilla team. it depends on how intrusive/disruptive the patch is. David Lang -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/