linux-kernel - Re: [PATCH 0/7] nfsd: cleanup "init

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]

Date:	Mon, 10 Dec 2012 07:34:13 -0500
From:	"J. Bruce Fields" <bfields@...ldses.org>
To:	Stanislav Kinsbursky <skinsbursky@...allels.com>
Cc:	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org,
	devel@...nvz.org
Subject: Re: [PATCH 0/7] nfsd: cleanup "init_net" references

On Mon, Dec 10, 2012 at 12:18:59PM +0300, Stanislav Kinsbursky wrote:
> Hard-coded "init_net" pointer is widely used in NFSd code.
> This patch replaces "init_net" references by passed struct net pointer where
> requied.
> In future, proper network namespace context will be taken from NFSd file
> system superblock private data or, where it's impossible, from current.

Thanks, applying.--b.

> 
> The following series implements...
> 
> ---
> 
> Stanislav Kinsbursky (7):
>       nfsd: use "init_net" for portmapper
>       nfsd: pass net to nfsd_init_socks()
>       nfsd: pass net to nfsd_startup() and nfsd_shutdown()
>       nfsd: pass net to nfsd_create_serv()
>       nfsd: pass net to nfsd_svc()
>       nfsd: pass net to nfsd_set_nrthreads()
>       nfsd: pass net to __write_ports() and down
> 
> 
>  fs/nfsd/nfsctl.c |   27 +++++++++++++++------------
>  fs/nfsd/nfsd.h   |    6 +++---
>  fs/nfsd/nfssvc.c |   35 ++++++++++++++---------------------
>  3 files changed, 32 insertions(+), 36 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/