From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753350Ab3C1Tsg (ORCPT ); Thu, 28 Mar 2013 15:48:36 -0400 Received: from mx1.redhat.com ([209.132.183.28]:42666 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752056Ab3C1Tsf (ORCPT ); Thu, 28 Mar 2013 15:48:35 -0400 Date: Thu, 28 Mar 2013 15:47:38 -0400 From: Naoya Horiguchi To: Ben Hutchings Cc: Greg KH , Andrew Morton , Mel Gorman , Hugh Dickins , Rik van Riel , KOSAKI Motohiro , stable@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Konstantin Khlebnikov Message-ID: <1364500058-epefjxd9-mutt-n-horiguchi@ah.jp.nec.com> In-Reply-To: <20130328193901.GQ9079@decadent.org.uk> References: <1364485358-8745-1-git-send-email-n-horiguchi@ah.jp.nec.com> <1364485358-8745-2-git-send-email-n-horiguchi@ah.jp.nec.com> <20130328155109.GA13075@kroah.com> <1364486669-10tbmvlb-mutt-n-horiguchi@ah.jp.nec.com> <20130328193901.GQ9079@decadent.org.uk> Subject: Re: [PATCH 1/2] hugetlbfs: stop setting VM_DONTDUMP in initializing vma(VM_HUGETLB) Mime-Version: 1.0 Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mutt-References: <20130328193901.GQ9079@decadent.org.uk> X-Mutt-Fcc: ~/Maildir/sent/ 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 Thu, Mar 28, 2013 at 07:39:01PM +0000, Ben Hutchings wrote: > On Thu, Mar 28, 2013 at 12:04:29PM -0400, Naoya Horiguchi wrote: > [...] > > I guess you mean this patch violates one/both of these rules: > > > > - It must fix a problem that causes a build error (but not for things > > marked CONFIG_BROKEN), an oops, a hang, data corruption, a real > > security issue, or some "oh, that's not good" issue. In short, something > > critical. > > - It or an equivalent fix must already exist in Linus' tree (upstream). > > > > I'm not sure if the problem "we can't get any hugepage in coredump" > > is considered as 'some "oh, that's not good" issue'. > > But yes, it's not a critical one. > > If you mean I violated the second rule, sorry, I'll get it into upstream first. > > The second rule is the clear one. If you are submitting a patch to > a subsystem maintainer and you want it to go into stable branches as > well, you must put 'Cc: stable@vger.kernel.org' in the commit message, > not just the mail header. Got it. Thank you. Naoya