All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Joshua Brindle <jbrindle@snu.edu>, SELinux <SELinux@tycho.nsa.gov>
Subject: Re: se-samba
Date: Thu, 20 May 2004 21:51:32 +0000	[thread overview]
Message-ID: <20040520215132.GI18182@lkcl.net> (raw)
In-Reply-To: <20040520211032.GG18182@lkcl.net>

On Thu, May 20, 2004 at 09:10:32PM +0000, Luke Kenneth Casson Leighton wrote:

>  by separating the SMB-processing from the file-accessing, you
>  effectively end up with an easy opportunity to emulate
>  multi-threading, and in the process a very very long-standing
>  and obscure bug will be fixed [which can be demonstrated by running
>  a multi-threaded benchmark test suite against a samba server].
> 
> 
>  now, you _might_ be able to get away with writing a VFS plugin,
>  or by subdiving the smbd source code so that the file-access bits
>  of smbd are called (eventually) by the SMB-parsing bits of smbd.
> 
>  in fact, if i was going to do the work, that's where i would start,
>  and once that was done, i would then add in a subdivision layer
>  over, oh, say, unix domain sockets or shared memory communication.
> 
>  the two separate tasks (making all file access go via the VFS layer
>  and then doing a daemon split at the same VFS interface) make very
>  clear and very straightforward milestones.

 it looks like, in samba 3.0.2a, that all file access already goes
 through the VFS layer.

 therefore the only task needed is to network / unix-socket / 
 shmem the file access via the VFS layer.

 and to ensure that each user context is separated out.

 the function vfs_connect will be responsible for initiating
 a new connection of a new user context;

 the function vfs_disconnect will be responsible for closing
 that connection.

 the rest of the work is getting each of those vfs functions,
 of which unfortunately there are about forty or more, over
 a network.

 ironically, i'd actually recommend doing something like use DCE/RPC
 to do that :) :)

 but that doesn't help because freedce requires, thanks to IBM,
 quite a lot of work to do security contexts, and also, being
 threaded, it would require the same reworking as samba, and you're
 back where you started.

 so _some_ sort of RPC system is required, with an IDL compiler,
 to simplify the task of turning the VFS api into a networked
 one.

 l.


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2004-05-20 21:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-20 18:42 se-samba Joshua Brindle
2004-05-20 21:10 ` se-samba Luke Kenneth Casson Leighton
2004-05-20 21:51   ` Luke Kenneth Casson Leighton [this message]
2004-05-29  9:51 ` se-samba Luke Kenneth Casson Leighton
2004-05-29 11:18   ` se-samba Luke Kenneth Casson Leighton
     [not found]   ` <200405312249.11522.rcoker@redhat.com>
     [not found]     ` <16571.47722.750708.219840@samba.org>
     [not found]       ` <20040531232931.GE8312@lkcl.net>
     [not found]         ` <1086081794.3268.39.camel@localhost.localdomain>
2004-06-01 11:09           ` se-samba Luke Kenneth Casson Leighton
     [not found]             ` <1086096477.3268.63.camel@localhost.localdomain>
     [not found]               ` <20040601133547.GU8312@lkcl.net>
     [not found]                 ` <E1BV9Yp-0002wU-00@intern.SerNet.DE>
     [not found]                   ` <16573.1058.707078.949935@samba.org>
2004-06-02 12:00                     ` se-samba Luke Kenneth Casson Leighton
2004-06-02 12:45                     ` se-samba Luke Kenneth Casson Leighton
2004-06-03 21:12                       ` se-samba Luke Kenneth Casson Leighton
2004-06-14 20:00                         ` se-samba Matthew Keller
2004-06-18 18:42                           ` se-samba Luke Kenneth Casson Leighton

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=20040520215132.GI18182@lkcl.net \
    --to=lkcl@lkcl.net \
    --cc=SELinux@tycho.nsa.gov \
    --cc=jbrindle@snu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.