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
| ||
|
Date: Sun, 08 Nov 2009 15:39:21 -0800 From: ebiederm@...ssion.com (Eric W. Biederman) To: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 00/23] Removal of binary sysctl support Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp> writes: > Hello. > > Eric W. Biederman wrote: >> >> This patchset reimplements sys_sysctl as a compatibility wrapper >> around /proc/sys. After which it removes all of the code to all over >> the kernel that is used today to implement the binary sysctls. >> >> I am posting this patchset to give everyone a heads up what is in >> flight. >> >> I intend to carry all of these patches in my sysctl tree. >> >> If you add new sysctls to other trees please don't set the .ctl_name >> or .strategy fields in struct ctl_table, as setting those fields >> is unnecessary now and are removed by this patchset. > > I have two questions. > > Is there (or was there) an entry with ->procname == NULL ? (I thought so > because the loop condition is > > for ( ; table->ctl_name || table->procname; table++) { > > .) > > This patchset removes ->ctl_name on the assumption that ->procname != NULL ? There has been a gradual transition from the assumption that the table ends with !ctl_name to the assumption that procname == NULL. There is no sysctl entry with a valid ctl_name without a valid procname. Eric -- 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/
Powered by blists - more mailing lists