From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Steve French" Subject: Re: projected date for mount.cifs to support DFS junction points Date: Thu, 10 Jan 2008 14:28:40 -0600 Message-ID: <524f69650801101228o3639363cp4c9710d747b71ead@mail.gmail.com> References: <1199988975.7483.3.camel@gn2.draper.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: sfrench@us.ibm.com, linux-fsdevel To: linux-cifs-client@lists.samba.org Return-path: Received: from py-out-1112.google.com ([64.233.166.177]:12854 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754108AbYAJU2n (ORCPT ); Thu, 10 Jan 2008 15:28:43 -0500 Received: by py-out-1112.google.com with SMTP id u52so1216141pyb.10 for ; Thu, 10 Jan 2008 12:28:41 -0800 (PST) In-Reply-To: <1199988975.7483.3.camel@gn2.draper.com> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > to CIFS not supporting DFS junction points. Any projected date for that > to be supported? I anticipate that it will make Linux kernel 2.6.25 (marked experimental) and eventually in a cifs version 1.53 backported for older kernels. Most of the support required for CIFS DFS for the Linux client has been written, reviewed and merged already. The servers (Samba, NetApp, Windows etc.) have supported DFS for years. This week I am reviewing four reasonably small patches to the Linux cifs client from Igor Mammedov (also on the linux-cifs-client mailing list) that provide the remaining pieces on the client side. Igor has done some excellent work here. The two questions being discussed are: 1) the size of the mount data retained for each implicit submount which occurs when we cross a DFS junction 2) the structure used to pass the dfs referral info around -- Thanks, Steve