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: <20080319151758.29e02848.akpm@linux-foundation.org>
Date:	Wed, 19 Mar 2008 15:17:58 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Roland McGrath <roland@...hat.com>
Cc:	mingo@...e.hu, tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] x86_64 ia32 ptrace vs -ENOSYS

On Sun, 16 Mar 2008 21:57:41 -0700 (PDT)
Roland McGrath <roland@...hat.com> wrote:

> When we're stopped at syscall entry tracing, ptrace can change the %eax
> value from -ENOSYS to something else.  If no system call is actually made
> because the syscall number (now in orig_eax) is bad, then the %eax value
> set by ptrace should be returned to the user.  But, instead it gets reset
> to -ENOSYS again.  This is a regression from the native 32-bit kernel.
> 
> This change fixes it by leaving the return value alone after entry tracing.

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

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

Thanks.
--
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/