linux-kernel - Re: [PATCH] ia64: fix ptrace(PTRACE_SYSCALL_INFO

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: <20210221130859.089ce1ed@sf>
Date:   Sun, 21 Feb 2021 13:08:59 +0000
From:   Sergei Trofimovich <slyfox@...too.org>
To:     John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        linux-kernel@...r.kernel.org, linux-ia64@...r.kernel.org,
        "Dmitry V . Levin" <ldv@...linux.org>
Subject: Re: [PATCH] ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign

On Sun, 21 Feb 2021 10:21:56 +0100
John Paul Adrian Glaubitz <glaubitz@...sik.fu-berlin.de> wrote:

> Hi Sergei!
> 
> On 2/21/21 1:25 AM, Sergei Trofimovich wrote:
> > In https://bugs.gentoo.org/769614 Dmitry noticed that
> > `ptrace(PTRACE_GET_SYSCALL_INFO)` does not return error sign properly.
> > (...)  
> 
> Do these two patches unbreak gdb on ia64?

gdb was somewhat working on ia64 for Gentoo. strace was the main
impacted here.

But I did not try anything complicated recently. Anything specific that
breaks for you?

$ uname -r
5.10.0
(even without the patches above)

$ cat c.c
int main(){}
$ gcc c.c -o a -ggdb3
$ gdb --quiet ./a
Reading symbols from ./a...
(gdb) start
Temporary breakpoint 1 at 0x7f2: file c.c, line 1.
Starting program: /home/slyfox/a
Failed to read a valid object file image from memory.

Temporary breakpoint 1, main () at c.c:1
1	int main(){}
(gdb) disassemble
Dump of assembler code for function main:
   0x20000008000007f0 <+0>:	[MII]       mov r2=r12
   0x20000008000007f1 <+1>:	            mov r14=r0;;
=> 0x20000008000007f2 <+2>:	            mov r8=r14
   0x2000000800000800 <+16>:	[MIB]       mov r12=r2
   0x2000000800000801 <+17>:	            nop.i 0x0
   0x2000000800000802 <+18>:	            br.ret.sptk.many b0;;
End of assembler dump.
(gdb) break *0x2000000800000800
Breakpoint 2 at 0x2000000800000800: file c.c, line 1.
(gdb) continue
Continuing.

Breakpoint 2, 0x2000000800000800 in main () at c.c:1
1	int main(){}

Looks ok for minor stuff.

> And have you, by any chance, managed to get the hpsa driver working again?

v5.10 seems to boot off hpsa just fine without extra patches:
  14:01.0 RAID bus controller: Hewlett-Packard Company Smart Array P600
	Subsystem: Hewlett-Packard Company 3 Gb/s SAS RAID
	Kernel driver in use: hpsa

v5.11 does not boot yet. Kernel does not see some files while boots after init is
started  (but I'm not sure it's a block device problem). Bisecting now why.

-- 

  Sergei