From: Po-Hsu Lin <po-hsu.lin@canonical.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: reproducable oops in btrfs/130 with latests mainline
Date: Tue, 17 Oct 2017 19:11:51 +0800 [thread overview]
Message-ID: <20171017111151.4316-1-po-hsu.lin@canonical.com> (raw)
In-Reply-To: <190cc125-d1c1-6005-c23b-cc54c825f242@fb.com>
Hello Chris,
I can reproduce this on my side too, with Ubuntu 16.04 + 4.4.0-97 kernel.
PREEMPT config:
$ cat config-4.4.0-97-generic | grep PREEMPT
CONFIG_PREEMPT_NOTIFIERS=y
# CONFIG_PREEMPT_NONE is not set
CONFIG_PREEMPT_VOLUNTARY=y
# CONFIG_PREEMPT is not set
Bug reports on launchpad:
https://bugs.launchpad.net/bugs/1718925
https://bugs.launchpad.net/bugs/1717443
next prev parent reply other threads:[~2017-10-17 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 12:35 reproducable oops in btrfs/130 with latests mainline Christoph Hellwig
2016-11-25 8:07 ` Christoph Hellwig
2016-11-26 17:23 ` Chris Mason
[not found] ` <190cc125-d1c1-6005-c23b-cc54c825f242@fb.com>
2017-10-17 11:11 ` Po-Hsu Lin [this message]
2017-10-17 12:46 ` Qu Wenruo
2017-10-17 13:03 ` Jeff Mahoney
2017-10-20 9:25 ` Po-Hsu Lin
2017-10-20 9:36 ` Qu Wenruo
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=20171017111151.4316-1-po-hsu.lin@canonical.com \
--to=po-hsu.lin@canonical.com \
--cc=linux-btrfs@vger.kernel.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 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).