From: David Sterba <dsterba@suse.cz>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: lkp@01.org, Stephen Rothwell <sfr@canb.auug.org.au>,
Liu Bo <bo.li.liu@oracle.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [btrfs] cc8385b59e: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h
Date: Thu, 11 May 2017 10:43:41 +0200 [thread overview]
Message-ID: <20170511084341.GD27439@suse.cz> (raw)
In-Reply-To: <20170508205048.GA101014@inn.lkp.intel.com>
On Tue, May 09, 2017 at 04:50:48AM +0800, kernel test robot wrote:
>
> FYI, we noticed the following commit:
>
> commit: cc8385b59e17d489814d54d6a846aba7051fdea5 ("btrfs: preallocate radix tree node for readahead")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
For the record, that's a known one and has been fixed, there were some
for-next branches without the fix.
prev parent reply other threads:[~2017-05-11 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-08 20:50 [btrfs] cc8385b59e: BUG:sleeping_function_called_from_invalid_context_at_mm/slab.h kernel test robot
2017-05-11 8:43 ` David Sterba [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=20170511084341.GD27439@suse.cz \
--to=dsterba@suse.cz \
--cc=bo.li.liu@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=sfr@canb.auug.org.au \
--cc=xiaolong.ye@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