From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 00/17] [RFC] AFS: Implement OpenAFS pioctls(version)s Date: Tue, 16 Jun 2009 23:59:52 +0100 Message-ID: <10437.1245193192@redhat.com> References: <20090616203845.4526.60013.stgit@warthog.procyon.org.uk> Cc: dhowells@redhat.com, torvalds@osdl.org, akpm@linux-foundation.org, linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, linux-afs@lists.infradead.org To: unlisted-recipients:; (no To-header on input) Return-path: Received: from mx2.redhat.com ([66.187.237.31]:35485 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752412AbZFPXAF (ORCPT ); Tue, 16 Jun 2009 19:00:05 -0400 In-Reply-To: <20090616203845.4526.60013.stgit@warthog.procyon.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: David Howells wrote: > This series of patches provides a pioctl() system call, and makes kAFS use it > to provide a number of of the OpenAFS pioctl functions sufficient to allow a > number of OpenAFS userspace utilities work with kAFS. The point of this is to permit unmodified OpenAFS userspace utilities to use either the OpenAFS kernel module or the kAFS kernel module. Whilst I might wish to ultimately replace the OpenAFS userspace utilities with my own set, that's no small piece of work, and so a handy halfway stage is a mixed environment as outlined above. Furthermore, the ability to use the OpenAFS userspace utilities unmodified with my kernel module, and, indeed vice-versa, makes testing much easier. David