linux-kernel - Re: SMB2 file system - should it be a distinct module

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <463678A2.7060000@nortel.com>
Date:	Mon, 30 Apr 2007 17:15:46 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Steve French <smfrench@...il.com>
CC:	linux-kernel@...r.kernel.org, linux-cifs-client@...ts.samba.org
Subject: Re: SMB2 file system - should it be a distinct module

Steve French wrote:

> ...we need to decide whether the kernel
> implementation of SMB2 client should be a distinct module or just part
> of the cifs.ko module.

<snip>

> My guess is that less than 1/3 of the cifs module would overlap - but
> that overlap is enough that it would be easier to do smb2 as part of
> cifs (although it would make the cifs module somewhat larger).

What about pulling out the common code into a helper module, which can 
then be used by both cifs and smb2?

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/