linux-kernel - Re: [BUG] Odd interaction between uninterruptible syscall and stack overflow

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

Date:	Sun, 15 Mar 2015 15:19:12 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Simonas <s@...lauskas.me>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] Odd interaction between uninterruptible syscall and stack overflow

On Sun, Mar 15, 2015 at 11:12 AM, Simonas <s@...lauskas.me> wrote:
> While working on stack related code in Rust’s stdandard library, I trigerred
> a very odd and amusing issue yesterday.

This sounds like a the subtle backporting issue we had where a subtle
semantic dependency was missed, and as a result 3.18.6 was buggered
for the case of a stack overflow.

Basically, commit 33692f27597f got backported without  commit
7fb08eca45270d, and broke. Normally these dependencies are obvious and
cause the patches to not apply at all, or the result to not work in
obvious ways, but in this case the stable trees were unlucky, and the
patch applied cleanly and everything normal seems to work, but then
stack overflows end up not releasing a semaphore.

It should be fixed in 3.18.7 already, but clearly a few distributions
were unlucky and hit the broken kernel.

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