All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kent Overstreet <kent.overstreet@gmail.com>
To: Huang Ying <ying.huang@intel.com>
Cc: Ming Lin <mlin@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	LKP ML <lkp@01.org>
Subject: Re: [lkp] [block] 86ecb9456ac:
Date: Tue, 14 Jul 2015 07:08:57 -0700	[thread overview]
Message-ID: <20150714140857.GA19627@kmo-pixel> (raw)
In-Reply-To: <1436880417.1264.16.camel@intel.com>

On Tue, Jul 14, 2015 at 09:26:57PM +0800, Huang Ying wrote:
> FYI, we noticed the below changes on
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/mlin/linux.git block-generic-req
> commit 86ecb9456ac74ba3996d05ca1b09a7756a31bfd7 ("block: make generic_make_request handle arbitrarily sized bios")
> 
> We found the following new message in kernel log, do you increase vmalloc usage in your patch?

not that I know of, use dump_stack() to get a backtrace when it happens

  reply	other threads:[~2015-07-14 14:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-14 13:26 [block] 86ecb9456ac: Huang Ying
2015-07-14 13:26 ` [lkp] " Huang Ying
2015-07-14 14:08 ` Kent Overstreet [this message]
2015-07-14 17:31 ` Ming Lin
2015-07-14 17:31   ` [lkp] " Ming Lin

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=20150714140857.GA19627@kmo-pixel \
    --to=kent.overstreet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=mlin@kernel.org \
    --cc=ying.huang@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 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.