From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268902AbUHZM3i (ORCPT ); Thu, 26 Aug 2004 08:29:38 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268915AbUHZM3L (ORCPT ); Thu, 26 Aug 2004 08:29:11 -0400 Received: from mail-relay-3.tiscali.it ([213.205.33.43]:26841 "EHLO mail-relay-3.tiscali.it") by vger.kernel.org with ESMTP id S268902AbUHZMSS (ORCPT ); Thu, 26 Aug 2004 08:18:18 -0400 Date: Thu, 26 Aug 2004 14:16:30 +0200 From: Andrea Arcangeli To: Christophe Saout Cc: Hans Reiser , viro@parcelfarce.linux.theplanet.co.uk, Linus Torvalds , Christoph Hellwig , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org, Alexander Lyamin aka FLX , ReiserFS List Subject: Re: silent semantic changes with reiser4 Message-ID: <20040826121630.GN5618@nocona.random> References: <20040824202521.GA26705@lst.de> <412CEE38.1080707@namesys.com> <20040825200859.GA16345@lst.de> <20040825204240.GI21964@parcelfarce.linux.theplanet.co.uk> <1093467601.9749.14.camel@leto.cs.pocnet.net> <20040825225933.GD5618@nocona.random> <412DA0B5.3030301@namesys.com> <20040826112818.GL5618@nocona.random> <1093520699.9004.11.camel@leto.cs.pocnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1093520699.9004.11.camel@leto.cs.pocnet.net> X-GPG-Key: 1024D/68B9CB43 13D9 8355 295F 4823 7C49 C012 DFA1 686E 68B9 CB43 X-PGP-Key: 1024R/CB4660B9 CC A0 71 81 F4 A0 63 AC C0 4B 81 1D 8C 15 C8 E5 User-Agent: Mutt/1.5.6i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 26, 2004 at 01:44:59PM +0200, Christophe Saout wrote: > I think you're not exactly understanding what a reiser4 "plugin" is. > > Currently plugins are not modules. It just means that there's a defined > interface between the reiser4 core and the plugins. Just like you could > see filesystems as "VFS plugins". but filesystems are exactly always modules (in precompiled kernels at least). Anyways I don't see any visible EXPORT_SYMBOL in reiser4. > > In fact, reiser4 plugins are > - users of the reiser4 core API > - some of them are implementing Linux VFS methods (thus being some sort > of glue code between the Reiser4 storage tree and the Linux VFS) then it seems a bit misleading to call those things plugins. As you wrote those are "users of the reiser4 core API", with plugins I always meant dynamically loadable things, like plugins for web browers (hence kernel modules in kernel space). While here apparently you can't plugin anything at runtime, it's just code that uses the reiser4 core API that can be modified with a kernel patch as usual.