linux-kernel - Re: Merge window closed: v2.6.19-rc1

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]

Date:	Fri, 06 Oct 2006 13:05:14 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Linus Torvalds <torvalds@...l.org>
Cc:	caszonyi@...link.ro,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Merge window closed: v2.6.19-rc1

Linus Torvalds <torvalds@...l.org> writes:

> On Fri, 6 Oct 2006, caszonyi@...link.ro wrote:
>> 
>> In dmesg:
>> warning: process `sleep' used the removed sysctl system call
>> warning: process `alsactl' used the removed sysctl system call
>> warning: process `nscd' used the removed sysctl system call
>> warning: process `tail' used the removed sysctl system call
>
> You need to compile with CONFIG_SYSCLT set to 'y' rather than 'n'.
>
> Alternatively, you can probably fix it by just upgrading user-land, but 
> the SYSCLT thing _does_ still exist, it's just deprecated and defaults to 
> off by default..
>
> (Or you can possibly even choose to just ignore the warnings, they 
> probably won't affect any actual behaviour)

I'm tempted to submit a patch that just kills the warning.

The only known user is lipthreads from glibc performing.
if ! uname -v | grep "SMP" ; then
	....
fi

That code if it gets -ENOSYS reads /proc/sys/kernel/version,
and it has worked this way since the day it was written.

I have been looking for other uses of sys_sysctl but I haven't
found any.  Why glibc doesn't call uname like any normal
program when it wants to uname information is beyond me.

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/