From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE9EBC07E96 for ; Tue, 6 Jul 2021 11:57:21 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3C49E620D5 for ; Tue, 6 Jul 2021 11:57:21 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3C49E620D5 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4GK1JH6p96z3blF for ; Tue, 6 Jul 2021 21:57:19 +1000 (AEST) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20161025 header.b=j9lcl5IO; dkim-atps=neutral Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=gmail.com (client-ip=2607:f8b0:4864:20::72f; helo=mail-qk1-x72f.google.com; envelope-from=radu.rendec@gmail.com; receiver=) Authentication-Results: lists.ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20161025 header.b=j9lcl5IO; dkim-atps=neutral Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4GK1Hc4Gwxz308V for ; Tue, 6 Jul 2021 21:56:43 +1000 (AEST) Received: by mail-qk1-x72f.google.com with SMTP id q190so19819484qkd.2 for ; Tue, 06 Jul 2021 04:56:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=yfpqCL72E4Ht1c8gFySvUZD3b/GK//s6Y+xpAXTl1u8=; b=j9lcl5IO5LEqX61SGy0w/QtICwEHlGB2KE+RBVNrIsJgV2fViAyR421Lgpbn12dsq1 yT60Jy6WvBzmilsM7S/wHiokAAn5V/rSRIkRHVScV0r96uSAx2+FAORNJgTmMayhalGc D4W8b7A0K58j/j+BSP51O5CGpRVvho50HpajU10yskYrZ717BcTPd4MX8qDWNxqWBvmF 1yAQ1TDH2l/dDvWv2FTsQhtGRNxYXBvSfII6kqBxSkNt6Ycyda6GO2yD+V8NhliM2a51 D9XVc/bEPrMiM1rfZjh6rFk5NDr/Q8bHKsRwHQL+l9AjJXWVPsfgmxQBhss1PMbjFupY AKDQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=yfpqCL72E4Ht1c8gFySvUZD3b/GK//s6Y+xpAXTl1u8=; b=EUPwHO9eT1WGkaW/G1LSUEaFYllNfCyfePcNpKMGeleKnkaJQRBfPIJn+pnkDZldKZ 3PLLOaumZcDnVHWg6eX7+nx5phcPMjG+G15IoPKM+DpUPpbvMrMMJele7+G+GohevU+j fyGQ5qUhg8HS8ZxYkAJ46mRrrIVbl3qQsmEs04toDbaYF8CwRvtIkIVYYJ3/GDxEj7G7 yeJzp50oMRD+a4vrpL3vrpxU3teebKiu0wlKv8r4hgi2m5BF9RndHmrAxpxzrvFIci1K W3xr6eL4FKUnF8IvBlprUiWStjiNe8CEULC06wYV/gAgarA3Z/g4muAOt4pdHZ8x9uGa 0tfw== X-Gm-Message-State: AOAM533o76MinHvV3+XSltHOqLNkSjwrp5lw2/JxmrlXsA1v2hs2qOG3 b42UF11EqY92yvyQXhn0PZg= X-Google-Smtp-Source: ABdhPJyjWyYMEPoc0WzDFaS/9ikth33M9VhD7SwYUqnWaKiimWkMDkP1a9P8z9S1YLBRuCIVMH3F8A== X-Received: by 2002:a37:8f44:: with SMTP id r65mr3764010qkd.20.1625572598818; Tue, 06 Jul 2021 04:56:38 -0700 (PDT) Received: from bat.mindbit.ro (cpe00fc8d79db03-cm00fc8d79db00.cpe.net.fido.ca. [72.137.118.157]) by smtp.gmail.com with ESMTPSA id e6sm6721562qkg.12.2021.07.06.04.56.37 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 06 Jul 2021 04:56:37 -0700 (PDT) Message-ID: <786399a77d82890a391172fee269272e12c52489.camel@gmail.com> Subject: Re: Hitting BUG_ON in do_notify_resume() with gdb and SIGTRAP From: Radu Rendec To: Christophe Leroy , linuxppc-dev@lists.ozlabs.org Date: Tue, 06 Jul 2021 07:56:36 -0400 In-Reply-To: References: <6b5327e32549860c1e6c73e5b669528bfb383df2.camel@gmail.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Tue, 2021-07-06 at 12:43 +0200, Christophe Leroy wrote: > Le 04/07/2021 à 23:38, Radu Rendec a écrit : > > I'm trying to set up my (virtual) environment to test an old bug in the > > PPC32 ptrace() code. I came across a completely different problem, > > which seems to make gdb pretty much unusable on PPC32. I'm not sure if > > this is a real kernel bug or maybe something wrong with my > > configuration. > > > > I'm running kernel 5.13 in a qemu VM with one e500mc CPU. I am running > > native gdb (inside the VM) and setting a breakpoint in main() in a test > > "hello world" program. Upon running the test program, I am hitting the > > BUG_ON in do_notify_resume() on line 292. The kernel bug log snippet is > > included below at the end of the email. > > > > FWIW, gdb says: > > Program terminated with signal SIGTRAP, Trace/breakpoint trap. > > The program no longer exists. > > > > I also added a pr_info() to do_notify_resume() just to see how much > > different 'regs' and 'current->thread.regs' are. Surprisingly, they are > > just 0x30 apart: regs=c7955f10 cur=c7955f40. Also, 'current' seems to > > be OK (pid and comm are consistent with the test program). > > The TRAP = 0x7d8 is obviously wrong. > > Need to know which 'TRAP' it is exactly. > Could you try to dump what we have at the correct regs ? > Something like 'show_regs(current->thread.regs)' should do it. Sure, please see the output below. It looks to me like the "correct" regs are just garbage. Either they are overwritten or current->thread.regs is wrong. But in any case, r1 = 0 doesn't look good. regs=c7a0ff10 cur=c7a0ff40 pid=139 comm=test CPU: 0 PID: 139 Comm: test Not tainted 5.13.0-dirty #4 NIP: 10000338 LR: 00030000 CTR: 00000003 REGS: c7a0ff40 TRAP: 670000 Not tainted (5.13.0-dirty) MSR: 1002d202 CR: 10000004 XER: 80670100 GPR00: b7fc36d8 00000000 00000000 b7fe17b4 00000000 b7ffd588 b7ffe8b8 b7ffee10 GPR08: b7fff214 b7ffdf40 b7fff208 bffff858 bffff970 b7fff130 00000001 bffff960 GPR16: b7fff2b0 b7ffd5f0 b7ffe8a8 bffff850 b7fc3714 1002d002 b7fff208 00000003 GPR24: b7fc3714 00000000 22000284 bffff960 000007d8 10000338 08000000 bffff850 NIP [10000338] 0x10000338 LR [00030000] 0x30000 Call Trace: [c7a0fe40] [c0008eac] show_regs+0x4c/0x1b0 (unreliable) [c7a0fe80] [c000969c] do_notify_resume+0x31c/0x320 [c7a0fee0] [c0010b94] interrupt_exit_user_prepare+0x94/0xc0 [c7a0ff00] [c00151e8] interrupt_return+0x14/0x13c --- interrupt: 7d8 at 0xb7fc3714 NIP: b7fc3714 LR: b7fc3714 CTR: 00000003 REGS: c7a0ff10 TRAP: 07d8 Not tainted (5.13.0-dirty) MSR: 1002d002 CR: 22000284 XER: 00000000 GPR00: b7fc3584 bffff850 00000000 00000000 00000000 00000000 000000a0 6474e552 GPR08: b7fbe0d4 00000001 b7fff230 bffff850 b7fc36d8 00000000 00000000 b7fe17b4 GPR16: 00000000 b7ffd588 b7ffe8b8 b7ffee10 b7fff214 b7ffdf40 b7fff208 bffff858 GPR24: bffff970 b7fff130 00000001 bffff960 b7fff2b0 b7ffd5f0 b7ffe8a8 bffff850 NIP [b7fc3714] 0xb7fc3714 LR [b7fc3714] 0xb7fc3714 --- interrupt: 7d8 ------------[ cut here ]------------ kernel BUG at arch/powerpc/kernel/signal.c:298! Oops: Exception in kernel mode, sig: 5 [#1] BE PAGE_SIZE=4K SMP NR_CPUS=24 QEMU e500 Modules linked in: CPU: 0 PID: 139 Comm: test Not tainted 5.13.0-dirty #4 NIP: c000969c LR: c000969c CTR: c065f540 REGS: c7a0fdc0 TRAP: 0700 Not tainted (5.13.0-dirty) MSR: 00028002 CR: 28000282 XER: 20000000 GPR00: c000969c c7a0fe80 c70ef500 c70efbd8 c70ef500 00000010 c7a0fc38 00000002 GPR08: 00000001 00000000 00000000 00000000 28000282 00000000 00000000 b7fe17b4 GPR16: 00000000 b7ffd588 b7ffe8b8 b7ffee10 b7fff214 b7ffdf40 b7fff208 bffff858 GPR24: bffff970 b7fff130 00000001 bffff960 c7a0ff10 00000800 c70ef500 00000102 NIP [c000969c] do_notify_resume+0x31c/0x320 LR [c000969c] do_notify_resume+0x31c/0x320 Call Trace: [c7a0fe80] [c000969c] do_notify_resume+0x31c/0x320 (unreliable) [c7a0fee0] [c0010b94] interrupt_exit_user_prepare+0x94/0xc0 [c7a0ff00] [c00151e8] interrupt_return+0x14/0x13c --- interrupt: 7d8 at 0xb7fc3714 NIP: b7fc3714 LR: b7fc3714 CTR: 00000003 REGS: c7a0ff10 TRAP: 07d8 Not tainted (5.13.0-dirty) MSR: 1002d002 CR: 22000284 XER: 00000000 GPR00: b7fc3584 bffff850 00000000 00000000 00000000 00000000 000000a0 6474e552 GPR08: b7fbe0d4 00000001 b7fff230 bffff850 b7fc36d8 00000000 00000000 b7fe17b4 GPR16: 00000000 b7ffd588 b7ffe8b8 b7ffee10 b7fff214 b7ffdf40 b7fff208 bffff858 GPR24: bffff970 b7fff130 00000001 bffff960 b7fff2b0 b7ffd5f0 b7ffe8a8 bffff850 NIP [b7fc3714] 0xb7fc3714 LR [b7fc3714] 0xb7fc3714 --- interrupt: 7d8 Instruction dump: 93a10054 90010064 93c10058 48b95369 80c20398 3c60c0dc 7f84e378 38e204b0 3863ce30 4809d819 80620704 4bfff7c9 <0fe00000> 3d20c0ff 8129c014 2c090000 ---[ end trace 1cbf27cd19ae39a0 ]--- > > If I'm not missing something, the 'regs' pointer that is eventually > > passed to do_notify_resume() is calculated in interrupt_return() by > > adding STACK_FRAME_OVERHEAD (defined to 112) to the value of r1. That > > means all registers are saved on the stack before entering the > > interrupt handler and, upon returning, a pointer to the register > > structure is calculated from the stack pointer. Either the offset > > itself is wrong, or the stack pointer is off by 0x30. > > > > This is as far as I have gone. Hopefully this rings a bell to someone > > who is familiar with that part of the code and has a better > > understanding of PPC32 interrupt handling in general. > > > > Last but not least, my configuration is fairly standard. I'm using the > > powerpc-e500mc--glibc--bleeding-edge-2020.08-1 toolchain from Bootlin > > to compile everything (kernel and user-space). The qemu version is > > 5.2.0 (Fedora 34) and the user-space is a small Busybox based rootfs > > that I built using Buildroot 2021.05. The gdb version is 9.2.