linux-kernel - (ptrace) regs->orig_ax == -1 upon (rt

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: <BANLkTi=kTwoVYEM410_Kz6jX4Kr90rGeAQ@mail.gmail.com>
Date:	Thu, 28 Apr 2011 20:01:20 +0200
From:	Robert Święcki <robert@...ecki.net>
To:	linux-kernel@...r.kernel.org
Subject: (ptrace) regs->orig_ax == -1 upon (rt_)sigreturn syscall exit

Hi, while ptrace()'ing a process which performs (rt_)sigreturn the
regs->orig_ax field upon syscall exit is set to -1 in
restore_sigcontext() (both in 32 and 64bit modes) with the following
comment:

regs->orig_ax = -1;     /* disable syscall checks */

As far as I understand this field (regs->orig_ax) should be a copy of
regs->ax from before syscall enter, and basically should display a
syscall number (even upon syscall exit). Therefore I was wondering if
the current behavior isn't too hackish and in order to achieve some
goals it is breaking the intended behavior. I guess I could prepare a
patch which "fixes" this unless there are any strong reasons to leave
it as is.

-- 
Robert Święcki
--
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/