From: Christoph Hellwig <hch@lst.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Christoph Hellwig" <hch@lst.de>, "Jens Axboe" <axboe@kernel.dk>,
"Dan Williams" <dan.j.williams@intel.com>,
"Vineet Gupta" <vgupta@synopsys.com>,
"Håvard Skinnemoen" <hskinnemoen@gmail.com>,
"Hans-Christian Egtvedt" <egtvedt@samfundet.no>,
"Miao Steven" <realmz6@gmail.com>,
"David Howells" <dhowells@redhat.com>,
"Michal Simek" <monstr@monstr.eu>,
"the arch/x86 maintainers" <x86@kernel.org>,
"David Woodhouse" <dwmw2@infradead.org>,
"Alex Williamson" <alex.williamson@redhat.com>,
grundler@parisc-linux.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
linux-alpha@vger.kernel.org,
"linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>,
linux-metag@vger.kernel.org,
linux-mips <linux-mips@linux-mips.org>,
"Parisc List" <linux-parisc@vger.kernel.org>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
linux-s390 <linux-s390@vger.kernel.org>,
sparclinux@vger.kernel.org, linux-xtensa@linux-xtensa.org,
"linux-nvdimm@lists.01.org" <linux-nvdimm@ml01.01.org>,
"Linux Media Mailing List" <linux-media@vger.kernel.org>
Subject: Re: [PATCH 31/31] dma-mapping-common: skip kmemleak checks for page-less SG entries
Date: Thu, 13 Aug 2015 16:33:25 +0200 [thread overview]
Message-ID: <20150813143325.GB17183@lst.de> (raw)
In-Reply-To: <CA+55aFxfZM81HNfo2ysfhGwrhx6GX-+F--+jLFmMVv+Z0id2rw@mail.gmail.com>
On Wed, Aug 12, 2015 at 09:05:15AM -0700, Linus Torvalds wrote:
> [ Again, I'm responding to one random patch - this pattern was in
> other patches too. ]
>
> A question: do we actually expect to mix page-less and pageful SG
> entries in the same SG list?
>
> How does that happen?
Both for DAX and the video buffer case people could do direct I/O
spanning the boundary between such a VMA and a normal one unless
we add special code to prevent that. Right now I don't think it's
all that useful, but then again it doesn't seem harmful either
and adding those checks might add up.
prev parent reply other threads:[~2015-08-13 14:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1439363150-8661-1-git-send-email-hch@lst.de>
[not found] ` <1439363150-8661-30-git-send-email-hch@lst.de>
2015-08-12 16:01 ` [PATCH 29/31] parisc: handle page-less SG entries Linus Torvalds
2015-08-13 14:31 ` Christoph Hellwig
2015-08-14 3:30 ` Dan Williams
2015-08-14 3:59 ` James Bottomley
[not found] ` <1439363150-8661-32-git-send-email-hch@lst.de>
2015-08-12 16:05 ` [PATCH 31/31] dma-mapping-common: skip kmemleak checks for " Linus Torvalds
2015-08-13 14:33 ` Christoph Hellwig [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=20150813143325.GB17183@lst.de \
--to=hch@lst.de \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=egtvedt@samfundet.no \
--cc=grundler@parisc-linux.org \
--cc=hskinnemoen@gmail.com \
--cc=linux-alpha@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-metag@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=linux-parisc@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-xtensa@linux-xtensa.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=monstr@monstr.eu \
--cc=realmz6@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=vgupta@synopsys.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