linux-kernel - Re: 2.6.24-rc5-mm1: problems with cat /proc/kpageflags

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: <200712161141.50012.m.kozlowski@tuxland.pl>
Date:	Sun, 16 Dec 2007 11:41:49 +0100
From:	Mariusz Kozlowski <m.kozlowski@...land.pl>
To:	Andrew Morton <akpm@...ux-foundation.org>,
	Matt Mackall <mpm@...enic.com>
Cc:	linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
	davem@...emloft.net
Subject: Re: 2.6.24-rc5-mm1: problems with cat /proc/kpageflags

Hello

> Will reply soon with correct data.

Ok here it goes:

        cat /proc/kpageflags on sparc64 causes the box to lock.
I can not write on any terminal - but I can issue sysrqs and switch
between consoles.

cat process hangs in read(3, ...

sysrq-w shows:

syslogd       D 000000000069240c     0  2470      1
Call Trace:
 [0000000000692224] __down+0x8c/0x100
 [000000000069240c] __down_interruptible+0x174/0x1a0 
 [00000000006935d4] mutex_trylock+0xfc/0x1e0 
 [0000000000695c7c] lock_kernel+0x24/0x40 
 [00000000005b0cc0] tty_write+0x168/0x200 
 [00000000004d0b08] do_loop_readv_writev+0x30/0x60
 [0000000000507540] compat_do_readv_writev+0x268/0x280
 [00000000005075b0] compat_sys_writev+0x58/0x80
 [00000000004062d4] linux_sparc_syscall32+0x3c/0x40
 [00000000f7e3f408] 0xf7e3f410

then when I try to ssh to the sparc machine I fail but at sparc you
can see this:

BUG: soft lockup - CPU#0 stuck for 11s! [sshd:3227]
TSTATE: 0000009911009607 TPC: 0000000000430c2c TNPC:0000000000430c30 Y: 00000000    Not tainted
TCP: <__delay+0x34/0x60>
g0: 0000000000000000 g1: 00000042875103e3 g2: 0000000000430800 g3: 000000000001869c
g4: fffff800bf086100 g5: fffff8007f832000 g6: fffff800be4a0000 g7: 0000000000000004
o0: 00000042875103e3 o1: 0000000000000000 o2: 0000000000430c78 o3: 0000000000000000
o4: 7fffffffffffffff o5: ffffffffffffffff sp: fffff800be4a2e81 ret_pc: 0000000000430c24
RPC: <__delay+0x2c/0x60>
l0: 00000042875100df l1: 00000000007a4000 l2: 0000000000000000 l3: 00000000007d9000
l4: 0000000000000000 l5: 0000000000000001 l6: 0000000000000000 l7: 0000000000000000
i0: 0000000000000382 i1: fffff800be4a0400 i2: 0000000000445d3c i3: 0000000000000000
i4: 0000000000000002 i5: 000000000045388c i6: fffff800be4a2f41 i7: 0000000000430c6c
I7: <udelay+0x14/0x20>

When this happens box seems to react only to sysrq-b or manual reset.
Anything else is useless.

Regards,

	Mariusz

View attachment ".config" of type "text/plain" (25723 bytes)