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
| ||
|
Message-Id: <200712101705.30428.maximlevitsky@gmail.com> Date: Mon, 10 Dec 2007 17:05:30 +0200 From: Maxim Levitsky <maximlevitsky@...il.com> To: "J. Bruce Fields" <bfields@...ldses.org> Cc: Neil Brown <neilb@...e.de>, "Rafael J. Wysocki" <rjw@...k.pl>, Andrew Morton <akpm@...ux-foundation.org>, Trond Myklebust <trond.myklebust@....uio.no>, gnome42@...il.com, linux-kernel@...r.kernel.org, "Eric W. Biederman" <ebiederm@...ssion.com>, "Denis V. Lunev" <den@...nvz.org>, linux-nfs@...r.kernel.org Subject: Re: 2.6.24-rc3-git4 NFS crossmnt regression On Monday 10 December 2007 16:36:09 J. Bruce Fields wrote: > On Mon, Dec 10, 2007 at 04:19:12PM +0200, Maxim Levitsky wrote: > > ... > > > It is best not to use nohide - we should probably mark it as > > > 'legacy'. > > > > > > Simply export the top level mountpoint as 'crossmnt' and everything > > > below there will be exported. > > > > > > > Where should I put those options in root file-system export or in submount export? > > > > > > crossmnt goes at the top. nohide goes in the submount. Both have > > > the same general effect though with subtle differences. > > > You don't need both (though that doesn't hurt). > > > Just use crossmnt at the top, Then you don't need to mention the > > > lower level filesystems at all. > > > > > > > > > ... > > > > (I decided to switch to NFS4 only due to the lack of ability to see underlying mounts) > > > > > > > > > > All of this should work fine with v3. Once you have the right patch > > > for the crossmnt bug applied, if you have further problems post them > > > to linux-nfs@...r.kernel.org. > > > > > > NeilBrown > > > > > > > Big thanks, > > > > Still NFS server just don't want to accept the connection > > I noticed that if I first mount with > > -tnfs, unmount, and then mount with -tnfs4, it works > > OK, in that case, that's definitely the bug Eric sent out the patch for; > you may want to try applying his patch. You mean "[PATCH 2.6.24-rc4] proc: Remove/Fix proc generic d_revalidate" ? I did apply it (on both kernel and server), and it doesn't help. Best regards, Maxim Levitsky PS: I am unfamiliar with nfs/nfs4, so this could be just a configuration/compilation issue. > > --b. > -- 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/
Powered by blists - more mailing lists