From: Paolo Bonzini <pbonzini@redhat.com>
To: Robin Murphy <robin.murphy@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: mark.rutland@arm.com, wanpengli@tencent.com, kvm@vger.kernel.org,
narmstrong@baylibre.com, catalin.marinas@arm.com,
will.deacon@arm.com, rkrcmar@redhat.com, hpa@zytor.com,
khilman@baylibre.com, joro@8bytes.org, x86@kernel.org,
mingo@redhat.com, linux-arm-kernel@lists.infradead.org,
syzbot <syzbot+46f1dd7dbbe2bfb98b10@syzkaller.appspotmail.com>,
devicetree@vger.kernel.org, syzkaller-bugs@googlegroups.com,
robh+dt@kernel.org, bp@alien8.de,
linux-amlogic@lists.infradead.org, tglx@linutronix.de,
Dmitry Vyukov <dvyukov@google.com>,
jmattson@google.com, USB list <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org, sean.j.christopherson@intel.com,
carlo@caione.org, Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: KASAN: slab-out-of-bounds Read in handle_vmptrld
Date: Fri, 13 Sep 2019 23:39:03 +0200 [thread overview]
Message-ID: <a85cee75-99f9-7de3-6e5c-86f9bb41bca5@redhat.com> (raw)
In-Reply-To: <462660f4-1537-cece-b55f-0ceba0269eb8@arm.com>
On 13/09/19 17:32, Robin Murphy wrote:
> Oh, that bit of usbdev_mmap() is already known to be pretty much totally
> bogus for various reasons - there have been a few threads about it, of
> which I think [1] is both the most recent and the most informative.
> There was another patch[2], but that might have stalled (and might need
> reworking with additional hcd_uses_dma() checks anyway).
Neither is enough, see my reply to Alan. Memory from kmalloc just
*cannot* be passed down to remap_pfn_range, dma_mmap_coherent or
anything like that. It's a simple alignment issue.
Paolo
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-09-13 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 20:38 KASAN: slab-out-of-bounds Read in handle_vmptrld syzbot
2019-09-12 12:25 ` Will Deacon
2019-09-12 13:54 ` Vitaly Kuznetsov
2019-09-12 16:49 ` Paolo Bonzini
2019-09-13 4:46 ` Greg Kroah-Hartman
2019-09-13 7:34 ` Paolo Bonzini
2019-09-13 13:02 ` Greg Kroah-Hartman
2019-09-13 15:01 ` Paolo Bonzini
2019-09-13 15:32 ` Robin Murphy
2019-09-13 21:39 ` Paolo Bonzini [this message]
2019-09-13 15:36 ` Alan Stern
2019-09-13 16:14 ` Paolo Bonzini
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=a85cee75-99f9-7de3-6e5c-86f9bb41bca5@redhat.com \
--to=pbonzini@redhat.com \
--cc=bp@alien8.de \
--cc=carlo@caione.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dvyukov@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=khilman@baylibre.com \
--cc=kvm@vger.kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=narmstrong@baylibre.com \
--cc=rkrcmar@redhat.com \
--cc=robh+dt@kernel.org \
--cc=robin.murphy@arm.com \
--cc=sean.j.christopherson@intel.com \
--cc=syzbot+46f1dd7dbbe2bfb98b10@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will.deacon@arm.com \
--cc=x86@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).