From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 203517] WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage.
Date: Tue, 07 May 2019 13:28:04 +0000 [thread overview]
Message-ID: <bug-203517-206035-C8MvJui3JB@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203517-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203517
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fs_btrfs@kernel-bugs.osdl.o
| |rg
Component|PPC-64 |btrfs
Hardware|All |PPC-64
Product|Platform Specific/Hardware |File System
--- Comment #3 from Erhard F. (erhard_f@mailbox.org) ---
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
d3c6ab752c4145cba9af85021f02bc4655534f93
3f93aef535c8ea03e40cd8acf0753b3e6ed33e96
commit 3f93aef535c8ea03e40cd8acf0753b3e6ed33e96
Author: Dennis Zhou <dennis@kernel.org>
Date: Mon Feb 4 15:20:08 2019 -0500
btrfs: add zstd compression level support
commit d3c6ab752c4145cba9af85021f02bc4655534f93
Author: Dennis Zhou <dennis@kernel.org>
Date: Mon Feb 4 15:20:07 2019 -0500
btrfs: make zstd memory requirements monotonic
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-05-07 13:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-05 0:21 [Bug 203517] New: WARNING: inconsistent lock state. inconsistent {SOFTIRQ-ON-W} -> {IN-SOFTIRQ-W} usage bugzilla-daemon
2019-05-05 0:22 ` [Bug 203517] " bugzilla-daemon
2019-05-06 19:50 ` bugzilla-daemon
2019-05-07 13:28 ` bugzilla-daemon [this message]
2019-05-07 13:29 ` bugzilla-daemon
2019-05-07 13:38 ` bugzilla-daemon
2019-05-17 15:48 ` bugzilla-daemon
2019-05-17 15:49 ` bugzilla-daemon
2019-05-21 8:58 ` bugzilla-daemon
2019-05-31 21:27 ` bugzilla-daemon
2019-06-02 10:00 ` bugzilla-daemon
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=bug-203517-206035-C8MvJui3JB@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.