Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753414Ab3GAJaF (ORCPT ); Mon, 1 Jul 2013 05:30:05 -0400 Received: from mail.parknet.co.jp ([210.171.160.6]:49309 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753037Ab3GAJaD (ORCPT ); Mon, 1 Jul 2013 05:30:03 -0400 From: OGAWA Hirofumi To: dmitry pervushin Cc: Bintian Wang , linux-kernel@vger.kernel.org, Mike Lockwood , Colin Cross , Android Kernel Team , Andrew Morton , John Stultz Subject: Re: [PATCH RFC] Add FAT_IOCTL_GET_VOLUME_ID References: <1372646398-4204-1-git-send-email-bintian.wang@linaro.org> <87wqpakdvd.fsf@devron.myhome.or.jp> <87sizykdjg.fsf@devron.myhome.or.jp> Date: Mon, 01 Jul 2013 18:29:58 +0900 In-Reply-To: (dmitry pervushin's message of "Mon, 1 Jul 2013 10:49:28 +0200") Message-ID: <874ncek4q1.fsf@devron.myhome.or.jp> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 864 Lines: 25 dmitry pervushin writes: > Hello Bintian, > > The original idea discussed with John was to allow > FAT_IOCTL_GET_VOLUME_ID (broken or not) only on directory nodes, and > even on the root directory node. That's why it is should be *not* in > fat_generic_ioctl. The question would be, why do we have to limit only on directory? When I'm reviewing this, I recalled fstatvfs(2) as referenced one. The both get the info of fs. fstatvfs(2) doesn't limit only on directory. But, in the FAT_IOCTL_GET_VOLUME_ID case, it limits. I wonder why? Thanks. -- OGAWA Hirofumi -- 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/