From: Jan Stancek <jstancek@redhat.com>
To: dftxbs3e <dftxbs3e@free.fr>
Cc: hch@infradead.org, darrick wong <darrick.wong@oracle.com>,
Memory Management <mm-qe@redhat.com>,
Eric Sandeen <sandeen@sandeen.net>,
linux-xfs@vger.kernel.org, CKI Project <cki-project@redhat.com>,
linux-fsdevel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
LTP Mailing List <ltp@lists.linux.it>
Subject: Re: [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later
Date: Mon, 9 Dec 2019 03:26:38 -0500 (EST) [thread overview]
Message-ID: <35957501.15762152.1575879998305.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <f874ea14-becc-9c4b-2f2f-351573e6a751@sandeen.net>
----- 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")
next prev parent reply other threads:[~2019-12-09 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c0af967-4916-4e8b-e77f-087515793d77@free.fr>
2019-12-07 0:09 ` [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later dftxbs3e
2019-12-08 20:30 ` Eric Sandeen
2019-12-09 8:26 ` Jan Stancek [this message]
[not found] <cki.6C6A189643.3T2ZUWEMOI@redhat.com>
[not found] ` <1738119916.14437244.1575151003345.JavaMail.zimbra@redhat.com>
2019-12-02 5:46 ` ❌ FAIL: Test report for kernel 5.3.13-3b5f971.cki (stable-queue) Michael Ellerman
2019-12-02 12:30 ` Jan Stancek
2019-12-03 12:50 ` [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later Jan Stancek
2019-12-03 13:07 ` Christoph Hellwig
2019-12-03 14:35 ` Jan Stancek
2019-12-03 16:08 ` Darrick J. Wong
2019-12-03 19:09 ` Christoph Hellwig
2019-12-04 14:43 ` Jan Stancek
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=35957501.15762152.1575879998305.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=cki-project@redhat.com \
--cc=darrick.wong@oracle.com \
--cc=dftxbs3e@free.fr \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ltp@lists.linux.it \
--cc=mm-qe@redhat.com \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).