linux-kernel - Re: ipc-msg broken again on 3.11-rc7?

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:	Tue, 3 Sep 2013 09:16:41 +0000
From:	Vineet Gupta <Vineet.Gupta1@...opsys.com>
To:	Manfred Spraul <manfred@...orfullife.com>
CC:	Vineet Gupta <Vineet.Gupta1@...opsys.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Davidlohr Bueso <dave.bueso@...il.com>,
	Sedat Dilek <sedat.dilek@...il.com>,
	Davidlohr Bueso <davidlohr.bueso@...com>,
	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-mm <linux-mm@...ck.org>, Andi Kleen <andi@...stfloor.org>,
	Rik van Riel <riel@...hat.com>,
	"Jonathan Gonzalez" <jgonzalez@...ets.cl>
Subject: Re: ipc-msg broken again on 3.11-rc7?

On 09/03/2013 02:27 PM, Manfred Spraul wrote:
> On 09/03/2013 10:44 AM, Vineet Gupta wrote:
>>> b) Could you check that it is not just a performance regression?
>>>       Does ./msgctl08 1000 16 hang, too?
>> Nope that doesn't hang. The minimal configuration that hangs reliably is msgctl
>> 50000 2
>>
>> With this config there are 3 processes.
>> ...
>>    555   554 root     S     1208  0.4   0  0.0 ./msgctl08 50000 2
>>    554   551 root     S     1208  0.4   0  0.0 ./msgctl08 50000 2
>>    551   496 root     S     1208  0.4   0  0.0 ./msgctl08 50000 2
>> ...
>>
>> [ARCLinux]$ cat /proc/551/stack
>> [<80aec3c6>] do_wait+0xa02/0xc94
>> [<80aecad2>] SyS_wait4+0x52/0xa4
>> [<80ae24fc>] ret_from_system_call+0x0/0x4
>>
>> [ARCLinux]$ cat /proc/555/stack
>> [<80c2950e>] SyS_msgrcv+0x252/0x420
>> [<80ae24fc>] ret_from_system_call+0x0/0x4
>>
>> [ARCLinux]$ cat /proc/554/stack
>> [<80c28c82>] do_msgsnd+0x116/0x35c
>> [<80ae24fc>] ret_from_system_call+0x0/0x4
>>
>> Is this a case of lost wakeup or some such. I'm running with some more diagnostics
>> and will report soon ...
> What is the output of ipcs -q? Is the queue full or empty when it hangs?
> I.e. do we forget to wake up a receiver or forget to wake up a sender?
/ # ipcs -q

------ Message Queues --------
key        msqid      owner      perms      used-bytes   messages   
0x72d83160 163841     root       600        0            0      


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