From: Mark Fasheh <mfasheh@suse.de>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: Josef Bacik <jbacik@fb.com>,
lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
0day robot <fengguang.wu@intel.com>
Subject: Re: [lkp] [Btrfs] 02507c91c8: BUG: unable to handle kernel NULL pointer dereference at 00000018
Date: Mon, 9 Nov 2015 19:27:40 -0800 [thread overview]
Message-ID: <20151110032740.GL15575@wotan.suse.de> (raw)
In-Reply-To: <87bnb2d2qt.fsf@yhuang-dev.intel.com>
Hi,
On Tue, Nov 10, 2015 at 10:09:30AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://github.com/0day-ci/linux Mark-Fasheh/btrfs-update-qgroups-in-drop-snapshot-V2/20151106-064051
> commit 02507c91c8944d71dae65bddc45b764be65069f8 ("Btrfs: use btrfs_get_fs_root in resolve_indirect_ref")
I browsed the repo above and didn't see this commit:
d9ee522 Btrfs: fix qgroup sanity tests
Which I believe would help your situation. Please let me know if I am
mistaken.
Thanks,
--Mark
--
Mark Fasheh
prev parent reply other threads:[~2015-11-10 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 2:09 [lkp] [Btrfs] 02507c91c8: BUG: unable to handle kernel NULL pointer dereference at 00000018 kernel test robot
2015-11-10 3:27 ` Mark Fasheh [this message]
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=20151110032740.GL15575@wotan.suse.de \
--to=mfasheh@suse.de \
--cc=fengguang.wu@intel.com \
--cc=jbacik@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ying.huang@linux.intel.com \
/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