linux-kernel - Re: [PATCH RFC] Add FAT_IOCTL_GET_VOLUME

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <87wqpaijyo.fsf@devron.myhome.or.jp>
Date:	Mon, 01 Jul 2013 20:43:43 +0900
From:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To:	dmitry pervushin <dpervushin@...il.com>
Cc:	Bintian Wang <bintian.wang@...aro.org>,
	linux-kernel@...r.kernel.org, Mike Lockwood <lockwood@...roid.com>,
	Colin Cross <ccross@...roid.com>,
	Android Kernel Team <kernel-team@...roid.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH RFC] Add FAT_IOCTL_GET_VOLUME_ID

dmitry pervushin <dpervushin@...il.com> 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 <hirofumi@...l.parknet.co.jp>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/