All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Jiri Kosina" <jikos@kernel.org>, "Jürgen Groß" <jgross@suse.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Michal Hocko" <mhocko@suse.com>,
	"Naoya Horiguchi" <n-horiguchi@ah.jp.nec.com>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Will Deacon" <will.deacon@arm.com>
Subject: Re: Access to non-RAM pages
Date: Mon, 03 Sep 2018 11:46:14 +1000	[thread overview]
Message-ID: <a0aaa8162a0152e4afdf81ed28da230708f199b5.camel@kernel.crashing.org> (raw)
In-Reply-To: <CA+55aFz_Kbu2PDjqvmgqCFcFSsoRPD=a8vAtPY=--t61X454Jg@mail.gmail.com>

On Sun, 2018-09-02 at 18:38 -0700, Linus Torvalds wrote:
> On Sun, Sep 2, 2018 at 6:32 PM Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > 
> > Also, if we cross page boundaries with those guys then we have a bigger
> > problem no ? we could fall off a vmalloc page into the nether or into
> > an ioremap mapping no ?
> 
> It's not used for vmalloc stuff. It's just regular kmalloc().
> 
> So it can cross pages, and it can fall off the end of memory, but it
> can't do random stuff.

Actually what about DEBUG_PAGEALLOC ? Can't we fall off a page and
fault that way too ?

Cheers,
Ben.


      parent reply	other threads:[~2018-09-03  1:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-29 12:10 Access to non-RAM pages Juergen Gross
2018-08-31 21:18 ` Jiri Kosina
2018-09-01 10:47   ` Juergen Gross
2018-09-01 17:13     ` Al Viro
2018-09-01 21:48       ` Jiri Kosina
2018-09-01 17:27   ` Linus Torvalds
2018-09-01 18:06     ` Linus Torvalds
2018-09-03  0:48       ` Benjamin Herrenschmidt
2018-09-03  0:55         ` Benjamin Herrenschmidt
2018-09-03  1:38           ` Linus Torvalds
2018-09-03  1:42             ` Linus Torvalds
2018-09-03  2:00               ` Benjamin Herrenschmidt
2018-09-03  2:10                 ` Linus Torvalds
2018-09-03  2:25                   ` Benjamin Herrenschmidt
2018-09-03  2:47                     ` Linus Torvalds
2018-09-03  2:52                       ` Linus Torvalds
2018-09-03  3:44                         ` Benjamin Herrenschmidt
2018-09-03  5:08                   ` Juergen Gross
2018-09-03  6:05                   ` Jiri Kosina
2018-09-03 10:36                   ` Will Deacon
2018-09-03  1:44             ` Benjamin Herrenschmidt
2018-09-03  1:46             ` Benjamin Herrenschmidt [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=a0aaa8162a0152e4afdf81ed28da230708f199b5.camel@kernel.crashing.org \
    --to=benh@kernel.crashing.org \
    --cc=jgross@suse.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=mpe@ellerman.id.au \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=torvalds@linux-foundation.org \
    --cc=will.deacon@arm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.