mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Sachin Kamat <sachin.kamat@linaro.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	chanho.min@lge.com, Kamil Debski <k.debski@samsung.com>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	Arun Kumar K <arun.kk@samsung.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: Regression introduced by commit "lib/bitmap.c: speed up bitmap_find_free_region"
Date: Fri, 31 May 2013 12:05:42 -0700	[thread overview]
Message-ID: <20130531120542.87e2056dc7c129e72b83f2af@linux-foundation.org> (raw)
In-Reply-To: <CAK9yfHyZH3DSg2ZLbPN2bjQppWZSMR+2hQE+OU76eqSJoWAWGA@mail.gmail.com>

On Fri, 31 May 2013 12:15:10 +0530 Sachin Kamat <sachin.kamat@linaro.org> wrote:

> Hi,
> 
> While testing MFC decoder on Exynos machines, I encountered some
> memory allocation errors due to failure of dma_alloc_coherent().
> File: drivers/media/platform/s5p-mfc/s5p_mfc_ctrl.c Line: 38.
> 
> Git bisect pointed me to the following commit as the first bad commit
> (linux-next tree of 20130531):
> 
> commit 3d5272d9b289cd0930b2ea9984406d757a72f4dd
> Author: Chanho Min <chanho.min@lge.com>
> Date:   Thu May 23 10:37:28 2013 +1000
>     lib/bitmap.c: speed up bitmap_find_free_region
> 
> Reverting this (and the commit 197e1cf7
> ("ib-bitmapc-speed-up-bitmap_find_free_region-fix") ) fixes this
> issue.
> 
> Looks like some regression has been introduced by the above patch?

Thanks.  I dropped the patches for now, to minimise linux-next
breakage.  Hopefully we'll be able to identify and fix this at a later
time.


  reply	other threads:[~2013-05-31 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-31  6:45 Sachin Kamat
2013-05-31 19:05 ` Andrew Morton [this message]
2013-06-03  6:31   ` Stephen Rothwell

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=20130531120542.87e2056dc7c129e72b83f2af@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=arun.kk@samsung.com \
    --cc=chanho.min@lge.com \
    --cc=k.debski@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sachin.kamat@linaro.org \
    --cc=sfr@canb.auug.org.au \
    --cc=sylvester.nawrocki@gmail.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
all inboxes | Powered by JetHome®