From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932681Ab0EKGUv (ORCPT ); Tue, 11 May 2010 02:20:51 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:36017 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751187Ab0EKGUt (ORCPT ); Tue, 11 May 2010 02:20:49 -0400 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 From: KOSAKI Motohiro To: Greg KH Subject: Re: [stable] cpumask: fix compat getaffinity Cc: kosaki.motohiro@jp.fujitsu.com, Rusty Russell , Arnd Bergmann , linux-kernel@vger.kernel.org, Ken Werner , Andi Kleen , stable@kernel.org In-Reply-To: <20100511031354.GA9327@kroah.com> References: <20100511104334.E572.A69D9226@jp.fujitsu.com> <20100511031354.GA9327@kroah.com> Message-Id: <20100511151526.E578.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.50.07 [ja] Date: Tue, 11 May 2010 15:20:45 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Tue, May 11, 2010 at 10:47:03AM +0900, KOSAKI Motohiro wrote: > > > How's this? > > > > > > cpumask: use nr_cpu_ids for printing and parsing cpumasks > > > > > > Commit a45185d2d "cpumask: convert kernel/compat.c" broke > > > libnuma, which abuses sched_getaffinity to find out NR_CPUS > > > in order to parse /sys/devices/system/node/node*/cpumap. > > > > > > However, the result now returned reflects nr_cpu_ids, and > > > cpumask_scnprintf et al. use nr_cpumask_bits which is NR_CPUS (for > > > CONFIG_CPUMASK_OFFSTACK=n) or nr_cpu_ids (for > > > CONFIG_CPUMASK_OFFSTACK=y). > > > > > > We should use nr_cpu_ids consistently. > > > > > > Reported-by: Arnd Bergmann > > > Signed-off-by: Rusty Russell > > > Cc: stable@kernel.org > > > > Well, This patch seems to have ABI change. please don't send abi-change to -stable. > > Why? There is no such thing as a "stable" internal abi in the kernel, > and that includes the -stable kernel releases. > > If it fixes a bug, that's all the requirement is. AFAIK, -stable is mainly used for distro and they have many and many packages. we can't assume no app read /sys files directly. IOW, To change /sys printing format is a bit risky change. frequently compatibility breaking natually break code stability. > > note: I'm not against this patch itself. > > Great, then it should be just fine, right? Yup, fine. Thanks.