From: David Vrabel <david.vrabel@citrix.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Linux Memory Management List <linux-mm@kvack.org>
Subject: Re: [mm/vmalloc] BUG: sleeping function called from invalid context at mm/vmalloc.c:74
Date: Wed, 19 Mar 2014 11:57:58 +0000 [thread overview]
Message-ID: <53298646.4080404@citrix.com> (raw)
In-Reply-To: <20140319115540.GA7277@localhost>
On 19/03/14 11:55, Fengguang Wu wrote:
> Hi David,
>
> FYI, we noticed the below BUG on
>
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> commit 032dda8b6c4021d4be63bcc483b47fd26c6f48a2 ("mm/vmalloc: avoid soft lockup warnings when vunmap()'ing large ranges")
Thanks, this patches have been are in the process of being dropped.
David
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-03-19 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 11:55 [mm/vmalloc] BUG: sleeping function called from invalid context at mm/vmalloc.c:74 Fengguang Wu
2014-03-19 11:57 ` David Vrabel [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=53298646.4080404@citrix.com \
--to=david.vrabel@citrix.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.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).