Re: silent semantic changes with reiser4

From: Hans Reiser (reiser_at_namesys.com)
Date: 08/27/04

  • Next message: Anton Blanchard: "[PATCH] Remove function prototype inside function" 
    Date:	Fri, 27 Aug 2004 01:08:39 -0700
To: Will Dyson <will_dyson@pobox.com>

    Will Dyson wrote:

    >
    >
    > In the original BeOS, they solved the problem by having the filesystem
    > driver itself take a text query string and parse it, returning a list
    > of inodes that match. The whole business of parsing a query string in
    > the kernel (let alone in the filesystem driver) has always seemed ugly
    > to me.

    Why?

    > However, the best alternative I've come up with is to simply export
    > the index data as a special file (perhaps in sysfs?) and have
    > userspace responsible for searching the index.

    That is the best implementation suggestion I've heard for splitting the
    filesystem into two parts, one in user space and one in kernel, but I
    still don't trust it to work well.

    > That would probably work, but it wouldn't help other filesystems that
    > implement even a different index format, much less a different form of
    > extra searchability.
    >
    After reiser6 is implemented, we'll have a better idea of what parts
    need what from what other parts. Until we get there, it needs to be
    kept together. Frankly, I suspect that naming is not going to split so
    easily, but when it is done we'll be able to know. The problems of
    putting too much functionality into the kernel are less than those of
    partitioning the filesystem code, and defining an inflexible API between
    the two parts. Kernel interfaces are fairly inflexible because there
    will always be some moron who sidesteps the fs library to program
    directly to the kernel interface, gets screwed when the interface
    changes, has the nerve to complain about it, and works for some powerful
    distro.

    Hans
    -
    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/

  • Next message: Anton Blanchard: "[PATCH] Remove function prototype inside function"

    Relevant Pages

    • Re: Screw Linux, Im going back to Windows!
      ... >> - The module unloader decides the CD driver is no longer ... >> But we need some kernel support. ... >> physical device from the block device even when it is ... We need it to be changed even during the time the filesystem ...
      (comp.os.linux.security)
    • Re: Dynamically loading binaries in Kernel mode.
      ... all he needs is something that pretends to be a filesystem with 1 constant file in 1 constant directory and can serve it up. ... But remember that not only does it have to be able to do the loading, but if it doesn't properly integrate into the rest of the kernel image handling it could very easily cause problems resulting in impossible to debug bluescreens. ... Anyway, unless the place you're going to load it from is reachable via a standard filesystem and unless you load it using standard export driver mechanisms and interfaces, you're going to end up having to rewrite the entire DLL loader by yourself. ...
      (microsoft.public.development.device.drivers)
    • Re: silent semantic changes with reiser4
      ... they solved the problem by having the filesystem ... >> driver itself take a text query string and parse it, ... String parsing bloats the kernel with code that will be called rarely, ...
      (Linux-Kernel)
    • Re: ext3fs errors with kernel 2.6.18 but not with 2.4.27
      ... My hunch was that the 2.6.x IDE driver is handling ... Perhaps his 2.6.x kernel is using the new 'merged' ... On 2.4.27, I get the CRC errors (not at boot time, later, and all the ... On 2.6.x, at boot time, errors are reported on the initial filesystem ...
      (Debian-User)
    • Re: Dynamically loading binaries in Kernel mode.
      ... Right now only the kernel will load ... Windows 2k/XP/2k3 Filesystem and Driver Consulting ...
      (microsoft.public.development.device.drivers)