From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 13520] WARNING: at lib/dma-debug.c:576 check_for_illegal_area+0xd3/0xfd()
Date: Wed, 17 Jun 2009 13:46:15 GMT	[thread overview]
Message-ID: <200906171346.n5HDkFrW004995@demeter.kernel.org> (raw)
In-Reply-To: <bug-13520-11633@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=13520
--- Comment #4 from Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>  2009-06-17 13:46:14 ---
On Tuesday 16 June 2009 12:28:01 bugzilla-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=13520
> 
> 
> 
> 
> 
> --- Comment #3 from Joerg Roedel <joro@8bytes.org>  2009-06-16 10:27:59 ---
> Ok, this was a dma-debug bug. The two warnings above are for memory areas which
> exactly ends at the beginning of the kernel text segment. I queued a fix in my
> tree and send it out when -rc1 is released. I also marked the patch for stable
> backporting.
Could you please post a link to the fix and then close the bug?  Thanks.
-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next prev parent reply	other threads:[~2009-06-17 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 13:43 [Bug 13520] New: WARNING: at lib/dma-debug.c:576 check_for_illegal_area+0xd3/0xfd() bugzilla-daemon
2009-06-15  8:41 ` [Bug 13520] " bugzilla-daemon
2009-06-15 17:39 ` bugzilla-daemon
2009-06-16 10:28 ` bugzilla-daemon
2009-06-17 13:51   ` Bartlomiej Zolnierkiewicz
2009-06-17 13:46 ` bugzilla-daemon [this message]
     [not found] <bug-13520-11633@https.bugzilla.kernel.org/>
2012-06-08 11:55 ` bugzilla-daemon
2012-06-08 11:55 ` bugzilla-daemon
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=200906171346.n5HDkFrW004995@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ide@vger.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;
as well as URLs for NNTP newsgroup(s).