OpenVZ Forum: Devel » [PATCH 00/11] SUNRPC: make sysctl per network namespcase context

Home » Mailing lists » Devel » [PATCH 00/11] SUNRPC: make sysctl per network namespcase context

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Re: [PATCH 01/11] SYSCTL: export root and set handling routines [message #44882 is a reply to message #44862]

Tue, 10 January 2012 22:38

ebiederm
Messages: 1354
Registered: February 2006

Senior Member

Stanislav Kinsbursky <skinsbursky@parallels.com> writes:

> 03.01.2012 07:49, Eric W. Biederman пишет:
>> Stanislav Kinsbursky<skinsbursky@parallels.com> writes:
>>
>>> 19.12.2011 20:37, Eric W. Biederman пишет:
>>>> Stanislav Kinsbursky<skinsbursky@parallels.com> writes:
>>>>
>>>> Doing that independently of the rest of the sysctls is pretty horrible
>>>> and confusing to users. What I am planning might suit your needs and
>>>> if not we need to talk some more about how to get the vfs to do
>>>> something reasonable.
>>>>
>>>
>>> Ok, Eric. Would be glad to discuss your sysctls plans.
>>> But actually you already know my needs: I would like to make sysctls work in the
>>> way like sysfs does: i.e. content of files depends on mount maker -
>>> not viewer.
>>
>> What drives the desire to have sysctls depend on the mount maker?
>
> Because we can (will, actually) have nested fs root's for containers. IOW,
> container's root will be accessible from it's creator context. And I want to
> tune container's fs from creators context.

Tuning the child context from the parent context is an entirely
reasonable thing to do. To affect a namespace that is not yours
the requirement is simply that we don't use current to lookup the
sysctl. So what I am proposing should work for your case.

>> Especially what drives that desire not to have it have a /proc/<pid>/sys
>> directory that reflects the sysctls for a given process.
>>
>
> This is not so important for me, where to access sysctl's. But I'm worrying
> about backward compatibility. IOW, I'm afraid of changing path
> "/proc/sys/sunprc/*" to "/proc/<pid>/sys/sunrpc". This would break a lot of
> user-space programs.

The part that keeps it all working is by adding a symlink from /proc/sys
to /proc/self/sys. That technique has worked well for /proc/net, and I
don't expect there will be any problems with /proc/sys either. It is
possible but is very rare for the introduction of a symlink in a path
to cause problems.

Eric

Report message to a moderator

[Message index]

		[PATCH 00/11] SUNRPC: make sysctl per network namespcase context By: Stanislav Kinsbursky on Wed, 14 December 2011 10:45
		[PATCH 11/11] SUNRPC: sysctl table for rpc_debug introduced By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Sat, 17 December 2011 22:25
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Mon, 19 December 2011 08:56
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Mon, 19 December 2011 10:14
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Mon, 19 December 2011 12:22
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Mon, 19 December 2011 16:37
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Mon, 19 December 2011 17:24
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Tue, 03 January 2012 03:48
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Tue, 10 January 2012 10:38
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Tue, 10 January 2012 22:38
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Wed, 11 January 2012 09:47
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Wed, 11 January 2012 17:20
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Wed, 11 January 2012 18:02
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: ebiederm on Wed, 11 January 2012 19:34
		Re: [PATCH 01/11] SYSCTL: export root and set handling routines By: Stanislav Kinsbursky on Thu, 12 January 2012 09:17
		[PATCH 02/11] SUNRPC: use syctl path instead of dummy parent table By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 03/11] SUNRPC: sysctl root for debug table introduced By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 05/11] SUNRPC: register debug sysctl table per network namespace By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 04/11] SUNRPC: per-net sysctl's set introduced By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 06/11] SUNRPC: register xs_tunables sysctl table per network namespace By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 07/11] SUNRPC: xs tunables per network namespace introduced By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 09/11] SUNRPC: remove xs_tcp_fin_timeout variable By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 10/11] SUNRPC: allow debug flags modifications only from init_net By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		[PATCH 08/11] SUNRPC: use per-net xs tunables instead of static ones By: Stanislav Kinsbursky on Wed, 14 December 2011 10:47
		Re: [PATCH 00/11] SUNRPC: make sysctl per network namespcase context By: Stanislav Kinsbursky on Tue, 07 February 2012 11:44
		Re: [PATCH 00/11] SUNRPC: make sysctl per network namespcase context By: Myklebust, Trond on Tue, 07 February 2012 13:21

Previous Topic:	[PATCH 1/5] make steal time's to-tick routine generic
Next Topic:	[PATCH 4/4] NFS: make nfs_client_lock per net ns

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Tue Apr 07 23:15:34 GMT 2026

Total time taken to generate the page: 0.43281 seconds