linux-kernel - Re: handle_futex_death() infinite loop on ARM (fwd)

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>] [day] [month] [year] [list]

Message-Id: <200707302354.l6UNs222023051@harpo.it.uu.se>
Date:	Tue, 31 Jul 2007 01:54:02 +0200 (MEST)
From:	Mikael Pettersson <mikpe@...uu.se>
To:	buytenh@...tstofly.org, mingo@...hat.com, tglx@...utronix.de
Cc:	linux-kernel@...r.kernel.org
Subject: Re: handle_futex_death() infinite loop on ARM (fwd)

On Wed, 4 Jul 2007 12:23:18 +0200, Lennert Buytenhek wrote:
>If you're also running into glibc's tst-robust1 test suite test
>locking up your ARM machine, you're probably running into the fact
>that asm-arm/futex.h includes asm-generic/futex.h, and
>asm-generic/futex.h defines futex_atomic_cmpxchg_inatomic() to
>return -ENOSYS.  This causes handle_futex_death() to loop forever.

Has there been any progress on fixing this yet?

I've studied the relevant futex code (handle_futex_death()
and asm-${arch}/futex.h), and it seems that many archs
are seriously broken now, not just arm. Any arch that wires
up the set_robust_list() syscall while implementing its
asm-${arch}/futex.h by including asm-generic/futex.h allows
its kernels to be hung by unprivileged user-space code.

My concern is arm, but it seems alpha, avr32, h8300, m68k,
m68knommu, and sh64 are also affected by this bug.

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