linux-kernel - Re: [PATCH 1/2] x86_64 ia32 ptrace vs -ENOSYS

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: <20080319233601.958B426F995@magilla.localdomain>
Date:	Wed, 19 Mar 2008 16:36:01 -0700 (PDT)
From:	Roland McGrath <roland@...hat.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	mingo@...e.hu, tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] x86_64 ia32 ptrace vs -ENOSYS

> It is unclear (to me) what are the consequences of this problem?  What
> are the user-visible effects of the fix?

I don't know off hand of something that cares.  (I have a test case, but
it's just contrived for the purpose.)  Something like UML could use this to
approximate PTRACE_SYSEMU when it's not there.  But we would have heard
before now if UML cared about this particular behavior on x86_64.

> IOW: is it a 2.6.25 thing and if so, why?

No hurry.  It's been broken forever (regression vs native 32-bit).
(OTOH, the fixes are quite safe.)

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/