public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: simo <idra@samba.org>
To: Jeremy Allison <jra@samba.org>
Cc: Gerald Carter <coffeedude.jerry@gmail.com>,
	Christoph Hellwig <hch@infradead.org>,
	Steve French <smfrench@gmail.com>,
	linux-cifs-client@lists.samba.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-cifs-client] Re: SMB2 file system - should it be a	distinct module
Date: Fri, 04 May 2007 17:43:13 +0000	[thread overview]
Message-ID: <1178300593.28758.85.camel@localhost.localdomain> (raw)
In-Reply-To: <20070504171200.GE31976@samba1>

On Fri, 2007-05-04 at 10:12 -0700, Jeremy Allison wrote:

> Actually I disagree. I think Christoph is correct. These
> are two independent protocols and should be in two different
> modules.

They are independent the same way NFS v4 is independent from NFS v3 and
v2. Independent but related, and most importantly, one is the fallback
of the other.

> > But NTLM 0.12 still works for Vista and DFS referrals.
> > Breaking out SMB2 initially means that it will not clutter
> > the working cifs.ko code.  Remember that an SMB2 client fs is
> > mostly research at this point, and not engineering.
> 
> Long term the common functions should be factored out
> and put into a lower-level module that both cifs and
> SMB2 are dependent upon.
> 
> That's the cleaner solution IMHO.

If the result is that the fallback work without user space intervention,
then I agree with you.
I was just pointing out that the 2 protocols are not in fact completely
independent and this fact need to be properly considered and factored in
into this decision, nothing more, nothing less.

Simo.

-- 
Simo Sorce
Samba Team GPL Compliance Officer
email: idra@samba.org
http://samba.org


  reply	other threads:[~2007-05-04 17:43 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 22:52 SMB2 file system - should it be a distinct module Steve French
2007-04-30 23:15 ` Chris Friesen
2007-05-01  9:06 ` Christoph Hellwig
2007-05-03 13:21   ` [linux-cifs-client] " simo
2007-05-03 14:17     ` Christoph Hellwig
2007-05-03 14:36       ` simo
2007-05-03 14:43         ` Christoph Hellwig
2007-05-03 14:53           ` simo
2007-05-03 15:14           ` Chuck Ebbert
2007-05-03 14:46         ` Gerald Carter
2007-05-03 14:56           ` simo
2007-05-03 15:35             ` Steve French
2007-05-03 15:44               ` Christoph Hellwig
2007-05-04 17:12           ` Jeremy Allison
2007-05-04 17:43             ` simo [this message]
2007-05-05  9:55               ` Christoph Hellwig
2007-05-04 18:35             ` Steve French
2007-05-01  9:30 ` Jan Engelhardt
2007-05-01 19:26   ` [linux-cifs-client] Re: SMB2 file system - should it be a distinctmodule Wagner, Chris (GEAE, CBTS)

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=1178300593.28758.85.camel@localhost.localdomain \
    --to=idra@samba.org \
    --cc=coffeedude.jerry@gmail.com \
    --cc=hch@infradead.org \
    --cc=jra@samba.org \
    --cc=linux-cifs-client@lists.samba.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smfrench@gmail.com \
    /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