From: Christoph Hellwig <hch@infradead•org>
To: Michael Schmitz <schmitzmic@gmail•com>
Cc: Marek Szyprowski <m.szyprowski@samsung•com>,
Linux-Arch <linux-arch@vger•kernel.org>,
scsi <linux-scsi@vger•kernel.org>,
Christoph Hellwig <hch@infradead•org>,
Geert Uytterhoeven <geert@linux-m68k•org>,
Jakub Kicinski <kuba@kernel•org>, Arnd Bergmann <arnd@arndb•de>,
Miquel van Smoorenburg <mikevs@xs4all•net>,
Denis Efremov <efremov@linux•com>,
linux-m68k <linux-m68k@lists•linux-m68k.org>,
John Paul Adrian Glaubitz <glaubitz@physik•fu-berlin.de>,
Khalid Aziz <khalid@gonehiking•org>,
Arnd Bergmann <arnd@kernel•org>,
Parisc List <linux-parisc@vger•kernel.org>,
Robin Murphy <robin.murphy@arm•com>,
Matt Wang <wwentao@vmware•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Mark Salyzyn <salyzyn@android•com>,
Linux IOMMU <iommu@lists•linux-foundation.org>,
alpha <linux-alpha@vger•kernel.org>,
linuxppc-dev <linuxppc-dev@lists•ozlabs.org>,
"Maciej W . Rozycki" <macro@orcam•me.uk>
Subject: Re: [PATCH v2 3/3] arch/*/: remove CONFIG_VIRT_TO_BUS
Date: Tue, 28 Jun 2022 23:21:50 -0700 [thread overview]
Message-ID: <YrvvfpW4MmQiM47H@infradead.org> (raw)
In-Reply-To: <9f812d3d-0fcd-46e6-6d7e-6d4bf66f24ab@gmail.com>
On Wed, Jun 29, 2022 at 11:09:00AM +1200, Michael Schmitz wrote:
> And all SCSI buffers are allocated using kmalloc? No way at all for user
> space to pass unaligned data?
Most that you will see actually comes from the page allocator. But
the block layer has a dma_alignment limit, and when userspace sends
I/O that is not properly aligned it will be bounce buffered before
it it sent to the driver.
next prev parent reply other threads:[~2022-06-29 6:23 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 12:57 [PATCH v2 0/3] phase out CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-17 12:57 ` [PATCH v2 1/3] scsi: dpt_i2o: drop stale VIRT_TO_BUS dependency Arnd Bergmann
2022-06-21 8:43 ` Hannes Reinecke
2022-06-17 12:57 ` [PATCH v2 2/3] scsi: BusLogic remove bus_to_virt Arnd Bergmann
2022-06-17 14:02 ` Robin Murphy
2022-06-21 8:45 ` Hannes Reinecke
2022-06-21 21:56 ` Khalid Aziz
2022-06-23 14:47 ` Arnd Bergmann
2022-06-24 15:38 ` Khalid Aziz
2022-06-24 15:43 ` Arnd Bergmann
2022-06-17 12:57 ` [PATCH v2 3/3] arch/*/: remove CONFIG_VIRT_TO_BUS Arnd Bergmann
2022-06-18 1:06 ` Michael Schmitz
2022-06-24 9:10 ` Arnd Bergmann
2022-06-26 5:21 ` Michael Schmitz
2022-06-26 8:36 ` Arnd Bergmann
2022-06-27 8:09 ` Michael Schmitz
2022-06-27 8:26 ` Geert Uytterhoeven
2022-06-27 21:12 ` Michael Schmitz
2022-06-28 3:25 ` Michael Schmitz
2022-06-28 7:03 ` Geert Uytterhoeven
2022-06-28 21:03 ` Michael Schmitz
2022-06-28 21:50 ` Arnd Bergmann
2022-06-28 23:09 ` Michael Schmitz
2022-06-28 23:50 ` Bart Van Assche
2022-06-29 0:01 ` Michael Schmitz
2022-06-29 0:14 ` Michael Schmitz
2022-06-29 6:21 ` Christoph Hellwig [this message]
2022-06-30 19:21 ` Michael Schmitz
2022-06-30 8:04 ` David Laight
2022-06-30 9:40 ` Christophe Leroy
2022-06-30 10:32 ` David Laight
2022-06-28 7:08 ` Arnd Bergmann
2022-06-28 21:38 ` Michael Schmitz
2022-06-28 21:55 ` Arnd Bergmann
2022-06-28 23:43 ` Michael Schmitz
2022-06-29 6:25 ` Christoph Hellwig
2022-06-30 19:26 ` Michael Schmitz
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=YrvvfpW4MmQiM47H@infradead.org \
--to=hch@infradead$(echo .)org \
--cc=arnd@arndb$(echo .)de \
--cc=arnd@kernel$(echo .)org \
--cc=efremov@linux$(echo .)com \
--cc=geert@linux-m68k$(echo .)org \
--cc=glaubitz@physik$(echo .)fu-berlin.de \
--cc=iommu@lists$(echo .)linux-foundation.org \
--cc=khalid@gonehiking$(echo .)org \
--cc=kuba@kernel$(echo .)org \
--cc=linux-alpha@vger$(echo .)kernel.org \
--cc=linux-arch@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-m68k@lists$(echo .)linux-m68k.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=linux-scsi@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=m.szyprowski@samsung$(echo .)com \
--cc=macro@orcam$(echo .)me.uk \
--cc=mikevs@xs4all$(echo .)net \
--cc=robin.murphy@arm$(echo .)com \
--cc=salyzyn@android$(echo .)com \
--cc=schmitzmic@gmail$(echo .)com \
--cc=wwentao@vmware$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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