From: Roland Dreier <rdreier@cisco.com>
To: Keir Fraser <keir@xensource.com>
Cc: Lukas Hejtmanek <xhejtman@ics.muni.cz>, xen-devel@lists.xensource.com
Subject: Re: Question regarding SLAB corruption
Date: Mon, 09 Jul 2007 14:26:45 -0700 [thread overview]
Message-ID: <adad4z1xo8a.fsf@cisco.com> (raw)
In-Reply-To: <C2B83D37.A8DF%keir@xensource.com> (Keir Fraser's message of "Mon, 09 Jul 2007 19:29:59 +0100")
> Oh! I take it then that the infiniband driver will call sync_single() on
> subsections of a mapped region? I haven't seen that behaviour before and it
> will kill lib/swiotlb.c (the generic Linux swiotlb implementation) just as
> surely as it does the Xen-specific swiotlb!
> We could make the swiotlb robust to this treatment, I guess. It will involve
> initialising all covered io_tlb_orig_addr[] slots rather than just the
> first.
Does this mean that lib/swiotlb.c's swiotlb_sync_single_range_for_cpu()
and swiotlb_sync_single_range_for_device() are broken? Given that (as
you say) io_tlb_orig_addr[] only gets one slot filled in at the end of
map_single(), I don't see any way it could work if more than one page
is mapped.
- R.
next prev parent reply other threads:[~2007-07-09 21:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 0:54 Question regarding SLAB corruption Lukas Hejtmanek
2007-07-08 9:59 ` Keir Fraser
2007-07-08 10:05 ` Lukas Hejtmanek
2007-07-08 10:11 ` Keir Fraser
2007-07-09 7:38 ` Lukas Hejtmanek
2007-07-09 8:02 ` Tian, Kevin
2007-07-09 8:31 ` Keir Fraser
2007-07-09 12:07 ` Lukas Hejtmanek
2007-07-09 12:47 ` Keir Fraser
2007-07-09 13:24 ` Lukas Hejtmanek
2007-07-09 13:42 ` Keir Fraser
2007-07-09 15:39 ` Lukas Hejtmanek
2007-07-09 16:13 ` Keir Fraser
2007-07-09 17:11 ` Lukas Hejtmanek
2007-07-09 17:21 ` Keir Fraser
2007-07-09 17:42 ` Lukas Hejtmanek
2007-07-09 18:29 ` Keir Fraser
2007-07-09 18:37 ` Lukas Hejtmanek
2007-07-09 18:46 ` Keir Fraser
2007-07-09 19:22 ` Keir Fraser
2007-07-09 19:43 ` Lukas Hejtmanek
2007-07-09 21:18 ` Keir Fraser
2007-07-09 21:26 ` Lukas Hejtmanek
2007-07-09 21:50 ` Lukas Hejtmanek
2007-07-09 19:25 ` Roland Dreier
2007-07-09 19:39 ` Keir Fraser
2007-07-09 20:56 ` Lukas Hejtmanek
2007-07-09 21:07 ` Roland Dreier
2007-07-09 21:14 ` Lukas Hejtmanek
2007-07-09 21:18 ` Roland Dreier
2007-07-09 21:42 ` Lukas Hejtmanek
2007-07-09 21:53 ` Roland Dreier
2007-07-09 22:13 ` Lukas Hejtmanek
2007-07-09 22:30 ` Keir Fraser
2007-07-09 22:30 ` Roland Dreier
2007-07-09 22:34 ` Keir Fraser
2007-07-10 18:47 ` Question: Dynamic code in x86_64 Xen Santos, Jose Renato G
2007-07-10 22:01 ` Keir Fraser
2007-07-10 22:06 ` Santos, Jose Renato G
2007-07-09 21:26 ` Roland Dreier [this message]
2007-07-09 21:33 ` Question regarding SLAB corruption Keir Fraser
2007-07-11 9:37 ` Question regarding vm creat&boot tgh
2007-07-09 19:21 ` Question regarding SLAB corruption Roland Dreier
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=adad4z1xo8a.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=keir@xensource.com \
--cc=xen-devel@lists.xensource.com \
--cc=xhejtman@ics.muni.cz \
/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.