linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-mtd@lists.infradead.org, linux-mm <linux-mm@kvack.org>,
	Dave Jones <davej@redhat.com>
Subject: Re: mtd: kernel BUG at arch/x86/mm/pat.c:279!
Date: Sun, 09 Sep 2012 20:04:32 +0100	[thread overview]
Message-ID: <1347217472.2068.35.camel@shinybook.infradead.org> (raw)
In-Reply-To: <504CCA31.2000003@zytor.com>

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

On Sun, 2012-09-09 at 09:56 -0700, H. Peter Anvin wrote:
> 
> > So it should either be start=0xfffffffffffff000 end=0xffffffffffffffff
> > or it should be start=0xfffffffffffff000 len=0x1000.
> 
> I would strongly object to the former; that kind of inclusive ranges 
> breed a whole class of bugs by themselves.

Another alternative that avoids overflow issues is to use a PFN rather
than a byte address.

-- 
dwmw2

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]

  reply	other threads:[~2012-09-09 19:04 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29  8:48 mtd: kernel BUG at arch/x86/mm/pat.c:279! Sasha Levin
2012-07-30 11:00 ` Sasha Levin
2012-09-07 16:55 ` Sasha Levin
2012-09-07 18:14   ` Linus Torvalds
2012-09-07 22:42     ` Suresh Siddha
2012-09-07 23:09       ` Linus Torvalds
2012-09-07 23:54         ` Suresh Siddha
2012-09-08 19:57           ` Linus Torvalds
2012-09-09 14:56             ` Suresh Siddha
2012-09-09 15:31               ` Linus Torvalds
2012-09-09 17:01                 ` H. Peter Anvin
2012-09-12 10:50               ` Sasha Levin
2012-09-12 10:56                 ` Sasha Levin
2012-09-28  9:00                   ` Sasha Levin
2012-09-28 16:44                     ` Linus Torvalds
2012-09-28 18:05                       ` Artem Bityutskiy
2012-09-28 19:13                         ` Linus Torvalds
2012-09-28 19:44                           ` Sasha Levin
2012-09-28 19:04                       ` David Woodhouse
2012-09-28 19:15                         ` richard -rw- weinberger
2012-09-28 19:18                           ` richard -rw- weinberger
2012-09-29 16:11                         ` David Woodhouse
2012-09-29 16:34                           ` David Woodhouse
2012-09-09 16:56             ` H. Peter Anvin
2012-09-09 19:04               ` David Woodhouse [this message]
2012-09-09 20:33                 ` H. Peter Anvin
2012-09-10  5:17               ` Sasha Levin
2012-09-08  8:10         ` Sasha Levin

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=1347217472.2068.35.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=hpa@zytor.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=suresh.b.siddha@intel.com \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).