From: Hugh Dickins <hugh@veritas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: gurudas pai <gurudas.pai@oracle.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [BUG] kernel BUG at arch/i386/mm/highmem.c:15! on 2.6.23-rc8/rc9
Date: Thu, 4 Oct 2007 17:53:46 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710041741250.24671@blonde.wat.veritas.com> (raw)
In-Reply-To: <alpine.LFD.0.999.0710040920400.23684@woody.linux-foundation.org>
On Thu, 4 Oct 2007, Linus Torvalds wrote:
>
> Ouch.
Very much so.
>
> The patch looks obviously correct, to the point that I don't understand
> how this bug happened in the first place. It seems to have been
> introduced by Nick in d0217ac04ca6591841e5665f518e38064f4e65bd ("mm: fault
> feedback #1") if I read it right.
Yes, I think you are reading that right.
>
> So "do_nonlinear_fault()" would effectively end up unmapping the PTE
> twice, right? And if I understand the problem right, this wasn't noticed
> immediately, because it probably only matters on:
>
> - CONFIG_HIGHPTE
> *and*
> - a filesystem that allows VM_NONLINEAR, which became very rare with
> dirty accounting.
>
> Correct?
Correct. And though I eventually realized the nonlinear dirty accounting
issue (which I did highlight in the patch comment), I'd forgotten all
about needing CONFIG_HIGHPTE in addition to CONFIG_HIGHMEM - yes, that
increased the probability of overlooking it too.
No excuses that we did miss it in all these months those patches have
been around; but it's an object lesson in the trouble rare paths give.
Hugh
next prev parent reply other threads:[~2007-10-04 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 6:37 gurudas pai
2007-10-03 14:53 ` Nick Piggin
2007-10-03 15:39 ` Nick Piggin
2007-10-04 10:02 ` gurudas pai
2007-10-04 15:56 ` Hugh Dickins
2007-10-04 16:38 ` Linus Torvalds
2007-10-04 16:53 ` Hugh Dickins [this message]
2007-10-05 2:49 ` gurudas pai
2007-10-05 3:54 ` gurudas pai
2007-10-05 10:26 ` Hugh Dickins
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=Pine.LNX.4.64.0710041741250.24671@blonde.wat.veritas.com \
--to=hugh@veritas.com \
--cc=akpm@linux-foundation.org \
--cc=gurudas.pai@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--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
all inboxes | Powered by JetHome®