Dave Hansen <[email protected]> writes:
> On Sat, 2006-03-04 at 03:27 -0700, Eric W. Biederman wrote:
>> > I don't see an immediately clear solution on how to containerize sysctls
>> > properly. The entire construct seems to be built around getting data
>> > from in and out of global variables and into /proc files.
>>
>> I successfully handled pid_max. So while it is awkward you can get
>> per task values in and out if sysctl.
>
> This:
>
> http://www.kernel.org/git/gitweb.cgi?p=linux/kernel/git/ebiederm/linux-2.6-ns.git;a=commitdiff;h=1150082e0bae41a3621043b4c5ce15e9112884fa
>
> sir, is a hack :)
I did mention awkward!
> We can't possibly do that for each and every sysctl variable. It would
> mean about fourteen billion duplicated _conv() functions.
>
> I'm wondering if, instead of having the .data field in that table, we
> can have a function pointer which, when called, gives a pointer to the
> data. I'll give it a shot.
Sounds like a step in the right direction. In the context of _conv() functions
it would also be nice if the limit checking between the sys_sysctl path and
the proc path were the same.
We definitely need some infrastructure cleanups if we are going to do much with
sysctl.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
