From: Andrew Morton <akpm@linux-foundation.org>
To: Casey Dahlin <cdahlin@redhat.com>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
beckyb@kernel.crashing.org
Subject: Re: [PATCH,resend] Fix strange panic message selection logic when swiotlb fills up
Date: Thu, 20 Aug 2009 16:25:10 -0700 [thread overview]
Message-ID: <20090820162510.063d603c.akpm@linux-foundation.org> (raw)
In-Reply-To: <4A8DA97C.9020406@redhat.com>
On Thu, 20 Aug 2009 15:52:28 -0400
Casey Dahlin <cdahlin@redhat.com> wrote:
> swiotlb_full in lib/swiotlb.c throws one of two panic messages based on whether
> the direction of transfer is from the device or to the device. The logic around
> this is somewhat weird in the case of bidirectional transfers. It appears to
> want to throw both in succession, but since its a panic only the first makes it.
>
> This patch adds a third, separate error for DMA_BIDIRECTIONAL to make things a
> bit clearer.
>
> Signed-off-by: Casey Dahlin <cdahlin@redhat.com>
>
> ---
> lib/swiotlb.c | 15 +++++++++------
> 1 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/lib/swiotlb.c b/lib/swiotlb.c
> index bffe6d7..35e01b3 100644
> --- a/lib/swiotlb.c
> +++ b/lib/swiotlb.c
> @@ -625,12 +625,15 @@ swiotlb_full(struct device *dev, size_t size, int dir, int do_panic)
> printk(KERN_ERR "DMA: Out of SW-IOMMU space for %zu bytes at "
> "device %s\n", size, dev ? dev_name(dev) : "?");
>
> - if (size > io_tlb_overflow && do_panic) {
> - if (dir == DMA_FROM_DEVICE || dir == DMA_BIDIRECTIONAL)
> - panic("DMA: Memory would be corrupted\n");
> - if (dir == DMA_TO_DEVICE || dir == DMA_BIDIRECTIONAL)
> - panic("DMA: Random memory would be DMAed\n");
> - }
> + if (size <= io_tlb_overflow || !do_panic)
> + return;
> +
> + if (dir == DMA_BIDIRECTIONAL)
> + panic("DMA: Random memory could be corrupted or DMAed\n");
> + if (dir == DMA_FROM_DEVICE)
> + panic("DMA: Memory would be corrupted\n");
> + if (dir == DMA_TO_DEVICE)
> + panic("DMA: Random memory would be DMAed\n");
> }
>
Seems sane to me.
While we're there, how about we make the final message less ambiguous?
--- a/lib/swiotlb.c~lib-swiotlbc-fix-strange-panic-message-selection-logic-when-swiotlb-fills-up-fix
+++ a/lib/swiotlb.c
@@ -633,7 +633,7 @@ swiotlb_full(struct device *dev, size_t
if (dir == DMA_FROM_DEVICE)
panic("DMA: Memory would be corrupted\n");
if (dir == DMA_TO_DEVICE)
- panic("DMA: Random memory would be DMAed\n");
+ panic("DMA: Random memory would be DMAed from\n");
}
/*
_
prev parent reply other threads:[~2009-08-20 23:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 19:52 [PATCH,resend] Fix strange panic message selection logic when swiotlb fills up Casey Dahlin
2009-08-20 23:25 ` Andrew Morton [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=20090820162510.063d603c.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=beckyb@kernel.crashing.org \
--cc=cdahlin@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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