Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753969Ab3GALnr (ORCPT ); Mon, 1 Jul 2013 07:43:47 -0400 Received: from mail.parknet.co.jp ([210.171.160.6]:49348 "EHLO mail.parknet.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753242Ab3GALnq (ORCPT ); Mon, 1 Jul 2013 07:43:46 -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> <874ncek4q1.fsf@devron.myhome.or.jp> Date: Mon, 01 Jul 2013 20:43:43 +0900 In-Reply-To: (dmitry pervushin's message of "Mon, 1 Jul 2013 12:53:35 +0200") Message-ID: <87wqpaijyo.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: 929 Lines: 24 dmitry pervushin writes: > Honestly, I do not understand why getting volume id might be the > function of the mounted filesystem. I'd rather think about generic > function "filesystem id" of the block device. I see. Yes, I have same question too. > But if we decided to implement getting volume id from the filesystem, > then getting it from the root of the filesystem (but not from any > subdirectory of it and even not from files) makes sense for me. Hm, finding the mount point and open fd (for only this) would be inconvenient, and need some costs. Especially, if user is using the bind mount. 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/