From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [bug] userspace hitting sporadic SIGBUS on xfs (Power9, ppc64le), v4.19 and later
Date: Wed, 4 Dec 2019 09:43:04 -0500 (EST) [thread overview]
Message-ID: <385099805.15030947.1575470584839.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191203190925.GA5150@infradead.org>
----- Original Message -----
> Please try the patch below:
I ran reproducer for 18 hours on 2 systems were it previously reproduced,
there were no crashes / SIGBUS.
next prev parent reply other threads:[~2019-12-04 14:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-30 5:26 [LTP] ❌ FAIL: Test report for kernel 5.3.13-3b5f971.cki (stable-queue) CKI Project
2019-11-30 21:56 ` Jan Stancek
2019-12-02 5:46 ` Michael Ellerman
2019-12-02 12:30 ` Jan Stancek
2019-12-03 12:50 ` [LTP] [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 [this message]
[not found] <9c0af967-4916-4e8b-e77f-087515793d77@free.fr>
2019-12-07 0:09 ` dftxbs3e
2019-12-08 20:30 ` Eric Sandeen
2019-12-09 8:26 ` 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=385099805.15030947.1575470584839.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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