Re: [PATCH 31/31] dma-mapping-common: skip kmemleak checks for page-less SG entries
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>
- Subject: Re: [PATCH 31/31] dma-mapping-common: skip kmemleak checks for page-less SG entries
- From: Christoph Hellwig <hch@xxxxxx>
- Date: Thu, 13 Aug 2015 16:33:25 +0200
- Cc: Christoph Hellwig <hch@xxxxxx>, Jens Axboe <axboe@xxxxxxxxx>, Dan Williams <dan.j.williams@xxxxxxxxx>, Vineet Gupta <vgupta@xxxxxxxxxxxx>, Håvard Skinnemoen <hskinnemoen@xxxxxxxxx>, Hans-Christian Egtvedt <egtvedt@xxxxxxxxxxxx>, Miao Steven <realmz6@xxxxxxxxx>, David Howells <dhowells@xxxxxxxxxx>, Michal Simek <monstr@xxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, David Woodhouse <dwmw2@xxxxxxxxxxxxx>, Alex Williamson <alex.williamson@xxxxxxxxxx>, grundler@xxxxxxxxxxxxxxxx, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, "linux-arch@xxxxxxxxxxxxxxx" <linux-arch@xxxxxxxxxxxxxxx>, linux-alpha@xxxxxxxxxxxxxxx, "linux-ia64@xxxxxxxxxxxxxxx" <linux-ia64@xxxxxxxxxxxxxxx>, linux-metag@xxxxxxxxxxxxxxx, linux-mips <linux-mips@xxxxxxxxxxxxxx>, Parisc List <linux-parisc@xxxxxxxxxxxxxxx>, ppc-dev <linuxppc-dev@xxxxxxxxxxxxxxxx>, linux-s390 <linux-s390@xxxxxxxxxxxxxxx>, sparclinux@xxxxxxxxxxxxxxx, linux-xtensa@xxxxxxxxxxxxxxxx, "linux-nvdimm@xxxxxxxxxxxx" <linux-nvdimm@xxxxxxxxxxx>, Linux Media Mailing List <linux-media@xxxxxxxxxxxxxxx>
- In-reply-to: <CA+55aFxfZM81HNfo2ysfhGwrhx6GX-+F--+jLFmMVv+Z0id2rw@mail.gmail.com>
- List-id: <linux-ia64.vger.kernel.org>
- References: <1439363150-8661-1-git-send-email-hch@lst.de> <1439363150-8661-32-git-send-email-hch@lst.de> <CA+55aFxfZM81HNfo2ysfhGwrhx6GX-+F--+jLFmMVv+Z0id2rw@mail.gmail.com>
- User-agent: Mutt/1.5.17 (2007-11-01)
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.
--
To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Kernel]
[Sparc Linux]
[DCCP]
[Linux ARM]
[Yosemite News]
[Linux SCSI]
[Linux x86_64]
[Linux for Ham Radio]