reiser4 semantics / BeFS Architect(s) Query Resolution

[Burnes, James]

(comments below)

> -----Original Message-----
> From: Hans Reiser [mailto:reiser@xxxxxxxxxxx]
> Sent: Saturday, August 28, 2004 3:55 AM
> To: Will Dyson
> Cc: Andrew Morton; hch@xxxxxx; linux-fsdevel@xxxxxxxxxxxxxxx; linux-
> kernel@xxxxxxxxxxxxxxx; flx@xxxxxxxxxxx; torvalds@xxxxxxxx; reiserfs-
> list@xxxxxxxxxxx
> Subject: Re: silent semantic changes with reiser4
> 
> I think there are two ways to analyze the code boundary issue.  One is
> "does it belong in the kernel?"  Another is, "does it belong in the
> filesystem. and if so should name resolution in a filesystem be split
> into two parts, one in kernel, and one in user space."  In ten years I
> might have the knowledge needed to make such a split, but I know for
> sure that I don't know how to do it today without regretting it
> tomorrow, and I don't really have confidence that I will ever be able
to
> do it without losing performance.
> 
> Glad that BeFS finds the new model better.:)
>

(glad that BeFS supposedly solved it)

> 
> > Hans Reiser wrote:
> >
> >> 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?
> >

Here is an interesting interview of Dominic Giampaolo and Benoit
Schillings regarding the structure of BeFS.  Some interesting issues
regarding how queries were done.

http://www.theregister.co.uk/2002/03/29/windows_on_a_database_sliced/

BTW: I get paid during the day to do security engineering work.
Wouldn't parsing the query in the kernel make the kernel susceptible to
buffer overflows?  Bad place to have an overflow.

j.burnes

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/