linux-kernel - Re: [PATCH 0/5] nfsd: more NFSv4 state containerization

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: <20121127222929.GK27142@fieldses.org>
Date:	Tue, 27 Nov 2012 17:29:29 -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 0/5] nfsd: more NFSv4 state containerization

On Mon, Nov 26, 2012 at 03:21:49PM +0300, Stanislav Kinsbursky wrote:
> This patch set makes NFSv4 state created and destroyed per net and thus
> completes it's containerization (the only exceprtion is client_mutex, but this
> one a hard nut to crack).
> 
> Note: patch set depend on previously sent patch named "nfsd4: remove state
> lock from nfs4_state_shutdown".

Looks OK.--b.

> 
> The following series implements...
> 
> ---
> 
> Stanislav Kinsbursky (5):
>       nfsd: make client_lock per net
>       nfsd: make delegations shutdown network namespace aware
>       nfsd: cleanup NFSd state shutdown a bit
>       nfsd: cleanup NFSd state start a bit
>       nfsd: call state init and shutdown twice
> 
> 
>  fs/nfsd/netns.h     |    3 +
>  fs/nfsd/nfs4state.c |  137 +++++++++++++++++++++++++++++----------------------
>  fs/nfsd/nfsd.h      |    4 +
>  fs/nfsd/nfssvc.c    |   15 +++++-
>  4 files changed, 99 insertions(+), 60 deletions(-)
> 
--
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/