public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Trofimovich <slyfox@gentoo.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	"Dmitry V . Levin" <ldv@altlinux.org>
Subject: Re: [PATCH] ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign
Date: Sun, 21 Feb 2021 13:08:59 +0000	[thread overview]
Message-ID: <20210221130859.089ce1ed@sf> (raw)
In-Reply-To: <66569d56-1af0-a6bb-8b54-9d1cded893cd@physik.fu-berlin.de>

On Sun, 21 Feb 2021 10:21:56 +0100
John Paul Adrian Glaubitz <glaubitz@physik.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

  reply	other threads:[~2021-02-21 13:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21  0:25 [PATCH] ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls Sergei Trofimovich
2021-02-21  0:25 ` [PATCH] ia64: fix ptrace(PTRACE_SYSCALL_INFO_EXIT) sign Sergei Trofimovich
2021-02-21  9:21   ` John Paul Adrian Glaubitz
2021-02-21 13:08     ` Sergei Trofimovich [this message]
2021-03-02 23:39   ` Sergei Trofimovich
2021-03-03 14:30     ` Oleg Nesterov
2021-03-03 21:40       ` Dmitry V. Levin
2021-03-03 21:44   ` Dmitry V. Levin
2021-03-02 23:40 ` [PATCH] ia64: fix ia64_syscall_get_set_arguments() for break-based syscalls Sergei Trofimovich
2021-03-03 21:51 ` Dmitry V. Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210221130859.089ce1ed@sf \
    --to=slyfox@gentoo.org \
    --cc=akpm@linux-foundation.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=ldv@altlinux.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox