From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alan Mikhak <alan.mikhak@sifive.com>
Cc: linux-kernel@vger.kernel.org, martin.petersen@oracle.com,
alexios.zavras@intel.com, ming.lei@redhat.com,
gregkh@linuxfoundation.org, tglx@linutronix.de,
christophe.leroy@c-s.fr, Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Subject: Re: [PATCH] scatterlist: Validate page before calling PageSlab()
Date: Tue, 1 Oct 2019 14:12:20 -0300 [thread overview]
Message-ID: <20191001171220.GF22532@ziepe.ca> (raw)
In-Reply-To: <CABEDWGzsJR+YpX7eDrt_EerT0VEHjpBXSpc6Nzbbmvqc2OiR8Q@mail.gmail.com>
On Tue, Oct 01, 2019 at 10:09:48AM -0700, Alan Mikhak wrote:
> On Tue, Oct 1, 2019 at 5:16 AM Jason Gunthorpe <jgg@ziepe.ca> wrote:
> >
> > On Mon, Sep 30, 2019 at 04:22:35PM -0700, Alan Mikhak wrote:
> > > From: Alan Mikhak <alan.mikhak@sifive.com>
> > >
> > > Modify sg_miter_stop() to validate the page pointer
> > > before calling PageSlab(). This check prevents a crash
> > > that will occur if PageSlab() gets called with a page
> > > pointer that is not backed by page struct.
> > >
> > > A virtual address obtained from ioremap() for a physical
> > > address in PCI address space can be assigned to a
> > > scatterlist segment using the public scatterlist API
> > > as in the following example:
> > >
> > > my_sg_set_page(struct scatterlist *sg,
> > > const void __iomem *ioaddr,
> > > size_t iosize)
> > > {
> > > sg_set_page(sg,
> > > virt_to_page(ioaddr),
> > > (unsigned int)iosize,
> > > offset_in_page(ioaddr));
> > > sg_init_marker(sg, 1);
> > > }
> > >
> > > If the virtual address obtained from ioremap() is not
> > > backed by a page struct, virt_to_page() returns an
> > > invalid page pointer. However, sg_copy_buffer() can
> > > correctly recover the original virtual address. Such
> > > addresses can successfully be assigned to scatterlist
> > > segments to transfer data across the PCI bus with
> > > sg_copy_buffer() if it were not for the crash in
> > > PageSlab() when called by sg_miter_stop().
> >
> > I thought we already agreed in general that putting things that don't
> > have struct page into the scatter list was not allowed?
> >
> > Jason
>
> Thanks Jason for your comment.
>
> Cost of adding page structs to a large PCI I/O address range can be
> quite substantial. Allowing PCI I/O pages without page structs may be
> desirable. Perhaps it is worth considering this cost.
This is generally agreed, but nobody has figured out a solution.
> Scatterlist has no problem doing its memcpy() from pages without a
> page struct that were obtained from ioremap(). It is only at
Calling memcpy on pointers from ioremap is very much not allowed. Code
has to use the iomem safe memcpy.
Jason
next prev parent reply other threads:[~2019-10-01 17:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 23:22 Alan Mikhak
2019-10-01 12:16 ` Jason Gunthorpe
2019-10-01 17:09 ` Alan Mikhak
2019-10-01 17:12 ` Jason Gunthorpe [this message]
2019-10-01 17:26 ` Alan Mikhak
2019-10-01 17:43 ` Jason Gunthorpe
2019-10-01 17:46 ` Alan Mikhak
2019-10-07 6:12 ` Christoph Hellwig
2019-10-07 6:13 ` Christoph Hellwig
2019-10-07 16:44 ` Alan Mikhak
2019-10-07 21:13 ` Alan Mikhak
2019-10-15 9:55 ` Christoph Hellwig
2019-10-15 16:12 ` Logan Gunthorpe
2019-10-15 19:02 ` Alan Mikhak
2019-10-15 17:40 ` Alan Mikhak
2019-10-15 17:45 ` Logan Gunthorpe
2019-10-15 18:11 ` Alan Mikhak
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=20191001171220.GF22532@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=alan.mikhak@sifive.com \
--cc=alexios.zavras@intel.com \
--cc=christophe.leroy@c-s.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=ming.lei@redhat.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®