From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 03/17] VFS: Implement handling for pathless pioctls Date: Wed, 17 Jun 2009 19:26:37 +0100 Message-ID: <28511.1245263197@redhat.com> References: <20090617074711.GZ13073@webber.adilger.int> <20090616203845.4526.60013.stgit@warthog.procyon.org.uk> <20090616203901.4526.200.stgit@warthog.procyon.org.uk> Cc: dhowells@redhat.com, torvalds@osdl.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-afs@lists.infradead.org, linux-fsdevel@vger.kernel.org, Wang Lei To: Andreas Dilger Return-path: Received: from mx2.redhat.com ([66.187.237.31]:49795 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752895AbZFQS0t (ORCPT ); Wed, 17 Jun 2009 14:26:49 -0400 In-Reply-To: <20090617074711.GZ13073@webber.adilger.int> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Andreas Dilger wrote: > Wouldn't it make a lot more sense to create a virtual device, open the > mountpoint, or do _something_ that associates these calls with AFS > directly instead of having the kernel magically route the call to a > specific filesystem? Ummm... You mean like mkdir, rmdir, symlink, readlink, mknod, creat, open, unlink, etc. aren't magically routed by the kernel to a specific filesystem based on the pathname? The exception to that is pathless pioctls which are most annoying and require special handling and foreknowledge whatever. David