mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: kyle@infradead.org
Cc: stable@kernel.org, arjan@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: [stable] [PATCH stable] resources: skip sanity check of busy resources
Date: Wed, 28 Jan 2009 16:43:06 -0800	[thread overview]
Message-ID: <20090129004306.GF23732@kroah.com> (raw)
In-Reply-To: <20090127161007.GG5034@bombadil.infradead.org>

On Tue, Jan 27, 2009 at 11:10:07AM -0500, Kyle McMartin wrote:
> From: Arjan van de Ven <arjan@linux.intel.com>
> 
> Impact: reduce false positives in iomem_map_sanity_check()
> 
> Some drivers (vesafb) only map/reserve a portion of a resource.
> If then some other driver comes in and maps the whole resource,
> the current code WARN_ON's. This is not the intent of the checks
> in iomem_map_sanity_check(); rather these checks want to
> warn when crossing *hardware* resources only.
> 
> This patch skips BUSY resources as suggested by Linus.
> 
> Note: having two drivers talk to the same hardware at the same
> time is obviously not optimal behavior, but that's a separate story.
> 
> Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> Signed-off-by: Kyle McMartin <kyle@redhat.com>
> ---
> 
> Bug fix for 2.6.28-stable only (relevant iomem_map_sanity_check hadn't
> been added to 2.6.27.) This resolves a fairly nasty boot time WARN
> in acpi ec seen on a number of systems. (RH #480700)

Thanks for the patch.  Next time, if you could let us know what the git
commit id is for the patch in Linus's tree, it would save me having to
dig to find it :)

thanks,

greg k-h

  reply	other threads:[~2009-01-29  1:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-27 16:10 Kyle McMartin
2009-01-29  0:43 ` Greg KH [this message]
2009-01-29  1:05   ` [stable] " Kyle McMartin

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=20090129004306.GF23732@kroah.com \
    --to=greg@kroah.com \
    --cc=arjan@linux.intel.com \
    --cc=kyle@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@kernel.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

all inboxes | Powered by JetHome®