linux-kernel - Re: Q: PTRACE

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: <20090609014449.8BE46FC3C6@magilla.sf.frob.com>
Date:	Mon,  8 Jun 2009 18:44:49 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	David Howells <dhowells@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: Q: PTRACE_ATTACH && -EINTR

> It was renamed in -next. Should I send these fixes now for 2.6.20, or we can
								 30
> wait for 2.6.31 ?

IMHO they should go in ASAP since we know this is a regression just
introduced in 2.6.29.  To me, the fact that nobody has noticed yet
makes it more important not to delay--this new problem is so obscure
that whoever is affected by it is likely to waste a lot of time figuring
out what has started happening deep down in a huge pile of userland code.

Thanks,
Roland
--
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/