mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Allison <jra@samba.org>
To: Anton Altaparmakov <aia21@cam.ac.uk>
Cc: "Jim McDonough" <jmcd@samba.org>, "Lars Müller" <lmuelle@suse.de>,
	linux-cifs@vger.kernel.org, samba-technical@lists.samba.org,
	LKML <linux-kernel@vger.kernel.org>,
	"PWF Linux" <pwf-linux@ucs.cam.ac.uk>,
	"Steve French" <sfrench@samba.org>,
	"Jeremy Allison" <jra@samba.org>
Subject: Re: CIFS kernel module bug
Date: Sun, 2 Oct 2011 19:44:02 -0700	[thread overview]
Message-ID: <20111003024402.GB1644@jeremy-desktop> (raw)
In-Reply-To: <65C75335-2A74-4B00-989A-212BAC06A646@cam.ac.uk>

On Sun, Oct 02, 2011 at 09:16:33PM +0100, Anton Altaparmakov wrote:
> 
> That is correct but apparently Salford Software (who handle our Netware & OES site license here in the UK including providing support) have told the guys running the file server that the samba server on OES is not scalable, has loads of bugs, and they must stay away from it at all costs and that they would not provide any support if our filestore runs that instead of the Novell CIFSd.
> 
> You can understand why the filestore is thus running the Novell CIFSd rather than Samba…
> 
> PS. Whether this is FUD or not I cannot comment on.  I am just passing on what I was told!

Wow. And Samba being (partly) a UK-written project too (at least
 from me :-).

I think the Samba Team members from Novell who work full time
on said Samba server in OES might have some follow-ups here,
so I think I'll let them do that.

FYI. Just for fun, try running smbtorture4 against the CIFSd
thing you're running now. I'll be (probably) grimly amused by
the results. A warning - don't do that on a production system :-).

Jeremy.

  reply	other threads:[~2011-10-03  2:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-30 13:58 Anton Altaparmakov
2011-09-30 18:04 ` Jeff Layton
2011-09-30 18:30   ` Steve French
2011-09-30 21:30   ` Anton Altaparmakov
2011-09-30 22:20     ` Steve French
2011-09-30 23:47     ` Jeremy Allison
2011-10-01  0:34       ` J.P. King
2011-10-01  8:48         ` Anton Altaparmakov
2011-10-01 15:07           ` Lars Müller
2011-10-01 19:53             ` Anton Altaparmakov
2011-10-01 20:22               ` Jim McDonough
2011-10-01 23:14                 ` Steve French
2011-10-02 20:16                 ` Anton Altaparmakov
2011-10-03  2:44                   ` Jeremy Allison [this message]
2011-10-03 16:56                   ` Lars Müller
2011-10-03 11:17     ` Jeff Layton

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=20111003024402.GB1644@jeremy-desktop \
    --to=jra@samba.org \
    --cc=aia21@cam.ac.uk \
    --cc=jmcd@samba.org \
    --cc=linux-cifs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lmuelle@suse.de \
    --cc=pwf-linux@ucs.cam.ac.uk \
    --cc=samba-technical@lists.samba.org \
    --cc=sfrench@samba.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

all inboxes | Powered by JetHome®