From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve French Subject: Re: CIFS kernel module bug Date: Sat, 1 Oct 2011 18:14:35 -0500 Message-ID: References: <20110930140409.51c1a94c@tlielax.poochiereds.net> <20110930234711.GD14147@samba2> <6704F264-5437-4948-8C1B-FE3F5CE59C24@cam.ac.uk> <20111001150730.GJ5170@giles.fritz.box> <6A5AB13C-F313-4BF2-A402-F41AB53493F0@cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, LKML , PWF Linux , Steve French , Anton Altaparmakov , Jeremy Allison To: Jim McDonough Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: samba-technical-bounces@lists.samba.org Errors-To: samba-technical-bounces@lists.samba.org List-Id: linux-cifs.vger.kernel.org On Sat, Oct 1, 2011 at 3:22 PM, Jim McDonough wrote: > On Sat, Oct 1, 2011 at 3:53 PM, Anton Altaparmakov wrot= e: >> Hi Lars, >> >> On 1 Oct 2011, at 16:07, Lars M=C3=BCller wrote: >>> On Sat, Oct 01, 2011 at 09:48:12AM +0100, Anton Altaparmakov wrote: >>>> >>>> On 1 Oct 2011, at 01:34, J.P. King wrote: >>>>> Anton will be asleep, so I'll attempt to answer this one. >>>>> >>>>>> What server code is the OES CIFS server running ? I thought Novell C= IFS >>>>>> services were all Samba based. >>>>> >>>>> We have been told by the people upstairs who run the server that it i= sn't. >>>> >>>> It is not Samba based. =C2=A0Like Apple, Novell have written their own= since Samba decided to go GPLv3=E2=80=A6 >>> >>> (Potential) FUD alert. ;) >> >> It wasn't deliberate! =C2=A0It was just a guess as until recently I also= though that OES just used Samba so when I two weeks ago found out that it = didn't I just assumed that Novell must have written it recently and then dr= ew the parallel to Apple and just assumed that it was an analogous case=E2= =80=A6 > > I believe both are available on OES, samba and the CIFS server that > has its origins in Netware. > >> >>> This Novell CIFS server existed before Novell bought SUSE. =C2=A0And th= e >>> decission to go with it instead of Samba had nothing to do with the mov= e >>> of Samba from GPL v2 to v3. >> >> I stand corrected. =C2=A0Thanks for the clarification! =C2=A0From your s= ignature I guess you would know a lot better than most. =C2=A0(-: >> >> Best regards, >> >> =C2=A0 =C2=A0 =C2=A0 =C2=A0Anton >> >>> Lars >>> -- >>> Lars M=C3=BCller [=CB=88la=CB=90(r)z =CB=88m=CA=8Fl=C9=90] >>> Samba Team >>> SUSE Linux, Maxfeldstra=C3=9Fe 5, 90409 N=C3=BCrnberg, Germany >> >> -- >> Anton Altaparmakov (replace at with @) >> Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK >> Linux NTFS maintainer, http://www.linux-ntfs.org/ Key point is - we will fix the Linux cifs kernel client to make reasonable workarounds for server bugs for something like this - especially if the server is easy to download and/or test against (and assuming it supports reasonable security - ntlmv2 and/or kerberos) --=20 Thanks, Steve From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753014Ab1JAXOo (ORCPT ); Sat, 1 Oct 2011 19:14:44 -0400 Received: from mail-qy0-f181.google.com ([209.85.216.181]:34790 "EHLO mail-qy0-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752494Ab1JAXOg convert rfc822-to-8bit (ORCPT ); Sat, 1 Oct 2011 19:14:36 -0400 MIME-Version: 1.0 In-Reply-To: References: <20110930140409.51c1a94c@tlielax.poochiereds.net> <20110930234711.GD14147@samba2> <6704F264-5437-4948-8C1B-FE3F5CE59C24@cam.ac.uk> <20111001150730.GJ5170@giles.fritz.box> <6A5AB13C-F313-4BF2-A402-F41AB53493F0@cam.ac.uk> Date: Sat, 1 Oct 2011 18:14:35 -0500 Message-ID: Subject: Re: CIFS kernel module bug From: Steve French To: Jim McDonough Cc: Anton Altaparmakov , =?ISO-8859-1?Q?Lars_M=FCller?= , linux-cifs@vger.kernel.org, samba-technical@lists.samba.org, LKML , PWF Linux , Steve French , Jeremy Allison Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Oct 1, 2011 at 3:22 PM, Jim McDonough wrote: > On Sat, Oct 1, 2011 at 3:53 PM, Anton Altaparmakov wrote: >> Hi Lars, >> >> On 1 Oct 2011, at 16:07, Lars Müller wrote: >>> On Sat, Oct 01, 2011 at 09:48:12AM +0100, Anton Altaparmakov wrote: >>>> >>>> On 1 Oct 2011, at 01:34, J.P. King wrote: >>>>> Anton will be asleep, so I'll attempt to answer this one. >>>>> >>>>>> What server code is the OES CIFS server running ? I thought Novell CIFS >>>>>> services were all Samba based. >>>>> >>>>> We have been told by the people upstairs who run the server that it isn't. >>>> >>>> It is not Samba based.  Like Apple, Novell have written their own since Samba decided to go GPLv3… >>> >>> (Potential) FUD alert. ;) >> >> It wasn't deliberate!  It was just a guess as until recently I also though that OES just used Samba so when I two weeks ago found out that it didn't I just assumed that Novell must have written it recently and then drew the parallel to Apple and just assumed that it was an analogous case… > > I believe both are available on OES, samba and the CIFS server that > has its origins in Netware. > >> >>> This Novell CIFS server existed before Novell bought SUSE.  And the >>> decission to go with it instead of Samba had nothing to do with the move >>> of Samba from GPL v2 to v3. >> >> I stand corrected.  Thanks for the clarification!  From your signature I guess you would know a lot better than most.  (-: >> >> Best regards, >> >>        Anton >> >>> Lars >>> -- >>> Lars Müller [ˈlaː(r)z ˈmʏlɐ] >>> Samba Team >>> SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany >> >> -- >> Anton Altaparmakov (replace at with @) >> Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK >> Linux NTFS maintainer, http://www.linux-ntfs.org/ Key point is - we will fix the Linux cifs kernel client to make reasonable workarounds for server bugs for something like this - especially if the server is easy to download and/or test against (and assuming it supports reasonable security - ntlmv2 and/or kerberos) -- Thanks, Steve