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] [day] [month] [year] [list]
Message-ID: <20121128160847.GJ11651@fieldses.org>
Date:	Wed, 28 Nov 2012 11:08:47 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Stanislav Kinsbursky <skinsbursky@...allels.com>
Cc:	linux-nfs@...r.kernel.org, Trond.Myklebust@...app.com,
	linux-kernel@...r.kernel.org, devel@...nvz.org
Subject: Re: [PATCH 1/2] nfsd: make NFSv4 lease time per net

On Wed, Nov 28, 2012 at 07:35:20PM +0400, Stanislav Kinsbursky wrote:
> 28.11.2012 19:15, J. Bruce Fields пишет:
> >On Wed, Nov 28, 2012 at 07:12:03PM +0400, Stanislav Kinsbursky wrote:
> >>28.11.2012 19:09, J. Bruce Fields пишет:
> >>>On Tue, Nov 27, 2012 at 02:11:44PM +0300, Stanislav Kinsbursky wrote:
> >>>>diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> >>>>index dab350d..4930981 100644
> >>>>--- a/fs/nfsd/nfsctl.c
> >>>>+++ b/fs/nfsd/nfsctl.c
> >>>>@@ -912,7 +912,8 @@ static ssize_t nfsd4_write_time(struct file *file, char *buf, size_t size, time_
> >>>>   */
> >>>>  static ssize_t write_leasetime(struct file *file, char *buf, size_t size)
> >>>>  {
> >>>>-	return nfsd4_write_time(file, buf, size, &nfsd4_lease);
> >>>>+	struct nfsd_net *nn = net_generic(&init_net, nfsd_net_id);
> >>>>+	return nfsd4_write_time(file, buf, size, &nn->nfsd4_lease);
> >>>
> >>>This is called in the context of whatever process writes to
> >>>nfsv4leasetime, so should be using its network namespace, right?
> >>>
> >>
> >>This is, actually, a interim solution to preserve existent logic.
> >>I.e. I'm going to convert "nfsd" filesystem into per-net one (like rpc_pipefs). I, actually, already done it in my tree.
> >>Thus proper network namespace will be taken from nfsd superblock.
> >
> >OK, remind me how that works?  It's mounted just once, but each network
> >namespace gets a different view of the filesystem?
> >
> 
> Nope. It's a single mount point, but per-namespace (network, in our case) - not globally.
> Pointer to namespace will be placed on sb->s_fs_info.

OK, anyway, applying these.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ