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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 A15CDC43603 for ; Mon, 9 Dec 2019 08:26:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 6D5432071E for ; Mon, 9 Dec 2019 08:26:50 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="JhhP0HRp" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726377AbfLII0u (ORCPT ); Mon, 9 Dec 2019 03:26:50 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:59424 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727044AbfLII0t (ORCPT ); Mon, 9 Dec 2019 03:26:49 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1575880008; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=xuQftgKLhIdfbe43m9PaVlygiTsJJ2gGUjVhGbD1VTM=; b=JhhP0HRpLHb/+ubPnNwToEoILbSOQ+xFAH3VHp0BZzz8f+Mup4pWRFDTFRczBreZ96g33y OirWuUwBZoDDWtjRB3bOQ+cQ1Yj5x9roZTQBUz3eYm7PFy+cltdObbsA+Rh4S1kLw5VOy8 RPEfFPdLwkS4kEUHpLCGGgRNmphmnZM= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-20-LYEmGze7OVu4X7zepRIt7g-1; Mon, 09 Dec 2019 03:26:41 -0500 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id A580C801E7A; Mon, 9 Dec 2019 08:26:39 +0000 (UTC) Received: from colo-mx.corp.redhat.com (colo-mx01.intmail.prod.int.phx2.redhat.com [10.5.11.20]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 69C1C60BE1; Mon, 9 Dec 2019 08:26:39 +0000 (UTC) Received: from zmail17.collab.prod.int.phx2.redhat.com (zmail17.collab.prod.int.phx2.redhat.com [10.5.83.19]) by colo-mx.corp.redhat.com (Postfix) with ESMTP id BC9DA18089C8; Mon, 9 Dec 2019 08:26:38 +0000 (UTC) Date: Mon, 9 Dec 2019 03:26:38 -0500 (EST) From: Jan Stancek To: dftxbs3e Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, Eric Sandeen , darrick wong , linuxppc-dev@lists.ozlabs.org, Memory Management , LTP Mailing List , CKI Project , Michael Ellerman Message-ID: <35957501.15762152.1575879998305.JavaMail.zimbra@redhat.com> In-Reply-To: References: <9c0af967-4916-4e8b-e77f-087515793d77@free.fr> Subject: Re: [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later MIME-Version: 1.0 X-Originating-IP: [10.43.17.163, 10.4.195.30] Thread-Topic: userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later Thread-Index: Dxe2axPz7lr/TlY+65kmscNpeXn5Kw== X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 X-MC-Unique: LYEmGze7OVu4X7zepRIt7g-1 X-Mimecast-Spam-Score: 0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Sender: linux-xfs-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-xfs@vger.kernel.org ----- Original Message ----- > > > On 12/6/19 6:09 PM, dftxbs3e wrote: > > Hello! > > > > I am very happy that someone has found this issue. > > > > I have been suffering from rather random SIGBUS errors in similar > > conditions described by the author. > > > > I don't have much troubleshooting information to provide, however, I hit > > the issue regularly so I could investigate during that. > > > > How do you debug such an issue? I tried a debugger etc. but besides > > crashing with SIGBUS, I couldnt get any other meaningful information. If it's same issue, you could check if dropping caches helps. Figure out what page is it with crash or systemtap and look at page->flags and ((struct iomap_page *)page->private)->uptodate bitmap. > > You may want to test the patch Christoph sent on the original thread for > this issue. Or v5.5-rc1, Christoph's patch has been merged: 1cea335d1db1 ("iomap: fix sub-page uptodate handling")