linux-kernel - Re: removed sysctl system call

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061004211428.GB16812@stusta.de>
Date:	Wed, 4 Oct 2006 23:14:28 +0200
From:	Adrian Bunk <bunk@...sta.de>
To:	Jesper Juhl <jesper.juhl@...il.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: removed sysctl system call - documentation and timeline

On Wed, Oct 04, 2006 at 10:35:01PM +0200, Jesper Juhl wrote:
> Hi,
> 
> With recent kernels I'm getting a lot of warnings about programs using
> the removed sysctl syscal.
> 
> Examples (after 5 min of uptime here) :
> root@...gon:/home/juhl# dmesg | grep "used the removed sysctl system
> call" | sort | uniq
> warning: process `dd' used the removed sysctl system call
> warning: process `ls' used the removed sysctl system call
> warning: process `touch' used the removed sysctl system call
> 
> and more can be found...
> 
> 
> I'm not, as such, opposed to removing sysctl (and yes, I know what it
> is and what it does). What I am a little opposed to is that it is
> being removed on such short notice (unless I missed the memo) and that
> it is hidden inside EMBEDDED.
> 
> I would like to propose that, at least for 2.6.19, it be default on
> (as it is now), not hide it in EMBEDDED where people usually don't go,

This abuse of EMBEDDED is nonsense.

SYSCTL_SYSCALL should be moved above EMBEDDED (for not breaking the 
menu), and the "if EMBEDDED" removed.

> some huge deprecation warnings be added, and that it then gets the
> usual 6-12months before being removed (did it already get that and I'm
> just slow?)...  ohhh, and correct the help text; it currently says

It seems you are slow...

It's entry in Documentation/feature-removal-schedule.txt fulfills the
6 months.

> "...Nothing has been using the binary sysctl interface for some time
> now so nothing should break if you disable sysctl syscall support" -
> that's obviously false as demonstrated by the above extract from my
> dmesg...

What did actually break (a dmesg message is not a breakage)?

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

-
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/