linux-kernel - Re: stat of /proc fails after CPU hot-unplug with EOVERFLOW in 2.6.18

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: <451A8E38.60300@cdi.cz>
Date:	Wed, 27 Sep 2006 16:44:08 +0200
From:	Martin Devera <devik@....cz>
To:	Andrew Morton <akpm@...l.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: stat of /proc fails after CPU hot-unplug with EOVERFLOW in 2.6.18

Andrew Morton wrote:
> On Wed, 27 Sep 2006 09:55:47 +0200
> Martin Devera <devik@....cz> wrote:
> 
>> Hello,
>>
>> I have 2way Opteron machine. I've done this:
>> echo 0 > /sys/devices/system/cpu/cpu1/online
>>
>> and then strace stat /proc:
>>
>> [snip]
>> personality(PER_LINUX)                  = 4194304
>> getpid()                                = 14926
>> brk(0)                                  = 0x804b000
>> brk(0x804b1a0)                          = 0x804b1a0
>> brk(0x804c000)                          = 0x804c000
>> stat("/proc", 0xbf8e7490)               = -1 EOVERFLOW
>>
>> When I do echo 1 > ... to start cpu again then the stat starts
>> to work again ... Weird.
>>
> 
> boggle.
> 
> Can you add this patch, see where it's going bad?

Ehh .. I finally learned how to code jprobe (I can't reboot the machine now),
tested, installed and ... guess what ? The overflow bug is gone :-(
It simply works now.
I will reboot it next week and try again.

thanks for a help and sorry for your wasted time,
Martin
-
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/