[opensuse] What does this mean?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I just noticed this message in the syslog: <0.4> 2016-07-09 00:00:06 Telcontar kernel - - - [30678.369090] nr_pdflush_threads exported in /proc is scheduled for removal <0.4> 2016-07-09 00:00:06 Telcontar kernel - - - [30678.369250] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux-mm@kvack.org. I suppose that something is using something that is scheduled for removal, but what is using it? (This is 13.1) - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAleALlwACgkQtTMYHG2NR9XgrgCcC886QNXnmyCllgN5f0Gn4QF3 XfkAn0flu1xC3EZVW+8QjcjByqRYE4k7 =dy+y -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
09.07.2016 01:51, Carlos E. R. пишет:
Hi,
I just noticed this message in the syslog:
<0.4> 2016-07-09 00:00:06 Telcontar kernel - - - [30678.369090] nr_pdflush_threads exported in /proc is scheduled for removal <0.4> 2016-07-09 00:00:06 Telcontar kernel - - - [30678.369250] sysctl: The scan_unevictable_pages sysctl/node-interface has been disabled for lack of a legitimate use case. If you have one, please send an email to linux-mm@kvack.org.
I suppose that something is using something that is scheduled for removal, but what is using it?
(This is 13.1)
Something tries to set sysctl values. Obvious thing to check is /etc/sysctl.conf(.d). If these knobs are not explicitly mentioned there, I think using audit could work.
On 2016-07-09 06:37, Andrei Borzenkov wrote:
09.07.2016 01:51, Carlos E. R. пишет:
I suppose that something is using something that is scheduled for removal, but what is using it?
(This is 13.1)
Something tries to set sysctl values. Obvious thing to check is /etc/sysctl.conf(.d). If these knobs are not explicitly mentioned there, I think using audit could work.
I had a look, but I don't know what might cause problems. This is what I have: cer@Telcontar:~> cat /etc/sysctl.conf # Disable response to broadcasts. # You don't want yourself becoming a Smurf amplifier. net.ipv4.icmp_echo_ignore_broadcasts = 1 # enable route verification on all interfaces net.ipv4.conf.all.rp_filter = 1 # disable IPv6 completely # net.ipv6.conf.all.disable_ipv6 = 1 # enable IPv6 forwarding #net.ipv6.conf.all.forwarding = 1 # increase the number of possible inotify(7) watches fs.inotify.max_user_watches = 65536 # avoid deleting secondary IPs on deleting the primary IP net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 ### converted from /etc/sysconfig/sysctl at Sun, 19 Aug 2012 01:25:29 +0200 net.ipv4.tcp_syncookies = 1 net.ipv4.ip_forward = 0 net.ipv4.tcp_ecn = 0 kernel.sysrq = 0 net.ipv6.conf.all.forwarding = 0 cer@Telcontar:~> cat /etc/sysctl.d/99-sysctl.conf # Disable response to broadcasts. # You don't want yourself becoming a Smurf amplifier. net.ipv4.icmp_echo_ignore_broadcasts = 1 # enable route verification on all interfaces net.ipv4.conf.all.rp_filter = 1 # disable IPv6 completely # net.ipv6.conf.all.disable_ipv6 = 1 # enable IPv6 forwarding #net.ipv6.conf.all.forwarding = 1 # increase the number of possible inotify(7) watches fs.inotify.max_user_watches = 65536 # avoid deleting secondary IPs on deleting the primary IP net.ipv4.conf.default.promote_secondaries = 1 net.ipv4.conf.all.promote_secondaries = 1 ### converted from /etc/sysconfig/sysctl at Sun, 19 Aug 2012 01:25:29 +0200 net.ipv4.tcp_syncookies = 1 net.ipv4.ip_forward = 0 net.ipv4.tcp_ecn = 0 kernel.sysrq = 0 net.ipv6.conf.all.forwarding = 0 cer@Telcontar:~> -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
On 07/08/2016 03:51 PM, Carlos E. R. wrote:
I suppose that something is using something that is scheduled for removal, but what is using it?
How many messages do you get? If just one: Its probably spit out as the kernel loads, and you won't see it again. If multiple, It could be just that you (or something) browsed the /proc file system, and each time you hit /proc/sys/vm/nr_pdflush_threads was encountered, it spits the message. Probably, Nobody or nothing may be actually using it, but simply browsing /proc might trigger it. You might have something that tried to write to it, which would be something related to virtual machines. -- After all is said and done, more is said than done.
On 2016-07-09 23:12, John Andersen wrote:
On 07/08/2016 03:51 PM, Carlos E. R. wrote:
I suppose that something is using something that is scheduled for removal, but what is using it?
How many messages do you get?
Dunno, I just saw it.
If just one: Its probably spit out as the kernel loads, and you won't see it again.
If multiple, It could be just that you (or something) browsed the /proc file system, and each time you hit /proc/sys/vm/nr_pdflush_threads was encountered, it spits the message.
Probably, Nobody or nothing may be actually using it, but simply browsing /proc might trigger it.
You might have something that tried to write to it, which would be something related to virtual machines.
Ah. Perhaps vmware player. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)
participants (3)
-
Andrei Borzenkov -
Carlos E. R. -
John Andersen