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: <20070501090657.GA17949@infradead.org>
Date:	Tue, 1 May 2007 10:06:57 +0100
From:	Christoph Hellwig <hch@...radead.org>
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

On Mon, Apr 30, 2007 at 05:52:43PM -0500, Steve French wrote:
> Any idea which would be preferred (smb2 support as part of cifs, or as
> a distinct smb2.ko module)?

Separate module please.  If we grow enough common code as some point
we can move it into a smb_common.ko helper library, but given your
above description I doubt that would useful.

-
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/