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  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:	Thu, 09 Aug 2007 20:35:55 -0600
From: (Eric W. Biederman)
To:	YOSHIFUJI Hideaki / ƣ 
Subject: Re: [PATCH 04/10] sysctl: Fix neighbour table sysctls.

YOSHIFUJI Hideaki / ƣ <> writes:

> In article <> (at Thu, 09 Aug 2007
> 20:23:16 -0600), (Eric W. Biederman) says:
>> YOSHIFUJI Hideaki / ƣ <> writes:
>> > Would you explain why it does not work properly
>> > for those cases?
>> Mostly no appropriate strategy routine was setup to 
>> report the data to the caller of sys_sysctl.
> I assume that default strategy have been existing for it, no?!
> Maybe, I do miss something...

I'd have to go through it case by case.  But in general
unless your proc_handler is proc_dointvec the default
strategy routine which does a raw binary copy of your data
out will generally do the wrong thing.

So especially if your data is jiffies or otherwise needs
processing you don't want to use the default strategy

Until relatively recently no one was really policing the
sysctl interfaces and even now it isn't too serious.

To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists