From: Will Dyson <will_dyson@pobox.com>
To: "Burnes, James" <james.burnes@gwl.com>
Cc: Hans Reiser <reiser@namesys.com>, Andrew Morton <akpm@osdl.org>,
hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, flx@namesys.com, torvalds@osdl.org,
reiserfs-list@namesys.com
Subject: Re: reiser4 semantics / BeFS Architect(s) Query Resolution
Date: Mon, 30 Aug 2004 22:23:05 -0400 [thread overview]
Message-ID: <4133E109.5040301@pobox.com> (raw)
In-Reply-To: <3DF9165145FACB4C96977FF650C1E9040C46A3D1@its-mail1.its.corp.gwl.com>
Burnes, James wrote:
> (comments below)
>
>
>>-----Original Message-----
>>From: Hans Reiser [mailto:reiser@namesys.com]
>>Sent: Saturday, August 28, 2004 3:55 AM
>>To: Will Dyson
>>Cc: Andrew Morton; hch@lst.de; linux-fsdevel@vger.kernel.org; linux-
>>kernel@vger.kernel.org; flx@namesys.com; torvalds@osdl.org; reiserfs-
>>list@namesys.com
>>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)
Solved what, exactly? I'm already having a hard time understanding what
Hans is talking about.
> 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.
--
Will Dyson
"Back off man, I'm a scientist!" -Dr. Peter Venkman
prev parent reply other threads:[~2004-08-31 2:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 14:32 reiser4 semantics / BeFS Architect(s) Query Resolution Burnes, James
2004-08-31 2:23 ` Will Dyson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4133E109.5040301@pobox.com \
--to=will_dyson@pobox.com \
--cc=akpm@osdl.org \
--cc=flx@namesys.com \
--cc=hch@lst.de \
--cc=james.burnes@gwl.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox